[JBoss JIRA] Created: (JOPR-27) Filename wrong for EAR file not in deploy/
by Heiko W. Rupp (JIRA)
Filename wrong for EAR file not in deploy/
------------------------------------------
Key: JOPR-27
URL: https://jira.jboss.org/jira/browse/JOPR-27
Project: Jopr
Issue Type: Bug
Components: Plugin - JBoss AS 4
Affects Versions: 2.1
Reporter: Heiko W. Rupp
Assignee: Heiko W. Rupp
Fix For: 2.2
I have the following config in jboss-servervice.xml for the URLDpeloymentScanner:
Dropping an EAR file in /home/hrupp/test gives on the AS:
11:10:48,162 INFO [EARDeployer] Init J2EE application: file:/home/hrupp/test/JBossDukesBank.ear
But gives a filename of /devel/jboss-4.2.2.GA/server/default/deploy/JBossDukesBank.ear in inventory.
The path for the embedded WAR file is wrong as well:
/devel/jboss-4.2.2.GA/server/default/deploy/JBossDukesBank.ear/web-client.war
The same is also true when the EAR file is not directly in deploy/ but in a subdirectory of if (e.g. deploy/test/ )
--
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
15 years, 11 months
[JBoss JIRA] Updated: (JOPR-9) Cannot handle multiple JBossAS connections with different credentials
by Charles Crouch (JIRA)
[ https://jira.jboss.org/jira/browse/JOPR-9?page=com.atlassian.jira.plugin.... ]
Charles Crouch updated JOPR-9:
------------------------------
Comment: was deleted
> Cannot handle multiple JBossAS connections with different credentials
> ---------------------------------------------------------------------
>
> Key: JOPR-9
> URL: https://jira.jboss.org/jira/browse/JOPR-9
> Project: Jopr
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Greg Hinkle
> Assignee: Ian Springer
> Fix For: 2.2
>
>
> Opened from RHQ-1030...
> Basically, the JBoss JNP context factory is storing principal and credentials in thread-locals so that we can have two stubs to different AS instances that require different principal/credentials. I tried jnp.restoreLoginIdentity and jnp.multi-threaded, but that will only let you support different connections in different threads.
> After some testing, it looks like we can just have EMS setup the SecurityAssociation before every call into the stub. It should be fairly easy since EMS uses dynamic proxies around the stubs.
> SecurityAssociation.setPrincipal(new SimplePrincipal("-principal-"));
> SecurityAssociation.setCredential("-credentials-");
--
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
15 years, 11 months
[JBoss JIRA] Updated: (JOPR-9) Cannot handle multiple JBossAS connections with different credentials
by Charles Crouch (JIRA)
[ https://jira.jboss.org/jira/browse/JOPR-9?page=com.atlassian.jira.plugin.... ]
Charles Crouch updated JOPR-9:
------------------------------
Attachment: (was: rhq-jmx-plugin-1.1.0.GA.jar)
> Cannot handle multiple JBossAS connections with different credentials
> ---------------------------------------------------------------------
>
> Key: JOPR-9
> URL: https://jira.jboss.org/jira/browse/JOPR-9
> Project: Jopr
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Greg Hinkle
> Assignee: Ian Springer
> Fix For: 2.2
>
>
> Opened from RHQ-1030...
> Basically, the JBoss JNP context factory is storing principal and credentials in thread-locals so that we can have two stubs to different AS instances that require different principal/credentials. I tried jnp.restoreLoginIdentity and jnp.multi-threaded, but that will only let you support different connections in different threads.
> After some testing, it looks like we can just have EMS setup the SecurityAssociation before every call into the stub. It should be fairly easy since EMS uses dynamic proxies around the stubs.
> SecurityAssociation.setPrincipal(new SimplePrincipal("-principal-"));
> SecurityAssociation.setCredential("-credentials-");
--
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
15 years, 11 months