7:05 a.m.
Binding java:comp must be optional
----------------------------------
Key: JBNAME-37
URL: https://jira.jboss.org/jira/browse/JBNAME-37
Project: JBoss Naming
Issue Type: Feature Request
Components: jnpserver
Reporter: Carlo de Wolf
Priority: Critical
--
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
3:16 a.m.
New subject: [JBoss JIRA] Updated: (JBNAME-37) Binding java:comp must be optional
[
https://jira.jboss.org/jira/browse/JBNAME-37?page=com.atlassian.jira.plug...
]
Carlo de Wolf updated JBNAME-37:
--------------------------------
Fix Version/s: 5.1.0.Beta1
Assignee: Carlo de Wolf
Binding java:comp must be optional
----------------------------------
Key: JBNAME-37
URL: https://jira.jboss.org/jira/browse/JBNAME-37
Project: JBoss Naming
Issue Type: Feature Request
Components: jnpserver
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
Priority: Critical
Fix For: 5.1.0.Beta1
--
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
4:04 a.m.
New subject: [JBoss JIRA] Updated: (JBNAME-37) Binding java:comp must be optional
[
https://jira.jboss.org/jira/browse/JBNAME-37?page=com.atlassian.jira.plug...
]
Carlo de Wolf updated JBNAME-37:
--------------------------------
Description:
Right now java:comp is bound by NamingBeanImpl. This should be made optional (for
backwards compatibility), so it can be taken over by a new component.
Note that this setting is also deprecated by design. The next step would be to eliminate
it altogether and have no java:comp initialization code anymore in NamingBeanImpl.
Binding java:comp must be optional
----------------------------------
Key: JBNAME-37
URL: https://jira.jboss.org/jira/browse/JBNAME-37
Project: JBoss Naming
Issue Type: Feature Request
Components: jnpserver
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
Priority: Critical
Fix For: 5.1.0.Beta1
Right now java:comp is bound by NamingBeanImpl. This should be made optional (for
backwards compatibility), so it can be taken over by a new component.
Note that this setting is also deprecated by design. The next step would be to eliminate
it altogether and have no java:comp initialization code anymore in NamingBeanImpl.
--
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
5:26 p.m.
New subject: [JBoss JIRA] Updated: (JBNAME-37) Binding java:comp must be optional
[
https://jira.jboss.org/jira/browse/JBNAME-37?page=com.atlassian.jira.plug...
]
Scott M Stark updated JBNAME-37:
--------------------------------
Fix Version/s: 5.0.4.GA
Binding java:comp must be optional
----------------------------------
Key: JBNAME-37
URL: https://jira.jboss.org/jira/browse/JBNAME-37
Project: JBoss Naming
Issue Type: Feature Request
Components: jnpserver
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
Priority: Critical
Fix For: 5.1.0.Beta1, 5.0.4.GA
Right now java:comp is bound by NamingBeanImpl. This should be made optional (for
backwards compatibility), so it can be taken over by a new component.
Note that this setting is also deprecated by design. The next step would be to eliminate
it altogether and have no java:comp initialization code anymore in NamingBeanImpl.
--
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
8:33 p.m.
New subject: [JBoss JIRA] Resolved: (JBNAME-37) Binding java:comp must be optional
[
https://jira.jboss.org/jira/browse/JBNAME-37?page=com.atlassian.jira.plug...
]
Scott M Stark resolved JBNAME-37.
---------------------------------
Resolution: Done
The removal of any java:comp creation is delayed to JBNAME-41 since it can be prevented
via the installJavaComp property.
Binding java:comp must be optional
----------------------------------
Key: JBNAME-37
URL: https://jira.jboss.org/jira/browse/JBNAME-37
Project: JBoss Naming
Issue Type: Feature Request
Components: jnpserver
Reporter: Carlo de Wolf
Assignee: Carlo de Wolf
Priority: Critical
Fix For: 5.1.0.Beta1, 5.0.4.GA
Right now java:comp is bound by NamingBeanImpl. This should be made optional (for
backwards compatibility), so it can be taken over by a new component.
Note that this setting is also deprecated by design. The next step would be to eliminate
it altogether and have no java:comp initialization code anymore in NamingBeanImpl.
--
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
6096
days inactive
6143
days old
4 comments
2 participants
participants (2)
-
Carlo de Wolf (JIRA) -
Scott M Stark (JIRA)