[
https://jira.jboss.org/jira/browse/JBAS-7588?page=com.atlassian.jira.plug...
]
jaikiran pai commented on JBAS-7588:
------------------------------------
> A month ago I worked through and tested how to move everything
into deploy, it's mostly a matter of checking whether M2 actually *has* deployers that
directly bind stuff in JNDI and then making a go/no-go decision. There were some in the
plans a month ago, but last I checked they weren't actually implemented.
The EJB3.1 no-interface view deployer (though not directly) does bind proxy to JNDI.
I'll comment in that thread with the details.
> Jaikiran, feel free to assign this JIRA to me, unless your
r100158 is sufficient to fix the test; otherwise it's just part of the overall work.
As of build 534,
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-test...
this testcase now passes. Marking this as JIRA as resolved.
Investigate org.jboss.test.ejb.lifecycle.test failures
------------------------------------------------------
Key: JBAS-7588
URL:
https://jira.jboss.org/jira/browse/JBAS-7588
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Reporter: jaikiran pai
Assignee: jaikiran pai
--
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