|
Rick, there's no requirement for the context to be lower case, though embedded spaces are probably not a good idea. I'm not sure whether logic has been added in 5.1.2 to "help" you by changing your context name to something it thinks is appropriate, but I can at least tell you how to find what that context name is. Open up your EAR Deployment Descriptor (if you haven't created your own EAR project, one called DefaultEAR will have been created for you). Click on the Modules tab and you will see all your WAR files (there may only be one if you only have one project). If you click on the WAR file, you should see the context root in the upper right portion of the view. Joe > From: Rick.Chevalier@xxxxxxxxxxxxxxx > > Hi Joe, > > I'm using version 5.1.2. All the updates have been applied even though > the version number doesn't reflect it. Don't know why. I believe it was > this way with 5.0 also. > > Is there any requirement that the context be in a specific case or not > have spaces? It seems odd that changing to lower case and removing spaces > would correct the problem. Maybe when the references were updated > something got changed behind the scenes that corrected the problem not the > changes I made.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.