WLS 6.0 NT Service with Cocoon2

I am getting Dr. Watson window(segmentation violation) while trying to the run
the attached installNTService.cmd file.
Any pointers will be greatly appreciated.
Thanks,
Dinkar
[installNtService.cmd]

Similar Messages

RUn WLS 7 as Windows 2K service with JDK 1.4.1

Has anyone able to get WLS 7 to run as Windows 2K service with JDK 1.4.1?

NO -- the first product to support JDK 1.4 is WLS 8.1. Period.
Wayne
cdd wrote:
Has anyone able to get WLS 7 to run as Windows 2K service with JDK 1.4.1?

Are the WLS 9.1 Web Service Ant Tasks ready for prime time?

I am trying to create a Proof of Concept (POC) for Enterprise and B2B Services at Wendy's Int'l, Inc.
As part of this POC, I created a WSDL for an in-house service and then used the wsdlc and jwsc Ant Tasks to translate this WSDL to Java classes and ultimately (I hoped) a deployable services.
In this document, I describe the issues I encountered setting up what I consider to be a simple POC.
I'll try to attach my WSDL file and build.xml so you can follow along.
I'll also try to attach my CSS file so you can compare how the generated WSDL appears in the Browser to the way I want it to appear.
If attachments are not allowed on these forums, then I will wait and see if there is interest in those documents before I paste them under this topic.
Some preliminary information about my environment.
Environment:
 Windows XP Pro SP2
 WebLogic 9.1
 Java 1.5.0_04
Service Name:
 AppRelease
Note: If I modify my WSDL (perhaps to add a new Operation or to change the definition of an element) and run wsdlc again, the AppReleaseSOAPPortImpl.java file is overwritten For this reason, I implemented my service logic in a class called AppReleaseServiceImple.java.
Now, for the issues.
1. Bug:
In the WSDL generated by wsdlc, the wsdl:part child of the wsdl:message tag is erroneously prefixed with a colon.
This occurs whether or not I specify a prefix for the http://schemas.xmlsoap.org/wsdl/ namespace.
Work around: Extract the wsdl from the jar file, fix it and add it back into the jar.
2. Bug:
In the WSDL generated by wsdlc, the wsdl:input and wsdl:output children of the wsdl:operation child of wsdl:portType tag are erroneously prefixed with a colon. Like 1 above, this occurs whether or not I specify a prefix for the http://schemas.xmlsoap.org/wsdl/ namespace.
Work around: Extract the wsdl from the jar file, fix it and add it back into the jar.
The error message generated by Bugs 1 and 2 is not helpful in diagnosing the problem:
[jwsc] Error at line:46 col:7 ':' expected [?! -- [CDATA[ ]
3. Bug:
In the WSDL generated by wsdlc, the documentation elements have all of my html elements stripped out, as well as my xhtml and wsdl namespace references. This completely negates one of the best features of the documentation tag, being able to present the WSDL in a browser as a nicely formatted, human friendly document which is also the underlying WSDL that can be viewed when the person views the source document.
I label this as a bug because it greatly reduces the functionality of the resulting WSDL.
4. Annoyance:
The WSDL generated by wsdlc has all of my comments stripped out, except the comments in the xsd:schema section of the wsdl:types element. I would prefer that all my comments be left in the WSDL, but if comments must be stripped out then I think all of the comments should be stripped out.
5. Annoyance:
The WSDL generated by wsdlc has my CSS specification stripped.
Work around: I donâ€™t know if adding the CSS back will do any good because I have not yet created a deployable service (see the last issue below).
6. Annoyance:
The WSDL generated by wsdlc has different namespace prefixes than the ones I specified for my application's namespace and for the http://schemas.xmlsoap.org/wsdl/soap/ namespace.
Work around: Perform a find/replace on namespace prefixes "s0" and "s1" to return them to my prefered values.
Another thing I can do at this point is simply replace the generated WSDL in the jar file with my original WSDL. This would address issues 1 thru 6 above.
7. Annoyance:
The java source files created by wsdlc are put into a jar file. This makes it annoying when working within a traditional IDE like Eclipse because there is no way to reference the source files within the jar as working source.
Work around: Extract the source files from the jar and identify the resulting directory structure as part of the source structure of the project.
8. Bug:
The jwsc task complains if the same parameter name is used in multiple operations. I received the following Errors from jwsc:
[jwsc] C:\IDE\workspace\Acre-WL9.1\AppReleaseSOAPPort.java 0:0
[jwsc] [ERROR] - Parameter element "{http://acre.services.wendys.com/AppRelease/}garRequest" is not unique across document/literal bare WebService.
Since the operation names are unique, I see no reason to also require uniqueness in the parameter names used by those operations.
Work around: Use unique element names for the input parameters of the services operations.
9. Bug:
Once items 1, 2 and 8 above are taken care of, jwsc fails with the following error:
java.lang.AssertionError: java.lang.ClassNotFoundException: weblogic.j2ee.descriptor.ApplicationBeanImpl
This seems to be due to the weblogic.jar file not being in the System Classpath.
However, I should note that when I set verbose="on" and debug="on" in the jwsc ant task, there was a message from the task which stated "[jwsc] [search path for class files: [big freakinâ€™ jar list]". In the big freakinâ€™ jar list, I did find weblogic.jar and weblogic.jar has the required ApplicationBeanImpl. This indicates to me that the jwsc task does not fully honor either its classpathref attribute, nor an embedded classpath element.
Work around: Make sure the weblogic.jar is in the System Classpath.
10. Bug:
I fixed bug #9 by running a setDomainEnv script and then ran my ant task. This time I received the following output:
ant build-serviceBuildfile: build.xml
build-service:
[jwsc] 1 JWS files will be processed.
[jwsc] Processing JWS: C:\IDE\workspace\Acre-WL9.1\src\com\wendys\services\acre\AppReleaseServiceImpl.java
[jwsc] JWS: C:\IDE\workspace\Acre-WL9.1\src\com\wendys\services\acre\AppReleaseServiceImpl.java Validated.
[AntUtil.deleteDir] Deleting directory <some temporary directory>
BUILD FAILED
java.lang.ExceptionInInitializerError
At this point, I am completely stymied about how to proceed.
I wonder what new issues await once this 10th issue is addressed.
Really, is this tool set ready for prime time?

Sorry to hear you are having so many issues with using the WLS 9.1 web service Ant tasks, inside of Eclipse.
I generally create a User Library for the couple weblogic jars needed, and use it (the User Library) in my Eclipse projects that I create JWSes in. 
I also have a separate WebLogic Library in Eclipse (actually 2 libraries since I work with WL 8.1 and now WL 9.1). As you may know, one of the long-standing issues with the Ant integration within Eclipse is the fact that Ant, being an External Tool, does not receive the Project-specific Paths/Libraries. However, since most Java-relevant Ant tasks can take classpath and classpathref attributes, this is usually not an issue. In the case of the BEA-supplied wsdlc Ant task, it is apparent from the verbose/debug console output that wsdlc can see the jars in its classpathref, but it ignores those references when resolving class references and instead only uses the system classpath.

I've only needed the weblogic.jar and xbean.jar, not all the ones you mentioned in an earlier thread of this post. 
I have not tried to winnow down exactly which jars are required. I simply included all the jars that exist and were added to the system classpath by the setDomainEnv.bat file created by WebLogic 9.1.

Afterwards, I create an Ant Builder to build the JWS Web Service EAR, as opposed to fiddlin' with Eclipse. 
I too use Ant to build my deployable archives. Eclipse is simply my IDE of choice. I validated that all the issues I listed occurred when running Ant from the command line.

If you are interested in how I do it, send me an e-mail (to [email protected]), and I'll send you a zip of one of these JWS projects. The build.xml script for the project, takes care of a lot of the "annoyances" you mentioned, one of which I think is not accurate. I have never had a situation where the wsdlc Ant task "overwrote" my XXXImpl.java file.. 
Since I'm doing a POC to determine how we want to proceed with developing Web Services and an SOA in general, I tried to perform the same tasks using Axis 2 1.0, the WebLogic 9.1 tools, and XFire 1.1. Overwriting the Impl class is a common failing in the tools which take a WSDL and create Java source files for all three frameworks.

Try my scenario. Add another operation to an existing WSDL, and run the wsdlc Ant Task. The old IMPL class will be over-written.

Because of this, I have a separate Impl class and I make sure that all its methods and annotations match the methods and annotations in the Skeleton Impl class created by wsdlc.

Maybe that's because I use the <exec> Ant task with jar.exe (the xvf options) in my build.xml, to only get what I need out of the .jar/.zip the wsdlc generates. I'm typically only interest in the interface class that my XXXImpl.java file needs to implements, because I use XMLBeans for the input args (and return values) of my web service operations. 
Perhaps. I am not using XMLBeans in any of the three frameworks because the resulting service seems to be lighter-weight in all three frameworks if XMLBeans is not used. I'm sure there will be scenarios where XMLBeans is preferred, but I have not encountered that case in this POC.

Regards,
Mike Wooten
Thanks for the follow-up.
Mike McAngus

Problems - WLS 10.0 web service client

I'm having a few issues with WLS 10.0 web service client.
 I generated a service control from the WSDL. The service is provided by a 3rd party (non-WLS) at another company. I generated the control within my web project and it's deployed as part of the web application. I experience the following problems with the service control API:
 1) The methods setKeyStore(), setTrustStore(), setClientCert() all seem to be ignored - the server always uses the values set in the server's environment definition. Note - the setEndpointAddress() seems to work.
 2) The client request does not set the 'Content-Type' HTTP header correctly (it's set to text/html) - I have no way to override this via the service control API (that I can see).
 3) I don't see any way/place to turn on more detailed tracing of what's going on internally with the service control invocation - is there a way to enable a detailed trace log of what is happening within the service control?
 Note: I'm able to call the web service via the test client (after importing the 3rd party server cert into my local cacerts).
 Thanks,
 [email protected]

