[
https://issues.jboss.org/browse/SEAMSECURITY-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589146#comment-12589146
]
Dan Allen edited comment on SEAMSECURITY-37 at 3/19/11 11:41 PM:
-----------------------------------------------------------------
{quote}
Thanks for the clarifications! That blog post is wonderfully enlightening. I'm
sorry if what I said came across a bit harsh. There is so much good stuff in
Seam 3 that I want to start using as soon as possible but is frustratingly just
out of reach.
{quote}
Trust me, I know exactly where you're coming from. What's important to me is
that the community feels in the loop. Naturally, we are going to run into
roadblocks, as we have with GlassFish. If we can keep everyone on the same
page, we can plow right through them.
{quote}
If I understand you correctly Seam Security has to change how it injects
Messages. Is that correct?
{quote}
I believe so, though I haven't personally tried Seam Security in the booking
example (haven't gotten to it yet). The reason putting the injection on the
method argument works is because Weld does not validate observer method
injections (doesn't try to work them out at startup). In a sense, it's a
backdoor. The funny part is that by the time the observer gets called, the bean
is available (as we discovered in Seam Faces). I'm optimistic the same will
apply here.
was (Author: dan.j.allen):
{quote}
Thanks for the clarifications! That blog post is wonderfully enlightening. I'm
sorry if what I said came across a bit harsh. There is so much good stuff in
Seam 3 that I want to start using as soon as possible but is frustratingly just
out of reach.
{quote}
Trust me, I know exactly where you're coming from. What's important to me is
that the community feels in the loop. Naturally, we are going to run into
roadblocks, as we have with GlassFish. If we can keep everyone on the same
page, we can plow right through them.
{quote}
If I understand you correctly Seam Security has to change how it injects
Messages. Is that correct?
{quote}
I believe so, though I haven't personally tried Seam Security in the booking
example (haven't gotten to it yet). The reason putting the injection on the
method argument works is because Weld does not validate observer method
injections (doesn't try to work them out at startup). In a sense, it's a
backdoor. The funny part is that by the time the observer gets called, the bean
is available (as we discovered in seam international). I'm optimistic the same
will apply here.
> Unsatisfied dependencies for type [Messages]...
> -----------------------------------------------
>
> Key: SEAMSECURITY-37
> URL: https://issues.jboss.org/browse/SEAMSECURITY-37
> Project: Seam Security
> Issue Type: Bug
> Affects Versions: 3.0.0.Beta2
> Environment: Mac OS X, Glassfish v3.1b42, Java 1.6
> Reporter: Aaron Siri
> Assignee: Shane Bryzak
> Fix For: 3.0.0.CR2
>
> Attachments: SecurityBreak-0.0.1-SNAPSHOT.war, SecurityBreak.zip
>
>
> Trying to deploy an app with simple security integration I get the following
> exception:
> SEVERE: Exception while loading the app : WELD-001408 Unsatisfied
> dependencies for type [Messages] with qualifiers [@Default] at injection
> point [[field] @Inject org.jboss.seam.security.SecurityEventMessages.messages]
> org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied
> dependencies for type [Messages] with qualifiers [@Default] at injection
> point [[field] @Inject org.jboss.seam.security.SecurityEventMessages.messages]
> at
> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:305)
> at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:139)
> at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:162)
> at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:385)
> at
> org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:371)
> at
> org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:390)
> ...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
