Hi Max and Alexey,
here is the JIRA filter for issues which affect JBoss Tools and its Seam2 integration - https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&requestId=1...
I will group all issues like these with label seam-gen and component Tools.
JBoss Seam Product Lead
Red Hat Czech s.r.o.
612 45 Brno
Office phone: +420 532 294 287, ext. 82-62 087
mobile: +420 608 509 230
I worked on OAuth integration in Seam Security.
Markek provided some code in Seam Social but I found it more relevant to put it in Security. So I moved and refactored the Authenticator in Seam Security External. Everything seems ok but I can't start the Web example application having this exception.
org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [SamlSignatureUtilForPostBinding] with qualifiers [@Default] at injection point [[field] @Inject private org.jboss.seam.security.external.saml.SamlMessageSender.signatureUtilForPostBinding]
I tested my security classes directly in the web app : it works. So I can't put them in external since I need to configure unrelated beans to avoid Weld error at boot time.
I pushed the code for others to test. Start with example/oauth web app. The version works. If you delete org.jboss.seam.security.external.oauth and org.jboss.seam.security.external.oauth.api package from the web app and add security-external (which contains the same classes) as a dependence you'll have the exception.
Is that still installed? I seem to remember that it was at one time because
most tests would pass on some of the examples that I am working on, now it
has no referral to any dependency management in the parent poms.
Programmer, Instructor, and Consultant
I know I've said in the past we need to get on a date for this :) Here I am
doing that now. I would like to propose April 30th for 3.1.1. This would be
a minor release addressing bugs, documentation and examples.
I know I blogged  about some additional examples so I think we have
those covered. We may not distribute them, but simple have them in a README
or something like that. Of course I'm open to other ideas here.
For bugs and documentation I'm looking for some help from all of you to
categorize issues and documentation spots we really need to focus on
correcting and improving. Does everyone feel like Friday would be enough
time for people get that list in, or should we extend it to next Wednesday?
I don't want to go too long and not have enough time to get things done.
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling
PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu