July 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2654) Support for OpenSSO

by Shane Bryzak (JIRA)

Support for OpenSSO ------------------- Key: JBSEAM-2654 URL: http://jira.jboss.com/jira/browse/JBSEAM-2654 Project: JBoss Seam Issue Type: Feature Request Reporter: Shane Bryzak Assigned To: Shane Bryzak Fix For: 2.1.0.GA It would be nice to support OpenSSO, as well as JBoss SSO. https://opensso.dev.java.net/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

7
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-740) URL authorization

by Gavin King (JIRA)

URL authorization ----------------- Key: JBSEAM-740 URL: http://jira.jboss.com/jira/browse/JBSEAM-740 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Gavin King Assigned To: Shane Bryzak Priority: Minor Fix For: 1.2.0.BETA1 Probably, for completeness, we need the SecurityFIlter after all, to allow GET/PUT/POST/DELETE authorization for URLs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-744) Support X509 certificates

by Gavin King (JIRA)

Support X509 certificates ------------------------- Key: JBSEAM-744 URL: http://jira.jboss.com/jira/browse/JBSEAM-744 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Gavin King Assigned To: Shane Bryzak Priority: Minor Fix For: 1.2.0.BETA1 I have no idea what these things are, but apparently people want to get them. Supposedly, they are nothing to do with certificates you get when you win something like a spelling competition in primary school. 'Cos if they were, we could have used Norman's PDF stuff. So anyway we can just steal code from Acegi. Then I can tell people "we've got a certificate for X509" in talks, and they will think I know what it is. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3103) Need ability to programmatically add Security Permissions

by Samuel Mendenhall (JIRA)

Need ability to programmatically add Security Permissions --------------------------------------------------------- Key: JBSEAM-3103 URL: http://jira.jboss.com/jira/browse/JBSEAM-3103 Project: Seam Issue Type: Feature Request Components: Security Reporter: Samuel Mendenhall Priority: Minor "One of the main advantages I can think of having a programmatic approach of adding permissions is that 'drl' file may no longer be required. The rules will be created according to what is described in standard RBAC tables (user-roles-permissions with many-to-many relationships). Any role/permission added to RBAC tables will not have to be re-defined inside a 'drl' file." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1543) Create a web service test page for seam-gen

by Shane Bryzak (JIRA)

Create a web service test page for seam-gen ------------------------------------------- Key: JBSEAM-1543 URL: http://jira.jboss.com/jira/browse/JBSEAM-1543 Project: JBoss Seam Issue Type: Feature Request Components: WS Reporter: Shane Bryzak Assigned To: Shane Bryzak Priority: Minor Fix For: 1.3.0.GA It would be extremely cool to be able to use the web service test page from the seambay example in all apps, not just in this one example. I need to investigate how we can include this in a seam-gen application or easily be able to add it to any seam app, ala the debug page. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3113) Seambay example gets into a looping condition when entering bids

by Jay Balunas (JIRA)

Seambay example gets into a looping condition when entering bids ---------------------------------------------------------------- Key: JBSEAM-3113 URL: http://jira.jboss.com/jira/browse/JBSEAM-3113 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.3.CR1 Reporter: Jay Balunas Priority: Minor >From JBSEAM-2956 I can now place bids on the camera with out an exception, but it does not seem to take. When I confirm the bid it keeps telling me to set my maximum bid. Even when valid it does not take it.. You seam to end up in a loop of some kind. A similar thing happens on the other auctions - when you enter a bid it is taken, but if you check the value of the bid it had not changed from the original amount. If you then try to bid again you end up in the same loop. Also with all auctions if you don't enter a value or one that is not valid (emptry, characters, etc..) get seam debug page with this error: 13:58:58,868 ERROR [ExceptionFilter] exception root cause javax.faces.FacesException: #{bidAction.updateBid}: java.lang.NumberFormatException: empty String at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:107) at javax.faces.component.UICommand.broadcast(UICommand.java:383) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:447) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752) at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:164) at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:141) at org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:90) at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:406) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) Caused by: javax.faces.el.EvaluationException: java.lang.NumberFormatException: empty String at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:91) at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) ... 45 more Caused by: java.lang.NumberFormatException: empty String at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:994) at java.lang.Double.parseDouble(Double.java:482) at org.jboss.seam.example.seambay.BidAction.updateBid(BidAction.java:58) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:46) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.persistence.ManagedEntityIdentityInterceptor.aroundInvoke(ManagedEntityIdentityInterceptor.java:48) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102) at org.jboss.seam.example.seambay.BidAction_$$_javassist_10.updateBid(BidAction_$$_javassist_10.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:329) at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:342) at org.jboss.el.parser.AstPropertySuffix.invoke(AstPropertySuffix.java:58) at org.jboss.el.parser.AstValue.invoke(AstValue.java:96) at org.jboss.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68) at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:77) ... 46 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3400) Begin natural conversation programatically

by Vladimir Kovalyuk (JIRA)

