[
https://issues.apache.org/jira/browse/TUSCANY-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
耿韶光 updated TUSCANY-1454:
-------------------------
Attachment: Tuscany.0717.rar
Hi, I explored Tuscany java sca in an eclipse workspace, expand my attachment
you will see this workspace. I deleted some big metadata and class files, so
please rebuild all the content first, and run the "binding.ws" from eclipse's
run::HelloWorldServer.
To simplify the test, I created a test plan in jakarta-jmeter, you could create
a "SOAP/XML-RPC Request" and write the soap as:
<soap:Envelope
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
xmlns="http://helloworld";>
<soap:Body>
<getGreetings>
<name>xSSSSSSSSSx</name>
<age>200</age>
</getGreetings>
</soap:Body>
</soap:Envelope>
First you run the jmeter-test, the soap will be responded correctly, but will
not for the following.
Change the wsdl and java files inside ws-service project, to find out the
difference.
To trace the class, just set break point in the Tuscany sources in other
projects.
Tuscany source code of this workspace is the SVN files at Jul.17.
> binding.ws malfunction with customer data types
> -----------------------------------------------
>
> Key: TUSCANY-1454
> URL: https://issues.apache.org/jira/browse/TUSCANY-1454
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Axis Binding Extension
> Affects Versions: Java-SCA-Next
> Environment: winXP, java5, sca java svn
> Reporter: 耿韶光
> Attachments: Tuscany.0717.rar
>
>
> I was working with Tuscany's binding.ws these two days, I established a
> service provider. I found that if the element type is base types(xsd type
> such as int, string), it worked find.
> Since I remember a mail in the list has metiond complexTypes doesn't work
> some what.
> So I tried this out, and, it was OOOO. The service just worked the first time
> it was accessed, then I refused to work any more.
> I traced the code for some depth, I found the error came from a dom instance
> was always held, and the same dom serves all the following request, then a
> error checking method produces a Exception.
> I will look into these code next monday, for the time being, I cry this out,
> wish some one could devote.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
