Although our properties file is defaulted to use the standalone pooling.
<!-- connection manager type -->
<property name="org.jboss.soa.esb.persistence.db.conn.manager"
value="org.jboss.soa.esb.persistence.manager.StandaloneConnectionManager"/>
<!-- property
name="org.jboss.soa.esb.persistence.db.conn.manager"
value="org.jboss.soa.esb.persistence.manager.J2eeConnectionManager"/ -->
I don't think we need to change the build for this. We can handle that
on the forums.
--K
Kurt T Stam wrote:
That's what I'm thinking, yes.
Mark Little wrote:
> So we can ignore that and go with what Kev tagged?
>
> Mark.
>
>
> On 24 Mar 2007, at 12:31, Kurt T Stam wrote:
>
>
>> It looks like cp3o went into the sar. Not sure why that is needed. You
>> should be
>> able to use a datasource of the appserver now (using pooling of the
>> appserver).
>>
>> Mark Little wrote:
>>
>>> I'm doing a diff at the moment to see what changed. Might take a while
>>> from home.
>>>
>>> Mark.
>>>
>>>
>>> On 24 Mar 2007, at 05:19, Kevin Conner wrote:
>>>
>>>
>>>> The MP1 cut was taken last night at 10:15pm GMT and tagged as
>>>>
https://svn.labs.jboss.com/labs/jbossesb/tags/JBESB_4_0_MP1.
>>>>
>>>> There appears to have been a change made since, does this need to
>>>> go in
>>>> the MP release?
>>>>
>>>> Kev
>>>> _______________________________________________
>>>> esb-dev mailing list
>>>> esb-dev(a)lists.jboss.org
>>>>
https://lists.jboss.org/mailman/listinfo/esb-dev
>>>>
>>> _______________________________________________
>>> esb-dev mailing list
>>> esb-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/esb-dev
>>>
_______________________________________________
esb-dev mailing list
esb-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/esb-dev