Hi Joerg!
Happy to hear that the existing portable mechanisms work for you.
As an addendum to keep in mind for the future, there is also the GFv3
Service and Component mechanism. It will be a while before there is a
GFv3-based release equivalent in functionality to SJS AS 9.1, but it may
be useful for you to know the direction we are moving.
See [1] for schedules and [2] for info on the GFv3 module
[1]
http://blogs.sun.com/pelegri/entry/future_glassfish_releases
[2]
http://hk2.dev.java.net
- eduard/o
Jörg Henne wrote:
> Binod schrieb:
>> JSR 112 specifies lifecycle of resource adapters.
>> http://java.sun.com/javaee/5/docs/api/javax/resource/spi/ResourceAdapter.html
>>
>> Please look at the start() method of the RA. They do get invoked
>> during AS startup.
>> http://java.sun.com/javaee/5/docs/tutorial/doc/bnckb.html
> Ah, brilliant! Just what we're looking for AND with a portable API!
>> If you want to wrap a specific protocol into a portable application,
>> then resource adapters
>> is the way to go. Note that you can also feed the incoming (non-jms)
>> traffic to an MDB.
> Sounds highly interesting as well. I'll definitely look into this.
>>> Application or EJB requesting the service by looking up a RA
>>> connection from JNDI and therefor no way to launch the service.
>> That is correct from a connector 1.0 perspective. Connector 1.5 has
>> improved on that
>> quite a bit.
> Well, it seems like I completely missed out on this great news. Thanks a
> lot for bringing me up to speed!
>
> Joerg Henne
>