This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 61124 - [50cat] generated WSDL contains incorrect operation parameter names
Summary: [50cat] generated WSDL contains incorrect operation parameter names
Alias: None
Product: webservices
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker with 3 votes (vote)
Assignee: Milan Kuchtiak
: 60496 66739 71276 (view as bug list)
Depends on:
Reported: 2005-07-19 16:03 UTC by athompson
Modified: 2006-06-06 15:13 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description athompson 2005-07-19 16:03:03 UTC
jdk 1.5 (project jdk 1.4)
daily 18 july 2005
sun app server 8.1.02 Q2

you can go through the Netbeans j2ee tutorial and get this problem as well.

1. create a web project
2. right-click the project node-->New-->Web Service
3. fill in the name and package
4. right-click the web service node-->New-->Operation
5. fill in the name
6. add various parameters; remember their names
7! build the project. the generated WSDL contains the wrong parameter names for
the operation.
Comment 1 Milan Kuchtiak 2005-08-05 08:49:41 UTC
The parameter names are generated in a generic way :

I agree they should correspond with names given by user, but I don't see this is
a P2.
Comment 2 athompson 2005-08-05 21:44:08 UTC
i dissagree. you don't generate the WSDL for your use, you generate it for the
people who want to create a client. it makes things extremely problematic if
both they and you have no way of knowing which parameter is which in the WSDL
(and thus their generated stubs), and if the WSDL does not match the documentation.
Comment 3 Lukas Jungmann 2005-10-14 16:24:57 UTC
*** Issue 66739 has been marked as a duplicate of this issue. ***
Comment 4 Lukas Jungmann 2005-10-18 15:00:32 UTC
*** Issue 60496 has been marked as a duplicate of this issue. ***
Comment 5 clever 2005-10-20 15:52:16 UTC
I agree with athompson. This should be fixed. WSDL is meant to make sense, not
just be 'used'. It's like a code generator that let's a user name UI elements
"txtName", but in code represents it as "string1".
Gets my vote. I'm also changing to read [50cat] to get on the radar.
Comment 6 Lukas Jungmann 2005-10-20 19:17:53 UTC
AFAIK we cannot do much for this, because the WSDL is generated by wscompile
which is a part of JAX-RPC library.
Comment 7 clever 2005-10-20 19:54:54 UTC
I submitted a bug against JAX_RPC.  I can only hope this gets fixed.  I think
it's an amateur mistake to let the wscompile tool clutter WSDL files for so long.

Perhaps the guys working for Sun can shed some light into the justification and
why it's not fixed already.  I've used reflection... I know parameter names can
be read in. Why doesn't the wscompile tool do it?

I can only hope for a fix. :(
VS 2003 and Whidby both do it.
Comment 8 clever 2005-10-28 15:32:41 UTC
How nice. Sun accepted my bug:
Thank you for reporting this issue.

We have determined that this report is a new bug and entered the bug into our
internal bug tracking system under Bug Id: 6342817.

You can monitor this bug on the Java Bug Database at

I will be on this like hot cake!  Hopefully they can create a fix soon and we
can sneak it into 5.0. { insert evil grin }

I still think it's lame that they shipped with something as silly as useless
(string_1, long_2, int_3, ...).. How '80s. :)
Comment 9 Petr Blaha 2005-12-08 10:31:16 UTC
Since the issue isn't in NetBeans, marking as WONTFIX.
Comment 10 Lukas Jungmann 2006-01-11 20:44:10 UTC
*** Issue 71276 has been marked as a duplicate of this issue. ***
Comment 11 Lukas Jungmann 2006-03-20 00:28:47 UTC
Reopening this one because this can be fixed on our side at least for JAX-WS 2.0
based web services using javax.jws.WebParam annotation.

We can generate eg. following code when adding websvc operation:

    public String sayHello(@WebParam(name="s") String s) {
        // TODO implement operation 
        return null;
Comment 12 Lukas Jungmann 2006-05-16 22:50:32 UTC
fixed in 5.5 (dailies/beta)
Comment 13 Lukas Jungmann 2006-06-06 15:13:17 UTC