From: "Pete Muir" <pmuir(a)redhat.com&gt; To: jdf-dev(a)lists.jboss.org Sent: Thursday, June 28, 2012 6:29:57 PM Subject: [jdf-dev] Migration: when and what One thing I picked up at Summit was that whilst people really appreciate the migration guides, they also want more advice on when (/whether) they should migrate, and what they should migrate too. We have the story pretty much sorted: * if you have an app that works, and you want to keep running it on Seam 2.2, then great. We'll support that for X more years on EAP. Stay where you are. * if you want to stay on Seam 2, but want to take advantage of the new features of Java EE 6, then you can take a look at Seam 2.3, which is currently beta quality. We haven't decided yet whether this will enter the supported product arena. * if you want to take advantage of Java EE, you need to do a bit of analysis of your app: ** if you have all the features you need in Java EE 6 (and look at TicketMonster, you can achieve a lot!) then migrate to Java EE 6 ** if you don't, but you can find them in DeltaSpike, and like living on the edge, then you can take the path of adding DeltaSpike to Java EE 6. But we don't have a well trodden path here, with guides for you to follow ** otherwise, take a look at the jdf roadmap to see when the features you need will enter jdf, will all the goodness of the stack and guides Comments? I'll get this written up for http://www.jboss.org/jdf/migrations/get-started/ next week. _______________________________________________ jdf-dev mailing list jdf-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jdf-dev

One thing I picked up at Summit was that whilst people really appreciate the migration guides, they also want more advice on when (/whether) they should migrate, and what they should migrate too. We have the story pretty much sorted: * if you have an app that works, and you want to keep running it on Seam 2.2, then great. We'll support that for X more years on EAP. Stay where you are. * if you want to stay on Seam 2, but want to take advantage of the new features of Java EE 6, then you can take a look at Seam 2.3, which is currently beta quality. We haven't decided yet whether this will enter the supported product arena. * if you want to take advantage of Java EE, you need to do a bit of analysis of your app: ** if you have all the features you need in Java EE 6 (and look at TicketMonster, you can achieve a lot!) then migrate to Java EE 6 ** if you don't, but you can find them in DeltaSpike, and like living on the edge, then you can take the path of adding DeltaSpike to Java EE 6. But we don't have a well trodden path here, with guides for you to follow ** otherwise, take a look at the jdf roadmap to see when the features you need will enter jdf, will all the goodness of the stack and guides Comments? I'll get this written up for http://www.jboss.org/jdf/migrations/get-started/ next week. _______________________________________________ jdf-dev mailing list jdf-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jdf-dev

From: "Rafael Benevides" <rafabene(a)gmail.com&gt; To: "Pete Muir" <pmuir(a)redhat.com&gt; Cc: jdf-dev(a)lists.jboss.org Sent: Thursday, July 5, 2012 9:45:59 AM Subject: Re: [jdf-dev] Migration: when and what For now I would only change the http://seamframework.org URL to be a link. Maybe making the "Classic Seam 2" Column wider. That's my 2 cents. 2012/7/5 Pete Muir < pmuir(a)redhat.com > All, Please review - http://www.jboss.org/jdf/stage/migrations/get-started/ Pete On 28 Jun 2012, at 23:29, Pete Muir wrote: > One thing I picked up at Summit was that whilst people really > appreciate the migration guides, they also want more advice on > when (/whether) they should migrate, and what they should migrate > too. We have the story pretty much sorted: > > * if you have an app that works, and you want to keep running it on > Seam 2.2, then great. We'll support that for X more years on EAP. > Stay where you are. > * if you want to stay on Seam 2, but want to take advantage of the > new features of Java EE 6, then you can take a look at Seam 2.3, > which is currently beta quality. We haven't decided yet whether > this will enter the supported product arena. > * if you want to take advantage of Java EE, you need to do a bit of > analysis of your app: > ** if you have all the features you need in Java EE 6 (and look at > TicketMonster, you can achieve a lot!) then migrate to Java EE 6 > ** if you don't, but you can find them in DeltaSpike, and like > living on the edge, then you can take the path of adding > DeltaSpike to Java EE 6. But we don't have a well trodden path > here, with guides for you to follow > ** otherwise, take a look at the jdf roadmap to see when the > features you need will enter jdf, will all the goodness of the > stack and guides > > Comments? I'll get this written up for > http://www.jboss.org/jdf/migrations/get-started/ next week. > _______________________________________________ > jdf-dev mailing list > jdf-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jdf-dev _______________________________________________ jdf-dev mailing list jdf-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jdf-dev _______________________________________________ jdf-dev mailing list jdf-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jdf-dev

