Red Hat Bugzilla – Bug 843439
URLs are changed if Sportsclub example is deployed via JBDS
Last modified: 2012-11-30 10:33:57 EST
If Sportsclub is deployed via JBDS, the URLs the example can be accessed by are different comparing to deployment via maven. For more detailed description see Comment 26 and Comment 29 of https://bugzilla.redhat.com/show_bug.cgi?id=800024.
Look at https://issues.jboss.org/browse/JBIDE-12369. There is a comment with the proposal, how to avoid this behavior, so the URLs remain the same regardless what tool is used for packaging/deployment.
Version-Release number of selected component (if applicable):
Copying solution from JBIDE-12369:
You need to remove the <earSourceExcludes>**/application.xml</earSourceExcludes> from your ear plugin config. And update the ear project configuration (right click on project > Maven > Update project configuration.
Basically all exclusion patterns in the pom are translated to packaging exclusion patterns in WTP / the JBoss AS server adapter. There's no easy way to match that maven feature in WTP, so it's a trade-off and you've hit one of the corner cases.
I removed <earSourceExcludes>**/application.xml</earSourceExcludes> from all sportsclub examples.
Only sportsclub-ear/pom.xml files for all spring variants have been fixed. The same fix has to be applied to sportsclub-jpa-ear/pom.xml files for all spring variants.
Ok, done - I applied the fix for all sportsclub-jpa-ear/pom.xml files.
Verified in WFK 2.1.0.CR1 and JBDS 5.0.1.GA.
Distributed as a part of WFK 2.1.0.GA release.