[JBoss JIRA] (AS7-2998) Lock down the ability to set/reset EJB client context selector on the server side by user code
9:05 p.m.
Lock down the ability to set/reset EJB client context selector on the server side by user
code
----------------------------------------------------------------------------------------------
Key: AS7-2998
URL: https://issues.jboss.org/browse/AS7-2998
Project: Application Server 7
Issue Type: Task
Components: EJB
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: 7.1.0.CR1
On the server side we shouldn't allow setting/resetting the EJB client context
selector, by the user code. An API to lock down setting the selector is being added in the
next version of EJB client API. The server should use that API to lock down the selector
once it has setup the server wide selector.
Creating this as a task for 7.1.0.CR1 so as to not forget adding this implementation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:57 p.m.
[
https://issues.jboss.org/browse/AS7-2998?page=com.atlassian.jira.plugin.s...
]
Jason Greene updated AS7-2998:
------------------------------
Fix Version/s: 7.1.0.Final
(was: 7.1.0.CR1)
Lock down the ability to set/reset EJB client context selector on the
server side by user code
----------------------------------------------------------------------------------------------
Key: AS7-2998
URL: https://issues.jboss.org/browse/AS7-2998
Project: Application Server 7
Issue Type: Task
Components: EJB
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: 7.1.0.Final
On the server side we shouldn't allow setting/resetting the EJB client context
selector, by the user code. An API to lock down setting the selector is being added in the
next version of EJB client API. The server should use that API to lock down the selector
once it has setup the server wide selector.
Creating this as a task for 7.1.0.CR1 so as to not forget adding this implementation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:12 a.m.
[
https://issues.jboss.org/browse/AS7-2998?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-2998:
-------------------------------------
I don't think that this is really possible to do without breaking the :reload command,
as org.jboss.as.ejb3.remote.DefaultEjbClientContextService will not be able to start a
second time, as the selector will be locked.
Adding an unlock method also seems to be kinda pointless, as it means that client code
could simply unlock and then set the selector.
I think that the existing security check is probably sufficient to handle this.
Lock down the ability to set/reset EJB client context selector on the
server side by user code
----------------------------------------------------------------------------------------------
Key: AS7-2998
URL: https://issues.jboss.org/browse/AS7-2998
Project: Application Server 7
Issue Type: Task
Components: EJB
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: 7.1.0.Final
On the server side we shouldn't allow setting/resetting the EJB client context
selector, by the user code. An API to lock down setting the selector is being added in the
next version of EJB client API. The server should use that API to lock down the selector
once it has setup the server wide selector.
Creating this as a task for 7.1.0.CR1 so as to not forget adding this implementation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:02 a.m.
[
https://issues.jboss.org/browse/AS7-2998?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-2998:
-----------------------------------
{quote}
I don't think that this is really possible to do without breaking the :reload command,
as org.jboss.as.ejb3.remote.DefaultEjbClientContextService will not be able to start a
second time, as the selector will be locked.
Adding an unlock method also seems to be kinda pointless, as it means that client code
could simply unlock and then set the selector.
{quote}
Agreed and infact that's the reason I haven't added this one line change yet. We
should however somehow have a similar ability since users can end up messing up the entire
server and other (independent) applications on the server if they switch the selector.
Lock down the ability to set/reset EJB client context selector on the
server side by user code
----------------------------------------------------------------------------------------------
Key: AS7-2998
URL: https://issues.jboss.org/browse/AS7-2998
Project: Application Server 7
Issue Type: Task
Components: EJB
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: 7.1.0.Final
On the server side we shouldn't allow setting/resetting the EJB client context
selector, by the user code. An API to lock down setting the selector is being added in the
next version of EJB client API. The server should use that API to lock down the selector
once it has setup the server wide selector.
Creating this as a task for 7.1.0.CR1 so as to not forget adding this implementation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:15 a.m.
[
https://issues.jboss.org/browse/AS7-2998?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-2998:
-----------------------------------
By the way, I do have an idea of achieving this without affecting the ability for service
restarts. I'll give it a try later today.
Lock down the ability to set/reset EJB client context selector on the
server side by user code
----------------------------------------------------------------------------------------------
Key: AS7-2998
URL: https://issues.jboss.org/browse/AS7-2998
Project: Application Server 7
Issue Type: Task
Components: EJB
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: 7.1.0.Final
On the server side we shouldn't allow setting/resetting the EJB client context
selector, by the user code. An API to lock down setting the selector is being added in the
next version of EJB client API. The server should use that API to lock down the selector
once it has setup the server wide selector.
Creating this as a task for 7.1.0.CR1 so as to not forget adding this implementation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4635
days inactive
4683
days old
4 comments
4 participants
participants (4)
-
jaikiran pai (Created) (JIRA) -
jaikiran pai (JIRA)
-
Jason Greene (Updated) (JIRA)
-
Stuart Douglas (JIRA)