You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Vishwanath (JIRA)" <ji...@apache.org> on 2011/05/17 00:19:47 UTC
[jira] [Created] (OPENEJB-1551) ejb-jar.xml should be optional.
ejb-jar.xml should be optional.
--------------------------------
Key: OPENEJB-1551
URL: https://issues.apache.org/jira/browse/OPENEJB-1551
Project: OpenEJB
Issue Type: Bug
Components: examples
Affects Versions: 3.1.4
Environment: Executed using maven
Reporter: Vishwanath
Priority: Minor
Expected: ejb-jar.xml file should be optional
Found: ejb-jar.xml file was required.
When run without the file, it looks like the ejbs are not deployed. The logs don't show JNDI bindings. And the client was not able to look up by the JNDI names,
How to reproduce: In the simple-stateless example project, delete the src/main/resources/META-INF/ejb-jar.xml and then do
mvn clean install
Logs don't show the JNDI name bindings.
The test fails, with javax,naming.NameNotFoundException
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OPENEJB-1551) ejb-jar.xml should be optional.
Posted by "David Blevins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins resolved OPENEJB-1551.
------------------------------------
Resolution: Fixed
> ejb-jar.xml should be optional.
> --------------------------------
>
> Key: OPENEJB-1551
> URL: https://issues.apache.org/jira/browse/OPENEJB-1551
> Project: OpenEJB
> Issue Type: Bug
> Components: examples
> Affects Versions: 3.1.4
> Environment: Executed using maven
> Reporter: Vishwanath
> Priority: Minor
> Labels: ejb-jar.xml
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> Expected: ejb-jar.xml file should be optional
> Found: ejb-jar.xml file was required.
> When run without the file, it looks like the ejbs are not deployed. The logs don't show JNDI bindings. And the client was not able to look up by the JNDI names,
> How to reproduce: In the simple-stateless example project, delete the src/main/resources/META-INF/ejb-jar.xml and then do
> mvn clean install
> Logs don't show the JNDI name bindings.
> The test fails, with javax,naming.NameNotFoundException
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENEJB-1551) ejb-jar.xml should be optional.
Posted by "Vishwanath (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034667#comment-13034667 ]
Vishwanath commented on OPENEJB-1551:
-------------------------------------
Thanks David, that clarifies !
> ejb-jar.xml should be optional.
> --------------------------------
>
> Key: OPENEJB-1551
> URL: https://issues.apache.org/jira/browse/OPENEJB-1551
> Project: OpenEJB
> Issue Type: Bug
> Components: examples
> Affects Versions: 3.1.4
> Environment: Executed using maven
> Reporter: Vishwanath
> Priority: Minor
> Labels: ejb-jar.xml
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> Expected: ejb-jar.xml file should be optional
> Found: ejb-jar.xml file was required.
> When run without the file, it looks like the ejbs are not deployed. The logs don't show JNDI bindings. And the client was not able to look up by the JNDI names,
> How to reproduce: In the simple-stateless example project, delete the src/main/resources/META-INF/ejb-jar.xml and then do
> mvn clean install
> Logs don't show the JNDI name bindings.
> The test fails, with javax,naming.NameNotFoundException
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (OPENEJB-1551) ejb-jar.xml should be optional.
Posted by "David Blevins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins reopened OPENEJB-1551:
------------------------------------
> ejb-jar.xml should be optional.
> --------------------------------
>
> Key: OPENEJB-1551
> URL: https://issues.apache.org/jira/browse/OPENEJB-1551
> Project: OpenEJB
> Issue Type: Bug
> Components: examples
> Affects Versions: 3.1.4
> Environment: Executed using maven
> Reporter: Vishwanath
> Priority: Minor
> Labels: ejb-jar.xml
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> Expected: ejb-jar.xml file should be optional
> Found: ejb-jar.xml file was required.
> When run without the file, it looks like the ejbs are not deployed. The logs don't show JNDI bindings. And the client was not able to look up by the JNDI names,
> How to reproduce: In the simple-stateless example project, delete the src/main/resources/META-INF/ejb-jar.xml and then do
> mvn clean install
> Logs don't show the JNDI name bindings.
> The test fails, with javax,naming.NameNotFoundException
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (OPENEJB-1551) ejb-jar.xml should be optional.
Posted by "Jean-Louis MONTEIRO (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Louis MONTEIRO closed OPENEJB-1551.
----------------------------------------
Resolution: Fixed
> ejb-jar.xml should be optional.
> --------------------------------
>
> Key: OPENEJB-1551
> URL: https://issues.apache.org/jira/browse/OPENEJB-1551
> Project: OpenEJB
> Issue Type: Bug
> Components: examples
> Affects Versions: 3.1.4
> Environment: Executed using maven
> Reporter: Vishwanath
> Priority: Minor
> Labels: ejb-jar.xml
> Fix For: 4.5.0
>
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> Expected: ejb-jar.xml file should be optional
> Found: ejb-jar.xml file was required.
> When run without the file, it looks like the ejbs are not deployed. The logs don't show JNDI bindings. And the client was not able to look up by the JNDI names,
> How to reproduce: In the simple-stateless example project, delete the src/main/resources/META-INF/ejb-jar.xml and then do
> mvn clean install
> Logs don't show the JNDI name bindings.
> The test fails, with javax,naming.NameNotFoundException
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENEJB-1551) ejb-jar.xml should be optional.
Posted by "David Blevins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034411#comment-13034411 ]
David Blevins commented on OPENEJB-1551:
----------------------------------------
[Didn't mean to close this issue yet]
The ejb-jar.xml is optional as long as alternate ways to discover the annotated apps are used. Check out this doc http://openejb.apache.org/3.0/application-discovery-via-the-classpath.html
Things work without an ejb-jar.xml by default in trunk (the future 4.0) which uses the EJBContainer API we [the EJB 3.1 EG] added to the EJB spec . The InitialContext embedded container concept in OpenEJB 3.1.x predates the EJB 3.1 version by a few years, so in terms of keeping things stable we have to maintain OpenEJB 3.x behavior.
> ejb-jar.xml should be optional.
> --------------------------------
>
> Key: OPENEJB-1551
> URL: https://issues.apache.org/jira/browse/OPENEJB-1551
> Project: OpenEJB
> Issue Type: Bug
> Components: examples
> Affects Versions: 3.1.4
> Environment: Executed using maven
> Reporter: Vishwanath
> Priority: Minor
> Labels: ejb-jar.xml
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> Expected: ejb-jar.xml file should be optional
> Found: ejb-jar.xml file was required.
> When run without the file, it looks like the ejbs are not deployed. The logs don't show JNDI bindings. And the client was not able to look up by the JNDI names,
> How to reproduce: In the simple-stateless example project, delete the src/main/resources/META-INF/ejb-jar.xml and then do
> mvn clean install
> Logs don't show the JNDI name bindings.
> The test fails, with javax,naming.NameNotFoundException
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENEJB-1551) ejb-jar.xml should be optional.
Posted by "Jean-Louis MONTEIRO (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Louis MONTEIRO updated OPENEJB-1551:
-----------------------------------------
Fix Version/s: 4.5.0
> ejb-jar.xml should be optional.
> --------------------------------
>
> Key: OPENEJB-1551
> URL: https://issues.apache.org/jira/browse/OPENEJB-1551
> Project: OpenEJB
> Issue Type: Bug
> Components: examples
> Affects Versions: 3.1.4
> Environment: Executed using maven
> Reporter: Vishwanath
> Priority: Minor
> Labels: ejb-jar.xml
> Fix For: 4.5.0
>
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> Expected: ejb-jar.xml file should be optional
> Found: ejb-jar.xml file was required.
> When run without the file, it looks like the ejbs are not deployed. The logs don't show JNDI bindings. And the client was not able to look up by the JNDI names,
> How to reproduce: In the simple-stateless example project, delete the src/main/resources/META-INF/ejb-jar.xml and then do
> mvn clean install
> Logs don't show the JNDI name bindings.
> The test fails, with javax,naming.NameNotFoundException
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira