Unable to deploy PetClinic JDBC SampleApp

[Beta User]

Hi,
I've downloaded the just-released PetClinic jdbc sample application, and I'm having problems installing it.

I start up the S2AP Server (startup.sh), Then I connect to the Admin Web Module, and I locate and upload the par file of the sample app.
First, I've got one error related to "hsqldb" not resolved => I grabbed it from the S2 Repository and installed it in springsource-ap-1.0.0.beta/repository/bundles/usr.
Then, sae issue with commons DBCP => same workaround.

But then, I get a cryptic eorror message:
Result of the last operation: 'Deployment Error: The modules of application 'org.springframework.petclinic.jdbc' version '1.0.0.RELEASE' cannot be resolved'.

Still can't find something useful in the logs, but I'm still looking into this.

[Andy Wilkinson]

Hi Jawher,

The Platform doesn't ship with all of the sample's dependencies so you need to collect them and add them to the Platform's bundle repository. The readme.txt in the sample's projects/par folder contains instructions regarding building the sample, collecting its dependencies, setting up the database etc. Please take a look at those and let us know if you have any further problems.

Thanks,
Andy

[Beta User]

Yop, I've got something: a stacktrace (I'll just give the tail here):

Caused by: com.springsource.platform.osgi.framework.OsgiFrame workException: Unable to satisfy dependencies of bundle 'org.springframework.petclinic.jdbc-1.0.0.RELEASE-org.springframework.petclinic.repository.jdbc':
Cannot resolve: org.springframework.petclinic.jdbc-1.0.0.RELEASE-org.springframework.petclinic.repository.jdbc
Unsatisfied leaf constraints:
Bundle: com.springsource.org.apache.commons.dbcp_1.2.2.osg i - Import-Package: org.apache.commons.pool.impl; version="[1.3.0,2.0.0)"
Did you mean: 'org.apache.commons.logging.impl'?
Bundle: com.springsource.org.apache.commons.dbcp_1.2.2.osg i - Import-Package: org.apache.commons.pool; version="[1.3.0,2.0.0)"
Did you mean: 'org.apache.commons.io'?

at com.springsource.platform.osgi.framework.equinox.E quinoxBundleInstaller.satisfyConstraints(EquinoxBu ndleInstaller.java:303)
... 74 more

Erf ... I should known better: commons DBCP depends on Commons Pool ... I'll add the latter to my local repository and post here the results.

Anyway, the Admin module seems not able to report problem on indirect/transitive dependancies ... can this be fixed ?

[Beta User]

Oups ... thanks Andy and sorry : I've jumped on it too damned fast :red:

[Andy Wilkinson]

Thanks for the feedback regarding the message in the admin console. I've opened http://issuetracker.springsource.com/browse/PLATFORM-18 to address this.

Andy

[Beta User]

Might be a foobar question ...
but after the app has been properly deployed, how do I call it ??

Below is the output taken from the admin console:

Associated Modules:
org.springframework.petclinic.web (type: Web) No personality identifer
org.springframework.petclinic.domain (type: Bundle) No personality identifer
org.springframework.petclinic.infrastructure.hsqld b (type: Bundle) No personality identifer
org.springframework.petclinic.jdbc-synthetic.context (type: Bundle) No personality identifer
org.springframework.petclinic.repository (type: Bundle) No personality identifer
org.springframework.petclinic.repository.jdbc (type: Bundle) No personality identifer

I took a look into the MANIFEST.MF from the ..petclinic.web-... bundle which said that a context "petclinic" should be available.
But trying to access it via
localhost:8080/petclinic
or
localhost:8080/petclinic/index.jsp
just produces 404 error.

Any idea ???

[Beta User]

I fixed this by:
- remove par from pickup
- restart s2ap server
- put par to pickup

--
Olex

[Andy Wilkinson]

Thorsten,

It looks like the deployment process failed to register the Web module in the application successfully. The first line in the list of associated modules should read:

org.springframework.petclinic.web (type: Web) /petclinic

We've seen this problem a few times when deploying via the admin console and we're working on a fix. Did you deploy via the admin console, or by copying the par to pickup?

Thanks,
Andy

[Beta User]

I used pickup and the same problem happened for the first time.
It was not reproduced after server restart and par redeploy.

--
Olex

[Beta User]

the problem was connected to a misconfigured hsql db on my site.
I did not use your provided hsql script at first place.

thanks for your help