Thank you for the reply..
But im still geting the same error. I have tried to include all the libraries in JWSDP pack but still.. I have managed to narrow down the place where the error occures.. It actually happens when I try to get the WebService Client Servant which is located in the package LSC:
---> LSC.LWServiceGenClient.LWS_Impl service = new LSC.LWServiceGenClient.LWS_Impl();
LSC.LWServiceGenClient.LWSServantInterface lagerServiceServant = LSC.LWServiceGenClient.LWSServantInterface_Stub)service.getLWSServantInterfacePort();
return lagerServiceServant;
Could something be wrong with the way I package the Jar? I'm using Sun One Studio and have tried including the 5 packages the application consists of; I have tried including just the files; moving the main class to <root>.. Still same problem..
Or could there be some different fundemental thingy I have forgotten ??
thanks
Aqoi

WLS 10.3 - Self Registration with External LDAP Fails (somewhat)

I have a WLS 10.3.5 instance with WebCenter Spaces.
I've added an OpenLDAP provider to the security realm, set the OpenLDAP provider and the default authenticator to "sufficient", and reordered the providers in the console to list the OpenLDAP provider first. I've also set "virtualize=true" via the enterprise manager interface, and added the <extendedProperty> attributes for "user.create.bases" and "group.create.bases" in the jps-config.xml file
Using the self registration feature in Spaces, I fill in a proposed new user name, and select "check availability". The check returns "available".
I finish the registration, and submit. I receive the following error, and the registration page remains on the screen:
"User not created. Either the user name or the password does not adhere to the registration policy or the identity store is unavailable. Specify the required user credentials or contact your administrator for assistance." NO ERROR in the Spaces logs.
But I look in OpenLDAP, and lo and behold, the user DID get created.
So remember I still haven't left the registration page. Clicking the "check availability" button still returns "available".
Now clicking the submit button throws the following message:
"A user with the name <insert name entered previously in the "failed" registration> already exists. Choose another name."
The following error is logged in the Spaces log:
[WC_Spaces] [WARNING] [] [oracle.ods.virtualization.exception] [tid: [ACTIVE].ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: anonymous] [ecid: 004h0uRltQY9Dgh_x9h8iW0003qO0001rr,0:1] [APP: webcenter#11.1.1.4.0] [URI: /webcenter/faces/oracle/webcenter/page/scopedMD/s8bba98ff_4cbb_40b8_beee_296c916a23ed/businessRolePages/AppSelfRegistration.jspx] OVD-40077[[
javax.naming.NameAlreadyBoundException: [LDAP: error code 68 - Entry Already Exists]; remaining name 'cn=<redacted>,ou=<redacted>,dc=<redacted>,dc=<redacted>,dc=<redacted>'
 at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3036)
 at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2987)
 at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2794)
 at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:788)
 at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:319)
 at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:248)
 at javax.naming.directory.InitialDirContext.createSubcontext(InitialDirContext.java:183)
 at oracle.ods.virtualization.engine.backend.jndi.ConnectionHandle.createSubcontext(ConnectionHandle.java:133)
 at oracle.ods.virtualization.engine.backend.jndi.BackendJNDI.add(BackendJNDI.java:457)
 at oracle.ods.virtualization.engine.chain.Chain.nextAdd(Chain.java:193)
 at oracle.ods.virtualization.engine.chain.BasePlugin.add(BasePlugin.java:67)
 at oracle.ods.virtualization.engine.chain.Chain.nextAdd(Chain.java:202)
 at oracle.ods.virtualization.engine.chain.BasePlugin.add(BasePlugin.java:67)
 at oracle.ods.virtualization.engine.chain.plugins.virtualattr.VirtualAttributePlugin.add(VirtualAttributePlugin.java:926)
 at oracle.ods.virtualization.engine.chain.Chain.nextAdd(Chain.java:202)
 at oracle.ods.virtualization.engine.chain.BasePlugin.add(BasePlugin.java:67)
 at oracle.ods.virtualization.engine.chain.plugins.usermanagement.UserManagement.add(UserManagement.java:531)
 at oracle.ods.virtualization.engine.chain.Chain.nextAdd(Chain.java:202)
 at oracle.ods.virtualization.engine.chain.PluginChain.runAdd(PluginChain.java:164)
 at oracle.ods.virtualization.engine.chain.PluginManager.runAdd(PluginManager.java:264)
 at oracle.ods.virtualization.engine.chain.PluginManager.runAdd(PluginManager.java:251)
 at oracle.ods.virtualization.engine.backend.AdapterServiceInterface.add(AdapterServiceInterface.java:240)
 at oracle.ods.virtualization.engine.backend.AdapterServiceInterface.add(AdapterServiceInterface.java:190)
 at oracle.ods.virtualization.engine.backend.BackendHandler.add(BackendHandler.java:329)
 at oracle.ods.virtualization.engine.chain.Chain.nextAdd(Chain.java:185)
 at oracle.ods.virtualization.engine.chain.BasePlugin.add(BasePlugin.java:67)
 at oracle.ods.virtualization.engine.chain.Chain.nextAdd(Chain.java:202)
 at oracle.ods.virtualization.engine.chain.PluginChain.runAdd(PluginChain.java:164)
 at oracle.ods.virtualization.engine.chain.PluginManager.runAdd(PluginManager.java:264)
 at oracle.ods.virtualization.engine.chain.PluginManager.runAdd(PluginManager.java:251)
 at oracle.ods.virtualization.engine.chain.GlobalServicesInterface.runAdd(GlobalServicesInterface.java:107)
 at oracle.ods.virtualization.operation.AddOperation.process(AddOperation.java:127)
 at oracle.ods.virtualization.service.DefaultVirtualizationSession.add(DefaultVirtualizationSession.java:148)
 at oracle.security.idm.providers.libovd.util.LibOVDRealm.createUser(LibOVDRealm.java:124)
 at oracle.security.idm.providers.libovd.LibOVDUserManager.createUser(LibOVDUserManager.java:177)
 at oracle.security.idm.providers.libovd.LibOVDUserManager.createUser(LibOVDUserManager.java:131)
 at oracle.webcenter.security.selfregistration.internal.view.backing.UserManagerBean.createUser(UserManagerBean.java:598)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at com.sun.el.parser.AstValue.invoke(Unknown Source)
 at com.sun.el.MethodExpressionImpl.invoke(Unknown Source)
 at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53)
 at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1256)
 at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183)
 at oracle.adf.view.rich.component.fragment.UIXRegion.broadcast(UIXRegion.java:148)
 at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92)
 at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361)
 at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96)
 at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:102)
 at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92)
 at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361)
 at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96)
 at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:96)
 at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents(LifecycleImpl.java:902)
 at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:313)
 at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:186)
 at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
 at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.bi.nanserver.adf.servlet.BIADFServletFilter.doFilter(BIADFServletFilter.java:27)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.bi.presentation.runtime.binding.BIRegionBindingFilter.doFilter(BIRegionBindingFilter.java:40)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.portlet.client.adapter.adf.ADFPortletFilter.doFilter(ADFPortletFilter.java:32)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.webcenter.framework.events.dispatcher.EventDispatcherFilter.doFilter(EventDispatcherFilter.java:44)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.wcps.client.PersonalizationFilter.doFilter(PersonalizationFilter.java:75)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.webcenter.content.integration.servlets.ContentServletFilter.doFilter(ContentServletFilter.java:168)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.webcenter.generalsettings.model.provider.GeneralSettingsProviderFilter.doFilter(GeneralSettingsProviderFilter.java:85)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.webcenter.webcenterapp.internal.view.webapp.WebCenterShellPageRedirectionFilter.doFilter(WebCenterShellPageRedirectionFilter.java:250)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.webcenter.webcenterapp.internal.view.webapp.WebCenterShellFilter.doFilter(WebCenterShellFilter.java:696)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.adf.view.page.editor.webapp.WebCenterComposerFilter.doFilter(WebCenterComposerFilter.java:109)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.adf.share.http.ServletADFFilter.doFilter(ServletADFFilter.java:62)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)
 at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
 at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
 at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
 at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)
 at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
 at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:175)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.webcenter.webcenterapp.internal.view.webapp.WebCenterLocaleWrapperFilter.processFilters(WebCenterLocaleWrapperFilter.java:335)
 at oracle.webcenter.webcenterapp.internal.view.webapp.WebCenterLocaleWrapperFilter.doFilter(WebCenterLocaleWrapperFilter.java:237)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
 at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
 at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
 at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
 at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
 at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
 at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
 at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
 at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
 at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
 at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Thoughts? Probably a simple config tweak, but it's not jumping out at me at the moment.