Begin natural conversation programatically ------------------------------------------ Key: JBSEAM-3400 URL: https://jira.jboss.org/jira/browse/JBSEAM-3400 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.0.BETA1 Reporter: Vladimir Kovalyuk -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3614) Document running seambay example on Tomcat

by Shane Bryzak (JIRA)

Document running seambay example on Tomcat ------------------------------------------ Key: JBSEAM-3614 URL: https://jira.jboss.org/jira/browse/JBSEAM-3614 Project: Seam Issue Type: Task Reporter: Shane Bryzak Fix For: 2.1.1.CR1 We need to document the steps for running seamBay under Tomcat, including whatever is required to install JBossWS. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3873) Memory leak using EJB transactions and jBpm contexts

by Torsten Fink (JIRA)

Memory leak using EJB transactions and jBpm contexts ---------------------------------------------------- Key: JBSEAM-3873 URL: https://jira.jboss.org/jira/browse/JBSEAM-3873 Project: Seam Issue Type: Bug Components: BPM, Core, EJB3 Affects Versions: 2.1.1.GA Environment: JBoss 4.2.x, Mac OSX and Linux environments, Java 1.5 Reporter: Torsten Fink Attachments: MemoryLeakEventKontext.tgz Our application had to survive a night with full load. On the next morning the heap was full of JbpmContext's. After looking at the source code of Seam and at the debug messages we came up with this hypothesis: * The SFSB EjbSynchronizations is placed in the event context, the Seam-JbpmContext-Component also lives in the event context. * Using EJB transactions, EjbSynchronizations is responsible for cleaning up the JbpmContext after the end of the transaction. * Unfortunately the event context ends BEFORE EjbSynchronizations has the chance to clean up the JbpmContext. Using BMT the transaction ends before the event context ends. Thus, the JbpmContext is cleaned up. We switch all our MDBs, EJB-timers, and Web-services from CMT to BMT and (after fixing some other leaks, e.g. a class loader issue in jBpm), we survived the night. I wrote a small test application that shows the memory leak and I will try to attach it to this issue. It is a Maven application that consists of - a Web-GUI to start the test and displays the results (http://localhost:8080/leak/) - a SFSB that sends 10 messages each to two queues (the standard queues A and B), waits a little bit, and does a gc - two MDBs, one with CMT, one with BMT, which uses Seam injection to access a jBpm-Context - an application scoped POJO that saves the contexts in a Set using a weak reference After executing the tests and the GC, the surviving references are displayed. You can see that the CMT references are not gs'ed whereas the BMT references are cleaned up. You can execute the test several times. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4196) Infinite Loop bug in JBPM integration

by Elias Ross (JIRA)

Infinite Loop bug in JBPM integration ------------------------------------- Key: JBSEAM-4196 URL: https://jira.jboss.org/jira/browse/JBSEAM-4196 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Reporter: Elias Ross See this forum post: http://seamframework.org/Community/InfiniteLoopBugInJBPMIntegration Stack trace (repeating): at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:154) at org.jboss.seam.Component.callComponentMethod(Component.java:2211) at org.jboss.seam.Component.unwrap(Component.java:2237) at org.jboss.seam.Component.getInstance(Component.java:2004) at org.jboss.seam.Component.getInstance(Component.java:1967) at org.jboss.seam.Component.getInstance(Component.java:1961) at org.jboss.seam.Component.getInstance(Component.java:1934) at org.jboss.seam.Component.getInstance(Component.java:1929) at org.jboss.seam.bpm.ProcessInstance.instance(ProcessInstance.java:65) at org.jboss.seam.contexts.BusinessProcessContext.getProcessInstance(BusinessProcessContext.java:229) at org.jboss.seam.contexts.BusinessProcessContext.getContextInstance(BusinessProcessContext.java:217) at org.jboss.seam.contexts.BusinessProcessContext.get(BusinessProcessContext.java:68) at org.jboss.seam.contexts.Contexts.lookupInStatefulContexts(Contexts.java:209) at org.jboss.seam.Component.getInstance(Component.java:1949) at org.jboss.seam.Component.getInstance(Component.java:1944) at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:55) at org.jboss.seam.Namespace.getComponentInstance(Namespace.java:50) at org.jboss.seam.el.SeamELResolver.resolveBase(SeamELResolver.java:166) at org.jboss.seam.el.SeamELResolver.getValue(SeamELResolver.java:53) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at org.jboss.el.parser.AstIdentifier.getValue(AstIdentifier.java:44) at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at org.jboss.seam.core.Expressions$1.getValue(Expressions.java:112) at org.jboss.seam.transaction.EntityTransaction.initEntityManager(EntityTransaction.java:67) at org.jboss.seam.transaction.EntityTransaction.begin(EntityTransaction.java:79) at org.jboss.seam.util.Work.workInTransaction(Work.java:42) at org.jboss.seam.bpm.ProcessInstance.getProcessInstance(ProcessInstance.java:39) at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144) etc. There is code to reproduce the issue there. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2009