All, We are aiming for a code freeze for 2.1.1.CR2 for midday Thursday (EST), and then move quickly to the GA. If you've got anything you want in for 2.1.1.GA, make sure it is in by the 2.1.1.CR2 code freeze :-) Best, Pete _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

https://jira.jboss.org - no jira = no fix :-) /Kenneth On 04/12/2008, at 16.31, Francisco Peredo wrote: > > Hi! > > It would be nice if this bugs could be fixed ;-): > > http://www.seamframework.org/Community/MorePossibleBugsInManyPlaces > http://www.seamframework.org/Community/PossibleBugInOrgjbossseamcoreValid... > http://www.seamframework.org/Community/PossibleBugInManagedEntityWrapper > http://www.seamframework.org/Community/PossibleBugInEjbEntityDescriptorjava > http://www.seamframework.org/Community/PossibleBugInJpaPermissionStorejave > http://www.seamframework.org/Community/PossibleConvertertChainjavaBug > http://www.seamframework.org/Community/IfAMethodReturnsBooleanItShouldntR... > > Sorry for cross-posting, I posted all this in the seam user forum, > but now > that I think about it they seem to be more "seam dev related" than > "seam > user related" so now I believe maybe I should have posted them here... > Am I right? > > Regards, > > Francisco > > > Pete Muir-2 wrote: >> >> All, >> >> We are aiming for a code freeze for 2.1.1.CR2 for midday Thursday >> (EST), and then move quickly to the GA. >> >> If you've got anything you want in for 2.1.1.GA, make sure it is in >> by >> the 2.1.1.CR2 code freeze :-) >> >> Best, >> >> Pete >> _______________________________________________ >> seam-dev mailing list >> seam-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/seam-dev >> >> > > -- > View this message in context: > http://www.nabble.com/Seam-2.1.1.CR2-tp20793809p20835746.html > Sent from the seam-dev mailing list archive at Nabble.com. > > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev > _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

I fixed the ManagedEntityWrapper, JpaPermissionStore, and ConverterChain. As for the rest, please submit a general JIRA for addressing FindBugs best practices (things like null checks, etc). Pete, does that sound like the best approach? -Dan On Thu, Dec 4, 2008 at 10:31 AM, Francisco Peredo <franciscoperedo(a)tabasco.gob.mx&gt; wrote: > > Hi! > > It would be nice if this bugs could be fixed ;-): > > http://www.seamframework.org/Community/MorePossibleBugsInManyPlaces > http://www.seamframework.org/Community/PossibleBugInOrgjbossseamcoreValid... > http://www.seamframework.org/Community/PossibleBugInManagedEntityWrapper > http://www.seamframework.org/Community/PossibleBugInEjbEntityDescriptorjava > http://www.seamframework.org/Community/PossibleBugInJpaPermissionStorejave > http://www.seamframework.org/Community/PossibleConvertertChainjavaBug > http://www.seamframework.org/Community/IfAMethodReturnsBooleanItShouldntR... > > Sorry for cross-posting, I posted all this in the seam user forum, but now > that I think about it they seem to be more "seam dev related" than "seam > user related" so now I believe maybe I should have posted them here... > Am I right? > > Regards, > > Francisco > > > Pete Muir-2 wrote: >> >> All, >> >> We are aiming for a code freeze for 2.1.1.CR2 for midday Thursday >> (EST), and then move quickly to the GA. >> >> If you've got anything you want in for 2.1.1.GA, make sure it is in by >> the 2.1.1.CR2 code freeze :-) >> >> Best, >> >> Pete >> _______________________________________________ >> seam-dev mailing list >> seam-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/seam-dev >> >> > > -- > View this message in context: http://www.nabble.com/Seam-2.1.1.CR2-tp20793809p20835746.html > Sent from the seam-dev mailing list archive at Nabble.com. > > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev > -- Dan Allen Software consultant | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.

Standard rules apply, one JIRA per distinct issue. On 4 Dec 2008, at 16:24, Dan Allen wrote: > I fixed the ManagedEntityWrapper, JpaPermissionStore, and > ConverterChain. As for the rest, please submit a general JIRA for > addressing FindBugs best practices (things like null checks, etc). > Pete, does that sound like the best approach? > > -Dan > > On Thu, Dec 4, 2008 at 10:31 AM, Francisco Peredo > <franciscoperedo(a)tabasco.gob.mx&gt; wrote: >> >> Hi! >> >> It would be nice if this bugs could be fixed ;-): >> >> http://www.seamframework.org/Community/MorePossibleBugsInManyPlaces >> http://www.seamframework.org/Community/PossibleBugInOrgjbossseamcoreValid... >> >> http://www.seamframework.org/Community/PossibleBugInManagedEntityWrapper >> >> http://www.seamframework.org/Community/PossibleBugInEjbEntityDescriptorjava >> >> http://www.seamframework.org/Community/PossibleBugInJpaPermissionStorejave >> >> http://www.seamframework.org/Community/PossibleConvertertChainjavaBug >> http://www.seamframework.org/Community/IfAMethodReturnsBooleanItShouldntR... >> >> >> Sorry for cross-posting, I posted all this in the seam user forum, >> but now >> that I think about it they seem to be more "seam dev related" than >> "seam >> user related" so now I believe maybe I should have posted them here... >> Am I right? >> >> Regards, >> >> Francisco >> >> >> Pete Muir-2 wrote: >>> >>> All, >>> >>> We are aiming for a code freeze for 2.1.1.CR2 for midday Thursday >>> (EST), and then move quickly to the GA. >>> >>> If you've got anything you want in for 2.1.1.GA, make sure it is in by >>> the 2.1.1.CR2 code freeze :-) >>> >>> Best, >>> >>> Pete >>> _______________________________________________ >>> seam-dev mailing list >>> seam-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/seam-dev >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/Seam-2.1.1.CR2-tp20793809p20835746.html >> Sent from the seam-dev mailing list archive at Nabble.com. >> >> _______________________________________________ >> seam-dev mailing list >> seam-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/seam-dev >> > > > > -- > Dan Allen > Software consultant | Author of Seam in Action > > http://mojavelinux.com > http://mojavelinux.com/seaminaction > > NOTE: While I make a strong effort to keep up with my email on a daily > basis, personal or other work matters can sometimes keep me away > from my email. If you contact me, but don't hear back for more than a > week, > it is very likely that I am excessively backlogged or the message was > caught in the spam filters. Please don't hesitate to resend a > message if > you feel that it did not reach my attention. > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev

On 4 Dec 2008, at 16:57, Francisco Jose Peredo wrote: > Hi! > > Great job Dan! > > You missed > http://www.seamframework.org/Community/PossibleBugInOrgjbossseamcoreValid... > > ;-) -> JIRA as Dan and I said

> > > Oh, and what is you opinon on: > > http://www.seamframework.org/Community/IfAMethodReturnsBooleanItShouldntR... > > ? I think its fine, null == undefined which is valid state for something to be in.

> > > Regards, > > Francisco >

Databases use this three-state for decades. It seems to work fine.

On Dec 4, 2008, at 19:43, Francisco Jose Peredo wrote: > Hi! > > Pete Muir escribió: >> >> On 4 Dec 2008, at 16:57, Francisco Jose Peredo wrote: >> >>> Hi! >>> >>> Great job Dan! >>> >>> You missed >>> http://www.seamframework.org/Community/PossibleBugInOrgjbossseamcoreValid... >>> >>> >>> ;-) >> >> -> JIRA as Dan and I said > Fine, I'll JIRA. >> >>> >>> >>> Oh, and what is you opinon on: >>> >>> http://www.seamframework.org/Community/IfAMethodReturnsBooleanItShouldntR... >>> >>> >>> ? >> >> I think its fine, null == undefined which is valid state for something >> to be in. > Yes, but I have always felt uneasy about a null boolean thing... the > point of boolean is to restrict the possible outcomes of something to > "true" or "false", but with a nullable boolean we now have 3 possible > outcomes "true", "false" and "undefined"... and the problem is that > "undefined" is also "typeless" and therefore bug prone, the code: > > if(isUserInRole("administrator)){ > //do something > } > else { > //do something else > } > > looks like something perfectly valid, but it turns out it can crash > because isUserInRole can return null. > > I mean I can understand it for MailComponent.getBoolean, and > org.jboss.seam.ui.util.JSF.getBooleanValue, but I don't like it for > org.jboss.seam.ui.graphicImage.Image.isRatio or > org.jboss.seam.web.IsUserInRole.isUserInRole. > > Wouldn't it be better to use an Enum if there are 3 or more possible > outcomes? > > Regards, > Francisco >> >>> >>> >>> Regards, >>> >>> Francisco >>> > > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev

So you never use outer joins? Every outer join produces null values. On Thu, Dec 4, 2008 at 1:04 PM, Francisco Jose Peredo <franciscoperedo(a)tabasco.gob.mx&gt; wrote: > I try to avoid it in databases, if there are 3 different possible > values, it is better to use a not null Integer column, all my boolean > columns are "not null" always. > > Emmanuel Bernard escribió: > >> Databases use this three-state for decades. It seems to work fine. >> > Many people believe it does not work fine: > http://en.wikipedia.org/wiki/Null_(SQL)#Controversy >

I mean, for those cases isnt it better to wrap the stuff in a view to hide and transform those nulls into true/false stuff? Francisco Jose Peredo escribió: > An outer join where the column in the join is a *nullable boolean*? > Can you give me an example where doing that is better (easier to > understand during maintenace) than using an integer? I do not go > against all nulls, just *boolean *nulls. > > Gavin King escribió: >> So you never use outer joins? Every outer join produces null values. >> >> On Thu, Dec 4, 2008 at 1:04 PM, Francisco Jose Peredo >> <franciscoperedo(a)tabasco.gob.mx&gt; wrote: >> >>> I try to avoid it in databases, if there are 3 different possible >>> values, it is better to use a not null Integer column, all my boolean >>> columns are "not null" always. >>> >>> Emmanuel Bernard escribió: >>> >>>> Databases use this three-state for decades. It seems to work fine. >>>> >>> Many people believe it does not work fine: >>> http://en.wikipedia.org/wiki/Null_(SQL)#Controversy >>> > > ------------------------------------------------------------------------ > > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev > -- Dirección Informática de Servicios Financieros Dirección General de Modernización e Innovación Gubernamental Secretaría de Administración y Finanzas Paseo de la Sierra 435 col. Reforma C.P. 86086, Villahermosa, Tabasco. Tel. 52 + 993 + 310 40 00 Ext. 7127 http://saf.tabasco.gob.mx/ IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente. ------------------------------------------------------------------------ _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

Sorry, but tutorial D handles nulls even worse than SQL: i.e. it doesn't have them, which means that in tutorial D, you have to represent an unknown value by some totally ad hoc "special value" of a non-null type. i.e. you have to define something like -666:=null in a totally arbitrary and ad hoc manner. They seriously recommend this in their books.

The completely broken treatment of null by those guys is one reason why I simply take very little they say seriously. (The other reason is that they don't seem to understand typing very well.)

Frankly, they bamboozle folks who don't know much math with some absurdly overblown mathematical formalism that is totally unnecessary for representing the mathematically trivial problems that occur in databases. Since I actually have a background in higher math, I'm not intimidated by that stuff and I can see straight through their silly arguments. These guys are poseurs (if you read their resumes, they don't actually have a mathematics background).

Sometimes you need null values, sometimes you don't. Java should let you declare whether a value accepts null as part of the type declaration (i.e. @Nullable Foo foo), and non-nullable should be the default. But Java doesn't have this facility, so we just have to live with it.

2008/12/4 Francisco Jose Peredo <franciscoperedo(a)tabasco.gob.mx&gt;: > All right, all right, you outer join arguments demonstrates that null are a > necessary evil (at least until something like D replaces SQL as the dominant > relational language). But we are talking about API here, and I think nulls > should be used only as last resort. Do you disagree? > > Francisco Jose Peredo escribió: > > I mean, for those cases isnt it better to wrap the stuff in a view to hide > and transform those nulls into true/false stuff? > > Francisco Jose Peredo escribió: > > An outer join where the column in the join is a nullable boolean? Can you > give me an example where doing that is better (easier to understand during > maintenace) than using an integer? I do not go against all nulls, just > boolean nulls. > > Gavin King escribió: > > So you never use outer joins? Every outer join produces null values. > > On Thu, Dec 4, 2008 at 1:04 PM, Francisco Jose Peredo > <franciscoperedo(a)tabasco.gob.mx&gt; wrote: > > > I try to avoid it in databases, if there are 3 different possible > values, it is better to use a not null Integer column, all my boolean > columns are "not null" always. > > Emmanuel Bernard escribió: > > > Databases use this three-state for decades. It seems to work fine. > > > Many people believe it does not work fine: > http://en.wikipedia.org/wiki/Null_(SQL)#Controversy > > > ________________________________ > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev > > > -- > Dirección Informática de Servicios Financieros > Dirección General de Modernización e Innovación Gubernamental > Secretaría de Administración y Finanzas > Paseo de la Sierra 435 col. Reforma > C.P. 86086, Villahermosa, Tabasco. > Tel. 52 + 993 + 310 40 00 Ext. 7127 > http://saf.tabasco.gob.mx/ > > IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos > insertados o "attachments", puede constituir información confidencial o > reservada, en los términos de la Ley de Acceso a la Información Pública del > Estado de Tabasco, y estar protegida por el derecho fundamental a la > privacidad. Se prohibe el uso de esta información por cualquier persona > distinta al receptor intencional o previsto. Si usted ha recibibido esta > transmisión electrónica por error, por favor responda inmediatamente al > emisor y borre esta información de su sistema. El uso, diseminación, > distribución o reproducción de esta transmisión electrónica por receptores > no intencionados o no previstos por el emisor, no está autorizada y puede > considerarse ilícita en los términos de la legislación penal y civil > vigente. > > ________________________________ > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev > > > -- > Dirección Informática de Servicios Financieros > Dirección General de Modernización e Innovación Gubernamental > Secretaría de Administración y Finanzas > Paseo de la Sierra 435 col. Reforma > C.P. 86086, Villahermosa, Tabasco. > Tel. 52 + 993 + 310 40 00 Ext. 7127 > http://saf.tabasco.gob.mx/ > > IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos > insertados o "attachments", puede constituir información confidencial o > reservada, en los términos de la Ley de Acceso a la Información Pública del > Estado de Tabasco, y estar protegida por el derecho fundamental a la > privacidad. Se prohibe el uso de esta información por cualquier persona > distinta al receptor intencional o previsto. Si usted ha recibibido esta > transmisión electrónica por error, por favor responda inmediatamente al > emisor y borre esta información de su sistema. El uso, diseminación, > distribución o reproducción de esta transmisión electrónica por receptores > no intencionados o no previstos por el emisor, no está autorizada y puede > considerarse ilícita en los términos de la legislación penal y civil > vigente. > > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev > > -- Gavin King gavin.king(a)gmail.com http://in.relation.to/Bloggers/Gavin http://hibernate.org http://seamframework.org _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

Sanne Grinovero escribió: > > 2008/12/4 Gavin King <gavin(a)hibernate.org&gt;: > >> Sometimes you need null values, sometimes you don't. Java should let >> you declare whether a value accepts null as part of the type >> declaration (i.e. @Nullable Foo foo), and non-nullable should be the >> default. But Java doesn't have this facility, so we just have to >> live >> with it. >> > A good practice should be to use "boolean" for not nullables (the > primitive one) > as it can't be null; reserve the wrapper Boolean for values which > can be null. > This has nothing to do with SQL of course ;-) > All right lets check the case of IsUserInRole.isUserInRole does it really make sense to answer to the question: "Is user XXXX in role YYYYY?" with a null? if we are not sure, shoulnt we default to "false" (or throw an exception?) _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

Yes, but I have always felt uneasy about a null boolean thing... the point of boolean is to restrict the possible outcomes of something to "true" or "false", but with a nullable boolean we now have 3 possible outcomes "true", "false" and "undefined"... and the problem is that "undefined" is also "typeless" and therefore bug prone, the code: if(isUserInRole("administrator)){ //do something } else { //do something else } looks like something perfectly valid, but it turns out it can crash because isUserInRole can return null. I mean I can understand it for MailComponent.getBoolean, and org.jboss.seam.ui.util.JSF.getBooleanValue, but I don't like it for org.jboss.seam.ui.graphicImage.Image.isRatio or org.jboss.seam.web.IsUserInRole.isUserInRole. Wouldn't it be better to use an Enum if there are 3 or more possible outcomes? Regards, Francisco > >> >> >> Regards, >> >> Francisco >> _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

On 4 Dec 2008, at 16:57, Francisco Jose Peredo wrote: > Hi! > > Great job Dan! > > You missed > > http://www.seamframework.org/Community/PossibleBugInOrgjbossseamcoreValid... > ;-) -> JIRA as Dan and I said > > > Oh, and what is you opinon on: > > > http://www.seamframework.org/Community/IfAMethodReturnsBooleanItShouldntR... > ? I think its fine, null == undefined which is valid state for something to be in.

> > > Regards, > > Francisco > > Pete Muir escribió: >> >> Standard rules apply, one JIRA per distinct issue. >> >> On 4 Dec 2008, at 16:24, Dan Allen wrote: >> >>> I fixed the ManagedEntityWrapper, JpaPermissionStore, and >>> ConverterChain. As for the rest, please submit a general JIRA for >>> addressing FindBugs best practices (things like null checks, etc). >>> Pete, does that sound like the best approach? >>> >>> -Dan >>> >>> On Thu, Dec 4, 2008 at 10:31 AM, Francisco Peredo >>> <franciscoperedo(a)tabasco.gob.mx&gt; wrote: >>>> >>>> Hi! >>>> >>>> It would be nice if this bugs could be fixed ;-): >>>> >>>> http://www.seamframework.org/Community/MorePossibleBugsInManyPlaces >>>> >>>> http://www.seamframework.org/Community/PossibleBugInOrgjbossseamcoreValid... >>>> >>>> >>>> http://www.seamframework.org/Community/PossibleBugInManagedEntityWrapper >>>> >>>> >>>> http://www.seamframework.org/Community/PossibleBugInEjbEntityDescriptorjava >>>> >>>> >>>> http://www.seamframework.org/Community/PossibleBugInJpaPermissionStorejave >>>> >>>> http://www.seamframework.org/Community/PossibleConvertertChainjavaBug >>>> >>>> http://www.seamframework.org/Community/IfAMethodReturnsBooleanItShouldntR... >>>> >>>> >>>> Sorry for cross-posting, I posted all this in the seam user forum, >>>> but now >>>> that I think about it they seem to be more "seam dev related" than >>>> "seam >>>> user related" so now I believe maybe I should have posted them here... >>>> Am I right? >>>> >>>> Regards, >>>> >>>> Francisco >>>> >>>> >>>> Pete Muir-2 wrote: >>>>> >>>>> All, >>>>> >>>>> We are aiming for a code freeze for 2.1.1.CR2 for midday Thursday >>>>> (EST), and then move quickly to the GA. >>>>> >>>>> If you've got anything you want in for 2.1.1.GA, make sure it is in by >>>>> the 2.1.1.CR2 code freeze :-) >>>>> >>>>> Best, >>>>> >>>>> Pete >>>>> _______________________________________________ >>>>> seam-dev mailing list >>>>> seam-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>>> >>>>> >>>> >>>> -- >>>> View this message in context: >>>> http://www.nabble.com/Seam-2.1.1.CR2-tp20793809p20835746.html >>>> Sent from the seam-dev mailing list archive at Nabble.com. >>>> >>>> _______________________________________________ >>>> seam-dev mailing list >>>> seam-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>> >>> >>> >>> >>> -- >>> Dan Allen >>> Software consultant | Author of Seam in Action >>> >>> http://mojavelinux.com >>> http://mojavelinux.com/seaminaction >>> >>> NOTE: While I make a strong effort to keep up with my email on a daily >>> basis, personal or other work matters can sometimes keep me away >>> from my email. If you contact me, but don't hear back for more than a >>> week, >>> it is very likely that I am excessively backlogged or the message was >>> caught in the spam filters. Please don't hesitate to resend a >>> message if >>> you feel that it did not reach my attention. >>> _______________________________________________ >>> seam-dev mailing list >>> seam-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/seam-dev >> >> > > > -- > Dirección Informática de Servicios Financieros > Dirección General de Modernización e Innovación Gubernamental > Secretaría de Administración y Finanzas > Paseo de la Sierra 435 col. Reforma > C.P. 86086, Villahermosa, Tabasco. > Tel. 52 + 993 + 310 40 00 Ext. 7127 > http://saf.tabasco.gob.mx/ > > IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos > insertados o "attachments", puede constituir información confidencial o > reservada, en los términos de la Ley de Acceso a la Información Pública del > Estado de Tabasco, y estar protegida por el derecho fundamental a la > privacidad. Se prohibe el uso de esta información por cualquier persona > distinta al receptor intencional o previsto. Si usted ha recibibido esta > transmisión electrónica por error, por favor responda inmediatamente al > emisor y borre esta información de su sistema. El uso, diseminación, > distribución o reproducción de esta transmisión electrónica por receptores > no intencionados o no previstos por el emisor, no está autorizada y puede > considerarse ilícita en los términos de la legislación penal y civil > vigente. > > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev