[
https://issues.jboss.org/browse/ARQ-592?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen closed ARQ-592.
-----------------------------
Bind CommandRunner to JNDI when GlassFish Embedded Container starts
-------------------------------------------------------------------
Key: ARQ-592
URL:
https://issues.jboss.org/browse/ARQ-592
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: GlassFish Containers
Reporter: Magnus Smith
Assignee: Magnus Smith
Fix For: glassfish_1.0.0.CR2
It would be really useful if the Glassfish CommandRunner could be bound to jndi when the
embedded container is started.
Looks like it would just be a case of adding
{code:java|borderStyle=solid}
CommandRunner commandRunner = glassfish.getCommandRunner();
new InitialContext().bind("org.glassfish.embeddable.CommandRunner",
commandRunner);
{code}
to the start method on the GlassfishContainer and then unbinding it on the stop method.
Then in the test class we could use
{code:java|borderStyle=solid}
@Resource(mappedName = "org.glassfish.embeddable.CommandRunner")
CommandRunner commandRunner;
{code}
This would open up all the glassfish admin commands from test classes.
api
[
http://embedded-glassfish.java.net/nonav/apidocs/org/glassfish/embeddable...]
asadmin [
http://download.oracle.com/docs/cd/E18930_01/html/821-2416/giobi.html#scr...]
--
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