On Wed, Mar 07, 2001 at 08:27:46PM -0600, Dan Kearns wrote:
> whoa, hey!
>
> Good to be prodded, I guess... I retried putting the shared classes in
> lib/ext and it frickin worked this time!
Phew, that's a relief :-)
> I must have just had my brain fried by the sheer number of times I was
> hitting undeploy/deploy and not restarted jboss like I thought I had...
>
> Anyway, that is very cool since now I have a working end-end adapter/bean
> thing going on.
>
> It would be a major plus to be able to get beans access to the classes in
> the ra.jar though... I assume this in the works? need any help?
The new deployment architecture that Dr Jung and myself (although mostly
Dr Jung) are slowly working on might allow this. The problem is knowing
which classes are meant to be visible to clients of the resource adapter
and which are internal.
I think that the best way is to create a separate jar containing the classes
needed by a client and include that as a library in your EAR. Or, if the
resource adapter is meant to be available to all applications, include it in
lib/ext.
Another option would be to have a JBoss-specific extension whereby you
nominate a jar in your RAR as the client jar and that gets made
available to the rest of the EAR.
Comments?
> One more question, is there a timeout someplace for how long to keep the
> adapter client waiting for an existing pooled connection to free up if
> creating a new connection fails?
>
> Often there are no existing connections to wait for and my client side just
> hangs (there isn't much point in waiting at all in that case!)
This is a Minerva issue, and therefore Aaron's domain. Have a look at
the Minerva source, available in jbosscx/external.
Toby.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
