Hi,
On 10/13/2011 03:26 PM, Rostislav Svoboda wrote:
Hi guys.
I have problem with AS7 usability. I tried to deploy jar file with WS endpoint defined in
EJB. I used standalone server without any additional configuration.
{code}
[standalone@localhost:9999 /] deploy
/home/rsvoboda/svn/jbossws-cxf-4.0.0.Beta6/modules/testsuite/shared-tests/target/test-libs/jaxws-benchmark-datatypes-ejb3.jar
'jaxws-benchmark-datatypes-ejb3.jar' deployed successfully.
{code}
There was no error in deployment and I expected to have endpoint accessible. But it
wasn't because WS subsystem is enabled only in -preview.xml profile. My deployment was
processed only by EJB subsystem.
I would expect something like:
{code}
'jaxws-benchmark-datatypes-ejb3.jar' deployed successfully.
WARN: WS subsystem is not enabled.
{code}
This is general issue, basically unresolved dependencies due to annotations only are not
detected.
I actually partially misled Rostislav on this on IRC - sorry. Currently,
jaxws api are added to any deployment, given a jaxws client can live
everywhere. They're part of javaee api after all.
We could probably figure out a way to have a DUP for checking for the
existence of @WebService annotation and print a warning if the
webservices subsystem is not there.
This said, I believe the mentioned silent behaviour is still an issue in
some cases; for instance when having a @Foo annotated class in a given
deployment which does not depend on the module providing Foo.
--
Alessio Soldano
Web Service Lead, JBoss