Luciano Resende wrote:
Some comments
(2) The DAS supports passing of a Connection object to the runtime.
Our unit tests are obtaining a Connection using DriverManager.
I think the issue is more around this use case in a DAS Container, as the
user will not be able to manualy pass a connection as the container
would be
doing the das instantiation. We might be able to solve this by telling
the
container that this is a J2SE env on the SCDL.
At one point, we intended to support both the DataSource info (as we
have today for J2EE applications) as well as DriverManager info for J2SE
applications. We may have rejected the idea early on because of the
need to put username/password info in the config for DriverManager.
I have opened TUSCANY-948 to track this.
As for :
3) Is it better to follow conventions in forming command name, it
can be
helpful in Declarative DAS development.
Well, I think we can try to follow one convention, but users can put
whatever they want on the das config file... and I also believe this is a
valid case... so if they don't follow the convention and there is no
other
ways to create maps, we would throw back an exceptio...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
