Decoupling different jboss versions

[penguine]

Hi,

we have different jboss server. jboss 3.2* and jboss 4.*
what do you think is the best way to decouple our servers.
are there jca solutions. should/can we use the ESB with JCA.
perhaps we´ll become other applicationserver such as SAPNetweaver.

or is there no standard solution. should we write our own integration classes.

with regards

chris

[kurtstam]

Hi Chris,

Is is not very clear from your post what it is you want to do, but you can sure use the ESB for application integration (send messages between apps on jboss3.2 and jboss4). What is the problem you are trying to solve? Do you have a lot of integration points? We don't support JCA at the moment.

--Kurt

[penguine]

hi, I was in holiday, so my response is a little bit late.
We have different jboss server which different versions (3.*, 4.*) and want to integrate them. if it is possible we don´t want to upgrade.

Yes, I want to send messages between different jboss versions and want to call applications from one jboss version to an other. So, I think, normally I need other client libraries when I call a application from jboss 3.* to a jboss4.*.
Is it better to use the ESB? Can ESB communicate with jboss3.*?


regards chris

[kurtstam]

Hi Chris,

Sure you can use the ESB is for sending messages, using files, jms, ftp etc. But it won't help you doing rpc. You still need rmi for that. Looks to me you should take the plunge and upgrade the client libs. Do you have a link to some info on which they were? (I know I had it before, but can't find it now).


--Kurt

[penguine]

jboss client-libs? in $JBOSS_HOME/client
the server doesn´t load the client library by default. they aren´t in $JBOSS_HOME/lib or in $JBOSS_HOME/server/default/lib

I think we better should use our own dispatcher implementation. hmm... or ... the jboss ESB can do this, doesn´t it? so we only need to implement different jboss adapter (one for each jboss version) in the ESB.