Thanks in advance!

Removed the <virtualize="true"> setting from Enterprise Manager, and the issue disappeared.

Compile build.xml with Ant for web service with annotations

Hi Friends,
I have a web service with annotations, using javax.annotation.PostConstruct, and javax.annotation.PreDestroy.
I have a build.xml to create a EAR for this web service.
When I run the ant task, the build complete successfully but the .war file cannot be deployed on the WLS server. Taking a closer look, I see that the required files such as, webservices.xml, weblogic.xml, weblogic-webservices.xml, Provision.wsdl files are not generated.
Following is the build.xml file:
<?xml version="1.0" encoding="windows-1252" ?>
<project default="jwsc">
<property file="build.properties"/>
<property name="weblogic.jar.classpath"
value="C:/bea_jDev/wlserver_10.3/server/lib"/>
<property name="oimclient.jar.classpath"
 value="C:/_data/Project_Dc/OIM_jars" />
 <property name="com.jar.classpath" value="C:/JDeveloper/mywork/Service_Test/lib" />
<taskdef name="jwsc" classname="weblogic.wsee.tools.anttasks.JwscTask">
<classpath>
<path id="weblogic.classpath">
<pathelement path="WEBLOGIC_HOME"/>
<fileset dir="${weblogic.jar.classpath}">
<include name="**/*.jar"/>
</fileset>
</path>
</classpath>
</taskdef>
<target name="all" depends="clean,build-service,deploy"></target>
<target name="build-service">
 <jwsc srcdir="${src.home}" destdir="ear_directory" >
