JAX RS in WLS 12.1.3

Hi,
I'm trying to create a helloworld jax rs application without any servlet or application.
According to WLS documentation (https://docs.oracle.com/middleware/1213/wls/RESTF/deploy-restful-service.htm#RESTF191) we are able to deploy war with some annotated RS classes and reach them by /resources/ path.
So I've done a simple application: https://gist.github.com/wqrts/2b53675cb8a662f8fa0a and deployed it with jax-rs-2.0.war as shared library.
But no luck, 404 on both http://localhost:7001/main-0/resources/test and http://localhost:7001/main-0/application.wadl
Any ideas on what I've done wrong would be great. Thanks.

Verified WebLogic Classloading using CAT '( wls-cat app ) and found oracle.dms.console.DMSConsole was loaded from web-inf jar and ucp classes were loaded from jar from weblogic, used below entry in weblogic.xml to load everything from web-inf to resolve the issue
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
Thanks
Sandeep

Similar Messages

ClassCastException in my WS over JMS using JAX-RPC in WLS 10.3...

Hi,
I am developing a WS over JMS using JAX-RPC in WLS 10.3 (I tried both WLS 10.3.0 and 10.3.1). And when WLS is trying to marshal the response, it throws "ClassCastException":
ava.lang.ClassCastException: org.tmforum.mtop.nrf.xsd.com.v1.EquipmentHolderEnumType cannot be cast to java.lang.String
at com.bea.staxb.runtime.internal.StringTypeConverter.print(StringTypeConverter.java:45)
at com.bea.staxb.runtime.internal.SimpleContentBeanMarshaller.print(SimpleContentBeanMarshaller.java:52)
at com.bea.staxb.runtime.internal.RuntimeBindingProperty.getLexical(RuntimeBindingProperty.java:154)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeCharData(PushMarshalResult.java:639)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:413)
at com.bea.staxb.runtime.internal.SimpleContentRuntimeBindingType.accept(SimpleContentRuntimeBindingType.java:46)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:153)
at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:631)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:403)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:153)
at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:631)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:403)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:153)
at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:631)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:400)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:153)
at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:631)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:403)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:153)
at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:631)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:400)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:153)
at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:631)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:403)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:153)
at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:631)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:400)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:153)
at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:631)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:403)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:153)
at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:631)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:403)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalTopType(PushMarshalResult.java:96)
at com.bea.staxb.runtime.internal.MarshallerImpl.marshalBindingType(MarshallerImpl.java:302)
at com.bea.staxb.runtime.internal.MarshallerImpl.marshalElement(MarshallerImpl.java:383)
at weblogic.wsee.bind.runtime.internal.LiteralSerializerContext.marshalElement(LiteralSerializerContext.java:82)
at weblogic.wsee.bind.runtime.internal.BaseSerializerContext.internalSerializeElement(BaseSerializerContext.java:197)
at weblogic.wsee.bind.runtime.internal.BaseSerializerContext.serializeElement(BaseSerializerContext.java:128)
at weblogic.wsee.codec.soap11.SoapEncoder.encodePart(SoapEncoder.java:322)
at weblogic.wsee.codec.soap11.SoapEncoder.encodeReturn(SoapEncoder.java:228)
at weblogic.wsee.codec.soap11.SoapEncoder.encodeParts(SoapEncoder.java:215)
at weblogic.wsee.codec.soap11.SoapEncoder.encode(SoapEncoder.java:134)
at weblogic.wsee.codec.soap11.SoapCodec.encode(SoapCodec.java:134)
at weblogic.wsee.ws.dispatch.server.CodecHandler.encode(CodecHandler.java:104)
at weblogic.wsee.ws.dispatch.server.CodecHandler.handleResponse(CodecHandler.java:51)
at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:287)
at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:271)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.callHandleResponse(ServerDispatcher.java:341)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:189)
at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
at weblogic.wsee.server.jms.JmsWebservicesMessageDispatcher.dispatchMessage(JmsWebservicesMessageDispatcher.java:175)
at weblogic.wsee.server.jms.JmsQueueListener.processMessage(JmsQueueListener.java:397)
at weblogic.wsee.server.jms.JmsQueueListener.onMessage(JmsQueueListener.java:392)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4585)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4271)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3747)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5096)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
The "EquipmentHolderEnumType" is generated JAXB object (obviously it is not a String) from WSDL using WLS wsld generation. And here is how that Enum is defined in XSD:
<xsd:simpleType name="EquipmentHolderEnumType">
<xsd:annotation>
<xsd:documentation>
<p>Equipment holder type</p>
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="MINOR_EXT"/>
<xsd:enumeration value="rack"/>
<xsd:enumeration value="shelf"/>
<xsd:enumeration value="sub_shelf"/>
<xsd:enumeration value="slot"/>
<xsd:enumeration value="sub_slot"/>
<xsd:enumeration value="remote_unit"/>
<xsd:enumeration value="remote_slots"/>
</xsd:restriction>
</xsd:simpleType>
My question is why WLS is trying to cast the EnumType to String when marshalling it? How can I fix this exception?
Also, second question: my WS will take some time to get the response ready (1+ minute). I was using WLS console test client to test my WS. And the test client always got time out:
java.io.IOException: Request timed out
at weblogic.wsee.connection.transport.jms.JmsTransport.receive(JmsTransport.java:356)
at weblogic.testclient.WebServiceOperation.invokeJms(WebServiceOperation.java:463)
at weblogic.testclient.WebServiceOperation.addWeblogicHeadersAndInvoke(WebServiceOperation.java:382)
at weblogic.testclient.WebServiceOperation.invokeComplex(WebServiceOperation.java:305)
at weblogic.testclient.WebServiceOperation.invoke(WebServiceOperation.java:626)
How can I configure the WLS console test client so that I can increase teh timeout setting for the client?
Thank you very much!
Jian

Hi, pls how did you solve your problem exatly? Because I have similar problem without solution.
I have WSDL contract like:
<xs:element name="duration">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="durationType">
<xs:attribute name="days" type="xs:int" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:simpleType name="durationType">
<xs:restriction base="xs:string">
<xs:enumeration value="PERIODIC"/>
<xs:enumeration value="PERPETUAL"/>
<xs:enumeration value="CREDIT_DAYS"/>
</xs:restriction>
</xs:simpleType>
And client site generated by WLS ant task "generate-from-wsdl" with "JAXRPC" option and when I use calling of this client and exeption was appeared:
FaultString [com.company.DurationType] FaultActor [null] Detail [<detail><java:string>java.lang.ClassCastException: com.company.DurationType</java:string></detail>];
Note: all other messages are correct.
thx

JAX-WS proxy and WS-ReliableMessaging

Hello all,
JDeveloper 11.1.2.3
I've started the foray into looking at reliable web services as specified by WS-ReliableMessaging. I have a very simple Hello World web service deployed (it was written in C# and deployed on IIS, if you have to ask :P). In JDeveloper, I've generated a JAX-WS Style proxy and test class using the JDeveloper wizard to do so. I've specified that no Async methods be generated and that there are no client OWSM policies (none are deemed compatible with the web service anyway).
I then add a bit of code to my test class and run to test. The first time I run the class, the WS calls work successfully, although after the sequence of calls, I get an exception displayed in the console (see below). If I try to run the class again, the web service calls don't even execute and I get a different exception in the console (again, see below - at least part of this error is captured by my ReliabilityErrorListener). This sequence of events alternates ad-infinitum (odd-numbered attempts work with an exception, even-numbered attempts don't work.
I show my test code here:
      // Add your code to call the desired methods.
    WsrmClientInitFeature f = new WsrmClientInitFeature(true);
    ReliabilityErrorListener listener = new ReliabilityErrorListener()
      public void onReliabilityError(ReliabilityErrorContext context)
        // At a *minimum* do this
        System.out.println("RM sequence failure: " + context.getFaultSummaryMessage());
        // And optionally do this...
        // The context parameter tells you whether a request or the entire
        // sequence has failed. If a sequence fails, you'll get a notification
        // for each undelivered request (if any) on the sequence.
        if (context.isRequestSpecific())
          // We have a single request failure (possibly as part of a larger
          // sequence failure).
          // We can get the original request back like this:
          String operationName = context.getOperationName();
          System.out.println("Failed to deliver request for operation '" + operationName + "'. Fault summary: " +
                             context.getFaultSummaryMessage());
        else
          // The entire sequence has encountered an error.
          System.out.println("Entire sequence failed: " + context.getFaultSummaryMessage());
    f.setErrorListener(listener);
    hello = helloService.getWSHttpBindingHello(f);
    WsrmClient c = WsrmClientFactory.getWsrmClientFromPort(hello);
    System.out.println("Sequence ID is " + c.getSequenceId());
    //   c.reset();
    System.out.println(hello.getGreeting("John"));
    System.out.println(hello.getGreeting("Fred"));
    System.out.println(hello.getGreeting("Josephine"));
    System.out.println("Sequence ID is " + c.getSequenceId());
    try
      System.out.println(c.getAckRanges().first().lowerBounds);
      System.out.println(c.getAckRanges().first().upperBounds);
    catch (Exception e)
    // c.setFinalMessage();The calls that work look like this in the console:
Sequence ID is null
<05-Mar-2013 14:55:53 o'clock EAT> <Info> <Store> <BEA-280008> <Opening the persistent file store "weblogic.wsee.persistence.WseeFileStore" for recovery: directory=C:\JDeveloper\11.1.2.3\mywork\WSReliableClientPOC\Client requestedWritePolicy="Cache-Flush" fileLockingEnabled=true driver="NIO".>
<05-Mar-2013 14:55:53 o'clock EAT> <Info> <Store> <BEA-280009> <The persistent file store "weblogic.wsee.persistence.WseeFileStore" (569ea4fb-b0fd-4906-bb74-003b6885b1d5) has been opened: blockSize=512 actualWritePolicy="Cache-Flush(single-handle-non-direct)" explicitIOEnforced=false records=57.>
Hello, John. You have just communicated with me using WS-reliablemessaging
Hello, Fred. You have just communicated with me using WS-reliablemessaging
Hello, Josephine. You have just communicated with me using WS-reliablemessaging
Sequence ID is uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffd
1
3
<05-Mar-2013 14:56:03 o'clock EAT> <Error> <WseeRm> <BEA-224016> <An unexpected error occurred: weblogic.wsee.sender.api.ConversationNotFoundException: [WseeSender:221102]The conversation with the given name (uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd) could not be found.
weblogic.wsee.sender.api.ConversationNotFoundException: [WseeSender:221102]The conversation with the given name (uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd) could not be found.
     at weblogic.wsee.sender.DefaultProvider.DefaultSendingServiceProvider.getConversation(DefaultSendingServiceProvider.java:222)
     at weblogic.wsee.sender.DefaultProvider.DefaultSendingServiceProvider.stopConversation(DefaultSendingServiceProvider.java:287)
     at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:257)
     at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:30)
     at weblogic.wsee.reliability2.store.SequenceStore.removePhysicalStore(SequenceStore.java:109)
     at weblogic.wsee.persistence.LogicalStore.close(LogicalStore.java:955)
     at weblogic.wsee.persistence.LogicalStore.closeLogicalStores(LogicalStore.java:402)
     at weblogic.wsee.persistence.LogicalStore.closeStore(LogicalStore.java:384)
     at weblogic.wsee.persistence.LogicalStore.closeAllStores(LogicalStore.java:365)
     at weblogic.wsee.persistence.LogicalStore$1.run(LogicalStore.java:164)
