On Wed, 22 Jan 2003, Paul King <[EMAIL PROTECTED]> wrote:
>>>I also wanted to support datasources directly
>
> OK, I'll scrap that idea for now - perhaps it belongs in a separate
> optional or similar tag in the future.
Or really implement that datatype which could be a facade
to JNDI among oth
Stefan Bodewig wrote:
On Tue, 21 Jan 2003, Paul King <[EMAIL PROTECTED]> wrote:
For the JDBC drivers I have used so far, one could always encode the
properties inside the URL, but a more explicit way may be better, I
agree.
And I can support properties:
properties="weblogic.server.url=t3:/
elements.
Just a thought.
Jose Alberto
-Original Message-
From: Paul King [mailto:[EMAIL PROTECTED]
Sent: Tue 1/21/2003 8:17 AM
To: [EMAIL PROTECTED]
Cc:
Subject: proposed patch to ANT SQL task
Hi, I needed
Paul,
Also, have a look at the DynamicConfigurator interface. This would
allow you to be completely dynamic about which attributes you accept.
As stated though, be careful about which JDK you are relying on and
that your code is backwards compatible to 1.1.
Erik
On Tuesday, January
On Tue, 21 Jan 2003, Paul King <[EMAIL PROTECTED]> wrote:
> Hi, I needed to pass properties in to a type-3 JDBC driver
> (WebLogic's RMI driver) in a SQL task. Perhaps I missed
> how this could be done using existing functionality.
I don't think you've missed anything.
For the JDBC drivers I ha
Hi, I needed to pass properties in to a type-3 JDBC driver
(WebLogic's RMI driver) in a SQL task. Perhaps I missed
how this could be done using existing functionality.
I also removed the need to have userid and password specified.
The JDBC spec doesn't require them and some database drivers
such a
