Sure. This isn't about technical merit unfortunately. The reason is that the ops team have a standard deployment approach. Think of it like an OS or VM or JVM. The ops team probaly have one specific OS they support, and if you are on Windows and they want to run Linux they are going to either just say no, or make a huge issue of it. Similarly if they are on IBM JDK 1.6 and you don't support that they are going to make it an issue.
Lots of ops teams do not just support a JVM. They support an app server. So *every* piece of Java code that runs in the server machine farm MUST be running on Weblogic 9, whether or not its really using the appserver features. Unfortunately this is the way many machine rooms are run and trying to fight it is counterproductive. I have a list of customers where we have run into this but I can't send it on this list. Paul On 1 September 2010 10:45, Supun Kamburugamuva <[email protected]> wrote: > The features provided by App Servers like JBoss, WebLogic may not be > available in tomcat and our users may not be able to use those. For > example I'm pretty sure WebLogic like servers will have more advanced > ways of monitoring and management capabilities. > > Thanks, > Supun.. > > On Wed, Sep 1, 2010 at 2:46 PM, Paul Fremantle <[email protected]> wrote: > > The big problem with this is not architecture but customers. Many of our > > customers *cannot* deploy Carbon standalone because their ops teams will > not > > allow it. They require us to be deployed into an existing App Server > > environment. > > > > Paul > > > > On 1 September 2010 10:03, Afkham Azeez <[email protected]> wrote: > >> > >> Hi Folks, > >> As you know, Carbon servers can run in standalone mode or can be > deployed > >> within an Application Server. This has caused us major architectural > >> constraints & issues since we have to start an OSGi container within the > >> Carbon webapp, while the Carbon webapp itself runs within a servlet > >> container. We've had to put in many ugly workarounds to make this setup > >> work, and still have some limitations. If we drop support for running > Carbon > >> as a webapp, then we can simply start an OSGi container, and run the > servlet > >> container as a bundle deployed on this OSGi container. Also, now that we > >> have support for deploying webapps, it doesn't make sense to have a > webapp > >> (Carbon) which allows you to deploy other webapps within it, This will > be > >> architecturally clean as well. > >> So, is every in agreement with going ahead with this? Thoughts welcome. > >> -- > >> Afkham Azeez > >> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com > , > >> > >> Member; Apache Software Foundation; http://www.apache.org/ > >> email: [email protected] cell: +94 77 3320919 > >> blog: http://blog.afkham.org > >> twitter: http://twitter.com/afkham_azeez > >> linked-in: http://lk.linkedin.com/in/afkhamazeez > >> > >> Lean . Enterprise . Middleware > >> > >> > >> _______________________________________________ > >> Architecture mailing list > >> [email protected] > >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >> > > > > > > > > -- > > Paul Fremantle > > CTO and Co-Founder, WSO2 > > OASIS WS-RX TC Co-chair, VP, Apache Synapse > > > > Office: +44 844 484 8143 > > Cell: +44 798 447 4618 > > > > blog: http://pzf.fremantle.org > > twitter.com/pzfreo > > [email protected] > > > > wso2.com Lean Enterprise Middleware > > > > Disclaimer: This communication may contain privileged or other > confidential > > information and is intended exclusively for the addressee/s. If you are > not > > the intended recipient/s, or believe that you may have received this > > communication in error, please reply to the sender indicating that fact > and > > delete the copy you received and in addition, you should not print, copy, > > retransmit, disseminate, or otherwise use the information contained in > this > > communication. Internet communications cannot be guaranteed to be timely, > > secure, error or virus-free. The sender does not accept liability for any > > errors or omissions. > > > > _______________________________________________ > > Architecture mailing list > > [email protected] > > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > > > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse Office: +44 844 484 8143 Cell: +44 798 447 4618 blog: http://pzf.fremantle.org twitter.com/pzfreo [email protected] wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.
_______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
