<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On 19 Feb 2015, at 22:25, Heiko W.Rupp <<a href="mailto:hrupp@redhat.com" class="">hrupp@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><blockquote type="cite" style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class="Apple-interchange-newline">Am 16.02.2015 um 16:07 schrieb Peter Palaga <<a href="mailto:ppalaga@redhat.com" class="">ppalaga@redhat.com</a>>:<br class="">Second, the possibility to run in a non-WF-like container is still<span class="Apple-converted-space"> </span><br class="">somewhere in my consciousness. Importing wf BoM does not seem to be a<span class="Apple-converted-space"> </span><br class="">step in that direction.<br class=""></blockquote><br style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Yes. We need to restrict ourselves to Java EE 6 and EJB 3.1, JMS 1.1 apis.</span><br style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">We can use what EAP 6.4 offers - including JAX-RS 2 (this is not in there by default, but</span><br style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">can be supplied by the application).</span><br style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">This does not imply that we have to develop on EAP 6.4 though.</span><br style="font-family: Helvetica; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""></div></blockquote></div><br class=""><div class=""><br class=""></div><div class="">These two statements are contradicting each other: running in a “non WF-like” container and assuming EE6 API’s on the target platform are two worlds apart.</div><div class=""><br class=""></div><div class="">First of all, if you build on EE6, you don’t “restrict” yourself. At least not in the way of “limiting” the API dependencies. But limiting the API dependencies is a prerequisite to successfully integrate with other platforms (or containers), which is what Peter has in mind, if I am correct.</div><div class=""><br class=""></div><div class="">Hawkular want’s to provide a set of re-usable components. Re-usable in a sense, that other software project can integrate them easily. On the other hand there is the goal to build a Hawkular application, which itself is a consumer of the before mentioned components. </div><div class=""><br class=""></div><div class="">I think the continuous mistake among the Hawkular contributors is that you don’t prioritise these two approaches. To do that, we need to acknowledge an intrinsic dependency of the Hawkular application onto the components. Furthermore, any decision of API and service dependencies of those components impacts the way in which they can be re-used. Dependencies would need to be carried over to any platform that want’s to leverage Hawkular components. Which, in a way, limits it’s reusability. </div><div class=""><br class=""></div><div class="">My suggestion would be to prioritise on the component re-use. Even if that results in inconveniences when building the Hawkular application: </div><div class=""><br class=""></div><div class="">- Get rid of all EE6 dependencies. </div><div class="">- Stop thinking in WAR and EAR deployments. </div><div class="">- Support reusability by strictly limiting the API dependencies. </div><div class="">- Come to an agreement about the priorities. </div><div class="">- Document and communicate the outcome of this discussion </div><div class="">- Make sure all contributors understand and respect these constraints.</div><div class=""><br class=""></div><div class="">Regards, Heiko B.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>