>
<05-Mar-2013 14:56:03 o'clock EAT> <Error> <WseePersist> <BEA-221000> <An unexpected error occurred: java.lang.IllegalStateException: Attempt to remove listener from weblogic.wsee.reliability2.sequence.SourceSequence@6ac27081 - uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd when it is not the master instance
java.lang.IllegalStateException: Attempt to remove listener from weblogic.wsee.reliability2.sequence.SourceSequence@6ac27081 - uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd when it is not the master instance
     at weblogic.wsee.reliability2.sequence.Sequence.removePropertyChangeListener(Sequence.java:1250)
     at weblogic.wsee.reliability2.store.SequenceMap.shutdownSequence(SequenceMap.java:558)
     at weblogic.wsee.reliability2.store.TimedSequenceMap.shutdownSequence(TimedSequenceMap.java:182)
     at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:274)
     at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:30)
     at weblogic.wsee.reliability2.store.SequenceStore.removePhysicalStore(SequenceStore.java:109)
     at weblogic.wsee.persistence.LogicalStore.close(LogicalStore.java:955)
     at weblogic.wsee.persistence.LogicalStore.closeLogicalStores(LogicalStore.java:402)
     at weblogic.wsee.persistence.LogicalStore.closeStore(LogicalStore.java:384)
     at weblogic.wsee.persistence.LogicalStore.closeAllStores(LogicalStore.java:365)
     at weblogic.wsee.persistence.LogicalStore$1.run(LogicalStore.java:164)
>
Process exited with exit code 0.The calls that don't work look like this:
Sequence ID is null
<05-Mar-2013 14:57:49 o'clock EAT> <Info> <Store> <BEA-280008> <Opening the persistent file store "weblogic.wsee.persistence.WseeFileStore" for recovery: directory=C:\JDeveloper\11.1.2.3\mywork\WSReliableClientPOC\Client requestedWritePolicy="Cache-Flush" fileLockingEnabled=true driver="NIO".>
<05-Mar-2013 14:57:49 o'clock EAT> <Info> <Store> <BEA-280009> <The persistent file store "weblogic.wsee.persistence.WseeFileStore" (569ea4fb-b0fd-4906-bb74-003b6885b1d5) has been opened: blockSize=512 actualWritePolicy="Cache-Flush(single-handle-non-direct)" explicitIOEnforced=false records=59.>
RM sequence failure:
weblogic.wsee.sender.api.PermanentSendException: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
Failed to deliver request for operation 'GetGreeting'. Fault summary:
weblogic.wsee.sender.api.PermanentSendException: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
Exception in thread "main" java.lang.AssertionError: weblogic.wsee.sender.api.PermanentSendException: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
     at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:689)
     at com.sun.xml.ws.client.Stub.process(Stub.java:272)
     at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:153)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:115)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
     at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
     at $Proxy36.getGreeting(Unknown Source)
     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 weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
     at $Proxy35.getGreeting(Unknown Source)
     at org.tempuri.WSHttpBinding_HelloClient.main(WSHttpBinding_HelloClient.java:96)
Caused by: weblogic.wsee.sender.api.PermanentSendException: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
     at weblogic.wsee.reliability2.store.SourceSequenceSender.checkForPermanentSendFailure(SourceSequenceSender.java:549)
     at weblogic.wsee.reliability2.store.SourceSequenceSender.handleFailureForSuspendedFiber(SourceSequenceSender.java:604)
     at weblogic.wsee.reliability2.store.SourceSequenceSender.sendRequestAndHandleResponseForSuspendedFiber(SourceSequenceSender.java:452)
     at weblogic.wsee.reliability2.store.SourceSequenceSender.sendRequestAndHandleResponse(SourceSequenceSender.java:293)
     at weblogic.wsee.reliability2.store.SourceSequenceSender.send(SourceSequenceSender.java:184)
     at weblogic.wsee.sender.DefaultProvider.Conversation.sendOneRequest(Conversation.java:671)
     at weblogic.wsee.sender.DefaultProvider.Conversation.sendPendingRequests(Conversation.java:579)
     at weblogic.wsee.sender.DefaultProvider.Conversation.access$1400(Conversation.java:44)
     at weblogic.wsee.sender.DefaultProvider.Conversation$2.timerExpired(Conversation.java:476)
     at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
     at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
Caused by: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
     at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:258)
     at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:273)
     at weblogic.wsee.reliability2.store.SourceSequenceSender.sendRequestAndHandleResponseForSuspendedFiber(SourceSequenceSender.java:442)
     ... 10 more
Caused by: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
     at weblogic.wsee.reliability2.tube.WsrmTubelineDeploymentListener$WsrmClientProtocolTube.processResponse(WsrmTubelineDeploymentListener.java:222)
     at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:877)
     at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:815)
     at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:778)
     at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:680)
     at com.sun.xml.ws.client.Stub.process(Stub.java:272)
     at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:238)
     ... 12 more
<05-Mar-2013 14:57:58 o'clock EAT> <Error> <WseeRm> <BEA-224016> <An unexpected error occurred: weblogic.wsee.sender.api.ConversationNotFoundException: [WseeSender:221102]The conversation with the given name (uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd) could not be found.
weblogic.wsee.sender.api.ConversationNotFoundException: [WseeSender:221102]The conversation with the given name (uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd) could not be found.
     at weblogic.wsee.sender.DefaultProvider.DefaultSendingServiceProvider.getConversation(DefaultSendingServiceProvider.java:222)
     at weblogic.wsee.sender.DefaultProvider.DefaultSendingServiceProvider.stopConversation(DefaultSendingServiceProvider.java:287)
     at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:257)
     at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:30)
     at weblogic.wsee.reliability2.store.SequenceStore.removePhysicalStore(SequenceStore.java:109)
     at weblogic.wsee.persistence.LogicalStore.close(LogicalStore.java:955)
     at weblogic.wsee.persistence.LogicalStore.closeLogicalStores(LogicalStore.java:402)
     at weblogic.wsee.persistence.LogicalStore.closeStore(LogicalStore.java:384)
     at weblogic.wsee.persistence.LogicalStore.closeAllStores(LogicalStore.java:365)
     at weblogic.wsee.persistence.LogicalStore$1.run(LogicalStore.java:164)
>
<05-Mar-2013 14:57:58 o'clock EAT> <Error> <WseePersist> <BEA-221000> <An unexpected error occurred: java.lang.IllegalStateException: Attempt to remove listener from weblogic.wsee.reliability2.sequence.SourceSequence@79424b7b - uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd when it is not the master instance
java.lang.IllegalStateException: Attempt to remove listener from weblogic.wsee.reliability2.sequence.SourceSequence@79424b7b - uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd when it is not the master instance
     at weblogic.wsee.reliability2.sequence.Sequence.removePropertyChangeListener(Sequence.java:1250)
     at weblogic.wsee.reliability2.store.SequenceMap.shutdownSequence(SequenceMap.java:558)
     at weblogic.wsee.reliability2.store.TimedSequenceMap.shutdownSequence(TimedSequenceMap.java:182)
     at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:274)
     at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:30)
     at weblogic.wsee.reliability2.store.SequenceStore.removePhysicalStore(SequenceStore.java:109)
     at weblogic.wsee.persistence.LogicalStore.close(LogicalStore.java:955)
     at weblogic.wsee.persistence.LogicalStore.closeLogicalStores(LogicalStore.java:402)
     at weblogic.wsee.persistence.LogicalStore.closeStore(LogicalStore.java:384)
     at weblogic.wsee.persistence.LogicalStore.closeAllStores(LogicalStore.java:365)
     at weblogic.wsee.persistence.LogicalStore$1.run(LogicalStore.java:164)
>
Process exited with exit code 1.Does anyone have any insight about this behaviour?
Thanks,
John

Some additional information for the second case. Using HTTP analyzer in JDeveloper, I can see 2 HTTP POSTs going to the web service. The first one is to initiate the WS-RM sequence and shows an offered conversation identifier and the reply shows that the server has given its own identifier instead of the offered one:
request:
POST http://xgis-lel-05717.ad.xglobal.com:80/WSReliablePOC/HelloService.svc HTTP/1.1
Proxy-Authorization:
Content-type: application/soap+xml;charset="utf-8";action="http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence"
Accept: application/soap+xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
User-Agent: Oracle JAX-WS 2.1.5
Host: xgis-lel-05717.ad.xglobal.com
Proxy-Connection: Keep-Alive
Content-Length: 1620
X-HTTPAnalyzer-Rules: 1@localhost:8099
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
    <env:Header>
        <wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing" env:mustUnderstand="true">http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence</wsa:Action>
        <wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:WLS1:WseeFileStore:3f3d2d8955322f32:201221c6:13d3a75f768:-7ffb</wsa:MessageID>
        <wsa:To xmlns:wsa="http://www.w3.org/2005/08/addressing">http://xgis-lel-05717.ad.xglobal.com/WSReliablePOC/HelloService.svc</wsa:To>
        <ReplyTo xmlns="http://www.w3.org/2005/08/addressing">
            <Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
        </ReplyTo>
        <FaultTo xmlns="http://www.w3.org/2005/08/addressing">
            <Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
        </FaultTo>
    </env:Header>
    <env:Body xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
        <wsrm:CreateSequence>
            <wsrm:AcksTo xmlns:wsa="http://www.w3.org/2005/08/addressing">
                <wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address>
                <wsa:ReferenceParameters xmlns:clspi="http://www.oracle.com/wsee/jaxws/cluster/spi">
                    <clspi:PhysicalStoreName
                        xmlns:wsa="http://www.w3.org/2005/08/addressing"
                        xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility" wsa:IsReferenceParameter="true">WseeFileStore</clspi:PhysicalStoreName>
                </wsa:ReferenceParameters>
            </wsrm:AcksTo>
            <wsrm:Expires>P1D</wsrm:Expires>
            <wsrm:Offer>
                <wsrm:Identifier>uuid:WLS1:WseeFileStore:3f3d2d8955322f32:201221c6:13d3a75f768:-7ffe</wsrm:Identifier>
                <wsrm:Expires>P1D</wsrm:Expires>
            </wsrm:Offer>
        </wsrm:CreateSequence>
    </env:Body>
</env:Envelope>
reply:
HTTP/1.1 200 OK
Content-Type: application/soap+xml; charset=utf-8
Cache-Control: private
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
Content-Length: 673
Server: Microsoft-IIS/7.5
Date: Tue, 05 Mar 2013 12:10:44 GMT
X-HTTPAnalyzer-RuleName: Pass through :
<?xml version="1.0" encoding="UTF-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
    <s:Header>
        <a:Action s:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequenceResponse</a:Action>
        <a:RelatesTo>uuid:WLS1:WseeFileStore:3f3d2d8955322f32:201221c6:13d3a75f768:-7ffb</a:RelatesTo>
    </s:Header>
    <s:Body>
        <CreateSequenceResponse xmlns="http://schemas.xmlsoap.org/ws/2005/02/rm">
            <Identifier>urn:uuid:b6886ed1-6cf2-40a4-99a3-f17cc5a295d7</Identifier>
            <Expires>P1D</Expires>
            <Accept>
                <AcksTo>
                    <a:Address>http://xgis-lel-05717.ad.xglobal.com/WSReliablePOC/HelloService.svc</a:Address>
                </AcksTo>
            </Accept>
        </CreateSequenceResponse>
    </s:Body>
</s:Envelope>The second POST shows the JDeveloper proxy calling the web service and sending a wsrm:Identifier value that the one originally offered by JDeveloper (see the sequence acknowledgement), not the one the server advised to use:
request:
POST http://xgis-lel-05717.ad.xglobal.com:80/WSReliablePOC/HelloService.svc HTTP/1.1
Proxy-Authorization:
Content-type: application/soap+xml;charset="utf-8";action="http://tempuri.org/Hello/GetGreeting"
Accept: application/soap+xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
User-Agent: Oracle JAX-WS 2.1.5
Host: xgis-lel-05717.ad.xglobal.com
Proxy-Connection: Keep-Alive
Content-Length: 1444
X-HTTPAnalyzer-Rules: 1@localhost:8099
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope">
    <S:Header>
        <wsa:To xmlns:wsa="http://www.w3.org/2005/08/addressing">http://xgis-lel-05717.ad.xglobal.com/WSReliablePOC/HelloService.svc</wsa:To>
        <wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing">http://tempuri.org/Hello/GetGreeting</wsa:Action>
        <ReplyTo xmlns="http://www.w3.org/2005/08/addressing">
            <Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
        </ReplyTo>
        <FaultTo xmlns="http://www.w3.org/2005/08/addressing">
            <Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
        </FaultTo>
        <wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:WLS1:WseeFileStore:3f3d2d8955322f32:201221c6:13d3a75f768:-7ffc</wsa:MessageID>
        <wsrm:SequenceAcknowledgement xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
            <wsrm:Identifier>uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-725c9c83:13d3a75543c:-7ffe</wsrm:Identifier>
            <wsrm:AcknowledgementRange Lower="1" Upper="3"/>
        </wsrm:SequenceAcknowledgement>
        <wsrm:Sequence
            xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm" S:mustUnderstand="true">
            <wsrm:Identifier>urn:uuid:b6886ed1-6cf2-40a4-99a3-f17cc5a295d7</wsrm:Identifier>
            <wsrm:MessageNumber>1</wsrm:MessageNumber>
        </wsrm:Sequence>
    </S:Header>
    <S:Body>
        <GetGreeting
            xmlns:ns2="http://schemas.microsoft.com/2003/10/Serialization/" xmlns="http://tempuri.org/">
            <name>John</name>
        </GetGreeting>
    </S:Body>
