> On Sep 30, 2020, at 3:06 AM, Jonathan Gallimore
> wrote:
>
> If its a drop-in replacement, we can probably handle that in the Maven
> build.
Agree. While we're at it we should also use the Tomcat 10 milestones.
Definitely the transformer is no the place to handle this. *Potentially* we
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 <
andraschko.tho...@gmail.com> wrote:
>
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 <
jlmonte...@tomitribe.com>:
> Yes namespace is everywhere in
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 <
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 <
andraschko.tho...@gmail.com> a écrit :
> Might work.
>
> I just
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 schrieb am Mi., 30. Sep.
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 <
jlmonte...@tomitribe.com> wrote:
> We are
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 <
andraschko.tho...@gmail.com>
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
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
up
Am Mo., 21. Sept. 2020 um 10:37 Uhr schrieb Thomas Andraschko <
andraschko.tho...@gmail.com>:
> Hey Guys,
>
> We recently released MyFaces 3.0 RC1.
> I think we have to use it for 9.0?
>
11 matches
Mail list logo