[jbossws-issues] [JBoss JIRA] (JBWS-3435) Enable appclient based tests
Richard Opalka (JIRA)
jira-events at lists.jboss.org
Mon Mar 12 11:00:47 EDT 2012
[ https://issues.jboss.org/browse/JBWS-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673061#comment-12673061 ]
Richard Opalka edited comment on JBWS-3435 at 3/12/12 10:59 AM:
----------------------------------------------------------------
How appclient tests work?
-------------------------
1) We're providing appclient-ws.xml configuration to configure JBoss remoting to allow for remote access to appclient JNDI env.
2) Our JAX-RPC proxies are de/serializable to be accessible remotely.
3) Our tests are always calling appclient.sh(.bat) scripts internally via java.lang.Process and passing --appclient-config=appclient-ws.xml parameter to use our custom config
4) Every appclient archive must be nested in ear, so we're using foo-appclient.ear#foo-appclient.jar syntax in our JBossWS test helper to specify which ear contains what appclient jar.
5) We're registering AppclientKiller for every appclient.jar that contains no main-class MANIFEST.MF entry.
The goal of this class is to detect shutdown mark files and call System.exit when mark file is found.
was (Author: ropalka):
How appclient tests work?
-------------------------
1) We're patching appclient.xml configuration to configure JBoss remoting to allow for remote access to appclient JNDI env.
2) Our JAX-RPC proxies are de/serializable to be accessible remotely.
3) Our tests are always calling appclient.sh(.bat) scripts internally via java.lang.Process.
4) Every appclient archive must be nested in ear, so we're using foo-appclient.ear#foo-appclient.jar syntax in our JBossWS test helper to specify which ear contains what appclient jar.
5) We're registering AppclientKiller for every appclient.jar that contains no main-class MANIFEST.MF entry.
The goal of this class is to detect shutdown mark files and call System.exit when mark file is found.
> Enable appclient based tests
> ----------------------------
>
> Key: JBWS-3435
> URL: https://issues.jboss.org/browse/JBWS-3435
> Project: JBoss Web Services
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: jbossws-integration
> Reporter: Richard Opalka
> Assignee: Richard Opalka
> Fix For: jbossws-native-4.1, jbossws-cxf-4.1
>
>
--
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
More information about the jbossws-issues
mailing list