May 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMINTL-14) EL resolving in messages

by Nicklas Karlsson (JIRA)

EL resolving in messages ------------------------ Key: SEAMINTL-14 URL: https://jira.jboss.org/browse/SEAMINTL-14 Project: Seam i18n Issue Type: Feature Request Reporter: Nicklas Karlsson It would be nice to have EL-resolves in messages so you could have a message mapping to "Order #{order.id}" resolved for a view. If we want to get really cute we could even provide nested EL expression, resolver from inside out. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMINTL-6) Decouple BundleKey from log method

by Ken Finnigan (JIRA)

Decouple BundleKey from log method ---------------------------------- Key: SEAMINTL-6 URL: https://jira.jboss.org/browse/SEAMINTL-6 Project: Seam i18n Issue Type: Feature Request Components: Messages Affects Versions: 3.0.0.Alpha1 Reporter: Ken Finnigan Fix For: 3.0.0.Alpha2 Specifying the BundleKey of the property being retrieved needs to be independant of the call to a specific log method -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
5
0 / 0

[JBoss JIRA] Created: (SEAMINTL-4) Named parameters in localized messages

by Aslak Knutsen (JIRA)

Named parameters in localized messages -------------------------------------- Key: SEAMINTL-4 URL: https://jira.jboss.org/browse/SEAMINTL-4 Project: Seam i18n Issue Type: Feature Request Components: Messages Reporter: Aslak Knutsen Priority: Minor When coming back to localized message files after being away for a while, it's always a problem to remember what object/value parameter {2} is suppose to be. At this point you have to find the specific message location in the source code and read through the code to figure out what's actually being passed in. It's also hard to send the file over to someone for translation, because they most likely also need an explanation of what {2} is. It would be nice to be able to used named parameters, but with Java(< 7) that is a bit of a pain to code. Would it be possible with some middle ground; e.g. A name/alias in the message file that is ignored by the parser, but there just for documentation. (Maybe even function as a named parameter when Java 7 comes out?) "Welcome {0:firstName} {1:lastName}!" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
8
0 / 0

[JBoss JIRA] Created: (SEAMINTL-22) @MessageParam to assign a method parameter to name contained within EL expression

by Ken Finnigan (JIRA)

@MessageParam to assign a method parameter to name contained within EL expression --------------------------------------------------------------------------------- Key: SEAMINTL-22 URL: https://issues.jboss.org/browse/SEAMINTL-22 Project: Seam International Issue Type: Feature Request Components: Messages Reporter: Ken Finnigan Fix For: 3.0.0.Beta2 Would enable you to do something like the following: @MessageBundle public interface BookingStatusMessages { @Message("You are booked to stay at the #{hotel.name} on {1,date}") String bookingConfirmed(@MessageParam("hotel")Hotel hotel, Date date); } Could potentially support @MessageParam without a value and pick up the parameter name -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (SEAMINTL-21) Provide @Key to define the name of a localized message property key

by Ken Finnigan (JIRA)

Provide @Key to define the name of a localized message property key ------------------------------------------------------------------- Key: SEAMINTL-21 URL: https://issues.jboss.org/browse/SEAMINTL-21 Project: Seam International Issue Type: Feature Request Components: Locales, Messages Reporter: Ken Finnigan Fix For: 3.0.0.Beta2 Support adding @Key onto a method that defines a message content to override the name of the property key for retrieval. Default is the method name, but supporting @Key would enable a developer to connect the annotation for the message content to an existing property file name. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-64) Provided the capability to retrieve the actual entity object when a user is created.

by Emanuel Zimmermann (JIRA)

Provided the capability to retrieve the actual entity object when a user is created. ------------------------------------------------------------------------------------ Key: SEAMSECURITY-64 URL: https://issues.jboss.org/browse/SEAMSECURITY-64 Project: Seam Security Issue Type: Feature Request Affects Versions: 3.0.0.Final Reporter: Emanuel Zimmermann Seam is now using PicketLink API to handle security, in Seam 2 an event was raised to retrieve the actual user entity, yet Seam 3 is lacking this feature. There is not practical way of retrieving a custom extended User. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-65) Criteria queries executed by JPAIdentityStore are not setup properly

