Re: JCA in a non-managed environment

--- Jon Dart <[email protected]> wrote:
> At 02:42 PM 1/12/03 +0100, Johan Eltes wrote:
> > > The specification states
> > > unambiguously that a connection factory should
> be
> > > obtained via a JNDI lookup in both a managed and
> a
> > > non-manged scenario.  This is fine; the goal is
> > > obviously to maintain a consistent client
> programming
> > > model.
>
> I don't think it's required that this be the only
> way to access your
> factory class. You could also allow users to
> directly instantiate the
> factory class instead of getting it indirectly from
> JNDI. This would allow
> you to run in an environment in which you don't have
> a suitable JNDI provider.
>
> --Jon

This is from section 10.5 of the 1.0 final release of
the specification.

<BEGIN QUOTED MATERIAL>
In both managed and non-managed application scenarios,
an application component (or application
client) is required to look up a connection factory
instance in the component?s environment
using the JNDI interface. The application component
then uses the connection factory
instance to get a connection to the underlying EIS.
Section 5.4 specifies the application programming
model in more detail.
</END QUOTED MATERIAL>

I agree it would be convenient if the requirement
didn't exist but as I read the spec it does.

-Jason


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff CONNECTOR-INTEREST".  For general help, send email to
[email protected] and include in the body of the message "help".