-
15. Re: Exclude jars from deploy
A lot of Seam libraries contain faces_config.xml which defines some JSF components.
See jboss-seam.jar/META-INF -
-
17. Re: Exclude jars from deploy
They are different faces_config.xml files.
The Configuration node shows all faces_config,xml files which is normal behavior. If you open some of those files, you will see that they contain different component. -
18. Re: Exclude jars from deploy
Hm. this is veeery strange.
And what i'v done now.
I'v got this project, copy on different PC and import in workspace.
So now i have only 1 faces-config.xml.
Where is the truth? -
19. Re: Exclude jars from deploy
Probably your classpath in the new workspace isn't configured correctly.
If Seam libraries are in the classpath, their faces_config.xml should be shown in the Configuration node. -
-
-
22. Re: Exclude jars from deploy
So what?Who cares about faces-config in seam.jar or in facelets.jar.
-
23. Re: Exclude jars from deploy
We should definitely name or group those resources differently when there are multiple resources.
Please report in jira if possible - thanks! -
24. Re: Exclude jars from deploy
Hi Krasig,
Why do you have richfaces jars in \standart\lib ?
They are not there by default. Who put them there ? -
25. Re: Exclude jars from deploy
I put them there because i have 9-10 application (JSF + RichFaces + Facelets) and all this application have identical set of jars. So now all jarsare in standard\lib, in this way deploy is smaller and faster.
Is this wrong? -
27. Re: Exclude jars from deploy
well, if you put different jars in there you need to make sure to remove those jars you are duplicating in your other projects.
The tools just adds the jars to help - if you don't want the jars in the war then just remove them