[jbossws-issues] [JBoss JIRA] Commented: (JBWS-1799) Two ejb3s exposed as 2 different web services in the same ear file. Can't have same methods with different parameters..

Heiko Braun (JIRA) jira-events at lists.jboss.org
Tue Oct 16 09:32:03 EDT 2007


    [ http://jira.jboss.com/jira/browse/JBWS-1799?page=comments#action_12382722 ] 
            
Heiko Braun commented on JBWS-1799:
-----------------------------------

>From JAX-WS 2.0 19. April 2006:

3.6.2.1 Document Wrapped:

* Conformance (Default wrapper bean names): In the absence of customizations, the wrapper request bean
class MUST be named the same as the method and the wrapper response bean class MUST be named the
same as the method with a "Response" suffix. The first letter of each bean name is capitalized to follow
Java class naming conventions.
* Conformance (Default wrapper bean package): In the absence of customizations, the wrapper beans pack-
age MUST be a generated jaxws subpackage of the SEI package.


Which means we cannot easily change it.


> Two ejb3s exposed as 2 different web services in the same ear file. Can't have same methods with different parameters..
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBWS-1799
>                 URL: http://jira.jboss.com/jira/browse/JBWS-1799
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: jbossws-1.2.1
>         Environment: Debian etch. 
>            Reporter: Sureshbabu Thyvalappil
>         Assigned To: Richard Opalka
>             Fix For:  jbossws-2.0.2
>
>
> Please look at the url for description. http://www.jboss.com/index.html?module=bb&op=viewtopic&t=116665
> First ejb:
> @WebService(name="UserAccountServiceEndPoint",
>             targetNamespace="namespace1", serviceName="UserAccountService1.0")
> @SOAPBinding(style=SOAPBinding.Style.DOCUMENT,use=SOAPBinding.Use.LITERAL)
> @Stateless
> @WebContext(transportGuarantee="NONE",contextRoot="/svc-useracctv1.0",urlPattern="/UserAccountService1.0")
> public class UserAccountService implements IUserAccountService
> {
>        
>   
>     @WebMethod
>     @TransactionAttribute(javax.ejb.TransactionAttributeType.SUPPORTS)
>     public boolean authenticate(@WebParam(name="username") String aUsername)
>     {
>         boolean ret;
>         .........
>         return ret;
>     }
> }
> interface for 1st ejb:
> @Remote
> public interface IUserAccountService
> {
>         public boolean authenticate(String aUsername);
> }
> second ejb:
> @WebService(name="UserAccountServiceExtEndPoint",
>             targetNamespace="namespaceExt", serviceName="UserAccountServiceExt1.0")
> @SOAPBinding(style=SOAPBinding.Style.DOCUMENT,use=SOAPBinding.Use.LITERAL)
> @Stateless
> @WebContext(transportGuarantee="NONE",contextRoot="/svc-useracctv1.0",urlPattern="/UserAccountServiceExt1.0")
> public class UserAccountServiceExt implements IUserAccountServiceExt
> {
>        
>   
>     @WebMethod
>     @TransactionAttribute(javax.ejb.TransactionAttributeType.SUPPORTS)
>     public boolean authenticate(@WebParam(name="username") String aUsername, @WebParam(name="password") String password)
>     {
>         boolean ret;
>         .........
>         return ret;
>     }
> }
> interface for 2nd ejb:
> @Remote
> public interface IUserAccountServiceExt
> {
>         public boolean authenticate(String aUsername, String aPassword);
> }

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jbossws-issues mailing list