The behavior you are seeing in Weld is correct per the spec. The docs aren't are canonical source of anything, *always* check the spec ;-)
On 25 Feb 2011, at 04:24, John D. Ament wrote: > Brian, > > I identified a potential issue tonight in Weld that will be a pretty big > blocker for Seam JMS to make it out anytime soon. A maintenance release of > Weld would definitely help in this one as well. WELD-860 is the issue if > you're interested. > > John > > On Thu, Feb 24, 2011 at 11:02 PM, Brian Leathem <[email protected]> wrote: > On 02/19/2011 07:37 AM, Clint Popetz wrote: > > Any way we can get a Weld 1.1.1 to have 3.0 rely upon? > > > > https://issues.jboss.org/browse/WELD-833 has been fixed in > > 1.1.1-SNAPSHOT, and without it seam-wicket it not usuable. > > > > -Clint > > I'm in a similar boat with Faces, in terms of needing a Weld maintenance > release. I became increasingly worried when I heard that Weld 1.2 might > come with SPI changes (although I've been told this is not yet set in > stone). > > I'm going to put togehter a post to the weld-dev list outlining the > benefit a Weld 1.1.1 release would have for Faces. I'll include you're > Wicket/Weld issue above as an example of another Seam module that would > benefit from such a release, please let me know of any other issues that > would strengthen the argument. > > Are there any other modules out there that have specific issues > requiring a Weld maintenance release? If so, please let me know, and > I'll put together a complete picture of how Seam could benefit from a > 1.1.1 release. > > Brian Leathem > _______________________________________________ > seam-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/seam-dev > > _______________________________________________ > seam-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ seam-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/seam-dev
