Build and use of jms-binding
Hi all, I'm new to Tuscany and very enthusiastic about the SCA concepts. After I played a little with some samples, I would like to try out the jms binding. The problem I face now is that it's not part of the official release yet (though some basic functionality is working already according to the Tuscany web site), so one has to build the module from the repository on his own. I tried it on several trunk revisions but the build never succeed (some artifacts where missing etc.). Has somebody done it before? Any hints on some stable revision/branch/tag of the source code, so one could build and use the jms binding module? I'd appreciate any help on this issue. Thanks, Philipp Konradi
AW: Build and use of jms-binding
Hi Simon, Thank you very much your hints. The build is still failing for me. It seems that 1 artifact is missing for binding-jms module. Though that's already some progress, the day before there were 3 artifacts missing. My environment is: - Windows XP Pro SP2 - Sun JDK 1.5.0_12 - Maven 2.0.5 ( previously tried it with 2.0.7 but as you already mentioned this version of maven isn't supported yet. It would be really good if the "tuscany - get involved"-web site would mention that) - My trunk is at revision 580013 (last change 11:45 Thursday 27.09.2007) The build is working for you…hmm... might it be the maven settings has to be configured in some special way to make the build process work? After Maven installation, I've just set the settings for a proxy. I've pasted here some maven output, maybe it will be of help Maven output for java/sca: … [INFO] Apache Tuscany SCA JMS Binding Extension .. SKIPPED (dependen cy build failed or was skipped) … [INFO] Apache Tuscany SCA Web Services Void Args and Return Test SKIPPED (depen dency build failed or was skipped) [INFO] [INFO] Error for project: Apache Tuscany SCA Contribution Model Implementation ( during install) [INFO] [INFO] There are test failures. [INFO] [INFO] Error for project: Apache Tuscany SCA WSDL2Java Tool (during install) [INFO] [INFO] There are test failures. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] BUILD ERRORS [INFO] [INFO] Total time: 1 minute 42 seconds [INFO] Finished at: Thu Sep 27 16:17:49 CEST 2007 [INFO] Final Memory: 28M/51M [INFO] Maven output for java/sca/modules/binding-jms: ... Downloading: http://people.apache.org/repo/m2-incubating-repository/org/apache/tuscany/sca/tuscany-host-embedded/1.1-incubating-SNAPSHOT/tuscany-host-embedded-1.1-incubating-SNAPSHOT.jar [WARNING] Unable to get resource ' org.apache.tuscany.sca:tuscany-host-embedded:jar:1.1-incubating-SNAPSHOT ' from repository apache.incubator ( http://people.apache.org/repo/m2-incubating-repository) Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/tuscany/sca/tuscany-host-embedded/1.1-incubating-SNAPSHOT/tuscany-host-embedded-1.1-incubating-SNAPSHOT.jar [WARNING] Unable to get resource ' org.apache.tuscany.sca:tuscany-host-embedded:jar:1.1-incubating-SNAPSHOT ' from repository apache.snapshots ( http://people.apache.org/repo/m2-snapshot-repository) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.tuscany.sca:tuscany-host-embedded:jar:1.1-incubating-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.tuscany.sca-DartifactId=tuscany-host-embedded \ -Dversion=1.1-incubating-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.tuscany.sca:tuscany-binding-jms:jar:1.1-incubating-SNAPSHOT 2) org.apache.tuscany.sca:tuscany-host-embedded:jar:1.1-incubating-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.tuscany.sca:tuscany-binding-jms:jar:1.1-incubating-SNAPSHOT from the specified remote repositories: central ( http://repo1.maven.org/maven2), apache.ws.zone (http://ws.zones.apache.org/repository2), apache.incubator ( http://people.apache.org/repo/m2-incubating-repository ), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository) Thanks, Philipp -Ursprüngliche Nachricht- Von: Simon Laws [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 27. September 2007 14:43 An: tuscany-user@ws.apache.org Betreff: Re: Build and use of jms-binding On 9/27/07, Philipp Konradi <[EMAIL PROTECTED]> wrote: > > Hi all, > > I'm new to Tuscany and very enthusiastic about the SCA concepts. > After I played a little with some samples, I would like to try out the jms > binding. > The problem I face now is that it's not part of the official release yet > (though some basic functionality is working already according to the > Tuscany > web site), so one has to build the module from the repository on his own. > I tried it on
Re: Build and use of jms-binding
le:/D:/Work/CodeLibrary/Java/Tuscany Java/modules/contribution-impl/./ at java.net.URI$Parser.fail(URI.java:2809) at java.net.URI$Parser.checkChars(URI.java:2982) at java.net.URI$Parser.parseHierarchical(URI.java:3066) at java.net.URI$Parser.parse(URI.java:3014) at java.net.URI.(URI.java:578) at java.net.URL.toURI(URL.java:918) at org.apache.tuscany.sca.contribution.processor.impl.FolderContributionProcessor.getArtifacts (FolderContributionProcessor.java:107) ... 24 more -Ursprüngliche Nachricht- Von: Simon Laws [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 28. September 2007 16:04 An: tuscany-user@ws.apache.org Betreff: Re: Build and use of jms-binding Hi Philipp Comments in line Regards Simon On 9/28/07, Philipp Konradi <[EMAIL PROTECTED]> wrote: > > Hi Simon, > > Thank you very much your hints. > > The build is still failing for me. > It seems that 1 artifact is missing for binding-jms module. Though that's > already some progress, the day before there were 3 artifacts missing. A step in the right direction at least :-) My environment is: > - Windows XP Pro SP2 > - Sun JDK 1.5.0_12 > - Maven 2.0.5 ( previously tried it with 2.0.7 but as you already > mentioned > this version of maven isn't supported yet. It would be really good if the > "tuscany - get involved"-web site would mention that) Done. Thanks for the suggestion. I've put a link into the java developer guide on the getting involved page and added the explicit maven version required to the java developer guide. - My trunk is at revision 580013 (last change 11:45 Thursday 27.09.2007) Am just updating to the very latest to make sure The build is working for you...hmm... might it be the maven settings has to be > configured in some special way to make the build process work? After Maven > installation, I've just set the settings for a proxy. Shouldn't be. I don't have any active proxy settings. The build should be able to get everything that it needs given the repo settings in the project poms. I've pasted here some maven output, maybe it will be of help > > > Maven output for java/sca: > ... > [INFO] Apache Tuscany SCA JMS Binding Extension .. SKIPPED > (dependen > cy build failed or was skipped) > ... > [INFO] Apache Tuscany SCA Web Services Void Args and Return Test SKIPPED > (depen > dency build failed or was skipped) > [INFO] > > [INFO] Error for project: Apache Tuscany SCA Contribution Model > Implementation ( > during install) > [INFO] > > [INFO] There are test failures. > [INFO] > > [INFO] Error for project: Apache Tuscany SCA WSDL2Java Tool (during > install) > [INFO] > > [INFO] There are test failures. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] BUILD ERRORS > [INFO] > > [INFO] Total time: 1 minute 42 seconds > [INFO] Finished at: Thu Sep 27 16:17:49 CEST 2007 > [INFO] Final Memory: 28M/51M > [INFO] > > > > > Maven output for java/sca/modules/binding-jms: > ... > Downloading: > > http://people.apache.org/repo/m2-incubating-repository/org/apache/tuscany/sca/tuscany-host-embedded/1.1-incubating-SNAPSHOT/tuscany-host-embedded-1.1-incubating-SNAPSHOT.jar > [WARNING] Unable to get resource ' > org.apache.tuscany.sca:tuscany-host-embedded:jar:1.1-incubating-SNAPSHOT ' > from repository apache.incubator ( > http://people.apache.org/repo/m2-incubating-repository) > Downloading: > > http://people.apache.org/repo/m2-snapshot-repository/org/apache/tuscany/sca/tuscany-host-embedded/1.1-incubating-SNAPSHOT/tuscany-host-embedded-1.1-incubating-SNAPSHOT.jar > [WARNING] Unable to get resource ' > org.apache.tuscany.sca:tuscany-host-embedded:jar:1.1-incubating-SNAPSHOT ' > from repository apache.snapshots ( > http://people.apache.org/repo/m2-snapshot-repository) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > > Missing: > -- > 1
RE: SCA WCF Integration
Hi, I do totally agree. The possibility to integrate SCA with WCF would be a top-feature. There is definitly interest from business side for that. Regards, Philipp -- Forwarded message -- -Ursprüngliche Nachricht- Von: Anderson, Jeff T (CA - Toronto) [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 24. Oktober 2007 00:08 An: tuscany-user@ws.apache.org; tuscany-user@ws.apache.org Betreff: RE: SCA WCF Integration Again, I think this would be a definite value. Jeff From: Jean-Sebastien Delfino [mailto:[EMAIL PROTECTED] Sent: Tue 2007-10-23 14:23 To: tuscany-user@ws.apache.org Subject: Re: SCA WCF Integration Jean-Sebastien Delfino wrote: > Anderson, Jeff T (CA - Toronto) wrote: >> Our client is also very interested in this topic, be very interested >> in seeing how it performed tighter integration, such as being able to >> declare an intent on a wcf service method and use the Tuscany or >> other SCA policy framework to satisfy the intent at runtime. Just >> one of many examples, I don't know a lot about W.CF but it does seem >> that the approach is very similar to SCA, so in theory, a binding >> shouldn't necessarily be Uber difficult. >> Is anybody else interested in tighter integration up there? >> Regards >> Jeff >> >> >> >> From: Simon Nash [mailto:[EMAIL PROTECTED] >> Sent: Mon 2007-10-22 10:33 >> To: tuscany-user@ws.apache.org >> Subject: Re: SCA WCF Integration >> >> >> >> You are correct that in Tuscany currently we don't have any way to >> make a WCF Web service part of the SCA domain. >> >> I think there are (at least) two options for how you could do this. >> >> 1. Use on a SCDL reference to connect from the SCA domain >> to the WCF Web service. The reference is part of the SCA domain but >> the WCF Web service that it invokes is not part of the SCA domain. >> >> 2. Create an SCA service that encapsulates the WCF service, and wire >> to this SCA service in the usual way. The encapsulating SCA service >> is part of the SCA domain. It would be possible to create a new >> component implementation type to specify this >> encapsulation and perform the necessary WCF invocations. >> >> This is a great topic to discuss and I'm sure others will have other >> alternatives and opinions on the pros and cons of various approaches. >> >>Simon >> >> James, Steven wrote: >> >> >>> I have a question regarding WCF and SCA integration which I am hoping >>> someone in this list can give clarity to. >>> >>> As far as I see it currently a WCF Web service is not part of the >>> SCADomain. If a composed component had a dependency on a WCF component >>> could an explicit reference be set to that WCF web service in the SCDL >>> file? Or is this an internal matter and how we connect and invoke the >>> WCF component should be encapsulated in our SCA component? >>> >>> Regards, >>> >>> Steve >>> >>> > > A few more thoughts, using the WCF Getting Started Calculator example > at http://msdn2.microsoft.com/en-us/library/ms751519.aspx to > illustrate what could be done... > > - Step 1: Model the WCF service as an SCA reference with a WS binding, > would look like this: > > http://www.osoa.org/xmlns/sca/1.0"; > targetNamespace="http://sample"; > xmlns:sample="http://sample"; > name="Calculator"> > > > > > > > > > > > > > > > Here the SCA domain only contains a reference to the external WCF > service and its WSDL configuration. > > > - Step 2: Model the WCF Calculator as an SCA component implementation, > like that: > > http://www.osoa.org/xmlns/sca/1.0"; > targetNamespace="http://sample"; > xmlns:sample="http://sample"; > name="Calculator"> > > > > > > > target="WCFCalculatorServiceComponent"/> > > > > > > > > config="C:\WCF-Samples\TechnologySamples\Basic\GettingStarted\CS\service\Web.config"/> > > > > > > > Here we would represent the WCF app as a component implementation, > introspect its WCF Web.config or App.config file to determine the > services it offers, its references and configuration. Once you've > represented the WCF app as an SCA implementation + component you can > start using SCA wiring in your SCA domain as usual. > > > To get Step 1 going will only require some configuration and Axis2 / > WCF interop testing. > > Step 2 will take a little bit of coding to support > and introspect WCF configs but it should be > pretty easy to do... > > Thoughts? > A few more code snippets to help illustrate Step 2: This Web.config could be represented as an SCA component providing a service: And that App.config could be represented as an SCA component with a reference:
Re: JMS binding
Hi Simon, just wanted to let you know that jms binding is working for me now (in a simple request/reply scenario where an external app invokes an java-sca-service via jms-binding). Thank you for your help! For some of other guys who might also be interested in jms-binding here the currently easiest way to get it to run: 1. Download the nightly build from http://incubator.apache.org/tuscany/tuscany-downloads-documentations.html 2. Download the jms-binding module from Continuum (Tuscany's Build-Monitoring-Site) http://vmbuild1.apache.org/continuum/buildResults.action?projectGroupId=19&projectId=277 A direct link to jms-binding.jar would be: http://vmbuild1.apache.org/continuum/workingCopy.action?projectId=277&projectName=Apache+Tuscany+SCA+Implementation+Project&userDirectory=modules/binding-jms/target&file=tuscany-binding-jms-1.1-incubating-SNAPSHOT.jar 3. Put /lib, /modules, jms-binding.jar on the classpath of your SCA-application 4. Start using the jms-binding :-) One important thing to know is(!!!): It looks like Tuscany currently supports only JMS-ObjectMessages with serialized Java-Object-Array as call parameters. If service has a return value, then the same is valid for receiving the reply message. With the only difference that instead of the Object[] the message contains a single Object. That's not really SCA-spec-compliant AFAIK, but I saw already some code for xml-based message content in the jms-binding-code and a flag to switch between the two modes. There seems some work to go on. Best, Philipp
SOAPProcessingException after update from SCA 0.99 to 1.0
Hi all, after upgrading from Tuscany SCA Java v0.99 to 1.0 one of my sample applications has broken. The app is pretty simple: a Java SCA service calls a Native SCA service via Web Services. After version upgrade I'm getting a SOAPProcessingException saying "Only Characters are allowed here". Does somebody else experienced something similar? Any explanations what's the reason and how to fix/workaround here? Here some details to the app: The Java SCA service is actually the helloworld-ws-reference sample. The Native SCA service is a simple helloworld implementation in C++ deployed in Axis2/C. The call makes it actually to Axis2/C but then Axis2/C returns a SOAP fault message. Here the axis2c log: [Sun Nov 11 16:07:29 2007] [info] Starting HTTP server thread [Sun Nov 11 16:12:34 2007] [debug] ..\..\modules\core\transport\http\http_worker.c(206) Client HTTP version HTTP/1.1 [Sun Nov 11 16:12:34 2007] [debug] ..\..\axiom\src\soap\soap_builder.c(868) Identified soap version is soap11 [Sun Nov 11 16:12:34 2007] [debug] ..\..\modules\core\engine\engine.c(776) Invoking phase TransportIn [Sun Nov 11 16:12:34 2007] [debug] ..\..\modules\core\engine\phase.c(358) Invoke the handler request_uri_based_dispatcher within the phase TransportIn [Sun Nov 11 16:12:34 2007] [debug] ..\..\modules\core\engine\req_uri_disp.c(104) Checking for service using target endpoint address : http://127.0.0.1:9090/HelloWorldService [Sun Nov 11 16:12:34 2007] [debug] ..\..\modules\core\engine\engine.c(776) Invoking phase PreDispatch [Sun Nov 11 16:12:34 2007] [debug] ..\..\modules\core\engine\phase.c(358) Invoke the handler AddressingInHandler within the phase PreDispatch [Sun Nov 11 16:12:34 2007] [info] Starting addressing in handler . [Sun Nov 11 16:12:34 2007] [debug] ..\..\axiom\src\soap\soap_fault_code.c(273) trying to set fault subcode to fault code more than once [Sun Nov 11 16:12:34 2007] [debug] ..\..\modules\core\engine\engine.c(776) Invoking phase MessageOut [Sun Nov 11 16:12:34 2007] [debug] ..\..\modules\core\engine\phase.c(358) Invoke the handler AddressingOutHandler within the phase MessageOut [Sun Nov 11 16:12:34 2007] [info] Request served successfully Here the output on the Java side: [java] Injected helloWorldService [java] Called getGreetings [java] Exception in thread "main" org.apache.axiom.soap.SOAPProcessingException: Only Characters are allowed here [java] at org.apache.axiom.soap.impl.builder.SOAP11BuilderHelper.processText (SOAP11BuilderHelper.java:151) [java] at org.apache.axiom.soap.impl.builder.SOAP11BuilderHelper.handleEvent (SOAP11BuilderHelper.java:63) [java] at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode( StAXSOAPModelBuilder.java:344) [java] at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement( StAXSOAPModelBuilder.java:187) [java] at org.apache.axiom.om.impl.builder.StAXOMBuilder.next( StAXOMBuilder.java:163) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.buildNext( OMElementImpl.java:552) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.getFirstOMChild( OMElementImpl.java:563) [java] at org.apache.axiom.om.impl.llom.OMElementImpl.getFirstChildWithName( OMElementImpl.java:219) [java] at org.apache.axiom.soap.impl.llom.soap11.SOAP11FaultImpl.getCode( SOAP11FaultImpl.java:129) [java] at org.apache.axis2.AxisFault.initializeValues(AxisFault.java:189) [java] at org.apache.axis2.AxisFault.(AxisFault.java:183) [java] at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext( Utils.java:486) [java] at org.apache.axis2.description.OutInAxisOperationClient.handleResponse( OutInAxisOperation.java:343) [java] at org.apache.axis2.description.OutInAxisOperationClient.send( OutInAxisOperation.java:389) [java] at org.apache.axis2.description.OutInAxisOperationClient.executeImpl( OutInAxisOperation.java:211) [java] at org.apache.axis2.client.OperationClient.execute( OperationClient.java:163) [java] at org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invokeTarget( Axis2BindingInvoker.java:102) [java] at org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invoke (Axis2BindingInvoker.java:77) [java] at org.apache.tuscany.sca.core.databinding.wire.DataTransformationInteceptor.invoke (DataTransformationInteceptor.java:73) [java] at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke (JDKInvocationHandler.java:233) [java] at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke (JDKInvocationHandler.java:130) [java] at $Proxy4.getGreetings(Unknown Source) [java] at helloworld.HelloWorldServiceComponent.getGreetings( HelloWorldServiceComponent.java:30) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke( NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:585) [java] at org.apache.tuscany.sca.imp
Re: SOAPProcessingException after update from SCA 0.99 to 1.0
Hi, thank you guys very much for taking this issue on. I've done tcpmonitoring as suggested and I noticed that the 1.0 runtime was sending additionally a Header with some Address element. Here the SOAP-Message send from 1.0 runtime: POST /axis2/services/HelloWorldComponent/HelloWorldService HTTP/1.1 Content-Type: text/xml; charset=UTF-8 SOAPAction: "HelloWorldService#getGreetings" User-Agent: Axis2 Host: localhost:9090 Content-Length: 508 http://schemas.xmlsoap.org/soap/envelope/";> http://www.w3.org/2005/08/addressing";> http://www.w3.org/2005/08/addressing";> http://localhost:9090/axis2/services/HelloWorldComponent/HelloWorldService <_ns_:getGreetings xmlns:_ns_="http://sample/helloworld";> <_ns_:param1>World Here the SOAP-Message send from 0.99 runtime: POST /axis2/services/HelloWorldComponent/HelloWorldService HTTP/1.1 Content-Type: text/xml; charset=UTF-8 SOAPAction: "HelloWorldService#getGreetings" User-Agent: Axis2 Host: localhost:9090 Content-Length: 271 http://schemas.xmlsoap.org/soap/envelope/";> <_ns_:getGreetings xmlns:_ns_="http://sample/helloworld";> <_ns_:param1>World Here the SOAP-Message send from Eclipse Web Service Explorer: POST http://localhost:9090/axis2/services/HelloWorldComponent/HelloWorldService HTTP/1.1 Host: localhost:9090 Content-Type: text/xml; charset=utf-8 Content-Length: 337 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: IBM Web Services Explorer Cache-Control: no-cache Pragma: no-cache SOAPAction: "HelloWorldService#getGreetings" Connection: close http://schemas.xmlsoap.org/soap/envelope/"; xmln s:q0="http://sample/helloworld"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xml ns:xsi="http://www.w3.org/2001/XMLSchema-instance";> ghdfzh For me it looks like the soap-header is causing the problem. What do you think? Could ws-binding configured in a way not to add the header to the SOAP message? Thanks, Philipp -Ursprüngliche Nachricht- Von: Simon Nash [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 13. November 2007 12:32 An: tuscany-user@ws.apache.org Betreff: Re: SOAPProcessingException after update from SCA 0.99 to 1.0 I can think of a few changes between 0.99 and 1.0 that could affect interoperability, but I don't think any of these would come into play for the scenario described here. For dynamically generated WSDL, a few changes were made to the generation algorithm that affect methods with no arguments and/or a void result. However, the helloworld-ws-reference sample uses statically created WSDL, not dynamically generated WSDL. For callbacks and conversations, the wire protocol used to pass the necessary information over Web services changed between 0.99 and 1.0. However, the helloworld-ws-reference sample does not use callbacks or conversations. This error seems to indicate that the Axis2/C service received a SOAP request containing some unexpected XML data. Can you run with a TCP monitor and post the SOAP messages that are being exchanged? Simon Nash Simon Laws wrote: > On Nov 11, 2007 4:52 PM, Philipp Konradi <[EMAIL PROTECTED]> wrote: > > >>Hi all, >> >>after upgrading from Tuscany SCA Java v0.99 to 1.0 one of my sample >>applications has broken. >>The app is pretty simple: a Java SCA service calls a Native SCA service >>via >>Web Services. >>After version upgrade I'm getting a SOAPProcessingException saying "Only >>Characters are allowed here". >> >>Does somebody else experienced something similar? Any explanations what's >>the reason and how to fix/workaround here? >> >>Here some details to the app: >>The Java SCA service is actually the helloworld-ws-reference sample. >>The Native SCA service is a simple helloworld implementation in C++ >>deployed >>in Axis2/C. >> >>The call makes it actually to Axis2/C but then Axis2/C returns a SOAP >>fault >>message. >> >>Here the axis2c log: >> >>[Sun Nov 11 16:07:29 2007] [info] Starting HTTP server thread >>[Sun Nov 11 16:12:34 2007] [debug] >>..\..\modules\core\transport\http\http_worker.c(206) Client HTTP version >>HTTP/1.1 >>[Sun Nov 11 16:12:34 2007] [debug] >>
Re: SOAPProcessingException after update from SCA 0.99 to 1.0
Hi all, Yes that matches also to what I've seen right now from further analysing the SOAP-messages sent. I'll post the results here, just for the case it might be of help while analyzing and fixing the problem: That's the return fault-soap-message from Axis2/C: http://schemas.xmlsoap.org/soap/envelope/";> http://www.w3.org/2005/08/addressing";> http://www.w3.org/2005/08/addressing/fault 3b31d7c1-69ae-476e-89e1-daf4b555b744 soapenv:Sender wsa:InvalidAddressingHeader wsa:InvalidCardinality A header representing a Message Addressing Property is not valid and the message cannot be processed http://www.w3.org/2005/08/addressing";> wsa:Action After the following modification of the SOAP-Message sent to Axis2/C the call went successfully (Eclipse Web Service Explorer did a good job allowing manual modification of soap-messages sent :-)): http://schemas.xmlsoap.org/soap/envelope/"; xmlns:q0="http://sample/helloworld"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://www.w3.org/2005/08/addressing "> http://localhost:9090/axis2/services/HelloWorldComponent/HelloWorldService ghdfzh The error is fixed already (message schema is satisfied) if I modify the header to: ... http://www.w3.org/2005/08/addressing";> http://localhost:9090/axis2/services/HelloWorldComponent/HelloWorldService http://www.w3.org/2005/08/addressing";> http://localhost:9090/axis2/services/HelloWorldComponent/HelloWorldService ... Although this leads to another error occuring later in the process since this change seems not to make sense to SCA-ws-binding module in Axis2/C. Thank you guys for your support! I appreciate that a lot! Philipp -Ursprüngliche Nachricht- Von: Simon Nash [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 14. November 2007 16:35 An: tuscany-user@ws.apache.org Betreff: Re: SOAPProcessingException after update from SCA 0.99 to 1.0 Philipp, Thanks for this information. There are two problems here. 1. The WS-Addressing To header should not be added unless callbacks or conversations are in use. Your test does not use callbacks or conversations, so this header should not be present. 2. The format of the WS-Addressing To header is wrong. This is a known problem in Tuscany SCA Java 1.0 and 1.0.1: see TUSCANY-1849. Axis2/C is trying to parse the WS-Addressing header according to the WS-Addressing spec. Because the header format is wrong, this parsing fails and you get the error message. I don't think there is any workaround. We need to fix TUSCANY-1849 urgently to resolve this problem. As part of this fix, we should also avoid sending WS-Addressing headers unless they are needed for callbacks or conversations. Simon Simon Laws wrote: > On Nov 14, 2007 12:26 PM, Philipp Konradi <[EMAIL PROTECTED]> wrote: > > >>Hi, >> >>thank you guys very much for taking this issue on. >>I've done tcpmonitoring as suggested and I noticed that the 1.0 runtime >>was >>sending additionally a Header with some Address element. >> >>Here the SOAP-Message send from 1.0 runtime: >>POST /axis2/services/HelloWorldComponent/HelloWorldService HTTP/1.1 >> Content-Type: text/xml; charset=UTF-8 >> SOAPAction: "HelloWorldService#getGreetings" >> User-Agent: Axis2 >> Host: localhost:9090 >> Content-Length: 508 >> >>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> >> >> http://www.w3.org/2005/08/addressing";> >> > xmlns:wsa=" >>http://www.w3.org/2005/08/addressing";> >> >>http://localhost:9090/axis2/services/HelloWorldComponent/HelloWorldService >>
JMS Binding: How to set the xml-format flag?
Hi, with the new 1.1 release of SCA Java the implementation of JMS Binding evolved to support XML-based JMS messages as SCA specs defines. What's really great. Now JMS binding supports two kinds of JMS messages XML-based and Java-Object-serialized ones. What I was wondering now is how the according xml-format flag can be set? Can it be done in the composite's JMS Binding configuration? Any help is very much appreciated, Philipp
Re: JMS Binding: How to set the xml-format flag?
Hi ant, thank you for your quick repsonse. > I'd really like to come up with a better way to make this easier, how about > we add a new Tuscany specific attribute to the JMS binding SCDL to control > this, say format="XML|Object", with the default being format="XML" so the > current functionality remains if you don't define this. So that would look > like: I think having such an option would ease the usage of this Tuscany JMS Binding feature. Thinking of alternatives: I'm really not an expert in Tuscany's databinding capabilities but what do you think about configuring it via databinding? e.g. having of http://tuscany.apache.org/xmlns/sca/databinding/1.0"; name=" org.apache.tuscany.sca.databinding.javabeans.SimpleJavaDataBinding" /> would mean that JMS messages contain serialized Java-Objects? Regards, Philipp -Ursprüngliche Nachricht- > Von: ant elder [mailto:[EMAIL PROTECTED] > Gesendet: Freitag, 15. Februar 2008 09:34 > An: tuscany-user@ws.apache.org > Betreff: Re: JMS Binding: How to set the xml-format flag? > > On Fri, Feb 15, 2008 at 8:08 AM, Philipp Konradi <[EMAIL PROTECTED]> > wrote: > > > Hi, > > > > with the new 1.1 release of SCA Java the implementation of JMS Binding > > evolved to support XML-based JMS messages as SCA specs defines. What's > > really great. > > Now JMS binding supports two kinds of JMS messages XML-based and > > Java-Object-serialized ones. > > > > What I was wondering now is how the according xml-format flag can be > > set? Can it be done in the composite's JMS Binding configuration? > > > > Any help is very much appreciated, > > Philipp > > > > > The SCA specs do not define how to do this although it is possible with > the > current Tuscany code, see > http://apache.markmail.org/message/7nvfyxzavua5fypu > > I'd really like to come up with a better way to make this easier, how > about > we add a new Tuscany specific attribute to the JMS binding SCDL to control > this, say format="XML|Object", with the default being format="XML" so the > current functionality remains if you don't define this. So that would look > like: > > > > > > > > > Would this do what you need? Anyone else have comments or alternative > suggestions? > >...ant >
