[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-26) Standalone Messaging configuration.

[Alex Pinkin (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-26?page=comments#action_12342433 ] 
            
Alex Pinkin commented on JBMESSAGING-26:
----------------------------------------

JEMS installer currently has a "JMS server" profile which is based on jbossmq. It currently includes jmx microkernel, logging, hsqldb, jndi, jaas, jta, and jbossmq services.

So my understanding is that we need to add "JBoss Messaging" profile to the installer. Since user can only select one profile, JBoss Messaging and current jbossmq-based "JMS Server" will be mutually exclusive.

Is there a need to have a standalone installer for JBoss Messaging or is it ok to just add a "Standalone JBoss Messaging" profile to the JEMS installer?

Which version of JBoss Messaging?


> Standalone Messaging configuration.
> -----------------------------------
>
>                 Key: JBMESSAGING-26
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-26
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: AS Integration
>            Reporter: Ovidiu Feodorov
>         Assigned To: Alex Pinkin
>             Fix For: 1.2.0.CR1
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Prepare a stripped-down JBoss configuration that will be the "stand-alone" JBoss Messaging server. 
> Must have at least the JNDI server, Logging, Remoting and AOP support.
> We should provide a pre-packaged downloadable "standalone" config - users don't want to have to download and install the AS just so they can create a standalone installation.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira