I've provided another PR adding some relationships I think were missing [1]. I'll try to provide some example of an individual project graph detailing its optional dependencies.
Wayne, do you think we could manually upload the generated SVG to the website while we find a way to automate it? I don't expect many people to actually contribute in the form a PR, but having the graph publicly available would encourage feedback.
Regards,
Guillermo González de Agüero
Sure you already know it, but while EJB doesn't hold a hard dependency on JCA, message driven beans can be customized via JCA.
It's probably too much for a single graph, but this kind of "integrates with" relationship are also very interesting. JACC would also integrate with EJB and Servlets; JASPIC with Servlets, etc.
Perhaps we can work on individual project graphs once we are done with this overview.
It's because I removed the "Jakarta EE
platform" item, which was the only thing that referenced those API
projects. GlassFish contains the implementations of those APIs.
As discussed previously, we decided that GlassFish would only
reference other projects that contained an implementation, even
though it actually does depend on all these API projects as well.
There's other "orphan" projects that aren't on the left so partly
this is just a layout issue.
Kevin Sutter wrote on 5/22/18 6:58 AM:
This is getting very useful... One
question... Why are there "orphan" projects on the left
hand side (Common Annotations, EJB, JACC, and JCA)? Are there
missing
relationships? Thanks!
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Java EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From:
Bill Shannon
<bill.shannon@xxxxxxxxxx>
To:
EE4J PMC Discussions
<ee4j-pmc@xxxxxxxxxxx>, "Guillermo González de Agüero"
<z06.guillermo@xxxxxxxxx>
Date:
05/21/2018 03:03 PM
Subject:
Re: [ee4j-pmc]
Project/Specification dependencies
Sent by:
ee4j-pmc-bounces@xxxxxxxxxxx
That is very cool! Thanks!
One minor issue... Can the hover text translate "\n" to
" "?
Guillermo González de Agüero wrote on 05/20/18
02:44 AM:
I've provided a PR adding URLs for projects [1] and
created
a simple HTML demo supporting dependency highligh on hover with
a jQuery
library [2].
Regards,
Guillermo González de Agüero
[1] https://github.com/eclipse-ee4j/ee4j-website/pull/16
[2] https://cdn.rawgit.com/ggam/jquery.graphviz.svg/master/demo.html
El dom., 20 may. 2018 a las 10:25, Guillermo
González
de Agüero (<z06.guillermo@xxxxxxxxx>)
escribió:
Additionally to the SVG output, seems like Graphviz
can
also generate a clickable HTML image map which could be better
suited for
the website.
El sáb., 19 may. 2018 a las 0:44, Bill Shannon
(<bill.shannon@xxxxxxxxxx>)
escribió:
I submitted another pull
request.
I think this is getting to be pretty close to accurate.
I removed the Jakarta EE platform because the picture was just
too cluttered
with it included and it didn't really add any value.
Is (or can) the svg output from "dot" published automatically
on the web site to make it easy for people to review it?
Wayne Beaton wrote on 05/17/18 08:33 PM:
I've rolled in the pull request.
I tweaked the diagram a bit more. I decided to, for
example,
separate the projects not hosted as Eclipse Projects.
Wayne
On Thu, May 17, 2018 at 10:24 PM, Bill Shannon <bill.shannon@xxxxxxxxxx>
wrote:
Wayne Beaton wrote on 05/17/2018 06:00 PM:
GlassFish absolutely
needs
the artifacts produced by the API projects; it won't function
without them.
I understand. But I don't think that having the
diagram
indicate that GlassFish implements all of the specifications is
useful.
Like I said earlier, it's not clear to me that expressing the
that Jakarta
EE references all of the specifications, while true, is all that
useful
on the diagram.
GlassFish does implement JPA, but it implements JPA
by
way of consuming EclipseLink. This is the interesting
relationship IMHO,
as it describes the relationships between the projects and makes
it clear
that GlassFish doesn't implement that particular specification
directly.
Again, I'm pretty sure that GlassFish does
implement EJB.
IMHO, by saying GlassFish consumes EclipseLink, but implements
EJB gives
me more information about where to look for stuff.
I understand. I just wanted to make sure we all
agreed on what this picture is trying to capture. I updated it
with
this in mind. If you want to remove Jakarta EE, that's fine
with
me.
I'll take a look at the pull request.
Thanks.
--
Wayne Beaton
Director of Open Source Projects
The Eclipse Foundation
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
