[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-2546) Support ejb modules according to JAX-WS 2.1 resp. JSR 181

[ https://jira.jboss.org/jira/browse/JBIDE-2546?page=com.atlassian.jira.plu... ] Juergen Zimmermann updated JBIDE-2546: -------------------------------------- Attachment: testcase-JBIDE-2546.zip JBossWS supports JAX-WS being specified in JSR 181 and JSR 224. For instance you could have a session bean as follows (see also in the attached testcase): @Stateless public class KundenverwaltungBean implements Kundenverwaltung { @EJB private KundenverwaltungDao dao; // methods ... } Such a session bean is part of an EJB module within an EAR. Now you want to expose some methods as a web service and very often have to do some transformations. Therefore, you're going to implement another session bean as a wrapper for the session bean above, and also you may place this new session bean in a new EJB module (see testcase): @WebService(name="Kundenverwaltung", targetNamespace="http://ws.hska.de/kundenverwaltung", serviceName="KundenverwaltungService") @Stateless public class KundenverwaltungServiceBean implements KundenverwaltungService { @EJB private Kundenverwaltung kv; @WebMethod @WebResult(name="kunde") public Kunde findKundeById(@WebParam(name="id") long id) throws ... { final Kunde kunde = kv.findKundeById(Long.valueOf(id)); return kunde; } //... } It would be excellent, if JBossWS Tools could support these steps: * Select a session bean to be exposed as a web service * Mark the methods to be exposed * Generate a new session bean with method wrappers for the selected methods * Optionally provide the possibility to generate the new session bean in a new EJB module. Can you catch my idea? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira