Hi Arun!

One of the simplest examples is our CODI playground jsf20 example [1]. 
Well, our examples are made for standalone usage. So please just remove the 
openwebbeans stuff from the WAR and cut down other dependencies which are not 
needed on a full EE server. 

With Glassfish-3.1 you will almost immediately fall over this very nasty 
mojarra bug (fixed in the meantime):
http://java.net/jira/browse/GLASSFISH-15905
This is a really weird thing and has nothing to do with Weld. It is just an 
incompletely initialized FacesContext. I also faced other weird errors of this 
kind when starting glassfish under load (jmeter running against it). There 
might be some startup problems, but it's hard to create a stable test case for 
it, so I didn't report it.

Matthias Wessendorf tried to work around the mentioned bug and found a bunch of 
other major issues in only a few hours testing. A few of them are still open 
and unfixed! Just check your Jira for reporter='mwessendorf'.

gf-3.2 looks a good bit better.


LieGrue,
strub


[1]
$> svn co https://svn.apache.org/repos/asf/myfaces/extensions/cdi/trunk codi
$> cd examples/jsf-playground/hello_myfaces-codi_jsf20/
$> mvn clean install
and then strip the WAR file

--- On Sat, 5/28/11, Gerhard Petracek <gerhard.petra...@gmail.com> wrote:

> From: Gerhard Petracek <gerhard.petra...@gmail.com>
> Subject: Re: [FYI] testing CODI and Seam3 with glassfish
> To: "MyFaces Discussion" <users@myfaces.apache.org>
> Date: Saturday, May 28, 2011, 9:04 PM
> hi arun,
> 
> welcome @ our mailing-list!
> 
> most issues faced by our users are specific to weld and/or
> glassfish in
> combination with bigger portable extensions and sometimes
> even with simpler
> cases.
> if you test the same implementation with openwebbeans and
> a
> servlet-container like tomcat or owb and a jee5 app-server,
> it just works.
> 
> however, several issues are quite specific. e.g. we have
> users who can use
> the fine-grained modules of codi with glassfish and others
> see
> deployment-issues with the same setup and have to use the
> all-in-one jar as
> a workaround.
> we already filed weld as well as glassfish issues, if an
> issue was
> reproducible.
> 
> anyway, the first version which worked in most of our
> (still quite simple)
> tests is the latest snapshot of glassfish v3.2. even the
> combination of
> glassfish v3.1 + weld v1.1.1 has major issues for some
> (quite common)
> use-cases.
> 
> regards,
> gerhard
> 
> http://www.irian.at
> 
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
> 
> Professional Support for Apache MyFaces
> 
> 
> 2011/5/28 Arun Gupta <arun.gu...@gmail.com>
> 
> > Hi Kito,
> >
> > Google alerts showed me this message and raised my
> curiosity. I wanted
> > to find out how bad GlassFish is broken :-)
> >
> > CDI 1.1 discussions are all happening in open and you
> can support your case
> > at:
> >
> > https://lists.jboss.org/mailman/listinfo/cdi-dev
> >
> > or githib:
> >
> > https://github.com/pmuir/cdi/wiki
> >
> > -Arun
> >
> > On Sat, May 28, 2011 at 1:08 PM, Kito Mann <kito.m...@virtua.com>
> wrote:
> > > Hello Arun,
> > >
> > > Glad to see you here. Not only is it good for
> CDI, but it's good for me,
> > > since I'm looking into using Glassfish.
> > >
> > > While you're on it, please push for portlet
> support in Weld :-).
> > > ---
> > > Kito D. Mann | twitter: kito99 | Author, JSF in
> Action
> > > Virtua, Inc. | http://www.virtua.com | JSF/Java EE
> training and
> > consulting
> > > http://www.JSFCentral.com - JavaServer Faces FAQ, news,
> and info |
> > twitter:
> > > jsfcentral
> > > +1 203-404-4848 x3
> > >
> > > * Listen to the latest headlines in the JSF and
> Java EE newscast:
> > >
> > http://blogs.jsfcentral.com/roller/editorsdesk/category/JSF+and+Java+EE+Newscast
> > > * See you at JAX and JSF Summit 2011 June 20-23rd
> in San Jose:
> > > http://jaxconf.com/
> > >
> > >
> > > On Sat, May 28, 2011 at 4:04 PM, arungupta <arun.gu...@gmail.com>
> wrote:
> > >
> > >>
> > >> Hi Mark,
> > >>
> > >>
> > >> struberg wrote:
> > >> >
> > >> > The result:
> > >> >
> > >> > Please skip glassfish-3.1 !
> > >> >
> > >> > It's really completely broken. It has
> lots of errors not only in Weld
> > but
> > >> > also in the Mojarra integration it ships
> (from minor glitches to not
> > >> > finding the FacesContext because the
> lookup integration seems
> > completely
> > >> > messed up)!
> > >> > Most of my tested projects even refused
> to start at all!
> > >> >
> > >>
> > >> Can you share more details of your tests ?
> Did you file any bugs ? I
> > know
> > >> several folks using GlassFish in production
> with Mojarra + PrimeFaces +
> > >> CDI.
> > >>
> > >>
> > >> struberg wrote:
> > >> >
> > >> > The solution: use glassfish-3.2-SNAPSHOT
> (*)!
> > >> > I was at least able to start a few
> samples successfully. There are
> > still
> > >> a
> > >> > few fixes needed (moving around
> beans.xml info, extracting jars to
> > >> > WEB-INF/classes, EAR scenario completely
> fucked up when using
> > >> Extensions),
> > >> > but for a WAR deployment it's
> sufficient...
> > >> >
> > >>
> > >> GlassFish 3.2 has Weld 1.1 so that might have
> solved some of the issues
> > you
> > >> faced.
> > >>
> > >>
> > >> struberg wrote:
> > >> >
> > >> > Oh yea, I did a 'bit' more than just a
> simple hello webworld - but not
> > >> too
> > >> > much. The projects were still pretty
> small.
> > >> >
> > >>
> > >> Can you share your samples so that I can try
> it as well ?
> > >>
> > >> Thanks,
> > >> -Arun
> > >>
> > >> --
> > >> View this message in context:
> > >>
> > http://old.nabble.com/-FYI--testing-CODI-and-Seam3-with-glassfish-tp31676813p31724974.html
> > >> Sent from the MyFaces - Users mailing list
> archive at Nabble.com.
> > >>
> > >>
> > >
> >
> >
> >
> > --
> > twitter.com/arungupta
> > blogs.sun.com/arungupta
> >
> 

Reply via email to