[Installation, Configuration & DEPLOYMENT] - seam example will not deploy
by woo37830
Installed using jems installer the JBoss-4.0.5.GA. Selected the full installation ( tried just the ejb and that didn't work either ).
Installed the jboss-seam-1.2.1.GA.
This is Mac OS X 10.4.10 so edited the build.properties to point to my tomcat.home and my jboss.home.
cd'd to examples/booking and did ant deploy. No errors! it copied ear file to JBoss.*/server/deploy.
Started JBoss server via bin/run.sh
I get
--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@7ae9c196 { url=file:/Applications/jboss-4.0.5.GA/server/default/deploy/jboss-seam-registration.ear }
deployer: org.jboss.deployment.EARDeployer@10ad7e
status: Deployment FAILED reason: ejb-jar.xml must either obey the right xml schema or define a valid DOCTYPE!
state: FAILED
watch: file:/Applications/jboss-4.0.5.GA/server/default/deploy/jboss-seam-registration.ear
altDD: null
lastDeployed: 1185976224917
lastModified: 1185976224000
mbeans:
WHY does the ejc-jar.xml not have the correct information?
How do I correct this? I want to get the first example working. booking doesn't work either and gives the same error.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069654#4069654
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069654
17Â years, 3Â months
[JBossCache] - duplicate dependencies, classloader isolation, JBoss version
by jfrancis_dsl
JBossCache version: 1.4.1SP3/1.4.1SP4.
I have a web application, packaged as a .war, that is targeted towards multiple-versions/multiple-vendors of J2EE. JBossCache is used as the second-level cache for Hibernate, and usually works quite well.
In jboss-web.xml, I keep java2ClassLoadingCompliance=false, to avoid conflicts with JBoss's system copies of libraries (this mainly for complete isolation of logging).
In web-inf/lib, I have copies of jboss-common.jar, jboss-system.jar, and jboss-jmx.jar (minus the javax.jmx api classes), along with jboss-cache.jar
The first three jars (system, common, jmx) MUST reside in web-inf/lib for JBossCache to work on non-JBoss appservers.
On appserver 4.0.5GA, this works great.
THE PROBLEM:
It doesn't work on JBoss versions other than 4.0.5. I've tried 4.0.4GA, 4.0.4GA-Patch1, and 4.2.0GA. On these JBoss versions, a vanilla JNDI lookup of a vanilla Datasource object in a servlet's init() method fails in a strange way. The datasource JNDI name is resolved without NamingException, but the object bound to the name is a null.
What seems to be occurring is that because java2ClassLoadingCompliance is set to false, the webapp is getting its own, half-corrupted JNDI tree, originating in the 3 jboss jars in web-inf/lib, instead of the usual system JNDI tree containing the datasource.
I need to be able to instruct the JBossCache of these peculiarities. Such that, when its running in JBoss Appserver, it should obtain its dependencies from the appserver, regardless of java2ClassLoadingCompliance setting.
How can I strip down the JBossCache dependencies to the bare minimum? I don't need to deploy it as a standalone JBoss service, nor monitor its stats via JMX.
If I remove the 3 jboss jars from web-inf/lib prior to deployment, the JNDI lookup works OK on 4.0.4/4.2.0. This is the solution of last resort, since it forces customization of the .war file for specific platforms beyond deployment descriptors, multiplying testing and management efforts.
Any thoughts?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069647#4069647
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069647
17Â years, 3Â months
[JBoss Seam] - Avoiding conversationId in links
by g.tomassoni
Dears,
I'm working on a very simple site adopting seam-1.2.1.GA.
The site must be easily indexable by search engines and uses a lot of links with parameters because is basically a tree navigator where items (i.e.: page contents) are keyed by two parameters.
Due to the indexability requirement, I would like to avoid any conversationId parameter in my links, since it is going to let search engines think a referenced page changed when it is not. Removing the conversationId shouldn't lead to any problem since I'm not using conversations at all in this site.
Is there any way to disable the output of the conversationId parameter page- or site-wide, or do I have to put a <s:conversationPropagation type="none"/> in every and each link?
Thanks,
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069641#4069641
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069641
17Â years, 3Â months