You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Simon Temple (JIRA)" <ji...@apache.org> on 2006/03/10 12:26:39 UTC
[jira] Updated: (DIRSERVER-285) JBoss 3.2 ApacheDS MBean -
contribution from SAA Consultants Ltd (UK)
[ http://issues.apache.org/jira/browse/DIRSERVER-285?page=all ]
Simon Temple updated DIRSERVER-285:
-----------------------------------
Attachment: apache-server-sar.zip
Alex
I have tested the attached with JBoss 3.2.5 and DS 1.0RC1
I still need some help with my pom.xml... can you assist as you update SVN?
The storm of refactoring that happened prior to the RC1 release rendered my previous submission(s) invalid... I hope this fares better.
Regards
SimonT
> JBoss 3.2 ApacheDS MBean - contribution from SAA Consultants Ltd (UK)
> ---------------------------------------------------------------------
>
> Key: DIRSERVER-285
> URL: http://issues.apache.org/jira/browse/DIRSERVER-285
> Project: Directory ApacheDS
> Type: New Feature
> Components: sar
> Versions: 1.0-RC1
> Environment: JBoss 3.2
> Reporter: Simon Temple
> Assignee: Alex Karasulu
> Priority: Minor
> Fix For: 1.0-RC2
> Attachments: apache-server-sar.zip
>
> This small contribution to the project is an MBean implementation of an embedded server with optional wire protocol support for JBoss 3.2
> I've tested this with JBoss 3.2.2RC2 and JDK 1.4.1_03 and 1.4.2_07 so far running with 0.9.4 SNAPSHOTs
> To install simply copy the directory.sar folder into the JBoss deploy folder.
> There are a few simple methods on the MBean:
> changedEmbeddedAdminPassword() - used to stop the log4j warning about using the default admin password
> flushEmbeddedServerData()
> DirContext openDirContext() - becuase the Mbean can be configured to hold context information of embedded and none-embedded servers, this method can be called to always return a valid DirContext without the user having to know the connection details
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira