[seam-issues] [JBoss JIRA] Moved: (SEAMREMOTING-2) Remoting interface generation problem

[Shane Bryzak (JIRA)]

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

Shane Bryzak moved JBSEAM-3565 to SEAMREMOTING-2:
-------------------------------------------------

        Project: Seam Remoting  (was: Seam)
            Key: SEAMREMOTING-2  (was: JBSEAM-3565)
    Component/s:     (was: Remoting)


> Remoting interface generation problem
> -------------------------------------
>
>                 Key: SEAMREMOTING-2
>                 URL: https://jira.jboss.org/jira/browse/SEAMREMOTING-2
>             Project: Seam Remoting
>          Issue Type: Bug
>            Reporter: Andy Siu
>            Assignee: Shane Bryzak
>
> There is a problem about the caching mechanism of generating remote interface for ajax call.
> at
> public void generateComponentInterface(Set<Component> components, OutputStream out, Set<Type> types)
> The generated interface is cached in interfaceCache. However, when passing more than one component at the same time, there may be problem.
> E.g.
> seam/resource/remoting/interface.js?A&B
> where both A and B contain a type C
> A->C will be cached with the name A
> but only B will be cached with the name B (C will be skipped as it is already generated in A)
> when another page only calls seam/resource/remoting/interface.js?B
> C will be missed as the cached B does not contains C
> I've make a workaround by passing a new HashSet<Type>() into appendComponentSource everytime
> appendComponentSource(bOut, c, new HashSet<Type>());

-- 
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