[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-4481) Failed to find the component with the GWT integration.

Ameeth Paatil (JIRA) jira-events at lists.jboss.org
Tue Nov 24 23:23:29 EST 2009

     [ https://jira.jboss.org/jira/browse/JBSEAM-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ameeth Paatil updated JBSEAM-4481:

    Priority: Major  (was: Minor)

> Failed to find the component with the GWT integration.
> ------------------------------------------------------
>                 Key: JBSEAM-4481
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4481
>             Project: Seam
>          Issue Type: Bug
>          Components: GWT
>    Affects Versions: 2.2.0.GA
>         Environment: Windows
>            Reporter: Ameeth Paatil
> Issue found in the GWTService class method RPC_invokeAndEncodeResponse. The method finds the incorrect interface name with the at the line. String serviceIntfName = serviceMethod.getDeclaringClass().getName();
> This happens in the below scenario.
> 1. Create base service interface say X.java which has method sayHello().
> 2. Create two other serviceInterfaces Y.java and Z.java which extends the X.java.
> 3. Create two seam components for these interfaces.
> then when you do remote method invocation for "sayHello" for the Y or Z interface it will try to search the component with interface name X insted it should have bean called for the Y or Z. depending on the service method invoked.
> The solution to this may be include the method name as well as interface name in SeamRPCRequest and do not use the interface name from the method object as it's returning the base interface.

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


More information about the seam-issues mailing list