</S:Envelope>
response:
HTTP/1.1 500 Internal Server Error
Content-Type: application/soap+xml; charset=utf-8
Cache-Control: private
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
Content-Length: 710
Server: Microsoft-IIS/7.5
Date: Tue, 05 Mar 2013 12:10:52 GMT
X-HTTPAnalyzer-RuleName: Pass through :
<?xml version="1.0" encoding="UTF-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
    <s:Header>
        <a:Action s:mustUnderstand="1">http://www.w3.org/2005/08/addressing/soap/fault</a:Action>
    </s:Header>
    <s:Body>
        <s:Fault>
            <s:Code>
                <s:Value>s:Sender</s:Value>
                <s:Subcode>
                    <s:Value xmlns:a="http://schemas.xmlsoap.org/ws/2005/02/rm">a:UnknownSequence</s:Value>
                </s:Subcode>
            </s:Code>
            <s:Reason>
                <s:Text xml:lang="en-GB">The value of wsrm:Identifier is not a known Sequence identifier.</s:Text>
            </s:Reason>
            <s:Detail>
                <r:Identifier xmlns:r="http://schemas.xmlsoap.org/ws/2005/02/rm">uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-725c9c83:13d3a75543c:-7ffe</r:Identifier>
            </s:Detail>
        </s:Fault>
    </s:Body>
</s:Envelope>This seems to be an issue in the JDev-generated Proxy (still need to find out why it happens "every other time" and not "every time." The time it works, JDeveloper is sending the Identifier returned by the service. The time it works, however - you can also see that the "conversation not found" exception is referring to the original "offered" identifier and not the one that was used in the conversation. I'm now starting to suspect that the proxy generation for WS-RM may be a bit buggy. Anyone else with experience in this area?
A quick look at support.oracle.com does find note 1082278.1 which although for old versions of WebLogic, that WS-RM isn't supported for JAX-WS in WLS, but is supported for JAX-RPC. Since this seems to be for publishing web services, it is not at all clear as to whether this applies to me. In any case, the JDeveloper WS proxy wizard won't let me generate a JAX-RPC proxy, instead saying that the WSDL has no SOAP 1.1 bindings (which is correct, it has SOAP 1.2 bindings).
John
John

WLS 8.1 JAX-RPC stubs and SSL

I am part of an industry effort to assess WS interop. We have created a common
WSDL that will be implemented in WAS, .NET and WLS 8.1. As part of this effort,
we are also trying to use two-way SSL authentication. However, I have not found
a way to configure WLS 8.1 JAX-RPC Stubs (generated using clientgen utilities)
to present the client certificates. I have a tried a couple of approaches but
neither of them works with the stubs.
First, I tried using the SSLAdapter (as explained in the "Programming Web Services")
documentation. Unfortunately, the service that I am trying to invoke has only
http binding and trying to invoke it using the SSLAdapter throws an exception
complaining that SSL can't be used on non-https binding.
I tried to try another approach. In this, I tried to invoke https: URL for the
web service instead of using the Adapter. However, in this case, I am getting
a peer certificate not presented exception. Everything that I have checked in
adding a client private key and trusted certificates utilize SSLSocketFactory
(& SSLContext) or HttpsURLConnection objects.
At this point, I have ran out of ideas on how to add SSL to the generated client
stubs to tell the generated StubImpl or ServiceImpl implementations to use a different
SocketFactory or connection. There may be some other global class or property
to set these things up, but I am not aware of those. The server side SSL configuration
seems to working fine, as the requests with SSL configuration of "Request Client
certificate but don't enforce it' seems to work fine.
Any responses and suggestions are greatly appreciated.
Thanks
Raj

Did you check out :
http://webservice.bea.com/
There is a 2 way SSL example here:
http://webservice.bea.com/SSL2way.zip
HTHs.
http://manojc.com
"Seshadri Rajagopal" <[email protected]> wrote in message
news:3ec24d41$[email protected]..
>
I am part of an industry effort to assess WS interop. We have created acommon
WSDL that will be implemented in WAS, .NET and WLS 8.1. As part of thiseffort,
we are also trying to use two-way SSL authentication. However, I have notfound
a way to configure WLS 8.1 JAX-RPC Stubs (generated using clientgenutilities)
to present the client certificates. I have a tried a couple of approachesbut
neither of them works with the stubs.
First, I tried using the SSLAdapter (as explained in the "Programming WebServices")
documentation. Unfortunately, the service that I am trying to invoke hasonly
http binding and trying to invoke it using the SSLAdapter throws anexception
complaining that SSL can't be used on non-https binding.
I tried to try another approach. In this, I tried to invoke https: URL forthe
web service instead of using the Adapter. However, in this case, I amgetting
a peer certificate not presented exception. Everything that I have checkedin
adding a client private key and trusted certificates utilizeSSLSocketFactory
(& SSLContext) or HttpsURLConnection objects.
At this point, I have ran out of ideas on how to add SSL to the generatedclient
stubs to tell the generated StubImpl or ServiceImpl implementations to usea different
SocketFactory or connection. There may be some other global class orproperty
to set these things up, but I am not aware of those. The server side SSLconfiguration
seems to working fine, as the requests with SSL configuration of "RequestClient
certificate but don't enforce it' seems to work fine.
Any responses and suggestions are greatly appreciated.
Thanks
Raj

Java.lang.Error: JAX-RPC 1.1 method is not supported in WLS 8.1 clients.

We have some web services that run under OC4J 10.1.3.4. We have various JEE 'client' apps (JSF, servlets etc.) that use these web services. These JEE apps also run under OC4J.
We started a migration project from oc4j to weblogic 10.3.2. In phase 1 we want to move these JEE 'client' apps to weblogic. In phase 2 we want to move the web services themselves to weblogic with adjustments to the JEE 'client' apps as needed.
However we ran into an issue during this phase 1. Deploying these JEE 'client' apps to weblogic results in an error like this:
java.lang.Error: JAX-RPC 1.1 method is not supported in WLS 8.1 clients. If you are attempting to run an OC4J 10.1.3 JAX-RPC client in WLS, please see the Web Service Migration Guide for instructions.
We are including Oracle web services client libraries (http://download.oracle.com/otn/java/oc4j/1013/wsclient_extended.zip) in these JEE 'client' apps's war files because weblogic does not have them.
What part of Web Service Migration Guide is the above error message talking about? Do we have to re-generate the client side proxies for all these web services using weblogic's clientgen task in 'JAXRPC' mode? Many of these web services are doc/literal jax-rpc web services. Or does the migration guide recommend we migrate the web services first to weblogic? Any other specific information on working around this error message would be greatly appreciated.

Hi,
I had the same issue but I just managed to fix it. You must upgrade and/or regenerate you proxy. This creates new classes (possibily in a new package) that you must use in your code. I had this error because the classes directory was not clean after the rebuild and the old classes (in the old package) were still present, so the compilation was successful with the old classes. So clean your classes directories, regenerate your proxy and use the new classes in your code.
Regards,
Sylvain

Jdeveloper 11g - JAX-RPC 1.1 method is not supported in WLS 8.1 clients.

Hi,
I am using Jdeveloper 11g and migrating a web Service Proxy created using jdeveloper 10g.
I imported all the proxy classes and when I try to run web service client In Jdeveloper 11g I get the following error
"JAX-RPC 1.1 method is not supported in WLS 8.1 clients. If you are attempting to run an OC4J 10.1.3 JAX-RPC client in WLS, please see the Web Service Migration Guide for instructions."
Please advise on how to solve this?
which is the offending jar/library file in Jdeveloper 11g which is causing the above error?.
Is the above problem there in the WebLogic Server Runtime also?
Please let me know.
2) I cannot generate web server proxies also with jdev11g because the wsdl has overloaded methods omitting the name property within the input and output message, ie, they have a null name. therefore Jdeveloper 11g is using the library which
when called with an overloaded operation that contains null input/output message names, a duplicate error occurs because it sees other operations with the same name. so it is effectively not allowing to create the web service proxies.
Thanks,
Appreciate your quick response to the above

Have you checked the 'Web Service Migration Guide' mentioned in the error message?
Timo

JAX-WS SOAPHandler can not deployed in BEA WLS 10.0 - Bug?

Hi,
currently I'm trying tp deploy a simple JAX-WS webservice with JAX-WS SOAPHandler in BEA WLS 10.0.
Therefore I provide a WAR file with the webservice and handler classes.
The SOAP Handler is defined in the webservice via the @HandlerChain(file="handler.xml")
My handler.xml looks as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<javaee:handler-chains xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<javaee:handler-chain>
<javaee:handler> <javaee:handler-class>com.bmw.wss.server.handler.AuthenticationHandler</javaee:handler-class>
</javaee:handler>
</javaee:handler-chain>
</javaee:handler-chains>
This handlers.xml is in the classpath within the WAR file.
If i trying to deploy this WAR file I always get the following exception from BEA WLS 10:
weblogic.application.ModuleException: [HTTP:101216]Servlet: "WSAATestService" failed to preload on startup in Web application: "wsaa-jaxwshandlertest.war".
java.lang.NullPointerException
at weblogic.wsee.monitoring.WseeRuntimeMBeanManager.createJaxWsHandlers(WseeRuntimeMBeanManager.java:108)
at weblogic.wsee.monitoring.WseeRuntimeMBeanManager.createJaxWsPort(WseeRuntimeMBeanManager.java:80)
at weblogic.wsee.monitoring.WseeRuntimeMBeanManager.createJaxWsMBean(WseeRuntimeMBeanManager.java:57)
I seems BEA WLS 10 has some problems with the JAX-WS SOAPHandler. I've deployed the same WAR-file on a Glassfish v2 server... without any problems!
Does anyone already used the JAX-WS handler mechanism in BEA WLS 10? Any ideas?
Thx.

Hi,
thx for your answer. Now I've found the problem. The BEA WLS don't accept null return value of the SOAPHandler method getHeaders(). If I return a dummy object everything wotks fine:
public Set<QName> getHeaders() {
return new TreeSet<QName>();
However I think this behaviour of the BEA WLS 10 is some kind of strange. Why do I have to implement the method getHeaders() if I don't want to use it.
Sun's Glassfish allows a null return value like expected.

[wls-11gR1]EJB3.0 SLSB converting to JAX-WS issue

I'm deploying an EJB.ear to wls 11gR1 patch2.
When converting SLSB(stateless session bean) EJB to JAX-WS,
all the methods in the SLSB will be converted to web service operations,
no matter the method is with annotation @WebMethod or not.
h3. Is there any way to limit the conversion?
Following is my testing SLSB. There's only two method, one with *@WebMethod* annotation, one no.
But when it is published to server, both of them are in the WSDL.
===========================================================
package com.sti.es.ejb.impl;
import javax.ejb.Local;
import javax.ejb.Remote;
import javax.ejb.Stateless;
import javax.jws.WebMethod;
import javax.jws.WebService;
import com.sti.es.ejb.TestServiceEJBLocal;
import com.sti.es.ejb.TestServiceEJBRemote;
@Remote(TestServiceEJBRemote.class)
@Local(TestServiceEJBLocal.class)
@Stateless(name = "TestService", mappedName = "TestService")
@WebService(name = "TestServicePortType", serviceName = "TestService")
public class TestBean implements TestServiceEJBRemote, TestServiceEJBLocal{
public String sayHello(String name){
return "Hello, " + name + "!";
@WebMethod
public String sayBye(String name){
return "Bye, " + name + "!";
===========================================================

Hi,
By Default All the Methods which are declared as <b><font color=maroon>public </font></b>inside the WebService class (which is declared using @WebService Annotation) will be considered as a WebService Operation. And Will be Published to the Client as part of the WSDL.
So if you dont want to Publish your "sayHello(String name)" Method as a WebService Operation then ...*Dont Declare it as a "public" Method*.
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic (WebLogic Wonders Are Here)

BIweb service proxy JAX-RPC 1.1 method is not supported in WLS 8.1 clients

Hello
I have an application in oracle Application server and I'm migrating to weblogic 11g .
I have used web service proxy for BIPublisher 10.1.3.4 , careated by jdeveloper web service proxy wizard , when I want using it in weblogic , In corresponding form that uses BI Publisher web service proxy , I encounter following error :
"JAX-RPC 1.1 method is not supported in WLS 8.1 clients , if you attempting to run oc4j 10.1.3 JAX-RPC client in WLS,please see Web service Migration Guide for Instructions"
What should I do?
Regards
Mehdi

Spoke to dev and there was a bug logged, it seems to be down to Weblogic's implementation.
+This is pure WLS issue. The root cause of this problem is that Weblogic's
SAAJ implementation. No codechange on BIP server side
WLS 10 ships with two SAAJ implementations. By default the buggy 9.x
implementation is used (which lives in the package
weblogic.webservice.core.soap), but there is a new implementation, which
supports SAAJ 1.3 (which lives in the package weblogic.xml.saaj). I also
checked in a debugging jsp page, which could help looking at the DEBUG
logging to see which SAAJ implementation is used.
JSP testpage xmlponline/wwwroot/wsclient/soapclient-wls-8270711.jsp
To use this new version, you have to make sure setting the
-Djavax.xml.soap.MessageFactory=weblogic.xml.saaj.MessageFactoryImpl
in startWebLogic script. +
Please give the solution a try and let me know if it works.
Regards
tim

Question about JAX-WS together with EJB 3.0 on WLS 10.3

Hi all,
I am developing a application that it is running on WebLogic 10.3. The application expose EJB 3.0 methods as web services by @WebService & @WebMethod annotation. And my question is,
1. Is there any way to specify the context path/root for those exposed EJB? Currently the contextpath is same as the EJB's name
2. And is there a method to disable the "scanning" of JAX-WS annotation on startup/deployment? The reason behind is that, some of the EJB jar files are coming from other team. I need to deploy it as EJB but not as a web service.
Thanks
Regards,
Rock

Hi guys,
Here is what Eduardo is talking about:
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=407022.1
(Doc ID: Note:407022.1)
Rgds,
Fábio.

How to call a jax-ws client from a jsp wls 10.3.6

instead of specifying this in the jsp
<%
client.HelloserviceService test = new client.HelloserviceService();
client.Helloservice port = test.getHelloservicePort();
%>
is there any other way , if there sample code appreciated

Using the @WebServiceRef annotation to associate the Web service client with the configuration defined for the specified Web service reference. The Web service reference configuration is defined in the weblogic.xml for Web containers and weblogic-ejb-jar.xml for EJB containers. For more information about the @WebServiceRef annotation, see Defining a Web Service Reference Using the @WebServiceRef Annotation.
http://docs.oracle.com/cd/E23943_01/web.1111/e13758/client.htm#CIHHJEHH
Regards,
Sunil P

Problems deploying a JAX-WS webservice on Weblogic 10.3

Hello Experts,
I have deveoped a SOAP1.2 over HTTP web service using JAX-WS @WebServiceProvider annotation and am trying to deploy it on Weblogic 10.3
The jwsc task is successful. However, I get the following exception when deploying it on weblogic 10.3:
===========================================================================================
####<Feb 16, 2010 12:35:18 PM PST> <Info> <Deployer> <....> <WLS_ManagedServer_1> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1266352518172> <BEA-149060> <Module OIMTrustedRecon of application OIMTrustedReconEar successfully transitioned from STATE_PREPARED to STATE_NEW on server WLS_ManagedServer_1.>
####<Feb 16, 2010 12:35:18 PM PST> <Error> <Deployer> <psharma-lap> <WLS_ManagedServer_1> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1266352518656> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1266352473562' for task '10'. Error is: 'weblogic.application.ModuleException: [HTTP:101216]Servlet: "weblogic.wsee.async.AsyncResponseBean" failed to preload on startup in Web application: "OIMTrustedRecon".
com.sun.xml.ws.model.RuntimeModelerException: The web service defined by the class weblogic.wsee.async.AsyncResponseBean does not contain any valid WebMethods.
     at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:262)
     at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:322)
     at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:188)
     at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467)
     at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:510)
     at weblogic.wsee.jaxws.JAXWSDeployedServlet.getEndpoint(JAXWSDeployedServlet.java:182)
     at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:164)
     at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:51)
     at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:53)
     at javax.servlet.GenericServlet.init(GenericServlet.java:241)
     at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
     at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
     at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1893)
     at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1870)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1790)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
     at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
     at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
     at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
===========================================================================================
Could you please let know if I have done something wrong or am missing something.
Please let me know if you need more information to help me.
Many Thanks,
Pulkit Sharma

Hi Pulkit,
If your WebService is not very complex ...then can you please paste it here ...Or can u describe something about your WebService. Like Which kind of methods are there? And Are u using any Asynchronous feature in it?
If you are not using any Asynchronous feature in your webservice then u can try disabling it by adding "-Dweblogic.wsee.skip.async.response=true"
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com/webservices/ (WebLogic Wonders Are Here)

WLS 10.3.5 Managed server is not starting in Windows 7

Hello there,
I had installed SOA suite 11 and weblogic server 10.3.5. setDomainEnv is setting environment variables like below.
Path
C:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\native;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1\bin;C:\Oracle\MIDDLE~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\JDK160~1\bin;C:\Oracle\instantclient_11_2;C:\Oracle\oraclexe\app\oracle\product\10.2.0\server\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\CREDANT\Shield v7.1\;C:\Program Files (x86)\SSH Communications Security\SSH Tectia\SSH Tectia AUX;C:\Program Files (x86)\SSH Communications Security\SSH Tectia\SSH Tectia AUX\Support binaries;C:\Program Files (x86)\SSH Communications Security\SSH Tectia\SSH Tectia Broker;C:\Program Files (x86)\SSH Communications Security\SSH Tectia\SSH Tectia Client;C:\Oracle\Middleware\jdeveloper\ant\bin;C:\Oracle\Middleware\jdk160_24\bin;C:\Oracle\product\10.2.0.1\BIN;C:\Program Files\Java\jre7\bin;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8
Classpath
C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.5.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\Middleware\wlserver_10.3\sip\server\lib\weblogic_sip.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar;.;C:\Oracle\Middleware\jdk160_24\lib;C:\Oracle\Middleware\jdeveloper\ant\lib;
Now i have given this command in user_domains/../bin folder
startManagedWebLogic.cmd soa_managed_server01 http://suchalam-ws:7002
But the managed server is shutting down. below is the trace from windows7 command prompt.
this server is being started in managed server independence mode in the absence of
the admin server.>
<Aug 30, 2012 1:13:28 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STARTING>
<Aug 30, 2012 1:13:28 AM IST> <Info> <WorkManager> <BEA-002900> <Initializing se
lf-tuning thread pool>
<Aug 30, 2012 1:13:28 AM IST> <Notice> <LoggingService> <BEA-320400> <The log fi
le C:\Oracle\Middleware\user_projects\domains\sudheers_domain\servers\soa_manage
d_server01\logs\soa_managed_server01.log will be rotated. Reopen the log file if
tailing has stopped. This can happen on some platforms like Windows.>
<Aug 30, 2012 1:13:28 AM IST> <Notice> <LoggingService> <BEA-320401> <The log fi
le has been rotated to C:\Oracle\Middleware\user_projects\domains\sudheers_domai
n\servers\soa_managed_server01\logs\soa_managed_server01.log00011. Log messages
will continue to be logged in C:\Oracle\Middleware\user_projects\domains\sudheer
s_domain\servers\soa_managed_server01\logs\soa_managed_server01.log.>
<Aug 30, 2012 1:13:28 AM IST> <Notice> <Log Management> <BEA-170019> <The server
log file C:\Oracle\Middleware\user_projects\domains\sudheers_domain\servers\soa
managedserver01\logs\soa_managed_server01.log is opened. All server side log e
vents will be written to this file.>
Aug 30, 2012 1:13:30 AM oracle.security.jps.internal.common.util.XmlSchemaValida
tionUtil$StrictErrorHandler warning
WARNING: Failed to validate the xml content. SchemaLocation: schemaLocation valu
e = 'http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd' must have e
ven number of URI's. Location: line 2 column 272.
<Aug 30, 2012 1:13:39 AM IST> <Notice> <Security> <BEA-090082> <Security initial
izing using security realm myrealm.>
<Aug 30, 2012 1:13:51 AM IST> <Warning> <JTA> <BEA-110503> <The migrator(the Adm
inServer for manual JTA migration policy, or the Singleton Master for automatic
JTA migration policy) is not available. Will skip JTA TRS failback because isStr
ictOwnershipCheck is [false]. This may lead to potencial TLOG corruption if TRS
of soa_managed_server01 has been migrated to backup server and the backup server
is accessing the TLOG of soa_managed_server01. More safety can be achieved by s
etting isStrictOwnershipCheck to [true].>
<Aug 30, 2012 1:13:52 AM IST> <Warning> <Management> <BEA-141277> <The JMX MBean
PlatformMBeanServerUsed attribute is true, but the Platform MBeanServer was cre
ated without the hooks for the WLS security infrastructure. The Platform MBeanSe
rver will NOT be used and Platform MBeans will NOT be available via the WLS Runt
ime or Domain Runtime MBeanServers. This can occur if you have defined Platform
MBeanServer system properties or JVM options (-Dcom.sun.management.jmxremote or
JRockit -XManagement).
To allow the Platform MBeanServer to be used, you must either remove the system
properties/JVM options or start WLS with the following system property:
-Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBean
ServerBuilder
If you want to eliminate this log error and do not need Platform MBeans to be a
vailable via WLS, then set the PlatformMBeanUsed attribute in the JMXMBean to fa
lse.>
<Aug 30, 2012 1:14:01 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STANDBY>
<Aug 30, 2012 1:14:01 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STARTING>
<Aug 30, 2012 1:14:04 AM IST> <Error> <Deployer> <BEA-149205> <Failed to initial
ize the application 'wsm-pm' due to error weblogic.management.DeploymentExceptio
n: [J2EE:160149]Error while processing library references. Unresolved applicatio
n library references, defined in weblogic-application.xml: [Extension-Name: orac
le.wsm.seedpolicies, Specification-Version: 11.1.1, Implementation-Version: 11.1
.1, exact-match: false]..
weblogic.management.DeploymentException: [J2EE:160149]Error while processing lib
rary references. Unresolved application library references, defined in weblogic-
application.xml: [Extension-Name: oracle.wsm.seedpolicies, Specification-Version
: 11.1.1, Implementation-Version: 11.1.1, exact-match: false].
at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(
CheckLibraryReferenceFlow.java:26)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.ja
va:613)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.j
ava:184)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.jav
a:58)
Truncated. see log file for complete stacktrace
>
<Aug 30, 2012 1:14:04 AM IST> <Notice> <SipServer.Resource> <BEA-332401> <Initia
lizing SipServer Resource with configuration com.bea.wcp.sip.management.descript
or.beans.SipServerBeanImpl>
<Aug 30, 2012 1:14:08 AM IST> <Notice> <WLSS.Engine> <BEA-330071> <WebLogic Sip
Server "soa_managed_server01" patch version: WebLogic Server 10.3.5.0 Fri Apr 1
20:20:06 PDT 2011 1398638
Javax Server Pages Client Capable 1.2 Tue Jul 13 02:43:41 EDT 2010
Expression Language 2.1 for JSP 1.0 Sun Jul 18 23:17:34 PDT 2010
Javax Enterprise Servlets Client Capable 1.0 Thu Aug 2 12:41:25 EDT 2007
Eclipse Java Development Tools 3.5.2 Thu Sep 2 09:47:11 EDT 2010
WebLogic java compiler utils package Client Capable 1.2 Thu Feb 11 03:38:50 EST
2010
WebLogic WebApp Container Public API Client Capable 1.4 Fri Oct 1 20:01:15 PDT 2
010
Oracle WebLogic Server Module Dependencies 10.3 Thu Mar 3 14:37:52 PST 2011
Oracle WebLogic Server on JRockit Virtual Edition Module Dependencies 10.3 Thu F
eb 3 16:30:47 EST 2011
ANTLR Java based compiler generator Client 2.7 Mon Jun 11 12:19:48 EDT 2007
WebLogic Descriptors for J2EE 1.5 Wed May 5 14:32:58 EDT 2010
WebLogic Descriptors for J2EE 1.5 Binding Bundle
WebLogic Specific Descriptors 1.3 Tue Sep 14 18:48:42 PDT 2010
WebLogic Specific Descriptors 1.3 Binding Bundle
WebLogic Datasource 1.9 Tue Oct 26 13:50:26 PDT 2010
WebLogic Datasource 1.9 Binding Bundle
WebLogic Beangen Client Capable 1.7 Wed Feb 24 16:02:48 PST 2010
WebLogic Beangen 1.7 Binding Bundle
WLDF Accessor Client Capable 1.5 Fri Sep 3 17:10:52 EDT 2010
WLDF Accessor 1.5 Binding Bundle
WebLogic Management Core Interfaces Client Capable 2.8 Thu Mar 3 12:10:10 EST 20
11
WebLogic Management Core Interfaces 2.8 Binding Bundle
WebLogic EJBGen Client Capable 1.1 Thu Jun 3 13:17:07 EDT 2010
Apache Byte Code Engineering Library (BCEL) extracted from 5.2.zip from http://j
akarta.apache.org/site/downloads/downloads_bcel.cgi with packages renamed from o
rg.apache.bcel to com.bea.core.repackaged.apache.bcel Client 5.2 Tue May 15 09:5
2:37 EDT 2007
Apache commons collections package 3.2 Tue Mar 20 15:48:25 MDT 2007
Apache commons lang package 2.1 Tue Mar 20 15:48:30 MDT 2007
Apache commons pool package 1.3 Tue Mar 20 15:48:36 MDT 2007
Apache commons io 1.4 package 1.0 Wed Jun 2 17:36:36 EDT 2010
Apache commons fileupload 1.2.1 package 1.0 Wed Jun 2 17:36:36 EDT 2010
Apache DOM implementation 1.0 Tue Mar 20 15:36:46 MDT 2007
Apache Logging Support 1.0 Tue Mar 20 15:36:50 MDT 2007
Apache OpenJPA classes 1.2 Thu Jul 22 05:16:07 EDT 2010
XMLBeans - Apache SVN rev 962560 2.1 Thu Jul 15 09:52:54 EDT 2010
BEA Logging Runtime Support Client Capable 1.8 Mon Jun 7 12:07:02 PDT 2010
BEA Common Security Open SAML 1.0 Fri May 14 20:18:10 PDT 2010
BEA OpenSAML 2.0 1.0 Wed Mar 24 13:18:27 PDT 2010
bea-harvester-api2.0 Client Capable 2.3 Mon Feb 15 14:41:06 EST 2010
bea-harvester-jmx2.0 Client Capable 2.3 Wed Feb 3 11:54:03 PST 2010
bea-harvester-utils Client Capable 1.4 Mon Feb 15 14:41:06 EST 2010
bea-mbean-typing-util 1.4 Wed Feb 24 19:15:33 EST 2010
Javolution 3.7.19 3.7 Tue Aug 28 17:32:21 PDT 2007
Joda-time 1.2.1 1.2 Tue Aug 28 17:32:27 PDT 2007
BEA STAX Build Time Support 1.5 Tue May 4 07:32:25 PDT 2010
BEA STAX Runtime Time Support Client Capable 1.7 Wed Aug 4 19:40:47 EDT 2010
BEA Generic Annotations Client Capable 1.3 Sat Jul 11 00:30:54 EDT 2009
BEA Kodo 1.4 Mon Feb 7 16:22:04 PST 2011
BEA Kodo Integration Client Capable 1.6 Sun Nov 22 16:29:06 PST 2009
BEA Kodo Integration 1.6 Binding Bundle
BEA Kodo Integration Tools 1.4 Thu Feb 3 16:07:53 EST 2011
XML Beans Marshalling (package renamed com.bea) SVN 962560 2.3 Thu Mar 3 12:10:1
0 EST 2011
WebLogic Utils Client Capable 1.9 Thu Mar 3 12:10:10 EST 2011
Aspect 5.3 Fri Jun 4 14:55:18 PDT 2010
BEA Apache Commons Logging Repackaged 1.2 Mon Jun 11 12:47:12 EDT 2007
Spring Framework 1.1 Thu Dec 3 12:21:08 EST 2009
Pitchfork 1.3 Thu Jun 3 13:17:07 EDT 2010
${description} 1.2 Fri Jun 25 16:25:26 EDT 2010
CSS i18n 1.0 Fri Oct 8 10:32:52 EDT 2010
CSS xacml 1.0 Fri Oct 8 10:32:52 EDT 2010
SAML2 Utils 1.0 Fri Oct 8 10:32:52 EDT 2010
BEA Common Security Engine Implementation 1.0 Fri Oct 8 10:32:52 EDT 2010
BEA Common Security Engine Interfaces 1.0 Fri Oct 8 10:32:52 EDT 2010
BEA Common Security API 1.0 Fri Oct 8 10:32:52 EDT 2010
BEA Common Security Implementation 1.0 Fri Oct 8 10:32:52 EDT 2010
BEA Common Security JDK Utilities 1.0 Fri Oct 8 10:32:52 EDT 2010
Security Utilities 1.0 Fri Oct 8 10:32:52 EDT 2010
Common Security SAML 2.0 1.0 Fri Oct 8 10:32:52 EDT 2010
Common Security SAML 2.0 Management JavaBeans 1.0 Fri Oct 8 10:32:52 EDT 2010
Security Provider Utilities 1.0 Fri Oct 8 10:32:52 EDT 2010
SAML Utils 1.0 Fri Oct 8 10:32:52 EDT 2010
XACML Utils 1.0 Fri Oct 8 10:32:52 EDT 2010
Security Provider Environment 1.0 Fri Oct 8 10:32:52 EDT 2010
RSA certj 3.1 Wed May 5 15:11:55 PDT 2010
Netscape LDAP JDK 1.2 Mon Jun 7 15:56:47 EDT 2010
Commons Networking Utilty classes 1.0 Wed Feb 6 15:01:03 PST 2008
WebLogic SAAJ 1.6 Wed Jun 16 22:02:31 EDT 2010
WebLogic STAX Client Capable 1.9 Thu Feb 10 18:00:52 PST 2011
jaxb-impl.jar taken from Glassfish JAXB 2.1.9 1.0 Fri Aug 20 14:37:07 EDT 2010
jaxb-impl.jar taken from Glassfish JAXB 2.1.12 1.0 Thu May 6 16:10:04 PDT 2010
resolver.jar taken from Glassfish JAXWS 2.1.5 1.0 Thu Dec 3 11:46:24 EST 2009
Fastinfoset.jar taken from Glassfish JAXWS 2.1.5 1.0 Thu Dec 3 11:46:27 EST 2009
jaxws-rt.jar taken from Glassfish JAXWS 2.1.5 1.2 Mon Feb 28 17:53:01 PST 2011
Java.net implementation of MimePull.jar taken from Glassfish JAXWS 2.1.5 1.0 Thu
Dec 3 11:46:33 EST 2009
Codehaus STaX Interfaces 3.0.1 1.0 Mon Mar 8 20:49:50 PST 2010
Woodstox STaX Parser 4.0.5 1.0 Thu Dec 3 11:35:43 EST 2009
jaxws-tools.jar taken from Glassfish JAXWS 2.1.5 1.1 Fri Sep 24 17:55:05 PDT 201
0
Java.net Stax Extensions 1.0 Tue Jun 3 07:12:06 PDT 2008
Java.net xml stream buffer 1.0 Tue Mar 17 05:24:12 PDT 2009
Jakarta ORO 1.0 Wed Feb 6 15:01:03 PST 2008
Javax Enterprise Activation 1.1 Tue Apr 8 09:31:17 PDT 2008
Javax Annotation 1.0 Fri Dec 25 09:02:47 PST 2009
Javax Interceptor 1.0 Tue Mar 20 15:37:16 MDT 2007
Javax Enterprise Beans 3.0 Mon Jun 11 12:21:01 EDT 2007
Java Data Objects 2.0 Mon Jun 11 12:20:56 EDT 2007
Java Enterprise Deployment APIs 1.2 Tue Mar 20 15:37:28 MDT 2007
Java Enterprise Messaging 1.1 Mon Jun 11 12:21:11 EDT 2007
Java Web Services 2.0 Tue Mar 20 15:37:37 MDT 2007
Javax Enterprise Mail 1.1 Mon Jul 6 10:41:09 MDT 2009
Java Enterprise Management APIs 1.0 Tue Mar 20 15:37:49 MDT 2007
Java Persistence Client Capable 1.0 Tue Oct 7 12:18:34 PDT 2008
Java Connector 1.5 Mon Jun 11 12:22:07 EDT 2007
Java Authorization Contract for Containers 1.0 Wed Feb 6 15:01:03 PST 2008
Javax Transaction APIs Client Capable 1.0 Thu Aug 2 12:42:14 EDT 2007
JAXB 2.1 Mon Jun 11 12:22:53 EDT 2007
Java XML Registry 1.0 Wed Feb 6 15:01:03 PST 2008
Java XML Soap Extensions 1.3 Mon Jun 11 12:22:59 EDT 2007
Java Stream XML Extensions 1.1 Mon Jun 11 12:23:05 EDT 2007
JAX-WS APIs 2.1 Mon Jun 11 12:23:16 EDT 2007
Java API for XML-based RPC 1.2 Mon Jun 11 12:23:10 EDT 2007
Monfox Dynamic SNMP Agent 1.1 Fri Mar 19 05:46:27 MDT 2010
Serp bytecode manipulation framework 1.14.3 Fri Jun 11 12:06:08 PDT 2010
WebLogic Apache Classes Client Capable 1.2 Thu Feb 18 22:06:19 PST 2010
WebLogic BeanInfo Caching and Discovery Client Capable 2.4 Sat Oct 25 20:46:29 P
DT 2008
WebLogic Descriptor Client Capable 1.9 Tue Jul 20 16:03:09 EDT 2010
Repackaged ASM-3.2 1.0 Fri Jul 31 19:30:27 MDT 2009
Repackaged asm-commons-3.2 1.0 Fri Jul 31 19:30:27 MDT 2009
Repackaged asm-tree-3.2 1.0 Fri Jul 31 19:30:27 MDT 2009
Repackaged asm-util-3.2 1.0 Fri Jul 31 19:30:27 MDT 2009
Oracle JFR 1.0 Thu Feb 18 19:06:33 PST 2010
WebLogic Diagnostics Core Interfaces Client Capable 2.5 Thu Jun 3 05:20:41 PDT 2
010
WebLogic Diagnostics Logging Client Capable 1.2 Fri Dec 12 11:37:59 MST 2008
WebLogic Diagnostics Query Module Client Capable 1.2 Tue Oct 27 02:48:36 PDT 200
9
WebLogic Diagnostics Instrumentor Tool 1.7 Tue May 18 03:51:46 PDT 2010
WebLogic Diagnostics Instrumentor Config Tool 1.7 Tue Jun 29 16:41:19 EDT 2010
WebLogic Diagnostics JRockit Flight Recorder Interfaces Client Capable 1.1 Fri O
ct 29 16:32:05 EDT 2010
Diagnostics Notifications Module Client Capable 1.4 Sun Nov 22 16:03:32 PST 2009
BEA Logging Runtime Support Client Capable 1.5 Thu Apr 29 20:43:42 EDT 2010
WebLogic i18n Runtime Support Client Capable 1.8 Fri Sep 10 08:12:34 EDT 2010
WebLogic i18n Build Support Client Capable 1.5 Fri Feb 19 15:03:15 EST 2010
WebLogic I18N tools Client Capable 1.3 Sun Nov 22 16:03:32 PST 2009
WebLogic Management JMX Interfaces 1.4 Thu Aug 12 11:16:22 PDT 2010
WebLogic Security Provider Generation Tool 1.5 Wed Oct 14 16:39:28 MDT 2009
WebLogic Security Provider Generation Tool Client Capable 1.5 Wed Oct 14 16:39:2
8 MDT 2009
WebLogic Messaging Kernel Client Capable 1.8 Mon Aug 23 21:42:11 EDT 2010
WebLogic Resource Pool Client Capable 1.7 Mon Sep 27 12:00:08 EDT 2010
WebLogic Socket Muxer API Client Capable 1.2 Thu Apr 1 21:16:27 EDT 2010
WebLogic RMI Client Capable 1.10 Tue Mar 22 16:56:32 PDT 2011
Common Security WebLogic Server Integration Support 1.0 Fri Oct 8 10:32:52 EDT
2010
Server Lifecycle Interfaces Client Capable 1.4 Fri Feb 19 15:03:15 EST 2010
WebLogic Store Client Capable 1.7 Fri Dec 17 16:52:31 EST 2010
WebLogic STORE GXA Client Capable 1.6 Mon Aug 23 21:16:10 EDT 2010
WebLogic Store Admin Tool Client Capable 1.2 Thu Jan 21 10:24:18 PST 2010
WebLogic JDBC Store Client Capable 1.3 Mon May 17 10:46:33 PDT 2010
WebLogic JTA implementation Client Capable 2.7 Fri Sep 17 12:19:45 PDT 2010
WebLogic Utils 1.9 Thu Mar 3 12:10:10 EST 2011
Agent Utililities 1.1 Tue Feb 16 00:16:03 EST 2010
WebLogic Utility Classloader implementations Client Capable 1.9 Wed Mar 2 14:10:
04 PST 2011
WebLogic Utils for working with Expressions Client Capable 1.4 Tue Sep 29 14:45:
53 EDT 2009
WebLogic Utils for Dynamically Generated Class Wrappers Client Capable 1.4 Fri F
eb 13 14:44:23 MST 2009
WebLogic Timers Client Capable 1.7 Thu Feb 18 13:08:44 EST 2010
WebLogic Work Manager Client Capable 1.10 Thu Feb 17 10:25:54 PST 2011
WebLogic Workarea Client Capable 1.7 Wed Feb 24 17:18:56 PST 2010
WebLogic XML XPath Implementation Client Capable 1.4 Mon Feb 22 15:07:14 PST 201
0
Weblogic Tuxedo Connector Core Client Capable 1.5 Sat Jul 3 19:05:38 EDT 2010
WebLogic Security 1.0 Fri Oct 8 10:32:52 EDT 2010
Weblogic Server Java Authentication Helper Classes Client Capable 1.1 Mon Jul 5
20:42:35 EDT 2010
Weblogic Server Message Digest Utilities Client Capable 1.0 Thu Aug 2 12:51:30 E
DT 2007
Weblogic Server Authenticated Subject Client Capable 1.1 Thu Oct 28 05:46:37 PDT
2010
Weblogic Server Authenticated Subject Client Capable 1.5 Thu Sep 9 10:23:21 MDT
2010
PrintingSecurityManager - PSM 1.1 Tue Feb 16 05:30:08 PST 2010
WebLogic security ssl classes 1.0 Tue Jun 15 17:39:53 EDT 2010
WebLogic Nodemanager Plugin Client Capable 1.3 Tue Nov 18 18:23:10 EST 2008
nodemanager module for managed processes 1.0 Thu Apr 8 15:14:38 PDT 2010
WebLogic JMS Pool Client Capable 1.8 Thu Mar 3 14:11:40 PST 2011
Contains compiled schema type from WLS 9.0 for WLP compatibility 1.3 Wed Feb 24
19:15:33 EST 2010
WebLogic Http Pub/Sub Module Client Capable 1.6 Mon Jul 12 02:31:07 EDT 2010
Class Redefinition Project 1.5 Mon May 10 19:48:21 EDT 2010
Class Redefinition Project Client Capable 1.5 Mon Apr 5 17:00:52 PDT 2010
Class Redefinition Project 1.5 Binding Bundle
Commonj SDO 1.0 Wed Sep 24 19:11:23 PDT 2008
WebLogic Coherence Descriptor 1.1 Wed May 5 15:17:47 EDT 2010
WebLogic Coherence Descriptor 1.1 Binding Bundle
This module contains all message catalogs 1.1 Fri Dec 17 08:04:35 PST 2010
WebLogic WebService Public API's 1.1 Tue Sep 21 22:15:05 EDT 2010
WebLogic EclipseLink Integration 1.0 Thu Feb 25 14:56:43 PST 2010
WebLogic SCA Client 1.0 Thu Feb 25 00:27:10 EST 2010
WebLogic RAC Module UCP Client Capable 1.0 Mon Sep 13 09:03:00 PDT 2010
BEA Patches of apache ant Client Capable 1.2 Wed Jan 13 08:48:17 PST 2010
Oracle WebLogic Server 10.3.4.0 at 710154 built on: 2010/09/30
Oracle WebLogic Server 10.3.4.0 at 710154 built on: 2010/09/30
Oracle WebLogic Server Datatier 10.3.4.0 at 710154 built on: 2010/09/30
Oracle WebLogic Server 10.3.4.0 at 710154 built on: 2010/09/30
WebLogic SIPServer Extension API 10.3.4.0 at 709997 built on 2010/09/27
WebLogic SIPServer Extension API 10.3.4 at 709997 built on 2010/09/27
WebLogic SIPServer CallState 10.3.4 at 709997 built on 2010/09/27
Oracle WebLogic Communications SCTP 10.3.1 at 688160 built on 2009/03/11
WebLogic WebService Databinding Plugins 1.3 Wed Dec 1 17:41:28 EST 2010
WebLogic WebService Databinding 1.3 Tue Oct 18 16:38:56 EDT 2011
WebLogic SIP Activator 10.3.4 at 710163 built on 2010/09/30
>
<Aug 30, 2012 1:14:08 AM IST> <Error> <WLSS.Engine> <BEA-330075> <There are no s
ip nor diameter channels targeted to server "soa_managed_server01">
<Aug 30, 2012 1:14:08 AM IST> <Error> <WLSS.Engine> <BEA-330049> <Failed to star
t the sip service, shutting down>
C:\Oracle\Middleware\user_projects\domains\sudheers_domain\bin
Thanks in advance,
Sudheer

