[seam-dev] weld 2.0 / soldr 3.x not compatible
Lincoln Baxter, III
lincolnbaxter at gmail.com
Fri Jun 7 07:52:01 EDT 2013
If anyone wants to fix these issues, and write pull requests that pass the
test suite, let me know and I can push a release.
On Fri, Jun 7, 2013 at 2:57 AM, Martin Kouba <mkouba at redhat.com> wrote:
> Actually I think this is an incorrect technique used in Solder which may
> lead to incalculable results. See also CDI issues [1] for more info. CDI
> 1.0 did not forbid this and it was definitely a mistake (on the other
> hand it's really hard to identify all such cases). In any case Weld is a
> reference implementation and thus must follow the spec.
>
> IMO CDI 1.1 compatible release of Solder would be a good move..
>
> Martin
>
> [1]
> https://issues.jboss.org/browse/CDI-274
> https://issues.jboss.org/browse/CDI-315
>
>
>
> Dne 7.6.2013 00:16, Korbinian Bachl napsal(a):
> > One needs to remember that many projects out there did use Seam Solder/
> > Solder and need a kind of drop in replacement, else they are all stuck
> > with CDI 1.0 for long time and JEE7 adoption or deployment on JEE7
> > Servers will not happen to them anytime soon (reminds me of bad times
> > when many software needing quite old JRE's to be run on some years
> ago...).
> >
> > Current problem I see is the
> > org.jboss.weld.exceptions.IllegalStateException during startup - John
> > Ament wrote sth about turning off exception handling, but I dont know
> > how I can do that in Weld 2.0 (or did I misunderstand this line?)
> >
> >
> > DeltaSpike itself looks promising but far away from good for production
> > IMHO and seems much work to be ported from soldr to it;
> >
> >
> >
> > 2013/6/6 John D. Ament <john.d.ament at gmail.com
> > <mailto:john.d.ament at gmail.com>>
> >
> > Yep, DS right now has some test failures in Weld 2.x
> >
> >
> > On Thu, Jun 6, 2013 at 5:47 PM, Lincoln Baxter, III
> > <lincolnbaxter at gmail.com <mailto:lincolnbaxter at gmail.com>> wrote:
> >
> > I think this might even be an issue with DeltaSpike, people have
> > informed me that some of my code is broken, and we use
> DeltaSpike.
> >
> >
> > On Thu, Jun 6, 2013 at 4:36 PM, Jason Porter
> > <lightguard.jp at gmail.com <mailto:lightguard.jp at gmail.com>>
> wrote:
> >
> > If you're looking for a comparable solution that works with
> > Weld 2, take a look at DeltaSpike. Solder has been
> > discontinued and most of the code has been ported to
> DeltaSpike.
> >
> >
> > On Thu, Jun 6, 2013 at 11:03 AM, John D. Ament
> > <john.d.ament at gmail.com <mailto:john.d.ament at gmail.com>>
> wrote:
> >
> > I'm pretty sure CDI 1.1 will break a lot of current CDI
> > extensions due to the behavioral changes. Do you need
> > exception handling? Did you try turning off the
> > exception handling extension?
> >
> >
> > On Thu, Jun 6, 2013 at 3:41 AM, Korbinian Bachl
> > <korbinian.bachl at gmail.com
> > <mailto:korbinian.bachl at gmail.com>> wrote:
> >
> > Hello,
> >
> > during our test for Glassfish 4.0 we found out that
> > seam-soldr/ now jboss-soldr isn't compatbile with
> > weld. We loggedn ans issue at glassfish (
> >
> https://java.net/jira/browse/GLASSFISH-20577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=364696#action_364696
> > ) and they pointed me to this list.
> >
> > Problem is that soldr calls getBeans() during init
> > and WELD 2 now throws an exception for this:
> >
> > org.jboss.weld.exceptions.IllegalStateException:
> > WELD-001332 BeanManager method getBeans() is not
> > available during application initialization
> >
> > Sadly the weld 2 people didn't think about backwards
> > compatibility in that position (why not just throw a
> > big warning?);
> >
> > Is there any way soldr3.x can get a last
> > compatibilitiy fix?
> > At least it was previous weld-extensions and
> > therefore seen as the de-facto standard. I know that
> > the future should be Apache DeltaSpike, but that
> > wouldnt be a drop in replacement like a new 3.x
> > version of soldr would be.
> >
> > Best,
> >
> > KBachl
> >
> >
> >
> > _______________________________________________
> > seam-dev mailing list
> > seam-dev at lists.jboss.org
> > <mailto:seam-dev at lists.jboss.org>
> > https://lists.jboss.org/mailman/listinfo/seam-dev
> >
> >
> >
> > _______________________________________________
> > seam-dev mailing list
> > seam-dev at lists.jboss.org <mailto:
> seam-dev at lists.jboss.org>
> > https://lists.jboss.org/mailman/listinfo/seam-dev
> >
> >
> >
> >
> > --
> > Jason Porter
> > http://en.gravatar.com/lightguardjp
> >
> > _______________________________________________
> > seam-dev mailing list
> > seam-dev at lists.jboss.org <mailto:seam-dev at lists.jboss.org>
> > https://lists.jboss.org/mailman/listinfo/seam-dev
> >
> >
> >
> >
> > --
> > Lincoln Baxter, III
> > http://ocpsoft.org
> > "Simpler is better."
> >
> >
> >
> >
> >
> > _______________________________________________
> > seam-dev mailing list
> > seam-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/seam-dev
> >
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20130607/e02d9f05/attachment-0001.html
More information about the seam-dev
mailing list