Any clues about a fix? This issue is pretty crucial for AND necessary for
deploying a JAX-WS based web service. Any alternatives to the flawed Jar file
are also welcome.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220174#4220174
Reply to the post :
http:
I've already found those posts, but none of them propose an actual solution.
Any ideas, or did I just miss the point of the two posts?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220084#4220084
Reply to the post :
http://www.jboss.org/index.html?module=b
Hi all,
I am encountering a very odd problem when deploying a vanilla EJB 3.0 web
service using the JAX-WS on JBoss 5.0.1 from NetBeans 6.5. The problem also
occurs on JBoss 5.0.0, so upgrading from the older version would not fix the
problem for me.
I have created the following test web ser
@jakiran: I already tried the @Service extension for EJB 3.0 in JBoss but it
didn't work out properly.
@wolfc: Will this bug be fixed in the next release of JBoss?
As such, I am open to any other design solution to this problem. I am not
saying that my @PostConstruct/@PreDestroy solution with
Hi,
I have started deploying an internal Java EE ejb application of ours in the new
JBoss AS 5.0.0CR2, due to the fact that -- as far as I can see -- JBoss 4.x
does not support the complete set of features in EJB 3.0. The application was
previously developed for Glassfish, but we've decided mo
