[ https://issues.jboss.org/browse/SEAMSECURITY-37?page=com.atlassian.jira.p... ] Shane Bryzak reassigned SEAMSECURITY-37: ---------------------------------------- Assignee: Shane Bryzak -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMSECURITY-37?page=com.atlassian.jira.p... ] Richard Barabe commented on SEAMSECURITY-37: -------------------------------------------- I have the same problem with seam-security 3.0.0.Beta2 under glassish 3.1-b43 I looked at the code but I really don't understand why the error occurs. Please explain if you find, I'm very curious. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMSECURITY-37?page=com.atlassian.jira.p... ] Shane Bryzak commented on SEAMSECURITY-37: ------------------------------------------ Are you including seam-international.jar in your project? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMSECURITY-37?page=com.atlassian.jira.p... ] Shane Bryzak commented on SEAMSECURITY-37: ------------------------------------------ Hmm, I'm not sure what to suggest next, as I can't reproduce this. How are you packaging your app? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMSECURITY-37?page=com.atlassian.jira.p... ] Aaron Siri updated SEAMSECURITY-37: ----------------------------------- Attachment: SecurityBreak.zip SecurityBreak-0.0.1-SNAPSHOT.war An Eclipse/Maven project that breaks and the .war file generated from "mvn package" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMSECURITY-37?page=com.atlassian.jira.p... ] Aaron Siri commented on SEAMSECURITY-37: ---------------------------------------- Why does Weld work with JBoss but appears to be broken on Glassfish? Is it Weld's fault or Glassfish's fault? What is the quickest way to get this whole mess resolved? I don't know how Seam 3 can possibly be in release candidate stage. Everything I try breaks in Glassfish. Seam 3 Security has never worked in Glassfish. Now Seam 3 International, which is an unwanted but required dependency, is breaking out-of-the-box too. Is any of this stuff tested on anything other than JBoss? Glassfish was one of the first app servers to include JSR-299 and, for myself and others, provides a better developer experience. However, from the outside, Glassfish appears to be completely ignored. Is Seam 3 really an extension/library on top of CDI or is it just for JBoss servers? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMSECURITY-37?page=com.atlassian.jira.p... ] Aaron Siri commented on SEAMSECURITY-37: ---------------------------------------- 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. If I understand you correctly Seam Security has to change how it injects Messages. Is that correct? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMSECURITY-37?page=com.atlassian.jira.p... ] Shane Bryzak commented on SEAMSECURITY-37: ------------------------------------------ I've modified the SecurityEventMessages bean to inject the Messages bean in the event observers -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMSECURITY-37?page=com.atlassian.jira.p... ] 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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMSECURITY-37?page=com.atlassian.jira.p... ] Dan Allen commented on SEAMSECURITY-37: --------------------------------------- Yes, I've already verified that Weld 1.1.1 fixes the issue. There is no need to change GlassFish. Check out the "UPDATE" section at the end of the blog for details. Brian's blog documents how to upgrade Weld in GlassFish 3.1. It's very straightforward...should only take a couple of minutes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMSECURITY-37?page=com.atlassian.jira.p... ] Dan Allen edited comment on SEAMSECURITY-37 at 3/20/11 1:45 AM: ---------------------------------------------------------------- It will even be simpler when WELD-871 is resolved, so you can just grab the snapshot from the Maven repository. was (Author: dan.j.allen): It would even be simpler when WELD-871 is resolved, so you can just grab the snapshot from the Maven repository. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMSECURITY-37?page=com.atlassian.jira.p... ] Aaron Siri commented on SEAMSECURITY-37: ---------------------------------------- Thanks for the quick updates guys. I updated my security dependency to CR2 which fixes the Messages issue but I'm still seeing the NPE in the same spot. I also still need to manually add dependencies for joda-time and slf4j to everything too. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira