WSDL2Java creates inconsistent pacakge names if the package name has any
uppercase characters
---------------------------------------------------------------------------------------------
Key: AXIS2-2487
URL: https://issues.apache.org/jira/browse/AXIS2-2487
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: adb
Affects Versions: nightly
Environment: Axis 1.5, Tomcat 5.5, Axis2 1.2 SNAPSHOT , Eclipse 3.2,
WTP 1.5.1, Windows 2003 server
Reporter: Tim Buss
Thik this problem existed in earlier releases also
If you try to generate a Service called say, ExampleService, and use the
namespace to package mapping option " -ns2p <ns1>=<pkg1>[,....] " and you
specify a package name like
myorg.ExamplePackage as in
-ns2p urn:example.namespace=myorg.ExamplePackage
then the "type" code files generated will observe this and create classes in
the package myorg.ExamplePackage but all the "service" code files generated eg:
ExampleService.java
ExampleService.MessgeReceiverInOut.java
ExampleServiceSkeleton.java
ExampleServiceSkeletonInterface.java
ExampleServiceStub.java
have the package name changed to all lower case (ie myorg.examplepackage)
I realize that it is a java convention to use all lowver case for package names
but the code generated should be consistent and should take what the user
gives. This does not seem an appropriate plac eto enforce the pacakge name
convention.
I think the eclipse plugin in 1.1.1 refuses to work if a mixed case package
name is specified which seems wrong. At mose it should issue a warning.
It is probably a "minor" bug really but if you happen to need it to work as I
do, the workaround is somewhat painful and I suspect it's fairly easy to fix.
--
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]
