[windup-dev] JBoss Web Framework Kit -- Good Migration Option

[Rodney Russ]

On 3 Sep 2015, at 2:11, Marek Novotny wrote:

> On 3.9.2015 04:18, Brad Davis wrote:
>> I have largely ignored the JBoss Web Framework Kit,
>
> Oh, what a shame on you :D
>
> but it should be something we are actively looking at for migrations.
> I would agree with that but to migrate to CDI and new stuff. We try 
> the
> best in the deadline we had in the latest WFK release, but we could be
> definitely better (that was/is my motivation to join WindUp team)
>
> We could be pushing it when we see versions of Seam, Struts, Spring 
> that
> aren't otherwise in JBoss EAP 6.x but that is their target.
>
> First from your list only Seam should be matter of our focus. Spring 
> was
> not delivered and supported in any way like a product until you didn't
> use Snowdrop, but that was not really required for Spring 3/4
> applications, and Spring as such is still certified/supported in EAP 6
> testing.

One thing that "may" be useful is finding versions of Spring in the 
application that are different from those that were certified on EAP.  
This could let the user know that these may be a problem given that the 
version they use is different from the version certified for EAP.

One "interesting" aspect of this approach is that this versioning could 
be a moving target with each EAP release.  So, it could prove a 
challenge to maintain.

>
> I believe Struts wasn't anything more than we gave advises and tested
> minimal examples on our platforms. In your referenced URL
> https://access.redhat.com/articles/1125, please read the explanation
> what Tier 4 is ;)
>
> In other words, if the customer doesn't want to rewrite things but 
> just
> wants support on the newest server, it might be an option.
> I don't think it should be the safe way for customer, because that 
> opens
> a pandora's box. It is always better to stay with out-of-date 
> technology
> in the application if they don't want to migrate that outdated tech. 
> We
> everywhere recommends to migrate from Seam to CDI and Deltaspike and 
> for
> Spring only versions 3 and 4 are certified for now. Struts are out of
> scope as it was a long time ago you should move to JSF from it.
>
>
> We are exploring this with one of our customers currently, and I think
> it is a good options in some scenarios.
> +1 for some very specific scenarios yes, but for majority application
> not. Take for instance jbpm 3 case used in Seam 2, that is definitely
> not good way to take such existing application and try to deploy to 
> EAP6.
>
>>
>> https://access.redhat.com/articles/112543
>>
>> Basically path of least resistance upgrades.
>>
>> Brad Davis
>> Senior Manager, Red Hat Consulting
>> Email: bdavis at redhat.com | c: 980.226.7865 | http://www.redhat.com
>>
>>
>> _______________________________________________
>> windup-dev mailing list
>> windup-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>
>
> -- 
> Marek Novotny
> --
> Windup team member and Seam Project Lead
>
> Red Hat Czech s.r.o.
> Purkynova 99
> 612 45 Brno
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev