how to include remoting war distribution

[tom.elrod]

This post is in reference to http://jira.jboss.com/jira/browse/JBREM-407.

JBossRemoting has a servlet based invoker which will receive http request from a servlet running within a web container and then forward that request onto the remoting invoker. To use this servlet based transport with remoting, requires that the servlet-invoker.war is deployed. Currently the servlet-invoker.war is just a build artifact of the remoting distribution build.

One question is how should servlet-invoker.war included with JBossAS distribution (if at all)? One solution would be to include in the all configuration (since put pretty much everything and the kitchen sink there now).

The other question (assuming do include in the JBossAS distribution), is how to version servlet-invoker.war? The jboss-remoting.jar is versioned and downloaded for the JBossAS distribution using the jboss repository. However, can the same thing be donw for a war file? Is this even appropriate?

Thanks.

-Tom

[ryan.campbell]

There is nothing preventing you from adding this war to the repository. Make sure you add it to the component-info. I think this is preferable.

[tom.elrod]

Ok. So putting into the all node sounds reasonable?

[starksm64]

The problem with this is that the war would be included in the remoting classpath in the jbossbuild thirdparty/libraries.ent generated file. I don't know how the maven repository would behave.

[ryan.campbell]

I don't think it is included in the classpath unless you export it? Ruel, can you verify this?

[ruel.loehr]

This is correct. It must be included in the export.

[tom.elrod]

Ok. Sound sounds like should be included in the JBossAS all config and can be done using the repository.

Let's include this as one of the tasks when doing the JBossRemoting 2.0.0 release next month (which is when we'll be handing over release responsibility over to QA)