by Zakaria Yussuf (JIRA)

Criteria queries executed by JPAIdentityStore are not setup properly -------------------------------------------------------------------- Key: SEAMSECURITY-65 URL: https://issues.jboss.org/browse/SEAMSECURITY-65 Project: Seam Security Issue Type: Bug Affects Versions: 3.0.0.Final, 3.1.0.Final Reporter: Zakaria Yussuf CriteriQuery.select() is not called on the criteria queries used in JPAIdentityStore. Some JPA implementations cannot execute the resulting queries. ObjectDB throws the following exception: java.lang.RuntimeException: com.objectdb.o._PersistenceException: Unexpected query token 'FROM' (SELECT is expected) at org.jboss.seam.security.IdentityImpl.authenticate(IdentityImpl.java:329) at org.jboss.seam.security.IdentityImpl.login(IdentityImpl.java:229) at org.jboss.seam.security.org$jboss$weld$bean-WEB-INF$lib$seam-security-3$0$0$Final-ManagedBean-class_org$jboss$seam$security$IdentityImpl_$$_WeldClientProxy.login(org$jboss$weld$bean-WEB-INF$lib$seam-security-3$0$0$Final-ManagedBean-class_org$jboss$seam$security$IdentityImpl_$$_WeldClientProxy.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:597) at com.sun.el.parser.AstValue.invoke(AstValue.java:234) at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:297) at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105) at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88) at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102) at javax.faces.component.UICommand.broadcast(UICommand.java:315) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259) at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:409) at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1534) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:281) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:655) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:595) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:98) at com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:91) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:162) at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:326) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:227) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:170) at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:822) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1013) at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:225) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59) at com.sun.grizzly.ContextTask.run(ContextTask.java:71) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513) at java.lang.Thread.run(Thread.java:662) Caused by: com.objectdb.o._PersistenceException: Unexpected query token 'FROM' (SELECT is expected) at com.objectdb.o._PersistenceException.b(_PersistenceException.java:45) at com.objectdb.o.JPE.g(JPE.java:140) at com.objectdb.o.ERR.f(ERR.java:59) at com.objectdb.o.OBC.onObjectDBError(OBC.java:1444) at com.objectdb.jpa.JpaQuery.getSingleResult(JpaQuery.java:617) at org.jboss.seam.security.management.picketlink.JpaIdentityStore.lookupIdentity(JpaIdentityStore.java:1233) at org.jboss.seam.security.management.picketlink.JpaIdentityStore.validateCredential(JpaIdentityStore.java:1899) at org.picketlink.idm.impl.repository.WrapperIdentityStoreRepository.validateCredential(WrapperIdentityStoreRepository.java:303) at org.picketlink.idm.impl.api.session.managers.AttributesManagerImpl.validateCredentials(AttributesManagerImpl.java:607) at com.asalsolutions.security.auth.TijAuthenticator.authenticate(TijAuthenticator.java:82) at org.jboss.seam.security.IdentityImpl.authenticate(IdentityImpl.java:305) ... 45 more Caused by: com.objectdb.o.UserException: Unexpected query token 'FROM' (SELECT is expected) at com.objectdb.o.MSG.d(MSG.java:61) at com.objectdb.o.TKN.J(TKN.java:755) at com.objectdb.o.TKI.u(TKI.java:256) at com.objectdb.o.TKI.n(TKI.java:133) at com.objectdb.o.QPR.s(QPR.java:276) at com.objectdb.o.QPR.o(QPR.java:145) at com.objectdb.o.QRC.<init>(QRC.java:119) at com.objectdb.o.QRM.UR(QRM.java:242) at com.objectdb.o.MST.UR(MST.java:878) at com.objectdb.o.WRA.UR(WRA.java:286) at com.objectdb.o.WSM.UR(WSM.java:113) at com.objectdb.o.QRR.g(QRR.java:220) at com.objectdb.o.QRR.b(QRR.java:143) at com.objectdb.jpa.JpaQuery.getSingleResult(JpaQuery.java:610) ... 51 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-62) Using identity management to add user in group set name to null in IdentityObjectRelationship

by wiktorowski maximilien (JIRA)

Using identity management to add user in group set name to null in IdentityObjectRelationship --------------------------------------------------------------------------------------------- Key: SEAMSECURITY-62 URL: https://issues.jboss.org/browse/SEAMSECURITY-62 Project: Seam Security Issue Type: Bug Affects Versions: 3.0.0.Final Reporter: wiktorowski maximilien Hi, I'm using seam-security with JPAIdentityStore. When i'm using RelationshipManager to add a user in a group (as said in reference guide) i can not login anymore with this user. Indeed when i call associateUser the entry created in identityobjectrelationship table has a null name and when i call identity.login for this user i got : 10:03:27,292 ERROR [org.jboss.seam.security.IdentityImpl] Login failed: java.lang.RuntimeException: java.lang.IllegalArgumentException: name cannot be null at org.jboss.seam.security.IdentityImpl.authenticate(IdentityImpl.java:329) [:3.0.0.Final] at org.jboss.seam.security.IdentityImpl.login(IdentityImpl.java:229) [:3.0.0.Final] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_20] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_20] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_20] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_20] at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [:6.0.0.Final] at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [:6.0.0.Final] at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [:6.0.0.Final] at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [:6.0.0.Final] at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [:6.0.0.Final] at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [:6.0.0.Final] at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:102) [:2.0.3-] at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:84) [:2.0.3-] at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:98) [:2.0.3-] at javax.faces.component.UICommand.broadcast(UICommand.java:311) [:2.0.3-] at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:781) [:2.0.3-] at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1246) [:2.0.3-] at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:77) [:2.0.3-] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:97) [:2.0.3-] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:114) [:2.0.3-] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:308) [:2.0.3-] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at com.ocpsoft.pretty.PrettyFilter.doFilter(PrettyFilter.java:118) [:] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.0.0.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:6.0.0.Final] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.0.Final] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.0.0.Final] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.0.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:6.0.0.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.0.0.Final] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.0.0.Final] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.0.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.0.0.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.0.0.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.0.0.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.0.0.Final] at java.lang.Thread.run(Thread.java:619) [:1.6.0_20] Caused by: java.lang.IllegalArgumentException: name cannot be null at org.picketlink.idm.impl.api.model.SimpleRoleType.<init>(SimpleRoleType.java:41) [:1.5.0.Alpha02] at org.picketlink.idm.impl.api.session.managers.RoleManagerImpl.findUserRoleTypes(RoleManagerImpl.java:580) [:1.5.0.Alpha02] at org.picketlink.idm.impl.api.session.managers.RoleManagerImpl.findUserRoleTypes(RoleManagerImpl.java:552) [:1.5.0.Alpha02] at org.jboss.seam.security.management.IdmAuthenticator.authenticate(IdmAuthenticator.java:49) [:3.0.0.Final] at org.jboss.seam.security.IdentityImpl.authenticate(IdentityImpl.java:305) [:3.0.0.Final] ... 46 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
12
0 / 0

[JBoss JIRA] Created: (SEAMJCR-7) SeamCatch integration for JCR exceptions

by John Ament (JIRA)

SeamCatch integration for JCR exceptions ---------------------------------------- Key: SEAMJCR-7 URL: https://issues.jboss.org/browse/SEAMJCR-7 Project: Seam JCR Issue Type: Task Reporter: John Ament We should provide integration with SeamCatch for Exceptions thrown by JCR. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (SEAMJCR-13) Seam Managed JCR Sessions

by John Ament (JIRA)

Seam Managed JCR Sessions ------------------------- Key: SEAMJCR-13 URL: https://issues.jboss.org/browse/SEAMJCR-13 Project: Seam JCR Issue Type: Feature Request Components: CDI & Injection API Reporter: John Ament Assignee: John Ament Fix For: 3.0.0.Beta1 Similar to Seam Persistence's Seam Managed PersistenceContext & Hibernate Session, we should support JCR Sessions in the same manner. This should tie the injection of an object to be bound to a request level, or similar context, and tying in the session.save & logout methods to happen at the end of the request. In the case of events, where they are triggered after logging out, to avoid a long loop or bad setup, developers will need to use dependent sessions if they want to modify node state as a part of an event. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2011