<classpath>
<path id="oim.classpath">
<pathelement path="OIM_HOME"/>
<fileset dir="${oimclient.jar.classpath}">
<include name="**/*.jar"/>
</fileset>
<fileset dir="${com.jar.classpath}">
<include name="**/*.jar"/>
</fileset>
</path>
</classpath>
<jws file="${jws.home}" type="JAXWS" />
</jwsc>
</target>
<target name="deploy">

</target>
<target name="clean">
<delete dir="output" />
</target>
</project>
Can you please point out what else is to be done and where exactly am I going wrong in writing the build.xml file.
Let me know if some else information is required.

This is what I get when I run the ant task:
Buildfile: C:\JDeveloper\mywork\ProvisioningService_Test2\Provision\resource\build.xml
build-service:
[jwsc] JWS: processing module /com/fox/provision/webservice/endpoint/impl/ProvisionEndPointImpl
[jwsc] Parsing source files
[jwsc] Parsing source files
[jwsc] 1 JWS files being processed for module /com/.../provision/webservice/endpoint/impl/ProvisionEndPointImpl
[jwsc] [JAM] Warning: failed to resolve class org.apache.xmlbeans.XmlObject
[jwsc] [JAM] Warning: failed to resolve class com.bea.xml.XmlObject
[jwsc] [JAM] Warning: failed to resolve class javax.xml.rpc.holders.Holder
[jwsc] JWS: C:\..\...\..\...\code\ProvisioningService\src\com\...\provision\webservice\endpoint\impl\..EndPointImpl.java Validated.
[jwsc] Processing 1 JAX-WS web services...
[jwsc] warning: Specified AnnotationProcessorFactory, 'com.sun.istack.ws.AnnotationProcessorFactoryImpl', not found on search path.
warning: No annotation processors found but annotations present.
2 warnings
[jwsc] Compiling 2 source files to C:\DOCUME~1\....\LOCALS~1\Temp\_lsgijm
[jwsc] Building jar: C:\..\...\..\...\code\ProvisioningService\src\com\...\provision\webservice\deploy\ear_directory\com\fox\provision\webservice\endpoint\impl\...EndPointImpl.war
[jwsc] Created JWS deployment outputFile: C:\..\...\..\...\code\ProvisioningService\src\com\...\provision\webservice\deploy\ear_directory\....\...\provision\webservice\endpoint\impl\..EndPointImpl.war
[jwsc] [EarFile] Application File : C:\..\...\..\...\code\ProvisioningService\src\com\.....\provision\webservice\deploy\ear_directory\META-INF\application.xml
[AntUtil.deleteDir] Deleting directory C:\DOCUME~1\....\LOCALS~1\Temp\_lsgijm
BUILD SUCCESSFUL
Total time: 7 seconds
Due to some limitations, I edited the path in the build.xml files.
Please let me know what can be done. Thanks.
Edited by: user9112073 on Nov 22, 2011 9:52 PM

Configuring NT service with disableWeblogicClassPath

Hi
Due to some classloader issues we start up WebLogic with the following
system property:
-Dweblogic.system.disableWeblogicClassPath=true
and no weblogic.class.path property.
However, when trying to set this up for an NT service using wlconfig,
wlconfig seems to insist on a weblogic.class.path system property. When
that property exists (although empty) WebLogic will not boot.
It seems that you can't run weblogic as an NT service with
weblogic.system.disableWeblogicClassPath=true?
Regards
Steffen Bering Jensen
Systems Architect * Nordija ApS * Denmark

