*Rationale:*
Back in the day (pre r11.x) we enabled users to have OFBiz working in external web containers, like Apache Tomcat, IBM Websphere and Jetty. However, focus of the community migrated away from that and improved the use of the internally used servlet solution (also Apache Tomcat). Since then the functionality of the component to have OFBiz work with these external web containers stopped working and in recent years no contributor felt the itch to correct/improve this situation. I therefor propose: - that we move the component from trunk to our attic, and - we don't include it in future releases (including the upcoming r14.x branch release r14.12.01) For this proposal the normal 72 hour rule applies. Best regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com |
+1
I would like to suggest a separate but related discussion: Should we re-engineer OFBiz so that it is easier to deploy in various application servers? Adrian Crum Sandglass Software www.sandglass-software.com On 3/17/2015 11:31 AM, Pierre Smits wrote: > *Rationale:* > Back in the day (pre r11.x) we enabled users to have OFBiz working in > external web containers, like Apache Tomcat, IBM Websphere and Jetty. > However, focus of the community migrated away from that and improved the > use of the internally used servlet solution (also Apache Tomcat). > Since then the functionality of the component to have OFBiz work with these > external web containers stopped working and in recent years no contributor > felt the itch to correct/improve this situation. > > I therefor propose: > > - that we move the component from trunk to our attic, and > - we don't include it in future releases (including the upcoming r14.x > branch release r14.12.01) > > For this proposal the normal 72 hour rule applies. > > Best regards, > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > |
Indeed
On Mar 17, 2015, at 12:38 PM, Adrian Crum <[hidden email]> wrote: > +1 > > I would like to suggest a separate but related discussion: Should we re-engineer OFBiz so that it is easier to deploy in various application servers? > > Adrian Crum > Sandglass Software > www.sandglass-software.com > > On 3/17/2015 11:31 AM, Pierre Smits wrote: >> *Rationale:* >> Back in the day (pre r11.x) we enabled users to have OFBiz working in >> external web containers, like Apache Tomcat, IBM Websphere and Jetty. >> However, focus of the community migrated away from that and improved the >> use of the internally used servlet solution (also Apache Tomcat). >> Since then the functionality of the component to have OFBiz work with these >> external web containers stopped working and in recent years no contributor >> felt the itch to correct/improve this situation. >> >> I therefor propose: >> >> - that we move the component from trunk to our attic, and >> - we don't include it in future releases (including the upcoming r14.x >> branch release r14.12.01) >> >> For this proposal the normal 72 hour rule applies. >> >> Best regards, >> >> Pierre Smits >> >> *ORRTIZ.COM <http://www.orrtiz.com>* >> Services & Solutions for Cloud- >> Based Manufacturing, Professional >> Services and Retail & Trade >> http://www.orrtiz.com >> |
In reply to this post by Pierre Smits
I would like to add that this vote is about moving the specialpurpose/appserver component to attic: the component was intended to create the configuration scripts for the deployment on application servers; as Pierre mentioned, this approach doesn't work anymore unless you use very old and discontinued OFBiz versions (pre 2011).
The effort of enabling OFBiz to be deployed on external application server is still valuable and should, in my opinion, a goal for the community, but this appserver component is no more the way to implement this and so it can be moved to attic. So my vote is: +1 Jacopo On Mar 17, 2015, at 12:31 PM, Pierre Smits <[hidden email]> wrote: > *Rationale:* > Back in the day (pre r11.x) we enabled users to have OFBiz working in > external web containers, like Apache Tomcat, IBM Websphere and Jetty. > However, focus of the community migrated away from that and improved the > use of the internally used servlet solution (also Apache Tomcat). > Since then the functionality of the component to have OFBiz work with these > external web containers stopped working and in recent years no contributor > felt the itch to correct/improve this situation. > > I therefor propose: > > - that we move the component from trunk to our attic, and > - we don't include it in future releases (including the upcoming r14.x > branch release r14.12.01) > > For this proposal the normal 72 hour rule applies. > > Best regards, > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com |
In reply to this post by Pierre Smits
+1
And I agree with Adrian: it would be a win for OFBiz if it could be deployed in various application servers easily. It could increase the acceptance bei companies who have a restrictive policy for their system landscape or simply have the know-how for other appliaction servers and don't like to add a new one. Michael Brohl ecomify.de Am 17.03.15 um 12:31 schrieb Pierre Smits: > *Rationale:* > Back in the day (pre r11.x) we enabled users to have OFBiz working in > external web containers, like Apache Tomcat, IBM Websphere and Jetty. > However, focus of the community migrated away from that and improved the > use of the internally used servlet solution (also Apache Tomcat). > Since then the functionality of the component to have OFBiz work with these > external web containers stopped working and in recent years no contributor > felt the itch to correct/improve this situation. > > I therefor propose: > > - that we move the component from trunk to our attic, and > - we don't include it in future releases (including the upcoming r14.x > branch release r14.12.01) > > For this proposal the normal 72 hour rule applies. > > Best regards, > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > |
In reply to this post by Pierre Smits
+1
And I also agree with Adrian. Thanks & Regards — Deepak Dixit > On Mar 17, 2015, at 5:01 PM, Pierre Smits <[hidden email]> wrote: > > *Rationale:* > Back in the day (pre r11.x) we enabled users to have OFBiz working in > external web containers, like Apache Tomcat, IBM Websphere and Jetty. > However, focus of the community migrated away from that and improved the > use of the internally used servlet solution (also Apache Tomcat). > Since then the functionality of the component to have OFBiz work with these > external web containers stopped working and in recent years no contributor > felt the itch to correct/improve this situation. > > I therefor propose: > > - that we move the component from trunk to our attic, and > - we don't include it in future releases (including the upcoming r14.x > branch release r14.12.01) > > For this proposal the normal 72 hour rule applies. > > Best regards, > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com |
+1.
Best Regards, -- Rishi Solanki Manager, Enterprise Software Development HotWax Systems Pvt. Ltd. Direct: +91-9893287847 http://www.hotwaxsystems.com On Tue, Mar 17, 2015 at 5:46 PM, Deepak Dixit < [hidden email]> wrote: > +1 > > And I also agree with Adrian. > > Thanks & Regards > — > Deepak Dixit > > > On Mar 17, 2015, at 5:01 PM, Pierre Smits <[hidden email]> > wrote: > > > > *Rationale:* > > Back in the day (pre r11.x) we enabled users to have OFBiz working in > > external web containers, like Apache Tomcat, IBM Websphere and Jetty. > > However, focus of the community migrated away from that and improved the > > use of the internally used servlet solution (also Apache Tomcat). > > Since then the functionality of the component to have OFBiz work with > these > > external web containers stopped working and in recent years no > contributor > > felt the itch to correct/improve this situation. > > > > I therefor propose: > > > > - that we move the component from trunk to our attic, and > > - we don't include it in future releases (including the upcoming r14.x > > branch release r14.12.01) > > > > For this proposal the normal 72 hour rule applies. > > > > Best regards, > > > > Pierre Smits > > > > *ORRTIZ.COM <http://www.orrtiz.com>* > > Services & Solutions for Cloud- > > Based Manufacturing, Professional > > Services and Retail & Trade > > http://www.orrtiz.com > > |
Administrator
|
In reply to this post by Pierre Smits
+1, I agree with Adrian, Jacopo and Michael comments
Jacques Le 17/03/2015 12:31, Pierre Smits a écrit : > *Rationale:* > Back in the day (pre r11.x) we enabled users to have OFBiz working in > external web containers, like Apache Tomcat, IBM Websphere and Jetty. > However, focus of the community migrated away from that and improved the > use of the internally used servlet solution (also Apache Tomcat). > Since then the functionality of the component to have OFBiz work with these > external web containers stopped working and in recent years no contributor > felt the itch to correct/improve this situation. > > I therefor propose: > > - that we move the component from trunk to our attic, and > - we don't include it in future releases (including the upcoming r14.x > branch release r14.12.01) > > For this proposal the normal 72 hour rule applies. > > Best regards, > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > |
Administrator
|
BTW, what about the jetty component?
I just found that it uses org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar and all version under 1.2.3 are vulnerable https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-0254 Jacques Le 17/03/2015 14:06, Jacques Le Roux a écrit : > +1, I agree with Adrian, Jacopo and Michael comments > > Jacques > > Le 17/03/2015 12:31, Pierre Smits a écrit : >> *Rationale:* >> Back in the day (pre r11.x) we enabled users to have OFBiz working in >> external web containers, like Apache Tomcat, IBM Websphere and Jetty. >> However, focus of the community migrated away from that and improved the >> use of the internally used servlet solution (also Apache Tomcat). >> Since then the functionality of the component to have OFBiz work with these >> external web containers stopped working and in recent years no contributor >> felt the itch to correct/improve this situation. >> >> I therefor propose: >> >> - that we move the component from trunk to our attic, and >> - we don't include it in future releases (including the upcoming r14.x >> branch release r14.12.01) >> >> For this proposal the normal 72 hour rule applies. >> >> Best regards, >> >> Pierre Smits >> >> *ORRTIZ.COM <http://www.orrtiz.com>* >> Services & Solutions for Cloud- >> Based Manufacturing, Professional >> Services and Retail & Trade >> http://www.orrtiz.com >> > |
In reply to this post by Jacques Le Roux
+1 also
Le 17/03/2015 14:06, Jacques Le Roux a écrit : > +1, I agree with Adrian, Jacopo and Michael comments > > Jacques > > Le 17/03/2015 12:31, Pierre Smits a écrit : >> *Rationale:* >> Back in the day (pre r11.x) we enabled users to have OFBiz working in >> external web containers, like Apache Tomcat, IBM Websphere and Jetty. >> However, focus of the community migrated away from that and improved the >> use of the internally used servlet solution (also Apache Tomcat). >> Since then the functionality of the component to have OFBiz work with >> these >> external web containers stopped working and in recent years no >> contributor >> felt the itch to correct/improve this situation. >> >> I therefor propose: >> >> - that we move the component from trunk to our attic, and >> - we don't include it in future releases (including the upcoming >> r14.x >> branch release r14.12.01) >> >> For this proposal the normal 72 hour rule applies. >> >> Best regards, >> >> Pierre Smits >> >> *ORRTIZ.COM <http://www.orrtiz.com>* >> Services & Solutions for Cloud- >> Based Manufacturing, Professional >> Services and Retail & Trade >> http://www.orrtiz.com >> |
Hi all,
Thanks for the votes. This proposal passed, according to following results: - Binding: 4 positive (+1) votes (Adrian, Jacopo, Jacques and Nicolas), 0 negative (-1) votes, 0 neutral (+0) votes - Non-Binding: 2 positive (+1) votes (Michael, Rishi), 0 negative (-1) votes, 0 neutral (+0) votes I will create an appropriate JIRA issue to track progress moving the special purpose/appserver component from trunk to attic. This will enable us to include it in release notes. Following comments/suggestion were made: - Discuss whether we should reengineer OFBiz so that it is easier to deploy in other application servers (by Adrian) Please start a new dev ml thread to discuss that, or start a wish or new feature issue in JIRA to track questions, comments and/or suggestions there. Thank you for your participation. Best regards Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Thu, Mar 19, 2015 at 6:00 PM, Nicolas Malin <[hidden email]> wrote: > +1 also > > Le 17/03/2015 14:06, Jacques Le Roux a écrit : > >> +1, I agree with Adrian, Jacopo and Michael comments >> >> >> Jacques >> >> Le 17/03/2015 12:31, Pierre Smits a écrit : >> >>> *Rationale:* >>> Back in the day (pre r11.x) we enabled users to have OFBiz working in >>> external web containers, like Apache Tomcat, IBM Websphere and Jetty. >>> However, focus of the community migrated away from that and improved the >>> use of the internally used servlet solution (also Apache Tomcat). >>> Since then the functionality of the component to have OFBiz work with >>> these >>> external web containers stopped working and in recent years no >>> contributor >>> felt the itch to correct/improve this situation. >>> >>> I therefor propose: >>> >>> - that we move the component from trunk to our attic, and >>> - we don't include it in future releases (including the upcoming >>> r14.x >>> branch release r14.12.01) >>> >>> For this proposal the normal 72 hour rule applies. >>> >>> Best regards, >>> >>> Pierre Smits >>> >>> *ORRTIZ.COM <http://www.orrtiz.com>* >>> Services & Solutions for Cloud- >>> Based Manufacturing, Professional >>> Services and Retail & Trade >>> http://www.orrtiz.com >>> >>> > |
*Correction on previous posting:*
adding vote of Deepak in the result. Hi all, Thanks for the votes. This proposal passed, according to following results: - Binding: 5 positive (+1) votes (Adrian, Jacopo, Deepak, Jacques and Nicolas), 0 negative (-1) votes, 0 neutral (+0) votes - Non-Binding: 2 positive (+1) votes (Michael, Rishi), 0 negative (-1) votes, 0 neutral (+0) votes I will create an appropriate JIRA issue to track progress moving the special purpose/appserver component from trunk to attic. This will enable us to include it in release notes. Following comments/suggestion were made: - Discuss whether we should reengineer OFBiz so that it is easier to deploy in other application servers (by Adrian) Please start a new dev ml thread to discuss that, or start a wish or new feature issue in JIRA to track questions, comments and/or suggestions there. Thank you for your participation. Best regards Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Fri, Mar 20, 2015 at 1:49 PM, Pierre Smits <[hidden email]> wrote: > Hi all, > > Thanks for the votes. > > This proposal passed, according to following results: > > - Binding: 4 positive (+1) votes (Adrian, Jacopo, Jacques and > Nicolas), 0 negative (-1) votes, 0 neutral (+0) votes > - Non-Binding: 2 positive (+1) votes (Michael, Rishi), 0 negative (-1) > votes, 0 neutral (+0) votes > > I will create an appropriate JIRA issue to track progress moving the > special purpose/appserver component from trunk to attic. This will enable > us to include it in release notes. > > Following comments/suggestion were made: > > - Discuss whether we should reengineer OFBiz so that it is easier to > deploy in other application servers (by Adrian) > > Please start a new dev ml thread to discuss that, or start a wish or new > feature issue in JIRA to track questions, comments and/or suggestions there. > > Thank you for your participation. > > Best regards > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Thu, Mar 19, 2015 at 6:00 PM, Nicolas Malin <[hidden email]> > wrote: > >> +1 also >> >> Le 17/03/2015 14:06, Jacques Le Roux a écrit : >> >>> +1, I agree with Adrian, Jacopo and Michael comments >>> >>> >>> Jacques >>> >>> Le 17/03/2015 12:31, Pierre Smits a écrit : >>> >>>> *Rationale:* >>>> Back in the day (pre r11.x) we enabled users to have OFBiz working in >>>> external web containers, like Apache Tomcat, IBM Websphere and Jetty. >>>> However, focus of the community migrated away from that and improved the >>>> use of the internally used servlet solution (also Apache Tomcat). >>>> Since then the functionality of the component to have OFBiz work with >>>> these >>>> external web containers stopped working and in recent years no >>>> contributor >>>> felt the itch to correct/improve this situation. >>>> >>>> I therefor propose: >>>> >>>> - that we move the component from trunk to our attic, and >>>> - we don't include it in future releases (including the upcoming >>>> r14.x >>>> branch release r14.12.01) >>>> >>>> For this proposal the normal 72 hour rule applies. >>>> >>>> Best regards, >>>> >>>> Pierre Smits >>>> >>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>> Services & Solutions for Cloud- >>>> Based Manufacturing, Professional >>>> Services and Retail & Trade >>>> http://www.orrtiz.com >>>> >>>> >> > Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Fri, Mar 20, 2015 at 1:49 PM, Pierre Smits <[hidden email]> wrote: > Hi all, > > Thanks for the votes. > > This proposal passed, according to following results: > > - Binding: 4 positive (+1) votes (Adrian, Jacopo, Jacques and > Nicolas), 0 negative (-1) votes, 0 neutral (+0) votes > - Non-Binding: 2 positive (+1) votes (Michael, Rishi), 0 negative (-1) > votes, 0 neutral (+0) votes > > I will create an appropriate JIRA issue to track progress moving the > special purpose/appserver component from trunk to attic. This will enable > us to include it in release notes. > > Following comments/suggestion were made: > > - Discuss whether we should reengineer OFBiz so that it is easier to > deploy in other application servers (by Adrian) > > Please start a new dev ml thread to discuss that, or start a wish or new > feature issue in JIRA to track questions, comments and/or suggestions there. > > Thank you for your participation. > > Best regards > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Thu, Mar 19, 2015 at 6:00 PM, Nicolas Malin <[hidden email]> > wrote: > >> +1 also >> >> Le 17/03/2015 14:06, Jacques Le Roux a écrit : >> >>> +1, I agree with Adrian, Jacopo and Michael comments >>> >>> >>> Jacques >>> >>> Le 17/03/2015 12:31, Pierre Smits a écrit : >>> >>>> *Rationale:* >>>> Back in the day (pre r11.x) we enabled users to have OFBiz working in >>>> external web containers, like Apache Tomcat, IBM Websphere and Jetty. >>>> However, focus of the community migrated away from that and improved the >>>> use of the internally used servlet solution (also Apache Tomcat). >>>> Since then the functionality of the component to have OFBiz work with >>>> these >>>> external web containers stopped working and in recent years no >>>> contributor >>>> felt the itch to correct/improve this situation. >>>> >>>> I therefor propose: >>>> >>>> - that we move the component from trunk to our attic, and >>>> - we don't include it in future releases (including the upcoming >>>> r14.x >>>> branch release r14.12.01) >>>> >>>> For this proposal the normal 72 hour rule applies. >>>> >>>> Best regards, >>>> >>>> Pierre Smits >>>> >>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>> Services & Solutions for Cloud- >>>> Based Manufacturing, Professional >>>> Services and Retail & Trade >>>> http://www.orrtiz.com >>>> >>>> >> > |
In reply to this post by Jacques Le Roux
On Mar 17, 2015, at 2:20 PM, Jacques Le Roux <[hidden email]> wrote:
> BTW, what about the jetty component? > > I just found that it uses org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar and all version under 1.2.3 are vulnerablehttps://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-0254 > > Jacques > This is probably worth of a new thread. Jacopo |
Indeed. Wil start that one coming monday.
Best regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Fri, Mar 20, 2015 at 2:00 PM, Jacopo Cappellato < [hidden email]> wrote: > On Mar 17, 2015, at 2:20 PM, Jacques Le Roux <[hidden email]> > wrote: > > > BTW, what about the jetty component? > > > > I just found that it uses > org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar and all > version under 1.2.3 are vulnerablehttps:// > web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-0254 > > > > Jacques > > > > This is probably worth of a new thread. > > Jacopo > > |
Administrator
|
Thanks Pierre
Looking forward Jacques Le 20/03/2015 14:15, Pierre Smits a écrit : > Indeed. Wil start that one coming monday. > > Best regards, > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Fri, Mar 20, 2015 at 2:00 PM, Jacopo Cappellato < > [hidden email]> wrote: > >> On Mar 17, 2015, at 2:20 PM, Jacques Le Roux <[hidden email]> >> wrote: >> >>> BTW, what about the jetty component? >>> >>> I just found that it uses >> org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar and all >> version under 1.2.3 are vulnerablehttps:// >> web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-0254 >>> Jacques >>> >> This is probably worth of a new thread. >> >> Jacopo >> >> |
Free forum by Nabble | Edit this page |