PartnerLink with complex type problem| JBoss.org Content Archive (Read Only)

15. Re: PartnerLink with complex type problem

normandesjr Feb 17, 2010 11:46 AM (in response to objectiser)

Hi,

I attached the projects (the war project has the source too). Follow the procedure:

1) Copy both project to deploy folder at JBoss with Riftsaw.

2) Using soapUI, create the project with wsdl of BPEL Process: http://127.0.0.1:8080/Quickstart_bpel_hello_worldWS?wsdl

3) Fill TestPart with any value and submit the SOAP package.

The WAR project has a Handler that will intercept and print the SOAP package, if there is a header value it will be printed.

For you test the Header direct to WebService (ComponentSMS), create a new soapUI project and use the wsdl: http://127.0.0.1:8080/Component-SMSCTBC-1.0.0/ComponentSMSCTBC?wsdl

Then add the header manually to SOAP Envelop:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:com="http://cocreation.com.br/componentsmsctbc">
   <soapenv:Header>
      <com:userName>admin</com:userName>
   </soapenv:Header>
   <soapenv:Body>
      <com:sendSMS>
         <from>123</from>
         <to>111</to>
         <message>aaa</message>
      </com:sendSMS>
   </soapenv:Body>
</soapenv:Envelope>

You will see at console the header "userName".

If you have some problem to test, please let me know.

Regards and thank you for you help.

Normandes Junior.

Quickstart_bpel_hello_world-1.jar 3.7 KB
Component-SMSCTBC-1.0.0.war 6.8 KB

16. Re: PartnerLink with complex type problem

objectiser Feb 19, 2010 6:12 AM (in response to normandesjr)

Sorry, only now getting time to have a look at this. When I deployed the war I got the following problem:

11:00:03,624 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/home/gbrown/testing/riftsaw/current/jboss-5.1.0.GA/server/default/deploy/Component-SMSCTBC-1.0.0.war/ state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/home/gbrown/testing/riftsaw/current/jboss-5.1.0.GA/server/default/deploy/Component-SMSCTBC-1.0.0.war/
    at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
    at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
    at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
    at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
    at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
    at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
    at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
    at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
    at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
    at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
    at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
    at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
    at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:362)
    at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:619)
Caused by: org.jboss.ws.WSException: Cannot process handler chain: http://localhost:8080/Component-SMSCTBC-1.0.0/myhandler.xml
    at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.getHandlerChainsMetaData(JAXWSMetaDataBuilder.java:290)
    at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.processHandlerChain(JAXWSMetaDataBuilder.java:189)
    at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:194)
    at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:50)
    at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:62)
    at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.start(UnifiedMetaDataDeploymentAspect.java:64)
    at org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer.internalDeploy(WSDeploymentAspectDeployer.java:107)
    at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
    at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
    ... 24 more
Caused by: java.io.FileNotFoundException: http://localhost:8080/Component-SMSCTBC-1.0.0/myhandler.xml
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1311)
    at java.net.URL.openStream(URL.java:1010)
    at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.getHandlerChainsMetaData(JAXWSMetaDataBuilder.java:268)
    ... 32 more
11:00:03,631 WARN [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

Which is strange seeing as the file does exist at the root of the war.

What is your environment? Jboss version, jbossws, OS, JDK, etc.

Regards

Gary

17. Re: PartnerLink with complex type problem

normandesjr Feb 19, 2010 6:35 AM (in response to objectiser)

Hi Gary,

There is no problem to wait for your help, you are doing more than I expect. Thank you.

You are right, this is strange. When I try to run jboss again, after saw you info, I couldn't start jboss too. So I move both files to other directory and then move back, first Component-SMSCTBC-1.0.0.war and then Quickstart_bpel_hello_world-1.jar. Doing this way works for me, please try this way and if you have some problem, I have other solution. Move the files with JBoss started, so hot deploy will do the job.

Follow my environment:

* OS: Linux (Fedora 12)

* JBoss Version: 5.1.0.GA

* JBossWS Version: 3.1.2 native

* JDK: 1.6.0_18

Thanks again for you help.

Regards,

Normandes Junior.

18. Re: PartnerLink with complex type problem

objectiser Feb 19, 2010 7:55 AM (in response to normandesjr)

The exception when deploying the war appears to be related to jbossws-native-3.2.2.GA.

I have raised a bug (https://jira.jboss.org/jira/browse/JBWS-2939) attaching your war file - hope you don't mind.

I will setup an environment equivalent to yours to try to reproduce your problem.

Regards

Gary

19. Re: PartnerLink with complex type problem

normandesjr Feb 19, 2010 8:03 AM (in response to objectiser)

There is no problem Gary to use my war file.

Alternatively you can deploy the myhandler.xml to httpd (apache) at /var/www/html and then use @HandlerChain(file="http://localhost/myhandler.xml")

But you have to compile again. If you prefer I can compile and send to you the new war file.

Regards,

Normandes Junior.

20. Re: PartnerLink with complex type problem

objectiser Feb 19, 2010 9:02 AM (in response to normandesjr)

Hi

Have reproduced this problem with jbossws-3.1.2.GA, and can't see anything obviously wrong. I tried setting the username using:

             <copy>
                <from><literal><types:userName>admin</types:userName></literal></from>
                <to part="userName" variable="inVar"/>
            </copy>

but that didn't work either.

Could you raise a bug attaching the jar and war, and we will try to get it resolved soon.

Regards

Gary

21. Re: PartnerLink with complex type problem

normandesjr Feb 19, 2010 1:57 PM (in response to objectiser)

I raised a bug at JIRA. I couldn't attach the files, but I did the reference to our chat at forum, so the files are attached at forum. If you could edit the JIRA to get a better description, go ahead.

Thanks for you help.

Normandes Junior.

22. Re: PartnerLink with complex type problem

jeff.yuchang Feb 24, 2010 7:34 AM (in response to normandesjr)

According to the 'ComponentSMS' wsdl, Should the soapHeader be as following:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:com="http://cocreation.com.br/componentsmsctbc">
<soapenv:Header>
<com:userName>

<userName xmlns='http://www.jboss.org/cid'>user</userName>

      </com:userName>
   </soapenv:Header>
   <soapenv:Body>
      <com:sendSMS>
         <from>123</from>
         <to>111</to>
         <message>aaa</message>
      </com:sendSMS>
   </soapenv:Body>
</soapenv:Envelope>

??

23. Re: PartnerLink with complex type problem

normandesjr Feb 24, 2010 10:04 AM (in response to jeff.yuchang)

I don't think so, I think that should be as following

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:com="http://cocreation.com.br/componentsmsctbc">
   <soapenv:Header>
      <com:userName>user</com:userName>
   </soapenv:Header>
   <soapenv:Body>
      <com:sendSMS>
         <from>123</from>
         <to>111</to>
         <message>aaa</message>
      </com:sendSMS>
   </soapenv:Body>
</soapenv:Envelope>

Do you close the JIRA? How could I get the new version for test?

24. Re: PartnerLink with complex type problem

jeff.yuchang Feb 24, 2010 10:12 AM (in response to normandesjr)

I made it as resolved status, which means ready for test. Currently I am still working on fixing the hudson job (it is related to the hudson server environment), once its completed, I will post the url here to let you know.

Regards

Jeff

25. Re: PartnerLink with complex type problem

jeff.yuchang Feb 24, 2010 11:50 AM (in response to normandesjr)

you can obtain the latest version from here: http://hudson.jboss.org/hudson/job/RiftSaw/114/

Regards

Jeff

26. [Resolved]Re: PartnerLink with complex type problem

normandesjr Feb 24, 2010 1:10 PM (in response to jeff.yuchang)

Works! Thanks Jeff and Gary. Works great.

Best regards,

Normandes Junior.