Hi Robert,
The configuration web page was written for the BasicDataSource
connection pool implementation. The other pools do not support all
params listed.
In this case you are correct that SharedDataSourceFactory doesn't
support the abandoned parameters (only BasicDataSource does).
Regards
There was no attachment to the mail, mayby it was removed by the mailing
list software. Please mail it with the code inline or mail the file to
me directly.
Thanks
Dirk
Pramodh Peddi wrote:
Hi Dirk/All,
I posted the junit test, which I found to have problems related to
*abandon* methods.
Exactly. But, as I said, there are other concepts (e.g. in JTA) that
work as well and sometimes even better.
Cheers
Oliver
On 6/27/05, Aaron Hamid [EMAIL PROTECTED] wrote:
Ah, I see! So for instance the abstract notion of owner detached from
thread can enable things like locks migrating
Hello, thanks for the tip.
I was surfing around the API and didn't even see
BasicDataSource. I guess because it's in a different
package -- org.apache.commons.dbcp , whereas
SharedDataSource is in
org.apache.commons.dbcp.datasources.
Anyway, looking at the BasicDataSource I see that all
methods
Hello,
I started off developing my current project utilizing 3.0 rc1 of httpclient.
It's all working fine, and perhaps the error I'm getting is fixed in rc3,
but here goes.
I'm attempting to register a new protocol which allows self-signed
certificates to be accepted without saying no trusted
Problem appears to have been resolved. When defining my new protocol
object I was assigning it as follows
new Protocol( https, new EasySSLSocketFactory(), 443 );
when it should be
new Protocol( myhttps, new EasySSLSocketFactory(), 443 );
Now when I register it as myhttps, and pass in an
Hello,
It appears that the sendFile() method in TFTPClient from Commons Net
release 1.4.0 is not working. What happens is all 512 byte fixed length
data packets are send, but the last packet (which is less then 512) is
never sent, yet the method exits cleanly. I discovered this issue when
writing
The reason why abandoned* methods are deprecated are explained in the
wiki: http://wiki.apache.org/jakarta-commons/DBCP
-- Dirk
Robert Bowen wrote:
Hello, thanks for the tip.
I was surfing around the API and didn't even see
BasicDataSource. I guess because it's in a different
package --
Hello
I'm defining my rules using XML and using the DigesterRuleParser.
How can I set multiple parent child relationships and vice versa if I create
more than one child object inside one pattern
example
class BBB {
void setAAA(AAA a) {...}
}
pattern value=x
object-create-rule
On Mon, 2005-06-27 at 10:13 -0500, Glenn Goldenberg wrote:
hi robert:
I updated my local version of Betwixt with the patch and rebuilt. The test
works fine now.
Thanks for the fix!
and thank you for finding the problem and testing the fix!
i'm going to go ahead and roll an RC2 very
Is there a way to have commons-modeler honor the case sensitivity of
Model MBean attribute (property) names?
According to the JMX spec:
All attribute and operation names derived from these design patterns
are case-sensitive. For example, this means that the methods getstate
and setState
On Tue, 2005-06-28 at 17:21 -0700, Jan Luehe wrote:
Is there a way to have commons-modeler honor the case sensitivity of
Model MBean attribute (property) names?
According to the JMX spec:
All attribute and operation names derived from these design patterns
are case-sensitive. For
Simon,
Simon Kitching wrote:
On Tue, 2005-06-28 at 17:21 -0700, Jan Luehe wrote:
Is there a way to have commons-modeler honor the case sensitivity of
Model MBean attribute (property) names?
According to the JMX spec:
All attribute and operation names derived from these design patterns
On Wed, 2005-06-29 at 12:32 +1200, Simon Kitching wrote:
On Tue, 2005-06-28 at 17:21 -0700, Jan Luehe wrote:
Is there a way to have commons-modeler honor the case sensitivity of
Model MBean attribute (property) names?
According to the JMX spec:
All attribute and operation names
Simon,
Simon Kitching wrote:
On Wed, 2005-06-29 at 12:32 +1200, Simon Kitching wrote:
On Tue, 2005-06-28 at 17:21 -0700, Jan Luehe wrote:
Is there a way to have commons-modeler honor the case sensitivity of
Model MBean attribute (property) names?
According to the JMX spec:
All attribute
In message [EMAIL PROTECTED]
l, Matthew Tobiasz writes:
Now is this a known issue?
The user-submitted patch that caused the problem was reverted in May.
A number of user patches were applied to Commons Net before releasing
1.4.0 and a bad one slipped through. To remedy the problem, you can
use
16 matches
Mail list logo