Hi
The problem with t3config and disableWeblogicClassPath (described below) also
seems to exist in WLS 5.1 - sp2.
Regards
Steffen Bering Jensen
Systems Architect * Nordija ApS * Denmark
[email protected] wrote:
I hope that it is fixed in post 4.5.0 versions.
[email protected] wrote:
Steffen
I ran into the same problem with 4.5.0 while using t3config
I would like to know the version you are working with.
Support, please tell me it can be fixed.
Madhu
"Steffen B. Jensen" wrote:
Hi
Due to some classloader issues we start up WebLogic with the following
system property:
-Dweblogic.system.disableWeblogicClassPath=true
and no weblogic.class.path property.
However, when trying to set this up for an NT service using wlconfig,
wlconfig seems to insist on a weblogic.class.path system property. When
that property exists (although empty) WebLogic will not boot.
It seems that you can't run weblogic as an NT service with
weblogic.system.disableWeblogicClassPath=true?
Regards
Steffen Bering Jensen
Systems Architect * Nordija ApS * Denmark

Looking for WLS 7.x Web Services interoperability information

Does anyone know of any published reports on compatibility when non-WLS clients
access a WLS web service? I’m completing some tests with clients created using
the Java Web Services Developers Pack but I’m more interested in how it also does
with other vendor implementations (Microsoft, IBM, Apache). I’m also interested
in whether WLS 6.x clients can access WLS 7.x web services. I haven’t seen BEA
referenced very often on the interoperability sites. Has BEA published any information
on their compatibility? Has anyone else published information on this?
Thanks,
Dave

The server seems to be OK (tried intra and internet) ... yes it's normally up.
Please try again and let me know of any further problems.
Thanks,
Bruce
Dave wrote:
Bruce,
Thanks for the link but it looks like the server is down (connection timed out).
Is the server normally up?
Thanks,
Dave
Bruce Stephens <[email protected]> wrote:
Hi Dave,
I think you will find that the round 3 tests build on most of the work
done in 1/2.
Also, there are results listed on our interop server
http://webservice.bea.com:7001/results/summary.html
Thanks,
Bruce
Dave wrote:
manoj,
I looked at test results on Sun’s site and whitemesa. I only noticedBEA in round
3. Can you point me to the other test results?
Thanks,
Dave
"manoj cheenath" <[email protected]> wrote:
BEA participate in the soapbuilder interop testing and WLS 7.0
pass all of the round I, II and III interop tests defined by soap
builders (with most vendors).
Also, we have internal interop tests for .Net and AXIS.
regards,
-manoj
"Dave" <[email protected]> wrote in message
news:[email protected]..
Does anyone know of any published reports on compatibility when
non-WLS
clients
access a WLS web service? I'm completing some tests with clients
created
using
the Java Web Services Developers Pack but I'm more interested in
how
it
also does
with other vendor implementations (Microsoft, IBM, Apache). I'm
also
interested
in whether WLS 6.x clients can access WLS 7.x web services. I haven'tseen BEA
referenced very often on the interoperability sites. Has BEA publishedany information
on their compatibility? Has anyone else published information on
this?
Thanks,
Dave

Stability of WLS 8.1 Timer Service?

Hi there,
Does anyone have anything to comment on the stability of the WLS 8.1
Timer service? One of our project teams indicated that BEA has a
whitepaper discouraging the use of the J2EE scheduler that comes with
WLS 8.1 as it might cause stability issues with the server.
Just wanted to know if anyone has any experience on this.
Cheers!
Steven

Steven wrote:
Hi there,
Does anyone have anything to comment on the stability of the WLS 8.1
Timer service? One of our project teams indicated that BEA has a
whitepaper discouraging the use of the J2EE scheduler that comes with
WLS 8.1 as it might cause stability issues with the server.
Just wanted to know if anyone has any experience on this.
Cheers!
StevenSteven,
Do you think you can get a hand on this whitepaper..? we are using the
timer service too, and it would be useful to take a look at this..
thanks
deepak

Having horrible service with 4GLTE I have had 3G for several weeks (I am not the only person I know having this problem), I have reset my network settings and it did not resolve the issue. I am also unable to send SMS and text messages without them eithe

Having horrible service with 4GLTE I have had 3G for several weeks (I am not the only person I know having this problem), I have reset my network settings and it did not resolve the issue. I am also unable to send SMS and text messages without them either failing or not sending at all. Is there an outage in the Cleveland, Ohio area (zip codes 44129, 44134, 44137) or anything else I can do to resolve this issue?

