-
1. Re: Calling switchyard service from Jax-ws EJB crashes
kcbabo Aug 3, 2012 2:33 PM (in response to khanser)1 of 1 people found this helpfulI haven't tried using @Inject to provide a SY reference inside a JAX-WS endpoint so I can't say for sure. If you deploy a JAX-WS endpoint along with a SY app in a WAR, both pieces should have access to the same CDI Bean Manager. The next question would be whether the JAX-WS endpoint is available for injection through our CDI extension. You say you got an error, can you post the details and/or an app to reproduce the problem?
-
2. Re: Calling switchyard service from Jax-ws EJB crashes
khanser Aug 6, 2012 6:16 AM (in response to kcbabo)Okay now it works, I had the switchyard-deploy-webapp at 0.6 snapshot instead of using the ${switchyard.version} variable pointing to 0.5
-
3. Re: Calling switchyard service from Jax-ws EJB crashes
kcbabo Aug 6, 2012 8:26 AM (in response to khanser)Are you deploying on JBoss AS 7? If so, you don't need the switchyard-deploy-webapp dependency at all. Here's an example of an app which is a war deployment:
https://github.com/jboss-switchyard/quickstarts/tree/master/demos/orders
If you're not deploying to JBoss AS 7, then I'd be interested to know what your target platform is. There may be a bug here in 0.6 if it doesn't work with the current snapshot.
~ keith
-
4. Re: Calling switchyard service from Jax-ws EJB crashes
khanser Aug 6, 2012 9:14 AM (in response to kcbabo)Really? Wow, last friday was mayhem at my workspace but now everything is working fine. I'm using JBOSS7 and today as I got to the office i build a new project from scratch with JEE6 full profile and I realized about the deployer version I changed it and tested my app. Everything points to me as I did something to screw the app last friday for good. Sorry for wasting your time and thanks!