Thanks for that. Just to see if I have interpreted your post correctly: When you say "Map it to a session bean" -> what do you mean by "it"?
Should I use JBossXB in my session bean which handles the WS invocations and then create entity beans using the java objects generated? I am using java 5 - which cannot interpret annotation tags? Does this mean I can't use JBossXB. So should I use JAXB instead?
The Wiki pages are helpful but I just want to clarify your answer.
Since a session is a valid endpoint for a webservice request, and an entity is not, you need to map the ws request to the session.
Yes, the WS requests are mapped to a session bean and the client can call the WS successfully. Now I want to take the WS params and create entity beans in ejb container. So, should I use Sun's JAXB implementation or JBossXB to translate my WS params into entity beans?
Thanks for your help on this. I would prefer to use a binding and marshalling mechanism rather than parsing the XML into a DOM or use a SAX parser.
I've downloaded the JWSDP 1.6 and will use JAXB to bind XML Schemas to Java classes and unmarshal the WS params using the generated Java classes.
Suggested alternatives to this approach welcomed (if in some way necessary).