With that change you backed out the 'fix' applied in JUDDI-221, and now
the datasource checker in happyjuddi works again, and we'll have to see
why JUDDI-221 broke things.
Hope you're on your way now!
--Kurt
Amit Deokar wrote:
With the change you suggested, I got the following output -
----
jUDDI Dependencies: Resource & Properties Files
jUDDI DataSource Validation
+ Got a JNDI Context!
+ Got a JDBC DataSource (dsname=java:comp/env/jdbc/juddiDB)
+ Got a JDBC Connection!
+ SELECT COUNT(*) FROM PUBLISHER = 2
----
So, it seems that the install works okay, right?
But, I am curious what did that change really do? I am still puzzled.
Best regards,
Amit
On Thu, Jun 25, 2009 at 10:35 AM, Kurt T Stam<[email protected]> wrote:
Amit,
In the happyjuddi.jsp try replacing
dsname = Util.escapeXml(request.getParameter("dsname"));
with
dsname = request.getParameter("dsname");
--Kurt
Amit Deokar wrote:
I did not mention in my earlier email that I also tried just using the
ready-to-go jUDDI v2.0 rc7 + Tomcat install package
(juddi-tomcat-2.0rc7.zip) in the hope that it would work with
pre-installed Apache Derby database. But, I got the same message from
happyjuddi page -
-----
jUDDI Dependencies: Resource & Properties Files
jUDDI DataSource Validation
- No JNDI Context (null)
- No 'null' DataSource Located(null)
- DB connection was not acquired. (null)
- SELECT COUNT(*) FROM PUBLISHER failed (null)
-----
On another note, I had JDK 1.6.0_13 earlier, so I tried installing JDK
1.5.0_19 and then giving it a shot - same result.
(Note - This is a follow up on my previous email. Please take a look
at that note too).
Thanks for your help in this.
Best regards,
Amit
