Built with Seam
You can find the full source code for this website in the Seam package in the directory /examples/wiki. It is licensed under the LGPL.
| Online: | 12 Members of 9401 |
| Forum: Seam Users |
 |
17. Apr 2008, 15:11 America/New_York | Link |
I use the maven repos and it seems like there have been some changes, although I use the same version number (2.0.1.GA).
From pom.xml
<parent> <groupId>org.jboss.seam</groupId> <artifactId>root</artifactId> <version>2.0.1.GA</version> </parent> <dependency> <groupId>org.jboss.seam</groupId> <artifactId>jboss-seam</artifactId> </dependency>
The jar files differ in size and I get the following error compared to before:
14:58:49,254 INFO [Initialization] reading /WEB-INF/components.xml 14:58:49,307 WARN [Initialization] namespace declared in components.xml does not resolve to a package annotated @Namespace: http://jboss.com/products/seam/core 14:58:49,307 WARN [Initialization] namespace declared in components.xml does not resolve to a package annotated @Namespace: http://jboss.com/products/seam/mail 14:58:49,307 WARN [Initialization] namespace declared in components.xml does not resolve to a package annotated @Namespace: http://jboss.com/products/seam/core 14:58:49,307 WARN [Initialization] namespace declared in components.xml does not resolve to a package annotated @Namespace: http://jboss.com/products/seam/persistence 14:58:49,307 WARN [Initialization] namespace declared in components.xml does not resolve to a package annotated @Namespace: http://jboss.com/products/seam/persistence 14:58:49,307 WARN [Initialization] namespace declared in components.xml does not resolve to a package annotated @Namespace: http://jboss.com/products/seam/security 14:58:49,307 WARN [Initialization] namespace declared in components.xml does not resolve to a package annotated @Namespace: http://jboss.com/products/seam/web 14:58:49,308 WARN [Initialization] namespace declared in components.xml does not resolve to a package annotated @Namespace: http://jboss.com/products/seam/web
And then, probably due to above, there is no Entitymanager etc.
What bothers me the most is not that this might be my bad or seam-people-bad, but that a jar in a repository with a certain version number, is changed...
Any comments from the seam developers?
No changes to the JAR in the jboss repo since the initial publish.
Read about how to report a bug.
OK, I guess this is just some kind of glitch (notice size difference)
Today
Older project
Both use a pom with the same Seam version number.
It's not an issue now that a newer version of Seam is availible.
Cheers
After the latest release (2.0.3.CR1) this occurs again. Running a maven script which gets 2.0.2.SP1 will result in a jboss-seam-2.0.2.SP1.jar which differs in size from the jboss-seam-2.0.2.SP1.jar that I have used for quite some time in production. (with daily builds...)
The new jar creates no entitymanager of course everything then crashes. Exchanging the jar for the old jar makes everything work again.
Upgrading the pom to use 2.0.3.CR1 also makes everything work.
I guess there might be some weird stuff happening in the maven parent structure, which messes up the versioning.
That's weird. try to clean you local repo...
We use 2.0.1.GA with no problems. Although we use Artifactory 'in between' which caches all artifacts to reduce traffic....
Regards,
Siarhei