May 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMFACES-159) Introduce multi-container test capabilities using Arquillian and JSFUnit

by Brian Leathem (JIRA)

Introduce multi-container test capabilities using Arquillian and JSFUnit ------------------------------------------------------------------------ Key: SEAMFACES-159 URL: https://issues.jboss.org/browse/SEAMFACES-159 Project: Seam Faces Issue Type: Feature Request Reporter: Brian Leathem Fix For: 3.0.2 Multi-container tests using Arquillian and JSFUnit are needed to verify the robustness of the Seam Faces Features. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMWICKET-18) Make Wicket Conversational control optional

by Dan Allen (JIRA)

Make Wicket Conversational control optional ------------------------------------------- Key: SEAMWICKET-18 URL: https://issues.jboss.org/browse/SEAMWICKET-18 Project: Seam Wicket Issue Type: Feature Request Affects Versions: 3.0.0.Beta1 Reporter: Clint Popetz Assignee: Clint Popetz Fix For: 3.0.0.CR1 >From Pete's suggestions: - define an api which allows wicket to control conversations - use service providers (META-INF/services) to discover impls - provide a built in impl which can use Weld, if it (WeldManager) is on the classpath - degrade gracefully if no impl is available -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (SEAM-87) Field marked @IdentityProperty must be public even if it has a public getter

by Zakaria Yussuf (JIRA)

Field marked @IdentityProperty must be public even if it has a public getter ---------------------------------------------------------------------------- Key: SEAM-87 URL: https://issues.jboss.org/browse/SEAM-87 Project: Seam 3 Distribution Issue Type: Bug Affects Versions: 3.0.0.Final Reporter: Zakaria Yussuf Background: IdentityObjectCredential is one of the entity classes setup to be used by JPAIdentityStore. It has a field 'value' that is private. The annotation @IdentityProperty(PropertyType.VALUE) is placed on the field itself (not on the getter). During the authentication process a call is made to org.jboss.seam.solder.reflection.Reflections.getFieldValue() which attempts to access IdentityObjectCredential.value directly, resulting in the following exception: java.lang.RuntimeException: java.lang.RuntimeException: Exception reading [value] field from object [com.asalsolutions.security.model.IdentityObjectCredential@74c13549]. at org.jboss.seam.security.IdentityImpl.authenticate(IdentityImpl.java:304) at org.jboss.seam.security.IdentityImpl.login(IdentityImpl.java:223) at org.jboss.seam.security.org$jboss$weld$bean-WEB-INF$lib$seam-security-impl-ManagedBean-class_org$jboss$seam$security$IdentityImpl_$$_WeldClientProxy.login(org$jboss$weld$bean-WEB-INF$lib$seam-security-impl-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: java.lang.RuntimeException: Exception reading [value] field from object [com.asalsolutions.security.model.IdentityObjectCredential@74c13549]. at org.jboss.seam.solder.reflection.Reflections.getFieldValue(Reflections.java:584) at org.jboss.seam.solder.properties.FieldPropertyImpl.getValue(FieldPropertyImpl.java:66) at org.jboss.seam.security.management.picketlink.JpaIdentityStore.validateCredential(JpaIdentityStore.java:1634) 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:86) at org.jboss.seam.security.IdentityImpl.authenticate(IdentityImpl.java:284) ... 45 more Caused by: java.lang.IllegalAccessException: Class org.jboss.seam.solder.reflection.Reflections can not access a member of class com.asalsolutions.security.model.IdentityObjectCredential with modifiers "private" at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65) at java.lang.reflect.Field.doSecurityCheck(Field.java:960) at java.lang.reflect.Field.getFieldAccessor(Field.java:896) at java.lang.reflect.Field.get(Field.java:358) at org.jboss.seam.solder.reflection.Reflections.getFieldValue(Reflections.java:582) ... 51 more This issue looks a lot like one fixed for Seam 2 (https://issues.jboss.org/browse/JBSEAM-3556) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-30) Create example to demonstrate rule-based permissions

by Shane Bryzak (JIRA)

Create example to demonstrate rule-based permissions ---------------------------------------------------- Key: SEAMSECURITY-30 URL: https://issues.jboss.org/browse/SEAMSECURITY-30 Project: Seam Security Issue Type: Task Reporter: Shane Bryzak Assignee: Shane Bryzak Fix For: 3.0.0.Beta2 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (SEAMXML-34) Create an example(s) demonstrating config features

