[JBoss Seam] - Re: 2.0.0.CR2 Seam-gen Error
by nathandennis
"pete.muir(a)jboss.org" wrote : Dan is away atm, but sent me this
|
| anonymous wrote : Interesting...when I added the H2MetadataDialect I just added all the ones that are available. Looks like there is some sort of problem with the postgres one (aside from the spelling error in the class name). We might want to see if this is a hibernate-tools issue or whether there is something about this person's database that is strange.
|
| Please file a JIRA issue so we get this fixed for the GA.
A little more info on the database..
postgres 8.1.5-13
postgresql.jar (JDBC 3) downloaded from postgresql.org
im not sure that there is anything strange about the database. it has been running like a rock using the same jar since seam 1.2.
i tell you what i have found that is strange.. entities that i had already written to this same database before the upgrade were working fine with RC1 but after the upgrade ,, they will no long persist or update. WITH NO ERROR MESSAGE. ???? but they retrieve just fine. im not sure if the two problems are related. i have some serious red eye going on over here.. i will be glad when all the dust settles. i really want all this new structure in place... because i have a sneaky suspicion it will make all the future upgrades that much easier.
i'll go make an attempt at the JIRA on the Dialect issue,,,
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092815#4092815
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092815
18Â years, 7Â months
[JBoss Seam] - Re: seam-gen : old issues
by atao
About i18n:
I agree with you, the #{messages...} are ugly, but it's the standard way to do i18n with Seam...
An other way is #{interpolator.interpolate...}, but imo it's worse and should be used only if necessary.
I think that seam-gen is not only for beginners, or "a fun prototype, but an excellent place to start with new applications" as said Dan Allen.
An option would be to be able to generate:
- either monolanguage application with hard coded messages, by default for beginners or if no multi languages is needed
- or fully i18n application if required
but then it adds a little more complexity in templates.
About i18n (2):
anonymous wrote :
| The patch might have been updated last time I saw it; but the first patch I looked at generated *alot* of additional files 1 per view artifcat...if that is not the case anymore then I rest my case ;)
|
I don't remember exactly what does the first patch. At least the second patch still uses a lot of properties files but not one per view artifact! And now the current version here uses by default 3 properties files by language, as stated before:
- one with constant messages provided by Seam
- one with all the messages generated
- one with specific messages provided by the developer
A lot of temp files are generated, but only the properties files above are to be know by the developer.
About many-to-many:
anonymous wrote :
| then that is an issue with seam-gen's templates; and since RHDS does its best to work with the seam developed templates we don't have a "fix" for that
|
If I understand, this issue has to be managed by seam-gen. Then the situation is:
- many-to-many can't be managed by target "generate-entities": I don't remember where but on the forum or in jira there is a discussion on this issue.
- I wrote a patch to add many-to-many above the patch for JBSEAM-843
- but JBSEAM-843 will not be added to seam-gen
So now I have no clear vision of the next step...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092800#4092800
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092800
18Â years, 7Â months