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 132874 - Building EJB module with stateless session bean as webservice on WL ignores wsgen
Summary: Building EJB module with stateless session bean as webservice on WL ignores w...
Status: RESOLVED WORKSFORME
Alias: None
Product: webservices
Classification: Unclassified
Component: JAX-WS (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker with 1 vote (vote)
Assignee: Denis Anisimov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-15 12:24 UTC by msmall
Modified: 2012-04-11 07:23 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description msmall 2008-04-15 12:24:03 UTC 
When building an EJB3 Module on Weblogic 10MP1 which includes a stateless session bean that is also exposed as a web
service, the wsgen task is not called.  After further investigation, it seems that jax-ws-build.xml is generated for the
ejb module, but the build-impl.xml does not reference this as is the case with a web application module.  Web
application modules work properly.

A workaround is to add the ant task manually into build.xml at "-post-compile" to call the wsgen build task which is in
the jax-ws-build.xml file.

To reproduce:

1)  New EJB module
2)  Set Weblogic 10 as the server
3)  Create a web service.  This should create a stateless session bean automatically.
4)  Add a dummy operation that does nothing just to keep the ide happy.
5)  Create EAR module and add the EJB module to this.
6)  Build and deplo the EJB module/EAR

an exception is thrown at deploy time that states that the session bean wsgen generated class cannot be found.
Comment 1 Lukas Jungmann 2008-04-17 19:40:54 UTC 
sth like this is already filed somewhere, I think... will try to find it.

Anyway this belongs somewhere between websvc support and weblogic plugin (ws expects that wl plugin will return
appropriate stuff from J2eePlatform.isToolSupported(String)...)
Comment 2 Petr Hejl 2008-08-28 09:56:03 UTC 
Is it only the missing jax-ws-build.xml the only reason? Perhaps belongs to websvc.
Comment 3 Milan Kuchtiak 2008-08-28 13:59:59 UTC 
In this case IDE expects JSR109 is supported by the server but likely it is not.
(it's the same as for GlassFish V2)

WS Support should detect if Weblogic supports JSR109 deployment or not.

wsgen targets are generated all the time, but build-imp.xml references those targets only in case JSR109 isn't supported.
This can be fixed in WS Stack implementation for WebLogic.
Comment 4 Milan Kuchtiak 2008-11-19 14:43:09 UTC 
JSR109 should be disabled for unknown server types.
Comment 5 Denis Anisimov 2011-10-07 12:11:01 UTC 
Current implementation of JAX-WS stack in WL always returns true for 
JSR109 feature.
JAX-WS stack should be refactored in the same way as JAX-RS stack support.
The fix of this issue  should be a consequence this refactoring.
Comment 6 Denis Anisimov 2012-04-11 07:23:03 UTC 
I'm not able to reproduce it with WL10.3.
JAX-WS stack is redone in 7.2 dev.