Standalone jboss-messaging without JBoss AS

[arvinder]

Hi there

I'm looking at building standalone jboss-messaging without jboss as, combined with the pojo microkernel - see http://jira.jboss.com/jira/browse/JBESB-13 - this is for JBoss ESB.

There is a dependency on jboss-remoting and the jmx mbean server therefore AFAIK the microkernel would need to start a pojo
wrapper around the mbean server. Have you had any thoughts on a standalone jboss-messaging server without jboss as, is there anything in cvs that I can look at?

At the moment I'm planning to write some pojo wrappers around the dependencies, once i've posted some questions on the microkernel/microcontainer forums.

TIA

[ovidiu.feodorov]

This is what http://jira.jboss.org/jira/browse/JBMESSAGING-26 is about. However, in implementing it we still rely on the JBoss microkernel and MBean (XMBean) support.

As far as I know, the POJO microkernel can work in backward-compatibility mode: MBeans can still be deployed, the MC comes with built-in JMX support for cases like this.

[arvinder]

Hi Ovidiu,

When do you think this will be completed (http://jira.jboss.org/jira/browse/JBMESSAGING-26)? AFAIK looks like there are dependencies on the Microcontainer development http://www.jboss.com/index.html?module=bb&op=viewtopic&t=76335

Hmm, I'll see how Mark wants to proceed for the esb development as these 2 Jira tasks are basically the same:

http://jira.jboss.org/jira/browse/JBMESSAGING-26
and
http://jira.jboss.com/jira/browse/JBESB-13[/url]

[timfox]

Both http://jira.jboss.com/jira/browse/JBMESSAGING-26 and http://jira.jboss.com/jira/browse/JBMESSAGING-25 have been bumped to critical after a few emails between Mark and I the other day, since these are obviously important for the ESB.

So far we don't know exactly when they're going to be done, but we should be doing a re-planning exercise very soon so should have some more firm dates.

[marklittle]

Thanks for the update Tim. If you need any testing let us know ;-)

Mark.

[timfox]

Maybe we should join forces on this if you guys have some resource (Arvinder?).

Let's wait 'til Ovidiu wakes and see what we can do.

[marklittle]

That's pretty much what I said (http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3935379#3935379), so keep us posted.

[arvinder]

Ok np, I think it would be good to join forces. Lets see what Ovidiu has to say and the best way to proceed.

[adrian.brock]

What code assumes an MBeanServer?

All our services should be pojos. That is certainly true for
StandardMBeans and XMBeans.

You will find some that assume an MBeanServer when they should
be changed to use IOC.

e.g.

private TransactionManager tm;
public void setTransactionManagerName(ObjectName name) { this.tmName = name };

protected void startService() throws Exception
{
 tm = server.getAttribute(tmName, "Instance");
}

should also have a:

public void setTransactionManager(TransactionManager tm) {this.tm = tm);

The MC/JMX to come in JBoss-Head will support both for JBossAS
but if you want to run standalone/embedded you need to have
proper IOC support.

[ovidiu.feodorov]

When do you think this will be completed (http://jira.jboss.org/jira/browse/JBMESSAGING-26)

Next week.

[arvinder]

Hi ovidiu,

Whereabouts in cvs can i get hold of the modifications which you are doing/have done for this pls ?

TIA

[ovidiu.feodorov]

This week ends on Friday.
The modifications are not there yet.

[arvinder]

Sorry ;-) didn't mean to be pushy or anything, I just thought
there was something in cvs.

[ovidiu.feodorov]

I modified the release management script to create a "standalone" Messaging server configuration based on 4.0.3SP1 installation .

The ant script slims down a default JBoss 4.0.3SP1 instance so it only contains the Messaging services, the JNDI server and the logging service. I also left Tomcat, jmx-console and web-console to allow an user to access the management console.

JBoss Messaging instance is non-scoped, since it's the only service that has remoting, AOP and serialization as dependencies.

Note that the script was only tested with an "expanded" (not installer-generated) 4.0.3SP1

Is this what you need?

To use it:

1. Checkout the latest util/release-admin.xml from CVS (this version will be also available with 1.0.1)
2. Set JBOSS_HOME to your JBoss 4.0.3.SP1 installation. You need to have a "default" configuration available there.
3. cd util; ant -f release-admin.xml standalone

[marklittle]

Thanks Ovidiu. Hopefully Arvinder will be able to take a look. In the absence of MC integration, this is a start.