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 <[email protected]>

> 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 <[email protected]> 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 <[email protected]> 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