Chris,
I just took a quick look at what you sent in jira TUSCANY-646. I couldn't find
anything wrong off the bat. There has been a lot of bring up in this web
services area in the last few days. I will say the web.xml you have for a server
will need changing. The best code model to look at right now in svn is
tuscany\java\samples\sca\helloworldws for the server and
tuscany\java\samples\sca\helloworldwsclient for the client.
As far as complex types and their databinding, *currently* SDO is hardwired in.
This area (DataBinding Framework) is currently being worked on and the initial
plans are to have sometime in the future besides SDOs, axiom(this should be
there), castor, jaxb, and xmlbeans. This is flexible and more databindings can
be implemented beyond those. The goal is to ultimately make this transparent to
the component implementer (and to other system extensions too)
So in short, right now we only support SDO's and primitive types.
------------------------------------------------------------------------
For the client :
Run "mvn" in "distribution\sca\standalone" to create a standalone build for SCA
Unzip "target\standalone-1.0-SNAPSHOT-bin.zip" to "<testdir>"
copy all the jars from
samples\sca\helloworldws\target\sample-helloworldws-1.0-SNAPSHOT\WEB-INF\lib" to
"<testdir>\boot" (to get axis jars)
copy "axis2-1.0-SNAPSHOT.jar" and "databinding-sdo-1.0-SNAPSHOT.jar" from
samples\sca\helloworldws\target\sample-helloworldws-1.0-SNAPSHOT\WEB-INF\lib" to
"<testdir>\extension" (to get axis binding)
Run the following command to launch the application
java -jar <testdir>\bin\launcher.jar --classpath <your sca application jar>
----------------------------------------------------------------------------
For the web server we are testing with tomcat 5.5.17
Build your sca application putting all jars WEB-INF/lib (maven should do this
by default)
Just note this deployment is also an area that is very actively changing. So
don't make hard effort to commit this to memory! :-)
Chris Wall wrote:
Hey Raymond. Let's for the speedy response.
1.) http://issues.apache.org/jira/browse/TUSCANY-646 (includes wsdl,
web.xml, default.scdl, and client code)
2.) Driver?
----- Original Message ----- From: "Raymond Feng" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: August 18, 2006 2:02 PM
Subject: Re: binding.ws (xmlbeans) sending empty soap message
Hi, Chris.
Thank you for reporting this. We would appreciate if you can provide us
more information about the problem.
1) The wsdl and scdl files were removed by the apache mailing list.
Would you please open a JIRA issue and attach the files there.
(http://issues.apache.org/jira/browse/TUScany).
2) Which driver are you using? Can you attach the client code as well?
Thanks,
Raymond
----- Original Message ----- From: Chris Wall
To: [email protected]
Sent: Friday, August 18, 2006 11:49 AM
Subject: binding.ws (xmlbeans) sending empty soap message
My web service is receiving empty soap requests from my Tuscany web
service client. See messages below. Is additional configuration
required to use binding.ws with XMLBeans binding? See attached wsdl,
web.xml, and default.scdl.
Soap request sent via Axis2 generated (Wsdl2Java) classes:
** S T A R T R E Q U E S T **
POST /ws_medrec/MedRecWebServices
SOAPAction: urn:getString
User-Agent: Axis2
Host: localhost:7001
Transfer-Encoding: chunked
Content-Type: text/xml; charset=UTF-8
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapen
v:Header /><soapenv:Body><getString
xmlns="http://www.bea.com/medrec"><str>hello</str></getString></soapenv:Body></soapen
v:Envelope>
** E N D R E Q U E S T **
Soap request sent via binding.ws:
** S T A R T R E Q U E S T **
POST /ws_medrec/MedRecWebServices
SOAPAction: ""
User-Agent: Axis2
Host: localhost:7001
Content-Length: 167
Content-Type: text/xml; charset=UTF-8
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapen
v:Header /><soapenv:Body /></soapenv:Envelope>
** E N D R E Q U E S T **
Thoughts/Suggestions?
-Chris
------------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]