Hi Vlad, Kalyan
Thanks for the response. Actually i am not planning to configure weblogic SIP... as it may need little insight. I just created domain including everything.
Now i have created a new domain with basic functionality with default configuration. Now everything is working fine. I can see the Admin console as well.
But i have stuck up in running the EM console. Below is the CMD prompt trace.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\suchalam>cd C:\Oracle\Middleware\user_projects\domains\sudheer_domain\b
in
C:\Oracle\Middleware\user_projects\domains\sudheer_domain\bin>startManagedWebLog
ic.cmd soa_server1
** Setting up SOA specific environment for win...
PATH=C:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\native;C:\Oracle\MIDDLE~1
\patch_jdev1111\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\nat
ive\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\modules\O
RGAPA~1.1\bin;C:\Oracle\MIDDLE~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\JDK160~1\bi
n;C:\Oracle\instantclient_11_2;C:\Oracle\oraclexe\app\oracle\product\10.2.0\serv
er\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System
32\WindowsPowerShell\v1.0\;C:\Program Files\CREDANT\Shield v7.1\;C:\Program File
s (x86)\SSH Communications Security\SSH Tectia\SSH Tectia AUX;C:\Program Files (
x86)\SSH Communications Security\SSH Tectia\SSH Tectia AUX\Support binaries;C:\P
rogram Files (x86)\SSH Communications Security\SSH Tectia\SSH Tectia Broker;C:\P
rogram Files (x86)\SSH Communications Security\SSH Tectia\SSH Tectia Client;C:\O
racle\Middleware\jdeveloper\ant\bin;C:\Oracle\product\10.2.0.1\BIN;C:\Oracle\Mid
dleware\jdk160_24\bin;;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920
_8;C:\Oracle\Middleware\Oracle_SOA1\soa\thirdparty\edifecs\XEngine\bin
USER_MEM_ARGS=-Xms512m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=512m
JAVA_OPTIONS=-Dweblogic.security.SSL.trustedCAKeyStore="C:\Oracle\Middleware\wls
erver_10.3\server\lib\cacerts" -Xverify:none
** End SOA Specific environment setup for win.
** SOA specific environment is already set. Skipping ...
JAVA Memory arguments: -Xms512m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=512m
WLS Start Mode=Development
CLASSPATH=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jdbc_11.1.1\ojdbc6dms.jar;C
:\Oracle\Middleware\Oracle_SOA1\soa\modules\user-patch.jar;C:\Oracle\Middleware\
Oracle_SOA1\soa\modules\soa-startup.jar;;C:\Oracle\MIDDLE~1\patch_wls1035\profil
es\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_jd
ev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDD
LE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp
.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\mo
dules\features\weblogic.server.modules_10.3.5.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.
3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.j
ar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\MIDDLE~
1\ORACLE~1\soa\modules\commons-cli-1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\soa\modul
es\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\Oracle\Middleware\Oracle_SOA1\so
a\modules\oracle.soa.common.adapters_11.1.1\oracle.soa.common.adapters.jar;C:\Or
acle\Middleware\Oracle_SOA1\communications\modules\usermessaging-config_11.1.1.j
ar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.xdk_11.1.0\xsu12.jar;C:\Oracle\MID
DLE~1\modules\features\weblogic.server.modules.xquery_10.3.1.0.jar;C:\Oracle\Mid
dleware\Oracle_SOA1\soa\modules\db2jcc4.jar;C:\Oracle\MIDDLE~1\USER_P~1\domains\
SUDHEE~2\config\soa-infra;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\fabric-ur
l-handler_11.1.1.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\quartz-all-1.6
.5.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\oracle.soa.fabric_11.1.1\ora
cle.soa.fabric.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\oracle.soa.fabri
c_11.1.1\fabric-runtime-ext-wls.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules
\oracle.soa.adapter_11.1.1\oracle.soa.adapter.jar;C:\Oracle\Middleware\Oracle_SO
A1\soa\modules\oracle.soa.b2b_11.1.1\oracle.soa.b2b.jar;C:\Oracle\MIDDLE~1\ORACL
E~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby
\lib\derbyclient.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar;C:\Oracle
\Middleware\jdeveloper\ant\lib;C:\Oracle\Middleware\jdk160_24\lib;
PATH=C:\Oracle\MIDDLE~1\patch_wls1035\profiles\default\native;C:\Oracle\MIDDLE~1
\patch_jdev1111\profiles\default\native;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\nat
ive\win\32;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;C:\Oracle\MIDDLE~1\modules\O
RGAPA~1.1\bin;C:\Oracle\MIDDLE~1\JDK160~1\jre\bin;C:\Oracle\MIDDLE~1\JDK160~1\bi
n;C:\Oracle\instantclient_11_2;C:\Oracle\oraclexe\app\oracle\product\10.2.0\serv
er\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System
32\WindowsPowerShell\v1.0\;C:\Program Files\CREDANT\Shield v7.1\;C:\Program File
s (x86)\SSH Communications Security\SSH Tectia\SSH Tectia AUX;C:\Program Files (
x86)\SSH Communications Security\SSH Tectia\SSH Tectia AUX\Support binaries;C:\P
rogram Files (x86)\SSH Communications Security\SSH Tectia\SSH Tectia Broker;C:\P
rogram Files (x86)\SSH Communications Security\SSH Tectia\SSH Tectia Client;C:\O
racle\Middleware\jdeveloper\ant\bin;C:\Oracle\product\10.2.0.1\BIN;C:\Oracle\Mid
dleware\jdk160_24\bin;;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920
_8;C:\Oracle\Middleware\Oracle_SOA1\soa\thirdparty\edifecs\XEngine\bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b50)
Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode)
Starting WLS with line:
C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xms512m -Xmx512m -XX:PermSize=12
8m -XX:MaxPermSize=512m -Dweblogic.Name=soa_server1 -Djava.security.policy=C:\Or
acle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.security.SSL.trus
tedCAKeyStore="C:\Oracle\Middleware\wlserver_10.3\server\lib\cacerts" -Xverify:
none -da -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MID
DLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -D
common.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.ap
ache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.ho
me=C:\Oracle\MIDDLE~1\USER_P~1\domains\SUDHEE~2 -Djrockit.optfile=C:\Oracle\MIDD
LE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.conf
ig.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SUDHEE~2\config\FMWCON~1\servers\soa_
server1 -Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SUDHEE~2\
config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\USER_P~1\domains\
SUDHEE~2\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~1\USER_P
~1\domains\SUDHEE~2\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=
C:\Oracle\MIDDLE~1\USER_P~1\domains\SUDHEE~2\config\fmwconfig\jps-config.xml -Do
racle.deployed.app.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SUDHEE~2\servers\soa_
server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirec
tory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~
1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle
.mds.net.protocol"|"oracle.fabric.common.classloaderurl.handler"|"oracle.fabric.
common.uddiurl.handler"|"oracle.bpm.io.fs.protocol -Dweblogic.jdbc.remoteEnable
d=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org
.apache.xmlbeans... -Dsoa.archives.dir=C:\Oracle\Middleware\Oracle_SOA1\soa -Dso
a.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=C:\Oracle\MID
DLE~1\USER_P~1\domains\SUDHEE~2 -Dtangosol.coherence.clusteraddress=227.7.7.9 -D
tangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soa
p.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transact
ion.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.n
et.ssl.trustStore=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.or
acle.home=C:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.orac
le.home=C:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=C:\Oracle\Middleware\
Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=ht
tp://SUCHALAM-WS:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.lo
gErrorsToConsole=false -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1035\prof
iles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_jdev1111\profile
s\default\sysext_manifest_classpath weblogic.Server
<Sep 2, 2012 6:51:28 PM IST> <Info> <Security> <BEA-090905> <Disabling CryptoJ J
CE Provider self-integrity check for better startup performance. To enable this
check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Sep 2, 2012 6:51:29 PM IST> <Info> <Security> <BEA-090906> <Changing the defaul
t Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable
this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Sep 2, 2012 6:51:30 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebL
ogic Server with Java HotSpot(TM) Client VM Version 19.1-b02 from Sun Microsyste
ms Inc.>
<Sep 2, 2012 6:51:32 PM IST> <Info> <Security> <BEA-090065> <Getting boot identi
ty from user.>
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
<Sep 2, 2012 6:51:42 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic
Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Sep 2, 2012 6:51:45 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to STARTING>
<Sep 2, 2012 6:51:45 PM IST> <Info> <WorkManager> <BEA-002900> <Initializing sel
f-tuning thread pool>
<Sep 2, 2012 6:51:46 PM IST> <Notice> <Log Management> <BEA-170019> <The server
log file C:\Oracle\Middleware\user_projects\domains\sudheer_domain\servers\soa_s
erver1\logs\soa_server1.log is opened. All server side log events will be writte
n to this file.>
<Sep 2, 2012 6:51:59 PM IST> <Notice> <Security> <BEA-090082> <Security initiali
zing using security realm myrealm.>
<Sep 2, 2012 6:53:56 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to STANDBY>
<Sep 2, 2012 6:53:56 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to STARTING>
<Sep 2, 2012 7:19:07 PM IST> <Warning> <J2EE> <BEA-160140> <Unresolved optional
package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.applcore.m
odel, Specification-Version: 0.1, Implementation-Version: 11.1.1.0.0, referenced
from: C:\Oracle\Middleware\user_projects\domains\sudheer_domain\servers\soa_ser
ver1\tmp\_WL_user\usermessagingserver\y73z7z]. Make sure the referenced optional
package has been deployed as a library.>
<Sep 2, 2012 7:19:12 PM IST> <Warning> <EJB> <BEA-015036> <In the EJB MessageRec
eiverBean(Application: usermessagingserver, EJBComponent: sdpmessagingengine.jar
), the value for the activation config property 'connectionFactoryJNDIName' will
be ignored since it is overridden with the value 'OraSDPM/QueueConnectionFactor
y';>
It kept on waiting here for so long. Can u please suggest me what is missing here.
Thanks in advance,
Sudheer

