compüonents.xml not scanned on Linux...fhh Jul 18, 2007 4:48 PM
I have a strange problem: On my development machine running windows my application work fine. When I deploy it to the server it fails because the components.xml file is not scanned properly.
The odd thing is that components.xml is found:
2007-07-19 00:09:10,785 DEBUG [org.jboss.seam.deployment.Scanner] archive: /opt/jboss-4.2.0.GA/server/default/tmp/deploy/tmp42377go100-backoffice.ear-contents/go100-model-ejb-0.1-SNAPSHOT.jar ... 2007-07-19 00:09:10,785 DEBUG [org.jboss.seam.deployment.Scanner] found: META-INF/components.xml
The only hint I have is the following warning during deployment:
2007-07-19 00:09:10,905 WARN [org.jboss.seam.init.Initialization] namespace declared in components.xml does not resolve to a package annotated @Namespace:
My compnents.xml looks like this:
<components xmlns="" xmlns: <persistence:managed-persistence-context </components>
Does anybody know why this might work under Windows and not under Linux? My first suspicion that this might be about the upper/lower case.
Regards
Felix
This content has been marked as final. Show 3 replies
1. Re: compüonents.xml not scanned on Linux...fhh Jul 19, 2007 7:31 PM (in response to fhh)
This only happens with Seam CVS as of 7/18.
Seam 2.0.0 BETA1 works well on Windows and Linux!
Regards
Felix
2. Re: compüonents.xml not scanned on Linux...fhh Jul 20, 2007 6:07 AM (in response to fhh)
Has anybody got an idea about this one? Is there any information I should supply?
If not I will create a JIRA issue.
Regards
Felix
3. Re: compüonents.xml not scanned on Linux...fhh Jul 21, 2007 7:27 PM (in response to fhh)
The problem is related to be JDK 1.6.0 which is installed on my windows machine. Using 1.5.0_08 produces jars which work under Linux and Windows.
Not sure what the problem might be but maybe this should go into the release notes.
Regards
Felix