aspose file tools*
The moose likes JBoss/WildFly and the fly likes Seam components.properties (Ant vs Maven style tokens) Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "Seam components.properties (Ant vs Maven style tokens)" Watch "Seam components.properties (Ant vs Maven style tokens)" New topic
Author

Seam components.properties (Ant vs Maven style tokens)

Duran Harris
Ranch Hand

Joined: Nov 09, 2008
Posts: 598

Hi Guys,

I am a bit confused at the moment regarding Seam's components.properties file. The documentation says that it's intended for replacement of ant-style tokens in components.xml (so @token@ vs ${token}) but the part that is really confusing me is that in the seam-booking example they use ${jndiPattern} in components.xml and then enable filtering when copying resources during the maven build... I really don't see what part Seam plays in this if Maven is simply replacing the value...

Can someone shed some light on this?


===>SCJP 1.5(72%)<===
==>SCWCD1.5(76%)<===
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10210
    
166

Duran Harris wrote: The documentation says that it's intended for replacement of ant-style tokens in components.xml (so @token@ vs ${token})


Can you point us to that doc?

[My Blog] [JavaRanch Journal]
Duran Harris
Ranch Hand

Joined: Nov 09, 2008
Posts: 598

Well I am actually reading Seam in Action, pg 62 says :

resources/components.properties Replacement properties for Ant-style tokens

Although I am aware that the book was written when Seam 2.0 was out. Another source of my confusion is that if I try the same approach that the seam booking example does (ie simply use a filter when copying resources during the maven build, I can see that the Maven filter replaced the value of ${jndiPattern} in components.xml with the value specified in the pom.xml of the web project but at runtime the application still tells me :

Caused by: java.lang.IllegalArgumentException: You must specify org.jboss.seam.core.init.jndiPattern or use @JndiName:

My main issue is that I have a single web-project and multiple seam-ejb projects, so I need to figure out a way for the jndi-pattern to correctly reflect the name of each ejb module...
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Seam components.properties (Ant vs Maven style tokens)