One thing I picked up at Summit was that whilst people really appreciate the migration guides, they also want more advice on when (/whether) they should migrate, and what they should migrate too. We have the story pretty much sorted: * if you have an app that works, and you want to keep running it on Seam 2.2, then great. We'll support that for X more years on EAP. Stay where you are. * if you want to stay on Seam 2, but want to take advantage of the new features of Java EE 6, then you can take a look at Seam 2.3, which is currently beta quality. We haven't decided yet whether this will enter the supported product arena. * if you want to take advantage of Java EE, you need to do a bit of analysis of your app: ** if you have all the features you need in Java EE 6 (and look at TicketMonster, you can achieve a lot!) then migrate to Java EE 6 ** if you don't, but you can find them in DeltaSpike, and like living on the edge, then you can take the path of adding DeltaSpike to Java EE 6. But we don't have a well trodden path here, with guides for you to follow ** otherwise, take a look at the jdf roadmap to see when the features you need will enter jdf, will all the goodness of the stack and guides Comments? I'll get this written up for http://www.jboss.org/jdf/migrations/get-started/ next week. _______________________________________________ jdf-dev mailing list jdf-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jdf-dev

Pull requests welcome :)

> - When the "get the source" button in the right-hand nav bar reaches > the top of the viewport, the text in the section list below it (the > div#toc element) reflows outside the bounds of its container. This > is due to the shift from display:static to display: fixed. A quick > fix is to set a width on that div, eg: <div id="toc" > style="position: static; top: 0px; width: 215px; ">

I think it's a bit more complicated than that. The javascript rewrites the style rules I think. I haven't had time to delve into it fully.

On 5 Jul 2012, at 15:49, Jonathan Fuerth wrote: > On http://www.jboss.org/jdf/stage/migrations/get-started/: > > - I like the table of scenarios. It's easy to follow, and should help people safely skip what doesn't apply to them > - Because of the TOC right above the "seam migration scenarios" table, I was led to expect similar tables for Spring and Java EE 5. Are these planned? If not, I think a page rework might be in order so that it doesn't appear that there is missing content. Good point. Ideally we can address this in the same matrix, but it may get overcrowded. I'll have a play. Partly, this is just about language, as obviously the "full out java ee 6" applies to all three starting points.

From: "Pete Muir" <pmuir(a)redhat.com&gt; To: "Jonathan Fuerth" <jfuerth(a)redhat.com&gt; Cc: jdf-dev(a)lists.jboss.org Sent: Thursday, July 5, 2012 12:38:24 PM Subject: Re: [jdf-dev] Migration: when and what Ok, I've added in Spring and Java EE 5 http://www.jboss.org/jdf/stage/migrations/get-started/ Please take a look. Burr has also asked for a "Where's my feature" section, which addresses what is in Java EE 6, what's in DeltaSpike, and (unstated) what's not there. I'll work on that now. On 5 Jul 2012, at 15:49, Jonathan Fuerth wrote: > On http://www.jboss.org/jdf/stage/migrations/get-started/: > > - I like the table of scenarios. It's easy to follow, and should > help people safely skip what doesn't apply to them > - Because of the TOC right above the "seam migration scenarios" > table, I was led to expect similar tables for Spring and Java EE > 5. Are these planned? If not, I think a page rework might be in > order so that it doesn't appear that there is missing content. > > On > http://www.jboss.org/jdf/stage/migrations/seam2/open18_migration/: > > - Change "used Apache Ant as it’s build tool of choice" -> "used > Apache Ant as its build tool of choice" > - When the "get the source" button in the right-hand nav bar > reaches the top of the viewport, the text in the section list > below it (the div#toc element) reflows outside the bounds of its > container. This is due to the shift from display:static to > display: fixed. A quick fix is to set a width on that div, eg: > <div id="toc" style="position: static; top: 0px; width: 215px; "> > - Similarly, the long lines in the code samples overflow their > containing boxes and actually overlap the TOC as you scroll down > the page > - First paragraph under Migrate to CDI is missing its terminating > period > - Change "It’s main purpose is to register" -> "Its main purpose is > to register" > - Change "below, the JSR 299 specification, or a CDI" -> "below, in > the JSR 299 specification, or in a CDI" > - Change "Because of the first difference, it, at times can be > necessary to to create" -> "Because of the first difference, at > times it is necessary to create" > - In the discussion on CDI scopes, the article claims there is a > @DependentScoped annotation. I think it means @Dependent. > - It would be nice if src/main/java/org/open18/model/dao/BaseDao > was a link to that file on github > - Eliminate the empty doc comment in the TeeSetAction.java code > example > > On http://www.jboss.org/jdf/stage/migrations/get-started/spring/: > > - Change "It also consists of sample code a working project." -> > "Its sample code is a working project." > - Change "you Java EE 6 application" -> "your Java EE 6 > application" > > On http://www.jboss.org/jdf/stage/migrations/get-started/javaee5/: > > - Change "It also consists of sample code a working project." -> > "Its sample code is a working project." > > Hm, that was more than I intended. Should have started with a fork > and sent this feedback in the form of a pull request :-/ .. next > time! > > -Jonathan > > ----- Original Message ----- > From: "Pete Muir" <pmuir(a)redhat.com&gt; > To: jdf-dev(a)lists.jboss.org > Sent: Thursday, July 5, 2012 8:47:17 AM > Subject: Re: [jdf-dev] Migration: when and what > > All, > > Please review - > http://www.jboss.org/jdf/stage/migrations/get-started/ > > Pete > > On 28 Jun 2012, at 23:29, Pete Muir wrote: > >> One thing I picked up at Summit was that whilst people really >> appreciate the migration guides, they also want more advice on >> when (/whether) they should migrate, and what they should migrate >> too. We have the story pretty much sorted: >> >> * if you have an app that works, and you want to keep running it >> on Seam 2.2, then great. We'll support that for X more years on >> EAP. Stay where you are. >> * if you want to stay on Seam 2, but want to take advantage of the >> new features of Java EE 6, then you can take a look at Seam 2.3, >> which is currently beta quality. We haven't decided yet whether >> this will enter the supported product arena. >> * if you want to take advantage of Java EE, you need to do a bit >> of analysis of your app: >> ** if you have all the features you need in Java EE 6 (and look at >> TicketMonster, you can achieve a lot!) then migrate to Java EE 6 >> ** if you don't, but you can find them in DeltaSpike, and like >> living on the edge, then you can take the path of adding >> DeltaSpike to Java EE 6. But we don't have a well trodden path >> here, with guides for you to follow >> ** otherwise, take a look at the jdf roadmap to see when the >> features you need will enter jdf, will all the goodness of the >> stack and guides >> >> Comments? I'll get this written up for >> http://www.jboss.org/jdf/migrations/get-started/ next week. >> _______________________________________________ >> jdf-dev mailing list >> jdf-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jdf-dev > > > _______________________________________________ > jdf-dev mailing list > jdf-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jdf-dev _______________________________________________ jdf-dev mailing list jdf-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jdf-dev

On http://www.jboss.org/jdf/stage/migrations/get-started/: - I like the table of scenarios. It's easy to follow, and should help people safely skip what doesn't apply to them - Because of the TOC right above the "seam migration scenarios" table, I was led to expect similar tables for Spring and Java EE 5. Are these planned? If not, I think a page rework might be in order so that it doesn't appear that there is missing content. On http://www.jboss.org/jdf/stage/migrations/seam2/open18_migration/: - Change "used Apache Ant as it’s build tool of choice" -> "used Apache Ant as its build tool of choice" - When the "get the source" button in the right-hand nav bar reaches the top of the viewport, the text in the section list below it (the div#toc element) reflows outside the bounds of its container. This is due to the shift from display:static to display: fixed. A quick fix is to set a width on that div, eg: <div id="toc" style="position: static; top: 0px; width: 215px; "> - Similarly, the long lines in the code samples overflow their containing boxes and actually overlap the TOC as you scroll down the page - First paragraph under Migrate to CDI is missing its terminating period - Change "It’s main purpose is to register" -> "Its main purpose is to register" - Change "below, the JSR 299 specification, or a CDI" -> "below, in the JSR 299 specification, or in a CDI" - Change "Because of the first difference, it, at times can be necessary to to create" -> "Because of the first difference, at times it is necessary to create" - In the discussion on CDI scopes, the article claims there is a @DependentScoped annotation. I think it means @Dependent. - It would be nice if src/main/java/org/open18/model/dao/BaseDao was a link to that file on github - Eliminate the empty doc comment in the TeeSetAction.java code example On http://www.jboss.org/jdf/stage/migrations/get-started/spring/: - Change "It also consists of sample code a working project." -> "Its sample code is a working project." - Change "you Java EE 6 application" -> "your Java EE 6 application" On http://www.jboss.org/jdf/stage/migrations/get-started/javaee5/: - Change "It also consists of sample code a working project." -> "Its sample code is a working project." Hm, that was more than I intended. Should have started with a fork and sent this feedback in the form of a pull request :-/ .. next time! -Jonathan ----- Original Message ----- From: "Pete Muir" <pmuir(a)redhat.com&gt; To: jdf-dev(a)lists.jboss.org Sent: Thursday, July 5, 2012 8:47:17 AM Subject: Re: [jdf-dev] Migration: when and what All, Please review - http://www.jboss.org/jdf/stage/migrations/get-started/ Pete On 28 Jun 2012, at 23:29, Pete Muir wrote: > One thing I picked up at Summit was that whilst people really appreciate the migration guides, they also want more advice on when (/whether) they should migrate, and what they should migrate too. We have the story pretty much sorted: > > * if you have an app that works, and you want to keep running it on Seam 2.2, then great. We'll support that for X more years on EAP. Stay where you are. > * if you want to stay on Seam 2, but want to take advantage of the new features of Java EE 6, then you can take a look at Seam 2.3, which is currently beta quality. We haven't decided yet whether this will enter the supported product arena. > * if you want to take advantage of Java EE, you need to do a bit of analysis of your app: > ** if you have all the features you need in Java EE 6 (and look at TicketMonster, you can achieve a lot!) then migrate to Java EE 6 > ** if you don't, but you can find them in DeltaSpike, and like living on the edge, then you can take the path of adding DeltaSpike to Java EE 6. But we don't have a well trodden path here, with guides for you to follow > ** otherwise, take a look at the jdf roadmap to see when the features you need will enter jdf, will all the goodness of the stack and guides > > Comments? I'll get this written up for http://www.jboss.org/jdf/migrations/get-started/ next week. > _______________________________________________ > jdf-dev mailing list > jdf-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jdf-dev _______________________________________________ jdf-dev mailing list jdf-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jdf-dev