by Ondrej Skutka (JIRA)

Create an example(s) demonstrating config features -------------------------------------------------- Key: SEAMXML-34 URL: https://issues.jboss.org/browse/SEAMXML-34 Project: Seam Config Issue Type: Feature Request Reporter: Ondrej Skutka Fix For: 3.0.0.Final Create an example(s) demonstrating config features or modify existing one(s): - Inline bean declarations - Configuring methods - Configuring bean constructor - Overriding type of injection point -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

6
9
0 / 0

[JBoss JIRA] Created: (SEAMSERVLET-28) Integrate Catch with *EventBridge* classes

by Jason Porter (JIRA)

Integrate Catch with *EventBridge* classes ------------------------------------------ Key: SEAMSERVLET-28 URL: https://issues.jboss.org/browse/SEAMSERVLET-28 Project: Seam Servlet Issue Type: Enhancement Components: Catch Integration Affects Versions: 3.0.0.Beta1 Reporter: Jason Porter None of the EventBridge classes catch exceptions to pass to Seam Catch, thus the following code does not invoke any exception handlers: {code} public void initial(@Observes @Path("NullPointer") @Initialized final HttpServletRequestContext ctx) { throw new NullPointerException(); } {code} I would expect the NPE to be passed to Catch for exception handling. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

5
9
0 / 0

[JBoss JIRA] Created: (SOLDER-98) Documentation issues

by Martin Gencur (JIRA)

Documentation issues -------------------- Key: SOLDER-98 URL: https://issues.jboss.org/browse/SOLDER-98 Project: Seam Solder Issue Type: Bug Components: Documentation Affects Versions: 3.0.0.Final Reporter: Martin Gencur Priority: Minor Fix For: Future 1) Introduction - question marks links ("???") pointing nowhere [only in Seam 3 distribution bundle] 2) Chapter 6. Getting Started -> Tip -> "Maven user-defined property" link pointing nowhere 3) 7.1.2. @Requires -> "Note" contains "The ProcessAnnotatedType container lifecycle event will be called for vetoed types." where the word "vetoed" should be "required", in fact 4) TYPO -> 7.5. @FullyQualified bean names -> "This behavior aligns is with the needs of"... (the "is" word shouldn't be there IMHO) 5) TYPO -> 11.1. JBoss Logging: The foundation -> "JBoss Logging has is parallel support" (the "is" should be "its" IMHO) 6) TYPO -> 11.3. Typed loggers -> "If injecting a typed logger seems to "enterprisy" to you" ("to" should be "too") 7) TYPO -> 1.6.2. Including the implementation classes in Arquillian tests -> "Otherwise, you may can an exception like:" 8) section "Chapter 17. Default Beans" has probably wrong formatting of the last code snippet of this subchapter (the one containing @DefaultBean(Cache.class)) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

5
7
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-23) Support global exception handler

by Jozef Hartinger (JIRA)

Support global exception handler -------------------------------- Key: SEAMREMOTING-23 URL: https://issues.jboss.org/browse/SEAMREMOTING-23 Project: Seam Remoting Issue Type: Feature Request Affects Versions: 3.0.0.Beta2 Reporter: Jozef Hartinger Fix For: 3.0.0.CR1 Besides allowing a specific exception handler to be associated with every method invocation, it would be nice to provide a way of registering a global exception handler i.e. Seam.globalExceptionHandler = function() { ... } This would most often be used to inform an end user that an unexpected exception occured. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-5) Add messages support for Remoting

by Shane Bryzak (JIRA)

Add messages support for Remoting --------------------------------- Key: SEAMREMOTING-5 URL: https://jira.jboss.org/browse/SEAMREMOTING-5 Project: Seam Remoting Issue Type: Feature Request Reporter: Shane Bryzak We need to add support for adding status messages. Any messages generated during a request will need to go into the context of the response packet, where they can then be accessed by the client. -- 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, 2 months

5
9
0 / 0

[JBoss JIRA] Created: (SEAM-61) Update the PrettyFaces version to 3.2.0

by Brian Leathem (JIRA)

Update the PrettyFaces version to 3.2.0 --------------------------------------- Key: SEAM-61 URL: https://issues.jboss.org/browse/SEAM-61 Project: Seam 3 Distribution Issue Type: Library Upgrade Components: Common Dependencies Reporter: Brian Leathem Fix For: 3.0.0.Final SEAMFACES-101 requires the pretty faces version to be bumped to version 3.2.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

5
4
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