Thanks for your quick reply Marvin,
There is no deployment failure, the app is definitely up.
In index.jsp of the CAS webapp, there is a redirect to <context-root>/
login - which is what is happening. So jboss obviously knows what the
context root is, and appends the /login URL.
My issue, I believe, is JBoss not reading a rule in an XML file
somewhere that would otherwise result in a URL rewrite from /cas/login
-> WEB-INF/view/jsp/default/ui/casLoginView.jsp
The only difference between my working Tomcat deployment and my semi-
working JBoss deployment is META-INF/jboss-structure.xml - which is as
follows:
<structure>
<context>
<path name=""/>
<metaDataPath>
<path name="META-INF"/>
</metaDataPath>
</context>
</structure>
Regards,
Alexander
On 17 Nov 2010, at 14:36, Marvin Addison wrote:
Error from jBoss - 404:
description The requested resource (/cas/login) is not available.
The first thing I would check is a deployment failure. Obviously that
resource would be unavailable if the application failed to deploy
cleanly. Check the log file that captures your startup and deployment
logs. Post the relevant parts if you need help troubleshooting the
deployment failure.
No stack trace, so I'm guessing it's an XML failure somewhere?
The most common problem with JBoss deployment is the persistence.xml
file which defines transaction-type="RESOURCE_LOCAL", which is not
suitable for JEE containers that expect container-managed
transactions. See
http://docs.jboss.org/hibernate/entitymanager/3.6/reference/en/html/configuration.html
for more info.
M
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
