directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <>
Subject [jira] Commented: (DIREVE-309) JBoss 3.2 ApacheDS MBean - contribution from SAA Consultants Ltd (UK)
Date Tue, 07 Feb 2006 19:36:58 GMT
    [ ] 

Alex Karasulu commented on DIREVE-309:

Simon I just trimmed it down because we just want the project to deploy the one artifact (the
sar).  Other things around this are extras like the schema build mechanism you incorporated
into it.  We can add stuff like this to another project.  The key though it to make this artifact
a single simple one that someone can drop in and the server will come up.  It should be as
generic as possible without some of the company specific stuff i found in it.

BTW I know you don't have commit access but you can modify a checked out version of the svn
repo and make modifications there.  When you're done you can attach an 'svn diff' generated
patch.  I can then apply these patches for you until you gain karma to the repo.

> JBoss 3.2 ApacheDS MBean - contribution from SAA Consultants Ltd (UK)
> ---------------------------------------------------------------------
>          Key: DIREVE-309
>          URL:
>      Project: Directory Server
>         Type: New Feature
>     Versions: 1.0-RC1
>  Environment: JBoss 3.2
>     Reporter: Simon Temple
>     Assignee: Alex Karasulu
>     Priority: Minor
>      Fix For: 1.0-RC1
>  Attachments:,,
> 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
> 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:
For more information on JIRA, see:

View raw message