Cleaning Libraries and Code #1754
poolborges
started this conversation in
Ideas
Replies: 2 comments 1 reply
-
Hello @poolborges Please review this new version and give your precious inputs |
Beta Was this translation helpful? Give feedback.
0 replies
-
Is there any framework KT session is available. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We need to clean the code without add breaking changes, for future modullarity, better code test
1. Remove JDK libraries
Why the library is here ?
"Studio" use sun compiler to compile generated "java" code
Solution 1 Common Practices
Should have requirement for JDK not JRE.
Solution 2 (Future/IDEIA): Introducing "Builder"
2. Remove CXF and use of Jersey as JAX-RS Client
Should not use two library for same SPEC
Solution 1 Remove Apache CXF
.Apache CXF
<cxf.rt.frontend.jaxrs.version>3.3.6</cxf.rt.frontend.jaxrs.version> <tomee.jaxrs.version>8.0.4</tomee.jaxrs.version>
.Jersey (Provide everything for form-multipart)
<jersey.version>2.29</jersey.version>
Solution 2 Better API to integrate with BPMN repository server
This MUST support the Activity 6.0.0 and also allow planning support for other: Activity 7.0.0, ...
3 Move Embedded Tomee from core
Should NOT implement Embedded Server inside core framework
Should be implemented as another maven artifact ("igrpweb-server-tomee)
BETTER to use springboot ("igrpweb-server-spboot)
-- IGRP is has a inhouse implement of "Front controller(FC) pattern "
-- Spring-Web has a powerful FC implementation .
--- How (S1): Register everything insise (web.xml) to spring and let spring do the magic
.Maven
<tomee.embedded.version>8.0.7</tomee.embedded.version>
4 ... and more
Beta Was this translation helpful? Give feedback.
All reactions