As we have seen so far -
1) testing the changes by unit test cases
- adds more dependencies and can have licensing issues
2) and testing the changes by sample
- creates sample just for a single feature and not for a set of features
From the above 2 approaches it is verified that the change is
I guess this is basically what I was trying to say.. documenting that
user can now configure username/password for password protected data
sources should be enough.
+1 for documenting and removing the sample.
On Nov 13, 2007 9:49 PM, Amita Vadhavkar [EMAIL PROTECTED] wrote:
As we have seen so
Basically, I changed the company-webapp not to create a database so I
could use the one I created with authentication required. And I didn't
use the new code, basically I used the support to configure
username/password when defining the data source.
On Nov 11, 2007 11:32 PM, Amita Vadhavkar
What are the modifications you did for this in company webapp? Did you
see that the DS.getConnection(id, pwd) signature is being used
by DAS during this case?
Regards,
Amita
On Nov 9, 2007 11:40 AM, Luciano Resende [EMAIL PROTECTED] wrote:
Hi Amita
I replied to this other thread [1] with
Hi Amita
I replied to this other thread [1] with some questions. But just
FYI, I was able to run a slightingly modified version of
company-webapp using a secured derby database in TC by specifying the
username/password on the datasource definition.
Resource name=jdbc/dastest
changes done -
1) cleaned readme files using eclipse IDE html editor - samples, dbconfig
2) replaced MySQL with Derby
3) replaced sun provided JNDI jars with jboss jar - because - these are
available in mvn repos and only 3 are required in the build path
(jboss-common 3.2.3, jnp-client 4.0.2 and
Comments inline :
On 11/6/07, Amita Vadhavkar [EMAIL PROTECTED] wrote:
changes done -
1) cleaned readme files using eclipse IDE html editor - samples, dbconfig
Good, Thanks, please committ this, you don't have to wait anymore :)
2) replaced MySQL with Derby
Just want to make sure you have
1 readmes commit - I will wait and make it along with any other
changes in JIRA-1698 as we are still deciding which sample to use to
demo the feature of
JIRA-1698
2 There are 3 test cases in ConnectionTests, please see if you find
some other cases that can be included.
3 Using jboss jars - as
On 11/5/07, Luciano Resende [EMAIL PROTECTED] wrote:
I was trying to run the new DAS sample (dataSource) and I looks like
it requires MySQL in order to run the sample, this might not be the
best default configuration to require, as it requires lots of steps in
order to just try the sample
I was trying to run the new DAS sample (dataSource) and I looks like
it requires MySQL in order to run the sample, this might not be the
best default configuration to require, as it requires lots of steps in
order to just try the sample (e.g install MySQL), and it also makes it
difficult to test
10 matches
Mail list logo