Cannot attach a WS-Policy to Jax-RPC Web Service

I am having trouble trying to associate a WS-Security Policy with a BEA Jax-RPC Web Service?
I am following the following procedure to try to associate a the policy:
http://edocs.bea.com/wls/docs100/ConsoleHelp/taskhelp/webservices/ConfigureWSPolicyFile.html
The problem is that when I navigate on the Administration Console to
Deployments
=> AdapterAdminService (this is the name of my application)
=> com.gateway.admin.wsdl.v10.AdminImpl (this is the name of my Web Service)
=> Configuration
=> WS-Policy
The Web console displays a stacktrace mentioning an "IndexOutOfBoundsException" :
Error opening /jsp/webservice/WebServiceConfigurationWebServicePoliciesForm.jsp.
The source of this error is java.lang.IllegalArgumentException: The property you provided 'contents' of form 'deploymentPlanForm' must not be set to null. at com.bea.console.taglib.html.TableTag.registerDataSet(TableTag.java:1588) at com.bea.console.taglib.html.TreeTableTag.doRegisterDataSet(TreeTableTag.java:49) at com.bea.console.taglib.html.TableTag.doStartTag(TableTag.java:1360) at jsp_servlet._jsp._webservice.__webserviceconfigurationwebservicepoliciesform._jsp__tag9(__webserviceconfigurationwebservicepoliciesform.java:498) at jsp_servlet._jsp._webservice.__webserviceconfigurationwebservicepoliciesform._jsp__tag8(__webserviceconfigurationwebservicepoliciesform.java:459) at jsp_servlet._jsp._webservice.__webserviceconfigurationwebservicepoliciesform._jsp__tag7(__webserviceconfigurationwebservicepoliciesform.java:416) at jsp_servlet._jsp._webservice.__webserviceconfigurationwebservicepoliciesform._jspService(__webserviceconfigurationwebservicepoliciesform.java:265) at weblogic.servlet.jsp.JspBase.service(JspBase.java:34) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175) at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454) at org.apache.beehive.netui.pageflow.scoping.internal.ScopedRequestDispatcher.include(ScopedRequestDispatcher.java:119) at com.bea.netuix.servlets.controls.content.JspContent.beginRender(JspContent.java:551) at com.bea.netuix.servlets.controls.content.NetuiContent.beginRender(NetuiContent.java:363) at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:483) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:375) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:341) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:332) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:306) at com.bea.netuix.nf.UIControl.render(UIControl.java:578) at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:482) at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146) at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62) at jsp_servlet._framework._skeletons._default.__gridlayout._jspService(__gridlayout.java:285) at weblogic.servlet.jsp.JspBase.service(JspBase.java:34) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175) at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454) at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:123) at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72) at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65) at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:479) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518) at
I have this issue with both IE7 and Firefox 2. My domain is a WLS 10.0MP1 domain and is deployed on my Windows XP laptop.
I am generating the WS from WSDL with the following ant command:
          <wsdlc srcWsdl="${wsdl.location.path}/AdapterAdministration.wsdl"
               destJwsDir="${gen.compiled.wsdl.dir}"
               packagename="com.gateway.admin.wsdl.v10.server"
               destImplDir="server_impl_example" />
