June 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMSECURITY-76) seam security external ScopeProducers doesn't work anywhere except AS6

by Marek Schmidt (JIRA)

seam security external ScopeProducers doesn't work anywhere except AS6 ---------------------------------------------------------------------- Key: SEAMSECURITY-76 URL: https://issues.jboss.org/browse/SEAMSECURITY-76 Project: Seam Security Issue Type: Bug Affects Versions: 3.0.0.Final Reporter: Marek Schmidt The design of the Security External module depends on undefined behaviour of alternatives. It defines alternatives (*ApplicationScopeProducer and *VirtualApplicationScopeProducer) in the module and expects the application to set the alternatives in its beans.xml, which isn't supported by CDI spec (see CDI-18) and doesn't seem to work anywhere except JBoss AS 6. We should probably just remove the Producers and make the beans @ApplicationScoped directly. Users interested in changing the scope of those beans could still use Seam Config for that. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-28) Create an example demonstrating EL in EJB-QL/HQL

by Ondrej Skutka (JIRA)

Create an example demonstrating EL in EJB-QL/HQL ------------------------------------------------- Key: SEAMPERSIST-28 URL: https://issues.jboss.org/browse/SEAMPERSIST-28 Project: Seam Persistence Issue Type: Task Reporter: Ondrej Skutka Or you can modify an existing example. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-38) Remoting broken on AS7

by Jozef Hartinger (JIRA)

Remoting broken on AS7 ---------------------- Key: SEAMREMOTING-38 URL: https://issues.jboss.org/browse/SEAMREMOTING-38 Project: Seam Remoting Issue Type: Bug Environment: Seam Remoting 3.0.1-SNAPSHOT (2011-06-09) JBoss AS 7.0.0-Beta4-SNAPSHOT (2011-06-07) Reporter: Jozef Hartinger Invoking any remote action I am getting the following exception. This can be reproduced on both remoting-helloworld and remoting-model examples. Note that you need to change the datasource definition to java:/H2DS for the remoting-model example to deploy to AS. 15:06:34,372 ERROR [org.jboss.seam.remoting.Remoting] (http-localhost-127.0.0.1-8080-3) Error: org.jboss.weld.exceptions.UnsatisfiedResolutionException: WELD-001308 Unable to resolve any beans for Types: [class org.jboss.seam.remoting.ExecutionHandler]; Bindings: [@javax.enterprise.inject.Default()] at org.jboss.weld.manager.BeanManagerImpl.getBean(BeanManagerImpl.java:809) [weld-core-1.1.1.Final.jar:2011-04-06 13:26] at org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:108) [weld-core-1.1.1.Final.jar:2011-04-06 13:26] at org.jboss.seam.remoting.Remoting.getExecutionHandler(Remoting.java:221) [seam-remoting-3.0.1-SNAPSHOT.jar:] at org.jboss.seam.remoting.Remoting.service(Remoting.java:251) [seam-remoting-3.0.1-SNAPSHOT.jar:] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [weld-core-1.1.1.Final.jar:2011-04-06 13:26] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:658) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [jbossweb-7.0.0.CR2.jar:7.0.0.Beta4-SNAPSHOT] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
8
0 / 0

[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

14 years, 7 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

14 years, 7 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

14 years, 7 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

14 years, 7 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

14 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-56) org.jboss.seam.security.externaltest.integration.client.IntegrationTest.openIdLoginWithClaimedIdentifierAndAttributeExchangeTest fails

by Jozef Hartinger (JIRA)

org.jboss.seam.security.externaltest.integration.client.IntegrationTest.openIdLoginWithClaimedIdentifierAndAttributeExchangeTest fails --------------------------------------------------------------------------------------------------------------------------------------- Key: SEAMPERSIST-56 URL: https://issues.jboss.org/browse/SEAMPERSIST-56 Project: Seam Persistence Issue Type: Bug Reporter: Jozef Hartinger Fix For: Future https://hudson.qa.jboss.com/hudson/view/Seam%203/job/Seam-3.X-security-CI... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-70) Calling RoleManager.removeRole(Roletype rt, User u, Group g) throws an NPE

by Charles Louppe (JIRA)

Calling RoleManager.removeRole(Roletype rt,User u, Group g) throws an NPE ------------------------------------------------------------------------- Key: SEAMSECURITY-70 URL: https://issues.jboss.org/browse/SEAMSECURITY-70 Project: Seam Security Issue Type: Bug Reporter: Charles Louppe Hi, I tried to use the function removeRole(Roletype rt,User u, Group g) of the class RoleManagerImpl which throws me an NullPointerException. I have fixed the bug, which was in the class JPAIdentityStore in the method removeRelationship : {code:java} public void removeRelationship(IdentityStoreInvocationContext ctx, IdentityObject fromIdentity, IdentityObject toIdentity, IdentityObjectRelationshipType relationshipType, String relationshipName) throws IdentityException { Property<?> fromProperty = modelProperties.get(PROPERTY_RELATIONSHIP_FROM); Property<?> toProperty = modelProperties.get(PROPERTY_RELATIONSHIP_TO); Property<?> relationshipTypeProp = modelProperties.get(PROPERTY_RELATIONSHIP_TYPE); EntityManager em = getEntityManager(ctx); CriteriaBuilder builder = em.getCriteriaBuilder(); CriteriaQuery<?> criteria = builder.createQuery(identityClass); Root<?> root = criteria.from(identityClass); List<Predicate> predicates = new ArrayList<Predicate>(); predicates.add(builder.equal(root.get(fromProperty.getName()), lookupIdentity(fromIdentity, em))); predicates.add(builder.equal(root.get(toProperty.getName()), lookupIdentity(toIdentity, em))); predicates.add(builder.equal(root.get(relationshipTypeProp.getName()), lookupRelationshipType(relationshipType, em))); criteria.where(predicates.toArray(new Predicate[predicates.size()])); Object relationship = em.createQuery(criteria).getSingleResult(); em.remove(relationship); } {code} The bug is due to those following lines : CriteriaQuery<?> criteria = builder.createQuery(identityClass); Root<?> root = criteria.from(identityClass); It should be instead : CriteriaQuery<?> criteria = builder.createQuery(relationshipClass); Root<?> root = criteria.from(relationshipClass); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues June 2011