Jon will be answer to answer this one, but yes the Eclipse Transformer can
also look for strings (constants) to replace
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Sep 30, 2020 at 3:01 PM Thomas Andraschko <
[email protected]> wrote:

> Looks like it SHOULD still work with MF 3.0.
> Will this string
>
> https://github.com/apache/tomee/blob/master/tomee/tomee-myfaces/src/main/java/org/apache/tomee/myfaces/TomEEWebConfigProvider.java#L40
> also be replaced with jakarta?
>
> Am Mi., 30. Sept. 2020 um 14:53 Uhr schrieb Thomas Andraschko <
> [email protected]>:
>
> > Yep, exactly.
> >
> > I will check the tomee-myfaces integration codebase now, if everything is
> > still valid for 3.0. So we could maybe just replace the JAR via maven
> build.
> >
> > Am Mi., 30. Sept. 2020 um 14:47 Uhr schrieb Jean-Louis Monteiro <
> > [email protected]>:
> >
> >> Yes namespace is everywhere in content parameters and in xml files.
> That's
> >> the issue. So as far as I can understand if we move TomEE 8 to new
> myfaces
> >> then we'll break EE 8 apps
> >>
> >> Le mer. 30 sept. 2020 à 12:38, Thomas Andraschko <
> >> [email protected]> a écrit :
> >>
> >> > Might work.
> >> >
> >> > I just aligned the changes with mojarra and they also changed e.g. xml
> >> > namespaces.
> >> > - So its replacing javax in packages, request params, context params
> >> > - new XML namespaces
> >> >
> >> > I will probably check newer commits in mojarra and do a RC2 soon
> >> >
> >> > Jonathan Gallimore <[email protected]> schrieb am Mi., 30.
> >> Sep.
> >> > 2020, 12:07:
> >> >
> >> > > If its a drop-in replacement, we can probably handle that in the
> Maven
> >> > > build. I'm curious about the change though; I was under the
> impression
> >> > that
> >> > > Jakarta EE 9, was a namespace-only change?
> >> > >
> >> > > Jon
> >> > >
> >> > > On Wed, Sep 30, 2020 at 10:20 AM Jean-Louis Monteiro <
> >> > > [email protected]> wrote:
> >> > >
> >> > > > We are probably reaching the limit of the Eclipse Transformer for
> >> > > Jakarta.
> >> > > > I'll start a new thread dedicated to that discussion
> >> > > > --
> >> > > > Jean-Louis Monteiro
> >> > > > http://twitter.com/jlouismonteiro
> >> > > > http://www.tomitribe.com
> >> > > >
> >> > > >
> >> > > > On Wed, Sep 30, 2020 at 11:18 AM Thomas Andraschko <
> >> > > > [email protected]> wrote:
> >> > > >
> >> > > > > Hi,
> >> > > > >
> >> > > > > oh, then it wont work.
> >> > > > > MyFaces 3.0 e.g. also changes context param and requests params,
> >> > that's
> >> > > > > really exclusive for EE9.
> >> > > > >
> >> > > > > How can we proceed then? Create a EE9 branch?
> >> > > > > Otherwise i dont think we can make it work easily.
> >> > > > >
> >> > > > > Best regards,
> >> > > > > Thomas
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > > > Am Mi., 30. Sept. 2020 um 11:15 Uhr schrieb Jean-Louis Monteiro
> <
> >> > > > > [email protected]>:
> >> > > > >
> >> > > > > > Hey Thomas.
> >> > > > > > Yes sure, we can open a ticket and do the dep upgrade.
> >> > > > > >
> >> > > > > > The issue is that we don't really have any EE 9 branch.
> >> > > > > > We work on EE 8 for master and we do use the Jakarta EE
> >> Transformer
> >> > > to
> >> > > > > > generate the EE 9 compatible binaries based on EE 8.
> >> > > > > >
> >> > > > > > If MyFaces 3 is EE 8 compatible, then I don't see any issue
> >> doing
> >> > the
> >> > > > > > upgrade.
> >> > > > > >
> >> > > > > > --
> >> > > > > > Jean-Louis Monteiro
> >> > > > > > http://twitter.com/jlouismonteiro
> >> > > > > > http://www.tomitribe.com
> >> > > > > >
> >> > > > > >
> >> > > > > > On Wed, Sep 30, 2020 at 11:12 AM Thomas Andraschko <
> >> > > > > > [email protected]> wrote:
> >> > > > > >
> >> > > > > > > up
> >> > > > > > >
> >> > > > > > > Am Mo., 21. Sept. 2020 um 10:37 Uhr schrieb Thomas
> Andraschko
> >> <
> >> > > > > > > [email protected]>:
> >> > > > > > >
> >> > > > > > > > Hey Guys,
> >> > > > > > > >
> >> > > > > > > > We recently released MyFaces 3.0 RC1.
> >> > > > > > > > I think we have to use it for 9.0?
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>

Reply via email to