1:52 p.m.
Hello Weld devs,
I am under the understanding that the next Weld release will be Weld
1.2, with potential SPI changes. I am writing to ask about the
possibility of more frequent weld maintenance releases, using the same
SPI. This would greatly benefit the Seam 3.0 release, as there are a
couple of modules that currently do not work as expected due to bugs in
Weld. Specifically:
WELD-846 - Incorrect handling of cyclic dependencies between
BeanDeploymentArchives
causes: SEAMFACES-82, no injection in JSF Converters/Validators
WELD-833 - ConcurrentModificationException while deactivating conversations
renders Seam Wicket unusable
and potentially:
WELD-855 - Error while catching NonexistentConversationException with
Seam Faces/Catch
causes: SEAMCATCH-46
Some of these issues have been already resolved in Weld, and can be
worked around by using a Weld SNAPSHOT. However, it is probable that
more issues will arise as more people start using Seam 3, and a quick
turnaround on Weld releases would help greatly with user acceptance of
Seam 3. It would also bode well for containers that were quick to adopt
the Weld maintenance releases.
If there is any more details I can provide, or further strengthening of
the above arguments, please let me know.
Regards,
Brian Leathem
Seam Faces - Module Lead
2:31 p.m.
The maintenance release 1.1.1. is being discussed.
Atm we don't have any SPI changes yet for 1.2.x, but that doesn't mean they
won't happen.
But, as the version change indicates, the changes should be back compatible.
e.g. possible mixin introduction
I know the first two issues are fixed, what's the status of the WELD-855?
Did you (Brian) and Pete get to the bottom of it?
I'll also check what else we can backport.
-Ales
On Mar 1, 2011, at 8:52 PM, Brian Leathem wrote:
5:38 p.m.
On 03/01/2011 12:31 PM, Ales Justin wrote:
The maintenance release 1.1.1. is being discussed.
While the Weld 1.1.1 release would be particularly beneficial to the
Seam 3.0 release, I hope you are also considering making regular
maintenance releases, as more issues are bound to come up. As Stuart
said, doing otherwise could hurt adoption.
I know the first two issues are fixed, what's the status of the
WELD-855?
Did you (Brian) and Pete get to the bottom of it?
No, that issue is still unresolved.
Thanks,
Brian Leathem
6:53 p.m.
On Tue, Mar 1, 2011 at 14:52, Brian Leathem <bleathem(a)gmail.com> wrote:
I want to emphasize how critical it is that we keep problems at bay as we
near the first release of Seam 3. We've really asked the growing Seam 3 user
community to stomach a lot of complications and thus far, they've been
hanging in there and working around the problems. But we need to get these
problems behind us, swiftly, and let them focus on their real business
problems and not exceptions. It doesn't just help the acceptance of Seam 3,
it's crucial to it.
-Dan
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction
6:52 a.m.
+1, I think it's pretty crucial to have regular maintenance release (fixing e.g. bugs
like WELD-833 which essentially make conversations unusable in AS6 final) + a simple Weld
update path for AS6, if Weld and Seam are to be used in any larger project. It's an
emerging technology so I think it needs pretty active support.
Of course it's possible to patch Weld etc by hand, but who is going to do that ;)
Adam
On Mar 1, 2011, at 8:52 PM, Brian Leathem wrote:
--
Adam Warski
http://www.warski.org
http://www.softwaremill.eu
5117
days inactive
5120
days old
5 comments
5 participants
participants (5)
-
Adam Warski -
Ales Justin -
Brian Leathem -
Dan Allen -
Stuart Douglas