Not that I'm a Verizon employee, but I have experience in the field. An LTE tower will only extend up to, on a perfect day, with no elevation, 6-7 miles. On a typical day, you will be lucky at four (4) miles. The three ZIP codes you've given are all within about a 12 mile radius. That would mean that 2-3 towers are currently down at the same time, and Verizon would know about it within the hour. Being it's Cleveland, I'm sure they would receive numerous calls regarding an outage of that size.
My point is that if you're having issues in all three ZIP codes, chances are it's a phone issue. If you're handset is simply not receiving LTE, but still receiving 3G, that would signify a SIM card issue. You need to get your SIM card replaced.

Issue with OSI PI WCF Web Service with wshttpbinding

Hi Experts,
System Details:
SAP MII 14 SP4
OSI PI Web Service: PITimeSeries
I am having issue when trying to call OSI PI web service using http post. it is returning status 0 when i am using exception handler in BLS.
Same web service works fine with basichttpbinding (SOAP 1.1) but with wshttpbinding (SOAP 1.2) it is giving error.
Following are Web config binding details for web service.
 <wsHttpBinding>
 <binding name="wsBinding_2011" sendTimeout="00:01:00" receiveTimeout="00:10:00" bypassProxyOnLocal="false" transactionFlow="false" hostNameComparisonMode="StrongWildcard" maxBufferPoolSize="524288" maxReceivedMessageSize="65536" messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true" allowCookies="false">
 <reliableSession ordered="true" inactivityTimeout="00:10:00" enabled="false" />
 <security mode="Message">
 <message clientCredentialType="Windows" negotiateServiceCredential="true" algorithmSuite="Default" establishSecurityContext="true" />
 </security>
 </binding>
 </wsHttpBinding>
I am not sure it could be the issue with passing windows credentials.
Did anybody consumed WCF web service with wshttpbinding with security mode as Message and clientCredentialType as Windows.
Also i was trying to pass MYSAPSSO2 SSO token to service in http post but first i am not sure if this is correct windows token and second which header property of service should be mapped and i am not sure that I am going into correct direction or not.
Please let me know what i am missing.
I have tried following other options and tools:
SOAP UI: basichttpbinding works fine for wshttpbinding receiving Internal Server error in log and Response as
 The security context token is expired or is not valid.
MII Web Service Action Block: basichttpbinding works fine for wshttpbinding not able to configure url through wizard because as per my discussion with other MII experts MII does not support SOAP1.2. that is one reason for using http post.
WCF Storm: both bindings works fine (There is option to select windows authentication and Impersonation level as delegation)
WCF Test Client: Both bindings works fine
Any help is appreciated.
Thanks & Regards,
Manoj Bilthare

Hi Sam,
The web service is valid following are details of testing on various tools.
SOAP UI: basichttpbinding works fine for wshttpbinding receiving Internal Server error in log and Response as The security context token is expired or is not valid.
MII Web Service Action Block: basichttpbinding works fine for wshttpbinding not able to configure url through wizard because as per my discussion with other MII experts MII does not support SOAP1.2. that is one reason for using http post.
WCF Storm: both bindings works fine (There is option to select windows authentication and Impersonation level as delegation)
WCF Test Client: Both bindings works fine
Please let me know if additional details required.
Thanks & Regards,
Manoj Bilthare

Is there a way to turn on location services with iCloud

Basically that.

This doesn't make sense. ...juat sayin'
Location services are a part of your iOS device (or Mac). You don't "turn on" location services with iCloud. You can visit http://www.icloud.com and use Find My iPhone to see the location of the device if you want (assuming you have enabled this from the iPhone first).

Looking for software or a service with which I can create a personalized photo calendar

I am looking for software or a service with which I can create a personalized photo calendar. Any recommendations?
Jerry

Thanks for the reply.
iPhoto, unfortunately, has some real problems in my opinion. Control over image placement and size is limited. This is compounded by the fact that Apple has not made the job any easier by refusing to publish information such as recommended aspect ratios and pixel sizes of images used to create a calendar. Obviously, these both change as the page layouts change. But, I don't think it is too much to ask that Apple supply image aspect ratios for each frame size, 2:3, 3:4, 1:1, or something else. What pixel sizes are required for each frame size/aspect? It is impossible to place 2 photos (or 1 photo and a name) on one date should 2 birthdays fall on one day.
Further, there is no recommendation for color space to be used by the printer.
I am tired of trying out a photo in the calendar only to find it looks bad at the pixel size and aspect I chose, then have to go back to the original, re-crop, resize, and wrestle with bringing it back to iPhoto. (I use Aperture to organize my images.)
I must also add that I had a very bad experience with an iPhoto book earlier this year. Don't know if Apple has fixed the problems as I refuse to invest another 20 hours of time and more then $150.00 to find out.
I am seriously looking for something to replace iPhoto (unless changes are made) to do the 10 or 15 calendars for my family again this year (and possibly redo my book).
Jerry

Calling Web Service with SOAP header from BPEL

Hi,
I am calling a web service (with header information) from BPEL. In the Invoke activity, i created a header variable to pass the header information.
But, when i test the BPEL service, invoke activity fails because the header information is not being passed.
Below is the error message (copied from clipboard).
+<messages><input><Invoke_1_getsubinfo_InputVariable><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="parameters"><getsubinfoElement xmlns="http://ws/its/tabs/webservices/SingleRowWS/SingleRowWS.wsdl">+
+<pSubnoin>+
+<insubno>12345678</insubno>+
+</pSubnoin>+
+</getsubinfoElement>+
+</part></Invoke_1_getsubinfo_InputVariable></input><fault><bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>exception on JaxRpc invoke:+
start fault message:+
Internal Server Error (Caught exception while handling request: javax.xml.rpc.JAXRPCException: Not authenticated user)+
*:end fault message*</summary>
+</part></bindingFault></fault></messages>+
As said, no header information is visible in the Invoke activity.
Please provide help for the above issue.
-MJ

Hello Patrick,
Thanks for the response. I am using normal assign activity to assign values to the header variable as shown below. HeadMT is the header variable which is passed in the invoke activity.
+<assign name="Assign_Header">+
+<copy>+
+<from expression="'tkl12'"/>+
+<to query="/ns1:LOGIN_INFO/ns1:USER_NAME" variable="*HeadMT*"+
part="payload"/>
+</copy>+
+<copy>+
+<from expression="'tkl123'"/>+
+<to query="/ns1:LOGIN_INFO/ns1:PASSWORD" variable="*HeadMT*"+
part="payload"/>
+</copy>+
+<copy>+
+<from expression="'TKL'"/>+
+<to query="/ns1:LOGIN_INFO/ns1:CHANNEL_ID" variable="*HeadMT*"+
part="payload"/>
+</copy>+
+</assign>+
The expected input by the web service is as below with the header information highlighted.
+<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://ws/webservices/RowWS/RowWS.wsdl">+
+*<soap:Header>*+
+*<ns1:LOGIN_INFO>*+
+*<ns1:USERNAME>tkl12</ns1:USERNAME>*+
+*<ns1:PASSWORD>tkl123</ns1:PASSWORD>*+
+*<ns1:CHANNEL_ID>TKL</ns1:CHANNEL_ID>*+
+*</ns1:LOGIN_INFO>*+
+*</soap:Header>*+
+<soap:Body>+
+<ns1:substatusElement>+
+<ns1:pInparam>+
+<ns1:insubno>7674988</ns1:insubno>+
+</ns1:pInparam>+
+</ns1:substatusElement>+
+</soap:Body>+
+</soap:Envelope>+

Invoke web service with DTO

Hey guys,
I am quite new in using BPEL. My first test worked fine, but know I have an issue, which I can not solve. Invoking web services with a basic return value is no problem. I could also you a dto object including some basic variables in order to invoke the web service without having problems.
But when I have a dto object as return value, I get the following exception.
Could someone give me a hint to fix my problem...that would be great!
Thanks alot!
Sven
<messages>
- <input>
- <carReserveRequest>
- <part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="in0">
- <in0 xmlns="" xmlns:def="urn:TravelBooking" xsi:type="def:CarReservationDTO" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<carType>
Mini
</carType>
<customerName>
9
</customerName>
<customerPhone>
9
</customerPhone>
<reservationEnd>
2030-12-12T00:00:00.000+01:00
</reservationEnd>
<reservationStart>
2029-12-12T00:00:00.000+01:00
</reservationStart>
</in0>
</part>
</carReserveRequest>
</input>
- <fault>
- <remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
- <part name="summary">
<summary>
exception on JaxRpc invoke: trailing block elements must have an id attribute
</summary>
</part>
</remoteFault>
</fault>
</messages
Message was edited by:
user606281

Here is more information. Below are the relevant sections of the web service's WSDL which I am trying to call from BPEL:
- <wsdl:message name="getNextIDResponse">
<wsdl:part name="part1" element="ns0:getNextIDResponse" />
</wsdl:message>
- <wsdl:message name="getNextIDFault">
<wsdl:part name="part1" element="ns0:SOAPExceptionFault" />
</wsdl:message>
<wsdl:message name="getNextIDMessage" />
- <wsdl:portType name="GetUniqueIDPortType">
- <wsdl:operation name="getNextID">
<wsdl:input message="axis2:getNextIDMessage" wsaw:Action="urn:getNextID" />
<wsdl:output message="axis2:getNextIDResponse" />
<wsdl:fault name="getNextIDFault" message="axis2:getNextIDFault" />
</wsdl:operation>
</wsdl:portType>

WLS 6.0 NT Service with Cocoon2

Similar Messages

Maybe you are looking for