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 190488 - ejb project using wsdl file where "generated sources" seems incorrect
Summary: ejb project using wsdl file where "generated sources" seems incorrect
Status: RESOLVED WORKSFORME
Alias: None
Product: webservices
Classification: Unclassified
Component: Client (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P1 normal (vote)
Assignee: Denis Anisimov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-21 17:52 UTC by toughlittleone
Modified: 2010-11-17 13:22 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description toughlittleone 2010-09-21 17:52:58 UTC
i'm not sure if this is a bug, but it seems really strange. 
1. I create a new project Java EE -> EJB Module
2. I add a web service from WSDL, with a package name and webservice name
3. it creates my package with the class where I enter my code, and the "generated sources" package with all the web service information and bean classes according to that which was in the wsdl file. 

here is the issue: in the "generated sources" package it creates2 packages. 
one for the web service, and the other for the bean classes. this package created for the bean classes looks like "java.test_service" where the package I initially specified in the wizard was test.service. My project builds by deos not deploy on weblogic because the name java.test_service is a security violation. On other projects this isn't like this, so I figured i hit some small issue with netbeans. And it won't let me create my own classes, and disregard the "generated sources" package either, or rename the package and the references in each class. 

please suggest a fix to this issue.
Comment 1 David Konecny 2010-09-29 00:23:33 UTC
I think that package names of generated classes are deduced from given WSDL. But that's just my guess. Could you attach WSDL you are using? Or if that's not possible could you test different WSDL to confirm that they work without problem (eg. try some public ones).
Comment 2 Denis Anisimov 2010-11-17 13:22:57 UTC
No response from the user.
Closing .