[Design of JBoss ESB] - JMSRouter refactoring
by beve
Hi,
we are using the JMSRouter and would like to use the setting of the correlation id which is now being done, or will after MR3 is released. More info about the correlation id can be found here http://jira.jboss.com/jira/browse/JBESB-652
Now, this is all good except that we want to be able to set the property unwrap to true, and still have the correlation id set.
This is currenlty not possible as unwrap will will extract the content of the Message's body (in AbstractRouter) and then pass that Object to JMSRouter's process method, hence the information from the Message object being lost and there is no way to set the outgoing messages correlation id to the Message objects ID.
The way I would like it do be is that setting unwrap to true means that I want the content of the Message objects body to be routed and the setting of JMSProperties should be performed.
The short term solution for this might be to change the createObjectMessage to be protected so that I can subclass it to suite my needs. But I think setting unwrap to true would be more logical, but other routers might depend on the current behaviour.
Any thought?
Thanks,
Daniel
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063836#4063836
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063836
19 years
[Design of JBoss Build System] - Re: JBoss/JCA Maven Build
by vickyk
"pgier" wrote :
| I think that pretty much sums up our options
| 1 - Break into separate projects
| 2 - Create maven plugin to generate artifacts
| 3 - use ant to build the jars
|
The Option 1 looks simpler , so I continue with it . I separated the projects as
| jboss-jca
| ------->pom.xml
| ------>core
| ---------->jbossjcacore-impl
| ------->src
| ------->pom.xml
| ---------->jbossjcacore-spi
| ------->src
| ------->pom.xml
| ---------->pom.xml
| ------->adapter
| -->src
| -->pom.xml
Now building of the jbossjcacore-impl needs the jbossjcacore-spi generated jar file . I wanted to know if I can use the generated spi.jar SNAPSHOT from the local system , using server to download it through depends would work ... I wanted to know if I can use it locally .
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063816#4063816
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063816
19 years
[Design of JBoss Transaction Services] - Listen address of JBossTS ports not configurable
by huuskart
See JBTM-253.
JBossTS opens a bunch of network ports (three, I think, but debug output only mentions two) it listens on, but JBossTS does not give me the option to specify at which address it listens for connections.
As such, this is not a bug or error. However, standard practice in practically every single network listening software is to give the option for the administrator to specify at which address the software listens on. JBoss AS also gives this option, it even has a global system property jboss.bind.address, and every single service except JBossTS can be separately configured to listen on a particular address, and by default the services usually are configured to listen on ${jboss.bind.address}.
I want to see JBossTS also support this.
My ultimate reason for this is simply the fact that I hate to have services listening globally on ports they have no business or need listening on. Of course my servers are firewalled, so there's no problem of getting rogue connections, but even so, if I'm running a simple single JBoss AS instance, nothing will ever need to connect to JBossTS services from outside of the localhost, then I want to configure JBossTS so that it listens only on localhost.
But really, for complex installations there may be even real reasons why this needs to be configured. The server could have multiple IP addresses, run several JBoss instances, and would need to configure JBossTS in each instance to listen on different IP.
>From another point of view, I could ask that if JBossTS does not need to support this configuration option, why would any service in JBoss support it, and why does JBossTS support configuring even the port at all, if listen address configuration need not be supported (these two really always go hand in hand).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063814#4063814
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063814
19 years