[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3152) Remoting does not work with qualified component names
1:20 a.m.
Remoting does not work with qualified component names
-----------------------------------------------------
Key: JBSEAM-3152
URL: http://jira.jboss.com/jira/browse/JBSEAM-3152
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.A1, 2.0.3.CR1
Reporter: Dan Allen
Assigned To: Dan Allen
Fix For: 2.0.3.GA, 2.1.0.BETA1
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:22 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3152) Remoting does not work with qualified component names
[ http://jira.jboss.com/jira/browse/JBSEAM-3152?page=all ]
Dan Allen updated JBSEAM-3152:
------------------------------
Attachment: JBSEAM-3152-branch20-v1.txt
Remoting does not work with qualified component names
-----------------------------------------------------
Key: JBSEAM-3152
URL: http://jira.jboss.com/jira/browse/JBSEAM-3152
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.A1, 2.0.3.CR1
Reporter: Dan Allen
Assigned To: Dan Allen
Fix For: 2.0.3.GA, 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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:33 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3152) Remoting does not work with qualified component names
[ http://jira.jboss.com/jira/browse/JBSEAM-3152?page=comments#action_12420919 ]
Shane Bryzak commented on JBSEAM-3152:
--------------------------------------
I'm surprised this doesn't work - InterfaceGenerator simply calls
Component.forName() for each of the request parameters (i.e. component/class names). Is
the problem that the dot (.) is being URL-encoded or something?
Remoting does not work with qualified component names
-----------------------------------------------------
Key: JBSEAM-3152
URL: http://jira.jboss.com/jira/browse/JBSEAM-3152
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.A1, 2.0.3.CR1
Reporter: Dan Allen
Assigned To: Dan Allen
Fix For: 2.1.0.BETA1, 2.0.3.GA
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:20 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3152) Remoting does not work with qualified component names
[ http://jira.jboss.com/jira/browse/JBSEAM-3152?page=comments#action_12420920 ]
Dan Allen commented on JBSEAM-3152:
-----------------------------------
No, the problem is that JavaScript doesn't official support namespaces. It's just
possible to emulate namespaces by assigning creating a new object for each segment.
Basically, for the example I gave, it would have to be setup as follows:
Seam.Remoting.type.com = new Object();
Seam.Remoting.type.mydomain = new Object();
Seam.Remoting.type.mydomain.throwaway = new Object();
Seam.Remoting.type.mydomain.throwaway.manager = new Object();
Then, you can actually use that "namespace".
It's possible to use a function if we want to allow the dot:
http://weblogs.asp.net/mschwarz/archive/2005/08/26/423699.aspx
Remoting does not work with qualified component names
-----------------------------------------------------
Key: JBSEAM-3152
URL: http://jira.jboss.com/jira/browse/JBSEAM-3152
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.A1, 2.0.3.CR1
Reporter: Dan Allen
Assigned To: Dan Allen
Fix For: 2.1.0.BETA1, 2.0.3.GA
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:29 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3152) Remoting does not work with qualified component names
[ http://jira.jboss.com/jira/browse/JBSEAM-3152?page=comments#action_12420925 ]
Shane Bryzak commented on JBSEAM-3152:
--------------------------------------
Oops, I should have read the issue description a bit slower. I think you're right,
replacing with underscores would be acceptable.
Remoting does not work with qualified component names
-----------------------------------------------------
Key: JBSEAM-3152
URL: http://jira.jboss.com/jira/browse/JBSEAM-3152
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.A1, 2.0.3.CR1
Reporter: Dan Allen
Assigned To: Dan Allen
Fix For: 2.1.0.BETA1, 2.0.3.GA
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:44 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3152) Remoting does not work with qualified component names
[
https://jira.jboss.org/jira/browse/JBSEAM-3152?page=com.atlassian.jira.pl...
]
Shane Bryzak closed JBSEAM-3152.
--------------------------------
Resolution: Done
Assignee: Shane Bryzak (was: Dan Allen)
Fixed in SVN. I decided to implement this properly by using JavaScript namespaces.
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
9:46 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3152) Remoting does not work with qualified component names
[
https://jira.jboss.org/jira/browse/JBSEAM-3152?page=com.atlassian.jira.pl...
]
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
5994
days inactive
6028
days old
6 comments
2 participants
participants (2)
-
Dan Allen (JIRA) -
Shane Bryzak (JIRA)