Re: [Springframework-developer] petclinic, hsqldb, & jboss

[Rajeev K. <Ra...@cu...>]

Hi Jean-Pierre,

I actually used the jboss supplied hsqldb-ds.xml file instead of =
hsql-petclinic-ds.xml.  I modified the petclinic build.properties to use =
the port 1701 for hsql, and the jboss-web.xml to use the =
"java:/DefaultDS" as the jndi name.  This eliminates the step of having =
to copy a separate hsql-petclinic-ds.xml file in the Jboss deploy dir. =
The petclinic application works fine with this setting.  However, I am =
still getting the JBOSS "MessageCache" error.

Rajeev
  ----- Original Message -----=20
  From: JP Pawlak=20
  To: 'Rajeev Kaul'=20
  Sent: Tuesday, July 29, 2003 12:12 AM
  Subject: RE : [Springframework-developer] petclinic, hsqldb, & jboss


  Hi Rajeev,



  Thanks for your feedback !



  1)

  , ObjectName: jboss.mq:service=3DMessageCache state: FAILED

  I used the same port number as the standard standalone HSql like =
Thomas used for Tomcat. However, this port seems be used by jboss.mq. As =
long as you don't use the messaging service,  you will not have trouble =
with this, except the message you reported.=20



  For fixing: change the port number from 9001 to 1701 in =
hsql-petclinic-ds.xml as well as inhsql.url in build.properties.

  I didn't make it for having the same port for JBoss and others AS.





  2)

  1.  The petclinic build does not automatically copy the =
hsql-petclinic-ds.xml to the deploy directory.

              It would complicate more the build process as the version =
of JBoss should be asked in the properties. The xxx-ds.xml files are =
different for jboss 3.0.xx and 3.2.xx.

  3)

  2. The web.xml does not contain the following information:

  <resource-ref>

  <res-ref-name>jdbc/petclinicHSQL</res-ref-name>

  <res-type>javax.sql.DataSource</res-type>

  <res-auth>Container</res-auth>

  </resource-ref>

  <resource-ref>

  <res-ref-name>jdbc/petclinicMYSQL</res-ref-name>

  <res-type>javax.sql.DataSource</res-type>

  <res-auth>Container</res-auth>

  </resource-ref>



              Right ! I added it.



  4)

  3.  The "DROP TABLE" sql commands cause a problem, when you run the =
script the first time.  I had to comment them out from the build.xml in =
the db dir for the 1st build. In subsequent builds it worked fine.

   I splitted drop and creation tasks, but using the attribute =
onerror=3D "continue" for these sql tasks.



  Regards,

  Jean-Pierre