One would think that if its technically feasible it will be done (in Seam 3 if not in JCDI)
Thanks. I would hope that the Java EE6 committee forces JSR299 into complete integration with Java EE because integration is absolutely critical for its acceptance.
The answer is absolutely yes. This is one of the main goals of the more recent 299 spec revs.
There is a another post on using seam with JAX-WS clients,
JaxWS Client Factory Component
which I'm going to be introducing into a Seam app soon (hope it works!)
It would be nice to be able to do this in CDI?
i.e. inject a jax-ws client service into a CDI beans.
The docs seems to talk about being able to inject CDI beans into a JAX-WS service endpoint but not the other way round.
This is probably dependent on the XML Bean Config Module since the JAX-WS client proxy classes are in most cases deployed in a jar file without the components.xml file that flags to CDI that the jar file contains CDI beans (hence the approach in the link above for Seam 2)
Looking at the CDI API documentation it looks like I should be doing
Not sure if this will work
Which is tempting as I don't want to have to bind an external web service client resource to JNDI in my container?
CDI doesn't change how @WebServiceRef works in any way, so anything you can do with it, you should be able to use in CDI.