[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3152) Remoting does not work with qualified component names
Shane Bryzak (JIRA)
jira-events at lists.jboss.org
Tue Aug 12 22:46:40 EDT 2008
[ https://jira.jboss.org/jira/browse/JBSEAM-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12424678#action_12424678 ]
Shane Bryzak commented on JBSEAM-3152:
--------------------------------------
Oh, I should add that this issue only affected action components. DTO components already had the dots in their fully qualified type names replaced with the $ sign.
> Remoting does not work with qualified component names
> -----------------------------------------------------
>
> Key: JBSEAM-3152
> URL: https://jira.jboss.org/jira/browse/JBSEAM-3152
> Project: Seam
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 2.0.3.CR1, 2.1.0.A1
> Reporter: Dan Allen
> Assignee: Shane Bryzak
> Fix For: 2.0.3.CR2, 2.1.0.BETA1
>
> Attachments: JBSEAM-3152-branch20-v1.txt
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> Remoting does not escape dots in a component name, thus generating JavaScript that does not run. For instance, if the name of the component is com.example.remoting.componentName, the InterfaceGenerator produces:
> Seam.Remoting.type.com.mydomain.throwaway.manager.prototype.methodName = ...
> Obviously, this isn't going to work. A reasonable quick fix is to replace dots with underscores.
--
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