Hi,
It's not a super clean API, but clean enough to compile against. It can't be actually on the class path.
What happens in the build process is that the full Mojarra jar is generated, which is then extracted and the API classes are repackaged. Those classes would not compile on their own, and when put on the class path lead to linking errors.
It's a quite unfortunate process, but the one we inherited.
Kind regards,
Arjan
Hi Arjan,
The current process
is to somehow "clean up" these APIs with code and distribute
them as *the* Faces API, correct? This is done as part of the build
process? Or, is it a manual process? I'm curious how we currently
generate a "clean" API for the Faces component. And, whatever
process that is, can it be done in reverse to add the code back into the
API for Mojarra? I know I'm probably over-simplifying this complicated
problem, but it sure would be nice to make this break.
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From:
arjan
tijms <arjan.tijms@xxxxxxxxx>
To:
faces
developer discussions <faces-dev@xxxxxxxxxxx>
Cc:
mojarra
developer discussions <mojarra-dev@xxxxxxxxxxx>
Date:
02/24/2020
09:13
Subject:
[EXTERNAL]
Re: [mojarra-dev] [faces-dev] Splitting the API into faces-api?
Sent
by: mojarra-dev-bounces@xxxxxxxxxxx
Hi,
It's been long on the list, but not a
trivial thing to do. Many API classes contain large amounts of code
(UIData is particularly bad).
We'd need to find a way to re-architect
that, presumably with some level of backward compatibility.
Kind regards,
Arjan
On Mon, Feb 24, 2020 at 4:09 PM Thomas
Andraschko <andraschko.thomas@xxxxxxxxx>
wrote:
+1 for doing a "empty" faces-api
without method implementations as they contain many implementation details
in both mojarra and myfaces
Am Mo., 24. Feb. 2020 um 15:32 Uhr
schrieb Kevin Sutter <sutter@xxxxxxxxxx>:
Hi,
As we look at the work in front of us for Jakarta EE 9, I am wondering
if there is any interest in breaking out the API from Mojarra and putting
it into the Faces project (faces-api repo)? I have no idea how much
work this would entail, but it seems like a good time to do this split.
We have to change the package names for the API anyway (and I doubt you'll
be changing the package names through out the implementation). So,
why not make the split into separate repos? Yes? No?
Reasons?
Thanks!
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
_______________________________________________
faces-dev mailing list
faces-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/faces-dev_______________________________________________
faces-dev mailing list
faces-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/faces-dev_______________________________________________
mojarra-dev mailing list
mojarra-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/mojarra-dev
_______________________________________________
mojarra-dev mailing list
mojarra-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/mojarra-dev