Hy Paul,
thank you for your solution.
trying to compile the code using bpelc from ODE it gives me the fllowing error:

The prefix "wsaw" for attribute "wsaw:Action" associated with an element type "wsdl:output" is not bound.

I resolve this problem manually putting "wsaw" URI in the definition tag with other ones. Because my thesis have to generate, compile and deploy automatically web-services using both BPEL and Session Bean, I can't modify manually each WSDL in the deploy process. I ask if there is a way to fix this bug using scrpt's input parameters, perhaps simply introducing another URI in the head, or I have to modify the class code.
This is all, I hope I was more clear then before.
Thank you and regards,
Simone


----- Original Message ----- From: "Paul Fremantle" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, January 31, 2008 2:22 PM
Subject: Re: Java2WSDL


Simone

I'm afraid I don't understand the first problem. Maybe you could
explain once more

As for getting nice names in the WSDL you can
1) Make sure you compile with javac -g which adds the names into the class file
2) Make sure you use classes not interfaces as interfaces don't retain
the parameter names.

Paul

On Jan 31, 2008 12:30 PM, Simone Maletta <[EMAIL PROTECTED]> wrote:



Hi guys,
    I'm an Italian student involved in my master thesis and I'm using
Java2WSDL tool in my thesis.
I automatically generate an enterprise java bean from a graphic description, then using the tool I create the wsdl file for the bean and develope it on
JBoss.
Now I want that a BPEL process developed in ODE can access with a
synchronous invoke to my beans; this the most important think in my project.
While compiling my BPEL process it find a bug into the code:

<wsdl:operation name="cccheck" >
    <wsdl:input xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl
wsaw:Action="urn:cccheck" message="axis2:cccheckMessage">
    </wsdl:input>
    <wsdl:output message="axis2:cccheckResponseMessage"
wsaw:Action="urn:cccheck">
    </wsdl:output>
</wsdl:operation>

in fact it ca be able to parse this because in the <wsdl:output> tag it can
found a reference to wsaw uri.
The only way to solve this problem I found is to put manually the URI just
like an attribute in the <definition> tag.
Now, I ask: may fix this using input parameters or I have to work into your
code? Please send me a response.
Another question: may I choose the mapping parameter into the translation?
There is, if my cean method take a parameter named "CCNum", why into the
translate it is called "param0"? May I cahnge this and getting a direct
mapping using class input parameters?
Thank you for time you spend reanding this mail, regards
Simone



--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

---------------------------------------------------------------------
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]

Reply via email to