then
               <jwsc     srcdir="${src.dir}" destdir="${dist.dir}" classpathref="project.class.path" debug="true">
                         <jws file="com/gateway/admin/wsdl/v10/AdminImpl.java"
                              compiledWsdl="${gen.compiled.wsdl.dir}/AdapterAdministration_wsdl.jar" />
                    </jwsc>
and finally, I deploy it with:
          <wldeploy action="deploy"
               name="AdapterAdminService"
               source="${dist.dir}/AdminImpl.war"
               user="${wls.domain.user}"
               password="${wls.domain.pwd}"
               verbose="true"
               stage="no"
               upload="true"
               adminurl="t3://${wls.domain.host}:${wls.domain.port}"
               targets="${wls.domain.servername}" />
Do you have any idea what might be wrong here?
Thanks in advance,
Svend

Hi all,
Some more information: I have created another very simple Jax-RPC Web Service, now using the @Policy annotation. The policy I specify is then correctly taken into account, but I still have the same symptom when I navigate to the Configuration => WS-Policy page on the Web Console (i.e., I cannot associate a WS-Policy to my WS with the Web Console)
Beginning of the JWS file:
@WebService(...)
@WLHttpTransport(serviceUri = "", portName = "AdapterAdmin")
@Binding(Binding.Type.SOAP12)
@Policy(uri="Wssp1.2-Http-UsernameToken-Digest.xml")
public class AdminImpl implements Admin {
Ant task I use to build and deploy the service:
<target name="build-service" depends="prepare">
          <mkdir dir="package"/>
          <mkdir dir="package/WEB-INF"/>
          <mkdir dir="package/WEB-INF/lib"/>
          <jwsc
               srcdir="${src.dir}"
               destdir="package"
               classpathref="project.class.path"
               debug="true">
               <jws
                    file="com/gateway/admin/wsdl/v10/AdminImpl.java"
                    contextpath="/AdminImpl2"
                    explode="true"
               />
          </jwsc>
          <move todir="package/WEB-INF">
               <fileset dir="package/com/gateway/admin/wsdl/v10/AdminImpl/WEB-INF"></fileset>
          </move>
          <move todir="package/META-INF">
               <fileset dir="package/xsize/gateway/admin/wsdl/v10/AdminImpl/META-INF"></fileset>
          </move>
          <copy todir="package/WEB-INF/lib">
               <fileset dir="${lib.dir}"
                              includes="client-1.0.jar,
                                   tools.jar />
          </copy>
          <delete dir="package/com" />
          <jar destfile="${dist.dir}/simpleWS2.war" >
               <fileset dir="package" />
          </jar>
          <wldeploy action="deploy"
               name="AdminService-withPolicyAnnotation"
               source="${dist.dir}/simpleWS2.war"
               user="weblogic"
               password="weblogic"
               verbose="true"
               stage="no"
               upload="true"
               adminurl="t3://localhost:9001"
               targets="AdminServer" />
     </target>
"

Deploying a webservice on WLS 9.1 and got an wsdl error.

Hi,
I hoped it is then right usergroup to publish the following question.
I'm trying to deploy a EJB webservice on a WLS 9.1.
But I got the following error message:
[java] port component "SystemServiceEndpointPort" is not found in wsdl.
It's simple JAX-RPC based webservice where a SessionBean method is used as
the service implementation. The same configuration (webservice.xml,
jaxrpc-mapping-SystemService.xml, SystemService.wsdl) works fine under JBoss 4.0, but not with
WLS 9.1. Maybe it's a simple configuration error and I hope someone can help.
I haved remembered the namespace in the webservices.xml file: <wsdl-port>wsdl:SystemServiceEndpointPort</wsdl-port> and also defined et in the top of the file.
Regards
Torben
<b>webservices.xml</b>
<webservices
xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:wsdl="http://www.organisator.dk"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/j2ee_web_services_1_1.xsd"
version="1.1">
<webservice-description>
<icon></icon>
<webservice-description-name>SystemService</webservice-description-name>
<wsdl-file>META-INF/wsdl/SystemService.wsdl</wsdl-file>
<jaxrpc-mapping-file>META-INF/jaxrpc-mapping-SystemService.xml</jaxrpc-mapping-file>
<port-component>
<icon></icon>
<port-component-name>SystemServiceEndpointPort</port-component-name>
<wsdl-port>wsdl:SystemServiceEndpointPort</wsdl-port>
<service-endpoint-interface>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint</service-endpoint-interface>
<service-impl-bean>
<ejb-link>SCSystem</ejb-link>
</service-impl-bean>
</port-component>
</webservice-description>
</webservices>
<b>weblogic-webservices.xml</b>
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-webservices xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<webservice-description>
<webservice-description-name>SystemService</webservice-description-name>
<port-component>
<port-component-name>SystemServiceEndpointPort</port-component-name>
<service-endpoint-address>
<webservice-contextpath>/winnie</webservice-contextpath>
<webservice-serviceuri>/SystemService</webservice-serviceuri>
</service-endpoint-address>
</port-component>
</webservice-description>
</weblogic-webservices>
<b>ejb-jar.xml</b>
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd" version="2.1">
<description><![CDATA[No Description.]]></description>
<display-name>Generated by XDoclet</display-name>
<enterprise-beans>

<session >
<description><![CDATA[System information handler]]></description>
<display-name>SCSystem</display-name>
<ejb-name>SCSystem</ejb-name>
<home>dk.organisator.winnie.system.ejbsystem.services.SCSystemHome</home>
<remote>dk.organisator.winnie.system.ejbsystem.services.SCSystemRemote</remote>
<service-endpoint>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint</service-endpoint>
<ejb-class>dk.organisator.winnie.system.ejbsystem.services.SCSystemBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
<b>SystemService.wsdl</b>
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="SystemService" targetNamespace="http://organisator.dk/winnie/wsdl" xmlns:tns="http://organisator.dk/winnie/wsdl" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns2="http://organisator.dk/winnie/types" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types>
<schema targetNamespace="http://organisator.dk/winnie/types" xmlns:tns="http://organisator.dk/winnie/types" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://www.w3.org/2001/XMLSchema">
<complexType name="getXxxxxxxxx">
<sequence>
<element name="String_1" type="string" nillable="true"/></sequence></complexType>
<complexType name="getXxxxxxxxxResponse">
<sequence>
<element name="result" type="string" nillable="true"/></sequence></complexType>
<complexType name="ping">
<sequence/></complexType>
<complexType name="pingResponse">
<sequence>
<element name="result" type="int"/></sequence></complexType>
<complexType name="setXxxxxxxx">
<sequence>
<element name="String_1" type="string" nillable="true"/></sequence></complexType>
<complexType name="setXxxxxxxxResponse">
<sequence/></complexType>
<element name="getXxxxxxxxx" type="tns:getXxxxxxxxx"/>
<element name="getXxxxxxxxxResponse" type="tns:getXxxxxxxxxResponse"/>
<element name="ping" type="tns:ping"/>
<element name="pingResponse" type="tns:pingResponse"/>
<element name="setXxxxxxxx" type="tns:setXxxxxxxx"/>
<element name="setXxxxxxxxResponse" type="tns:setXxxxxxxxResponse"/></schema></types>
<message name="SystemServiceEndpoint_getXxxxxxxxx">
<part name="parameters" element="ns2:getXxxxxxxxx"/></message>
<message name="SystemServiceEndpoint_getXxxxxxxxxResponse">
<part name="result" element="ns2:getXxxxxxxxxResponse"/></message>
<message name="SystemServiceEndpoint_ping">
<part name="parameters" element="ns2:ping"/></message>
<message name="SystemServiceEndpoint_pingResponse">
<part name="result" element="ns2:pingResponse"/></message>
<message name="SystemServiceEndpoint_setXxxxxxxx">
<part name="parameters" element="ns2:setXxxxxxxx"/></message>
<message name="SystemServiceEndpoint_setXxxxxxxxResponse">
<part name="result" element="ns2:setXxxxxxxxResponse"/></message>
<portType name="SystemServiceEndpoint">
<operation name="getXxxxxxxxx">
<input message="tns:SystemServiceEndpoint_getXxxxxxxxx"/>
<output message="tns:SystemServiceEndpoint_getXxxxxxxxxResponse"/></operation>
<operation name="ping">
<input message="tns:SystemServiceEndpoint_ping"/>
<output message="tns:SystemServiceEndpoint_pingResponse"/></operation>
<operation name="setXxxxxxxx">
<input message="tns:SystemServiceEndpoint_setXxxxxxxx"/>
<output message="tns:SystemServiceEndpoint_setXxxxxxxxResponse"/></operation></portType>
<binding name="SystemServiceEndpointBinding" type="tns:SystemServiceEndpoint">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<operation name="getXxxxxxxxx">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/></input>
<output>
<soap:body use="literal"/></output></operation>
<operation name="ping">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/></input>
<output>
<soap:body use="literal"/></output></operation>
<operation name="setXxxxxxxx">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/></input>
<output>
<soap:body use="literal"/></output></operation></binding>
<service name="SystemService">
<port name="SystemServiceEndpointPort" binding="tns:SystemServiceEndpointBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/></port></service></definitions>
<b>jaxrpc-mapping-SystemService.xml</b>
<?xml version="1.0" encoding="UTF-8"?>
<java-wsdl-mapping xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.1" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://www.ibm.com/webservices/xsd/j2ee_jaxrpc_mapping_1_1.xsd">
<package-mapping>
<package-type>dk.organisator.winnie.system.ejbsystem.services</package-type>
<namespaceURI>http://organisator.dk/winnie/types</namespaceURI>
</package-mapping>
<package-mapping>
<package-type>dk.organisator.winnie.system.ejbsystem.services</package-type>
<namespaceURI>http://organisator.dk/winnie/wsdl</namespaceURI>
</package-mapping>
<java-xml-type-mapping>
<java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_ping_ResponseStruct</java-type>
<root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:pingResponse</root-type-qname>
<qname-scope>complexType</qname-scope>
<variable-mapping>
<java-variable-name>result</java-variable-name>
<xml-element-name>result</xml-element-name>
</variable-mapping>
</java-xml-type-mapping>
<java-xml-type-mapping>
<java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_getXxxxxxxxx_RequestStruct</java-type>
<root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:getXxxxxxxxx</root-type-qname>
<qname-scope>complexType</qname-scope>
<variable-mapping>
<java-variable-name>String_1</java-variable-name>
<xml-element-name>String_1</xml-element-name>
</variable-mapping>
</java-xml-type-mapping>
<java-xml-type-mapping>
<java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_setXxxxxxxx_ResponseStruct</java-type>
<root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:setXxxxxxxxResponse</root-type-qname>
<qname-scope>complexType</qname-scope>
</java-xml-type-mapping>
<java-xml-type-mapping>
<java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_setXxxxxxxx_RequestStruct</java-type>
<root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:setXxxxxxxx</root-type-qname>
<qname-scope>complexType</qname-scope>
<variable-mapping>
<java-variable-name>String_1</java-variable-name>
<xml-element-name>String_1</xml-element-name>
</variable-mapping>
</java-xml-type-mapping>
<java-xml-type-mapping>
<java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_ping_RequestStruct</java-type>
<root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:ping</root-type-qname>
<qname-scope>complexType</qname-scope>
</java-xml-type-mapping>
<java-xml-type-mapping>
<java-type>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint_getXxxxxxxxx_ResponseStruct</java-type>
<root-type-qname xmlns:typeNS="http://organisator.dk/winnie/types">typeNS:getXxxxxxxxxResponse</root-type-qname>
<qname-scope>complexType</qname-scope>
<variable-mapping>
<java-variable-name>result</java-variable-name>
<xml-element-name>result</xml-element-name>
</variable-mapping>
</java-xml-type-mapping>
<service-interface-mapping>
<service-interface>dk.organisator.winnie.system.ejbsystem.services.SystemService</service-interface>
<wsdl-service-name xmlns:serviceNS="http://organisator.dk/winnie/wsdl">serviceNS:SystemService</wsdl-service-name>
<port-mapping>
<port-name>SystemServiceEndpointPort</port-name>
<java-port-name>SystemServiceEndpointPort</java-port-name>
</port-mapping>
</service-interface-mapping>
<service-endpoint-interface-mapping>
<service-endpoint-interface>dk.organisator.winnie.system.ejbsystem.services.SystemServiceEndpoint</service-endpoint-interface>
<wsdl-port-type xmlns:portTypeNS="http://organisator.dk/winnie/wsdl">portTypeNS:SystemServiceEndpoint</wsdl-port-type>
<wsdl-binding xmlns:bindingNS="http://organisator.dk/winnie/wsdl">bindingNS:SystemServiceEndpointBinding</wsdl-binding>
<service-endpoint-method-mapping>
<java-method-name>getXxxxxxxxx</java-method-name>
<wsdl-operation>getXxxxxxxxx</wsdl-operation>
<wrapped-element/>
<method-param-parts-mapping>
<param-position>0</param-position>
<param-type>java.lang.String</param-type>
<wsdl-message-mapping>
<wsdl-message xmlns:wsdlMsgNS="http://organisator.dk/winnie/wsdl">wsdlMsgNS:SystemServiceEndpoint_getXxxxxxxxx</wsdl-message>
<wsdl-message-part-name>String_1</wsdl-message-part-name>
<parameter-mode>IN</parameter-mode>
</wsdl-message-mapping>
</method-param-parts-mapping>
<wsdl-return-value-mapping>
<method-return-value>java.lang.String</method-return-value>
<wsdl-message xmlns:wsdlMsgNS="http://organisator.dk/winnie/wsdl">wsdlMsgNS:SystemServiceEndpoint_getXxxxxxxxxResponse</wsdl-message>
<wsdl-message-part-name>result</wsdl-message-part-name>
</wsdl-return-value-mapping>
</service-endpoint-method-mapping>
<service-endpoint-method-mapping>
<java-method-name>ping</java-method-name>
<wsdl-operation>ping</wsdl-operation>
<wrapped-element/>
<wsdl-return-value-mapping>
<method-return-value>int</method-return-value>
<wsdl-message xmlns:wsdlMsgNS="http://organisator.dk/winnie/wsdl">wsdlMsgNS:SystemServiceEndpoint_pingResponse</wsdl-message>
<wsdl-message-part-name>result</wsdl-message-part-name>
</wsdl-return-value-mapping>
</service-endpoint-method-mapping>
<service-endpoint-method-mapping>
<java-method-name>setXxxxxxxx</java-method-name>
<wsdl-operation>setXxxxxxxx</wsdl-operation>
<wrapped-element/>
<method-param-parts-mapping>
<param-position>0</param-position>
<param-type>java.lang.String</param-type>
<wsdl-message-mapping>
<wsdl-message xmlns:wsdlMsgNS="http://organisator.dk/winnie/wsdl">wsdlMsgNS:SystemServiceEndpoint_setXxxxxxxx</wsdl-message>
<wsdl-message-part-name>String_1</wsdl-message-part-name>
<parameter-mode>IN</parameter-mode>
</wsdl-message-mapping>
</method-param-parts-mapping>
</service-endpoint-method-mapping>
</service-endpoint-interface-mapping>
</java-wsdl-mapping>

the problem is with the xmlns:wsdl="http://www.organisator.dk" line in your webservices.xml. It does not match the namespace of the corresponding PortType in your wsdl: targetNamespace="http://organisator.dk/winnie/wsdl"

JAX RS in WLS 12.1.3

Similar Messages

Maybe you are looking for