You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Reynardine <re...@loveable.com> on 2003/06/19 20:08:03 UTC
Lost service method parameter names when deploying
Hello,
I have deployed my new service under Tomcat/Axis. The problem is that all my helpful parameter names have been lost during the transformation. My original code had useful names like "mYearofBirth" "CountryOfBirth" but these have been transformed into
names like (String in1, String in2)...
How can I make sure my parameter names are retained when I use Java2WSDL and WSDL2Java ?
I tried compiling all my classes with debug information first to encourage Axis to do this but it did not work.
As a last resort, I could manually edit the stubs generated by Axis, put back my parameter names and then redeploy, but is there a better way ?
Any help gratefully received.
Rey.
--
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup
CareerBuilder.com has over 400,000 jobs. Be smarter about your job search
http://corp.mail.com/careers
Re: Lost service method parameter names when deploying
Posted by James Black <jb...@ieee.org>.
Chris wrote:
>Not on interfaces . . . even with -g the information doesn't get saved. What
>I was wondering is even if you say -g when you build, do you have to say -i
>when you run Java2Wsdl.
>
When you compile the implementation stub, which implements your
interface, then that should be compiled with the -g flag, then when you
use java2wsdl use -i.
Here is a part of my line:
java org.apache.axis.wsdl.Java2Wsdl --implClass
edu.usf.acomp.axis.AxisLMSServerStub iT 1.2 edu.usf.acomp.axis.AxisLMSServer
AxisLMSServer is my interface and AxisLMSServerStub is the
implementation class.
--
"We do not lose our identity in our relations with others; in part, at least, we achieve our identity by those relations." Tony Blair, 1993
RE: Lost service method parameter names when deploying
Posted by Chris <cl...@trefs.com>.
Not on interfaces . . . even with -g the information doesn't get saved. What
I was wondering is even if you say -g when you build, do you have to say -i
when you run Java2Wsdl.
- C
-----Original Message-----
From: James Black [mailto:jblack@ieee.org]
Sent: Thursday, June 19, 2003 3:09 PM
To: axis-user@ws.apache.org
Subject: Re: Lost service method parameter names when deploying
Chris wrote:
>I suppose I never actually tried -i. I was using Java2Wsdl on an interface,
>in which case -i doesn't help, but is -i required to retain param names
from
>code built with debug info? If so, then perhaps that was Rey's problem (and
>future posters!). If that's the case then I'll know not to pounce on every
>"Param Name Retention" question with the No Debug Info In Interfaces spiel.
>
You just have to remember to use the -g flag when you compile the
implementation source, else it won't work.
--
"We do not lose our identity in our relations with others; in part, at
least, we achieve our identity by those relations." Tony Blair, 1993
Re: Lost service method parameter names when deploying
Posted by James Black <jb...@ieee.org>.
Chris wrote:
>I suppose I never actually tried -i. I was using Java2Wsdl on an interface,
>in which case -i doesn't help, but is -i required to retain param names from
>code built with debug info? If so, then perhaps that was Rey's problem (and
>future posters!). If that's the case then I'll know not to pounce on every
>"Param Name Retention" question with the No Debug Info In Interfaces spiel.
>
You just have to remember to use the -g flag when you compile the
implementation source, else it won't work.
--
"We do not lose our identity in our relations with others; in part, at least, we achieve our identity by those relations." Tony Blair, 1993
RE: Lost service method parameter names when deploying
Posted by Chris <cl...@trefs.com>.
Mike -
I suppose I never actually tried -i. I was using Java2Wsdl on an interface,
in which case -i doesn't help, but is -i required to retain param names from
code built with debug info? If so, then perhaps that was Rey's problem (and
future posters!). If that's the case then I'll know not to pounce on every
"Param Name Retention" question with the No Debug Info In Interfaces spiel.
- C
-----Original Message-----
From: Michael Woinoski [mailto:michaelw@pineneedleconsulting.com]
Sent: Thursday, June 19, 2003 1:58 PM
To: axis-user@ws.apache.org
Subject: Re: Lost service method parameter names when deploying
I've been using the Java2WSDL's "-i" option, and it retains the parameter
names
in the WSDL. "-i" takes the fully-qualified implementation class name as an
argument (you still need to pass the interface as an argument to Java2WSDL).
No
need to hand edit the WSDL.
-i, --implClass
optional class that contains implementation of methods in
class-of-portType.
The debug information in the class is used
to obtain the method parameter names, which are used to set
the WSDL part names.
(from AXIS_HOME/docs/reference.html#Java2WSDL)
Cheers,
Mike
Chris wrote:
>
> Hi Rey,
>
> I went through this last week on the list. You can check the archives if
you
> like, for subject line="Preserving param names in WSDL". My issue, and
> perhaps yours, is that parameter names for interface methods don't get
saved
> along with the debug info. Same goes for abstract methods in an abstract
> class, by the way.
>
> If you want parameter names to be preserved, looks like you have the
> following options:
>
> 1. Hand edit the WSDL to add them in
> 2. Hand edit the WSDD (I forget the syntax but you can find it in the
> archives)
> 3. Screw Java2WSDL, and build your interfaces using an WSDL editor rather
> than a Java editor.
>
--
Mike Woinoski Pine Needle Consulting
mailto:michaelw@pineneedleconsulting.com
Re: Lost service method parameter names when deploying
Posted by Michael Woinoski <mi...@pineneedleconsulting.com>.
I've been using the Java2WSDL's "-i" option, and it retains the parameter names
in the WSDL. "-i" takes the fully-qualified implementation class name as an
argument (you still need to pass the interface as an argument to Java2WSDL). No
need to hand edit the WSDL.
-i, --implClass
optional class that contains implementation of methods in
class-of-portType.
The debug information in the class is used
to obtain the method parameter names, which are used to set
the WSDL part names.
(from AXIS_HOME/docs/reference.html#Java2WSDL)
Cheers,
Mike
Chris wrote:
>
> Hi Rey,
>
> I went through this last week on the list. You can check the archives if you
> like, for subject line="Preserving param names in WSDL". My issue, and
> perhaps yours, is that parameter names for interface methods don't get saved
> along with the debug info. Same goes for abstract methods in an abstract
> class, by the way.
>
> If you want parameter names to be preserved, looks like you have the
> following options:
>
> 1. Hand edit the WSDL to add them in
> 2. Hand edit the WSDD (I forget the syntax but you can find it in the
> archives)
> 3. Screw Java2WSDL, and build your interfaces using an WSDL editor rather
> than a Java editor.
>
--
Mike Woinoski Pine Needle Consulting
mailto:michaelw@pineneedleconsulting.com
RE: Lost service method parameter names when deploying
Posted by Chris <cl...@trefs.com>.
Hi Rey,
I went through this last week on the list. You can check the archives if you
like, for subject line="Preserving param names in WSDL". My issue, and
perhaps yours, is that parameter names for interface methods don't get saved
along with the debug info. Same goes for abstract methods in an abstract
class, by the way.
If you want parameter names to be preserved, looks like you have the
following options:
1. Hand edit the WSDL to add them in
2. Hand edit the WSDD (I forget the syntax but you can find it in the
archives)
3. Screw Java2WSDL, and build your interfaces using an WSDL editor rather
than a Java editor.
I've opted for door #3, though I did run Java2WSDL initially to get me
started. I've been using CapeClear as a WSDL editor. You have to know what
you're doing, for example if you break dependencies within your WSDL file it
won't stop you, so being completely clueless about WSDL can be a problem.
(I'm 95% clueless and it's been a problem for me!) But it's a decent editor,
and so far the process has worked for me.
Good luck,
Chris
-----Original Message-----
From: Reynardine [mailto:reynardine@loveable.com]
Sent: Thursday, June 19, 2003 1:08 PM
To: axis-user@ws.apache.org
Subject: Lost service method parameter names when deploying
Hello,
I have deployed my new service under Tomcat/Axis. The problem is that all my
helpful parameter names have been lost during the transformation. My
original code had useful names like "mYearofBirth" "CountryOfBirth" but
these have been transformed into
names like (String in1, String in2)...
How can I make sure my parameter names are retained when I use Java2WSDL and
WSDL2Java ?
I tried compiling all my classes with debug information first to encourage
Axis to do this but it did not work.
As a last resort, I could manually edit the stubs generated by Axis, put
back my parameter names and then redeploy, but is there a better way ?
Any help gratefully received.
Rey.
--
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup
CareerBuilder.com has over 400,000 jobs. Be smarter about your job search
http://corp.mail.com/careers