Ok, it is clearer now as to the reasons why this doesn't work... but I think
we need to find a solution too this, else users (like myself) will be a tad
bit confused.
I think this problem is caused by the assumption that .jar/.ear/.war files
are rather selfcontained (all support, class and config files are in the
archinve). This seems like a very weak part of J2EE in general. They are
forcing users/deployers to use some sort of configuration tool (some type of
gui usually) to setup the descriptors before deploying.
What they really need is a clean seperation from support/class/resource
files which are deployed and a robust and flexible configuration database
which will link the deployment to a given configuration.
This is what I was refering to with the .sar stuff a while ago.
I guess this is sort of what is happening with the deployed file and the
ConnectionFactoryLoader. Perhaps the CFL could log a warning after x
minutes if it has not been connected with an adapter and possibly shutdown
with an error after y warnings, where x and y are configurables.
Just a thought. I wish J2EE was more complete in this area. Perhaps this
will be fixed, or perhaps we should provide a solution to the community and
lets the gobble it up 'cause it will be so darn cool!
--jason
On Thu, 16 Aug 2001, David Jencks wrote:
> Unfortunately it doesn't seem to be possible to issue a warning if you
> supply the wrong resource adapter name, since the way it works is:
>
> ConnectionFactoryLoader mbean gets its ResourceAdapterName and registers as
> a NotificationListener with the jmx server, filtering on Deployment events
> with message = ResourceAdapterName
>
> When the RARDeployer finds a .rar to deploy, it does so, and sends a
> Deployment notification with message = resource adapter name.
>
> The ConnectionFactoryLoader gets this message, checks to see if it is the
> resource adapter it is expecting, and if so sets up the ConnectionFactory,
> ManagedConnectionFactory....
>
> So if you put in the wrong name, it will happily wait forever until a rar
> with that name is deployed.
>
> I don't see a way to determine (automatically) that a ResourceAdapterName
> is wrong - ever. Do you?
>
> Regarding your earlier problem with jars deploying before rars, it seems as
> if we _could_ implement a similar notification mechanism for ejb
> deployment: if say the DataSource isn't ready when the bean is deployed, it
> could register a listener waiting for it, and when the DataSource is
> deployed, it could notify waiting ejbs (or their persistence managers I
> guess?) Would this be worthwhile/ a more robust solution than trying to be
> sure to deploy in the right order?
>
> david jencks
>
> On 2001.08.16 19:19:34 -0400 Jason Dillon wrote:
> > It looks like ResourceAdapterName is used to bind a connection factory
> > loader to a deployed adapter's <display-name> (as david mentioned). It
> > also
> > looks like if the connection factory specifies an invalid name (one that
> > does not match up with the one in the ra.xml), that it will not complain
> > and
> > will not bind anything into JNDI.
> >
> > I found this out due to a typo in one of my JmsXA configurations.
> >
> > It should really complain about something in this case.
> >
> > --jason
> >
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-development
> >
> >
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development