-
1. solved Re: migration from 1.2 to 2.0beta1 @In
livenow Jun 29, 2007 11:03 AM (in response to livenow)works with session2 instead of session.
could you please post a list of restricted keywords for Seam component names?
cheers,
Christoph -
2. Re: migration from 1.2 to 2.0beta1 @In
gavin.king Jun 29, 2007 2:02 PM (in response to livenow)Ouch. I need to alias org.jboss.seam.web.session to some other name than just "session". Ooops!
please raise an issue in JIRA -
3. Re: migration from 1.2 to 2.0beta1 @In
awhitford Jul 12, 2007 8:24 PM (in response to livenow)The lack of qualification for the component name presents this risk. Why not make it best practice to qualify the component name? So built-in components are "org.jboss.seam.Session", and my own objects would be "com.domain.project.Session". I know it seems verbose, but it just seems practical for large projects.
-
4. Re: migration from 1.2 to 2.0beta1 @In
pmuir Jul 13, 2007 11:23 AM (in response to livenow)All seam components have qualified names, they are aliased using @Factory to their short name. If you are in a large project qualifying your names is a very good idea :)
-
5. Re: migration from 1.2 to 2.0beta1 @In
gavin.king Jul 15, 2007 5:43 AM (in response to livenow)For commonly-used components, @In("org.jboss.seam.web.session") is really verbose.
I should try and figure out some concept of "namespaces", where components in the same namespaces don't need to use qualified names to refer to each other. And where there is some mechanism for "importing" a namespace into another namespace.
But we don't have anything like that yet. -
6. Re: migration from 1.2 to 2.0beta1 @In
matt.drees Jul 15, 2007 3:53 PM (in response to livenow)That'd be neat.