I will have to look at it again, last time I looked I got the impression
the deployment scanner was only scanning once so did not pick up a jar
dropped in after JBoss was started.
For archives in deploy when JBoss was started I think they were deployed
before the JBossWS deployer so were not deployed as web services,
Regards,
Darran Lofthouse.
On Thu, 2007-01-11 at 14:51 +0100, Thomas Diesler wrote:
I take your word for it. Do we need to fix that now?
Darran Lofthouse wrote:
> I just wanted to check if this is a known problem, I have not looked
> closely at it yet.
>
> If I copy a jar to the deploy folder containing an EJB3 web service the
> EJB is deployed but it is not deployed as a web service when JBoss is
> started.
>
> However if I run a test from the testsuite (that uses the same jar) the
> deployment works correctly.
>
> It looks as if the deployment works fine if the main deployer is called
> after JBoss is started but if the jar is deployed during startup JBossWS
> is not involved in the deployment.
>
> Regards,
> Darran Lofthouse.
>
>
> _______________________________________________
> jbossws-dev mailing list
> jbossws-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbossws-dev
>