At my direction, the company I work for is using JBoss as its production (and test and development) app server. However, you may find that people are a little reluctant to reveal their company's name. Since JBoss is open source, anyone (good or bad) can see it and dig into it for security exposures. Revealing company names that are using JBoss in production might expose those companies to heightened level of attacks.
----- Original Message ----- From: "Ben Sabrin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, August 08, 2002 12:26 AM Subject: [JBoss-user] Success Stories > Hello all, > > We need to put together production references of JBoss and can not do this > without your help. You have all taken the path that will lead your > companies to superior infrastructure and reduces cost, however, we need your > help to lure others down this path. > > If you are in production with JBoss or are getting ready to be in production > with JBoss, please let me know when we can speak about putting together a > case study. > > This community is thriving with your help. JBoss Group strives to deliver > the highest quality service at a much more competitive price than our > competitors. We can not do this alone. > > Thanks for your help. > > Regards, > > Ben Sabrin > Director of Sales and Business Development > JBoss Group, LLC > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Jules > Gosnell > Sent: Monday, August 05, 2002 7:50 AM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] "env-entry-value" is not allowed? > > > The xml parser is in strict mode and considers element order important. > This is to ensure maximum portability from JBoss to other platforms. > > Try using the same element order as in the DTD - below. > > I will check as to why this strict ordering is deemed necessary... > > > Jules > > > > > <!-- > The env-entry element contains the declaration of a web application's > environment entry. The declaration consists of an optional > description, the name of the environment entry, and an optional > value. If a value is not specified, one must be supplied > during deployment. > --> > <!ELEMENT env-entry (description?, env-entry-name, env-entry-value?, > env-entry-type)> > > > Geer, Benjamin wrote: > > I'm trying to deploy a simple WAR file using JBoss 3.0.1RC1 with Jetty. > > My web.xml contains the following (just at the end, before the > > </web-app> closing tag): > > > > <env-entry> > > <env-entry-name>serverJndiName</env-entry-name> > > <env-entry-type>java.lang.String</env-entry-type> > > <env-entry-value>java:comp/meridian/test</env-entry-value> > > </env-entry> > > > > The WAR file fails to deploy, and JBoss prints the following error > > message: > > > > org.jboss.deployment.DeploymentInfo@fc00fc9 { > > url=file:/D:/jboss-3.0.1RC1/serv > > er/default/deploy/meridian-soaptest.war } > > deployer: org.jboss.jetty.JettyService@edf389 > > status: Deployment FAILED reason: Parse error on > > jar:file:/D:/jboss-3.0.1RC1/server/default/tmp/deploy/server/default/dep > > loy/meridian-soaptest.war/91.meridian > > -soaptest.war!/: org.xml.sax.SAXParseException: Element "env-entry" > > allows no further input; "env-entry-value" is not allowed.; - nested > > throwable: (java.io.IOException: Parse error on > > jar:file:/D:/jboss-3.0.1RC1/server/default/tmp/deploy/server/default/dep > > loy/meridian-soaptest.war/91.meridian-soaptest.war!/: > > org.xml.sax.SAXParseException: Element "env-entry" allows no further > > input; "env-entry-value" is not allowed.) > > > > The J2EE spec definitely requires support for <env-entry> containing > > <env-entry-value>, and I'd be very surprised if JBoss was noncompliant > > in this respect; can anyone shed any light on what might be causing the > > problem? > > > > Benjamin > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
