You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2005/09/11 06:32:30 UTC
[jira] Created: (GERONIMO-1002) Make orb objectname resolved by a query.
Make orb objectname resolved by a query.
----------------------------------------
Key: GERONIMO-1002
URL: http://issues.apache.org/jira/browse/GERONIMO-1002
Project: Geronimo
Type: Bug
Versions: 1.0-M5
Reporter: David Jencks
Assigned to: David Jencks
Fix For: 1.0-M5
When we're binding the orb to java:comp/ORB, currently you have to supply the exact object name of the orb. This can result in some brittleness since it is not in a plan that is always started. You might want to include the orb in your application. So, let's make it so that if you supply a query for the orb object name in the runtime deployer, it gets resolved at deploy time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1002) Make orb objectname resolved by a query.
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1002?page=all ]
Matt Hogstrom updated GERONIMO-1002:
------------------------------------
Fix Version: 1.1
(was: 1.0)
Deferring to 1.1
> Make orb objectname resolved by a query.
> ----------------------------------------
>
> Key: GERONIMO-1002
> URL: http://issues.apache.org/jira/browse/GERONIMO-1002
> Project: Geronimo
> Type: Bug
> Versions: 1.0-M5
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.1
>
> When we're binding the orb to java:comp/ORB, currently you have to supply the exact object name of the orb. This can result in some brittleness since it is not in a plan that is always started. You might want to include the orb in your application. So, let's make it so that if you supply a query for the orb object name in the runtime deployer, it gets resolved at deploy time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1002) Make orb objectname resolved by a query.
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1002?page=all ]
David Jencks closed GERONIMO-1002:
----------------------------------
Resolution: Fixed
Sending modules/j2ee-builder/src/java/org/apache/geronimo/j2ee/deployment/RefContext.java
Sending modules/naming-builder/src/java/org/apache/geronimo/naming/deployment/ENCConfigBuilder.java
Transmitting file data ..
Committed revision 280069.
> Make orb objectname resolved by a query.
> ----------------------------------------
>
> Key: GERONIMO-1002
> URL: http://issues.apache.org/jira/browse/GERONIMO-1002
> Project: Geronimo
> Type: Bug
> Versions: 1.0-M5
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.0-M5
>
> When we're binding the orb to java:comp/ORB, currently you have to supply the exact object name of the orb. This can result in some brittleness since it is not in a plan that is always started. You might want to include the orb in your application. So, let's make it so that if you supply a query for the orb object name in the runtime deployer, it gets resolved at deploy time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1002) Make orb objectname resolved by a
query.
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1002?page=all ]
Aaron Mulder updated GERONIMO-1002:
-----------------------------------
Component: CORBA
> Make orb objectname resolved by a query.
> ----------------------------------------
>
> Key: GERONIMO-1002
> URL: http://issues.apache.org/jira/browse/GERONIMO-1002
> Project: Geronimo
> Type: Bug
> Components: CORBA
> Versions: 1.0-M5
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.1
>
> When we're binding the orb to java:comp/ORB, currently you have to supply the exact object name of the orb. This can result in some brittleness since it is not in a plan that is always started. You might want to include the orb in your application. So, let's make it so that if you supply a query for the orb object name in the runtime deployer, it gets resolved at deploy time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Reopened: (GERONIMO-1002) Make orb objectname resolved by a query.
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1002?page=all ]
David Jencks reopened GERONIMO-1002:
------------------------------------
This needs more thought. I think there is some use in allowing patterns, but currently using one prevents you from deploying a j2ee app when there is no orb present.
We could:
1. look for the orb, and set nothing if no orb is found (I don't like this)
2. let you set the target orb, using a pattern, in the geronimo plan somewhere. This would override the "default" set in the builder.
Sending modules/assembly/src/plan/j2ee-runtime-deployer-plan.xml
Transmitting file data .
Committed revision 280075.
> Make orb objectname resolved by a query.
> ----------------------------------------
>
> Key: GERONIMO-1002
> URL: http://issues.apache.org/jira/browse/GERONIMO-1002
> Project: Geronimo
> Type: Bug
> Versions: 1.0-M5
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.0-M5
>
> When we're binding the orb to java:comp/ORB, currently you have to supply the exact object name of the orb. This can result in some brittleness since it is not in a plan that is always started. You might want to include the orb in your application. So, let's make it so that if you supply a query for the orb object name in the runtime deployer, it gets resolved at deploy time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1002) Make orb objectname resolved by a query.
Posted by "David Blevins (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1002?page=all ]
David Blevins updated GERONIMO-1002:
------------------------------------
Fix Version: 1.0
(was: 1.0-M5)
> Make orb objectname resolved by a query.
> ----------------------------------------
>
> Key: GERONIMO-1002
> URL: http://issues.apache.org/jira/browse/GERONIMO-1002
> Project: Geronimo
> Type: Bug
> Versions: 1.0-M5
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.0
>
> When we're binding the orb to java:comp/ORB, currently you have to supply the exact object name of the orb. This can result in some brittleness since it is not in a plan that is always started. You might want to include the orb in your application. So, let's make it so that if you supply a query for the orb object name in the runtime deployer, it gets resolved at deploy time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira