February 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMSECURITY-11) Use Infinispan to cache user role and group memberships

by Shane Bryzak (JIRA)

Use Infinispan to cache user role and group memberships ------------------------------------------------------- Key: SEAMSECURITY-11 URL: https://jira.jboss.org/browse/SEAMSECURITY-11 Project: Seam Security Issue Type: Feature Request Reporter: Shane Bryzak Assignee: Shane Bryzak Fix For: 3.0.0.Beta1 -- 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, 3 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4045) Add first class support for groups

by Shane Bryzak (JIRA)

Add first class support for groups ---------------------------------- Key: JBSEAM-4045 URL: https://jira.jboss.org/jira/browse/JBSEAM-4045 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.1.GA Reporter: Shane Bryzak Assignee: Shane Bryzak We should add first class support for user groups - these are a separate from roles, and allow applications to group users by department, location, etc. -- 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

13 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (SEAMJMS-6) Routes should be produced instead of returned from an annotated method

by Jordan Ganoff (JIRA)

Routes should be produced instead of returned from an annotated method ---------------------------------------------------------------------- Key: SEAMJMS-6 URL: https://jira.jboss.org/browse/SEAMJMS-6 Project: Seam JMS Issue Type: Feature Request Components: Event Bridging Reporter: Jordan Ganoff Change EventRouting to be produced instead of allowing any method to be annotated. -- 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, 3 months

1
6
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-43) Manifest.mf files in jars generated from the module contain unreachable Implementation-URL

by Martin Gencur (JIRA)

Manifest.mf files in jars generated from the module contain unreachable Implementation-URL ------------------------------------------------------------------------------------------- Key: SEAMCATCH-43 URL: https://issues.jboss.org/browse/SEAMCATCH-43 Project: Seam Catch Issue Type: Bug Components: Build Infrastructure Affects Versions: 3.0.0.Beta1 Reporter: Martin Gencur Assignee: Jason Porter Fix For: 3.0.0.Beta2 The URL is specified in each module's pom.xml via <url>....</url>. You can override it for submodules, otherwise it will be inherited. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
1
0 / 0

[JBoss JIRA] Moved: (SEAMJMS-16) Event to JMS to Event mapping behavior

by Ales Justin (JIRA)

[ https://issues.jboss.org/browse/SEAMJMS-16?page=com.atlassian.jira.plugin... ] Ales Justin moved WELD-850 to SEAMJMS-16: ----------------------------------------- Project: Seam JMS (was: Weld) Key: SEAMJMS-16 (was: WELD-850) Workflow: Seam Workflow (was: jira) > Event to JMS to Event mapping behavior > -------------------------------------- > > Key: SEAMJMS-16 > URL: https://issues.jboss.org/browse/SEAMJMS-16 > Project: Seam JMS > Issue Type: Bug > Reporter: John Ament > > While working on seam jms, I've noted the following behavior. > java.lang.IllegalStateException: Singleton not set for BaseClassLoader@3479404a{vfs:///apps/jboss/jboss-6.0.0.Final/server/all/conf/jboss-service.xml} > at org.jboss.weld.integration.provider.JBossSingletonProvider$EarSingleton.get(JBossSingletonProvider.java:59) [:6.0.0.Final] > at org.jboss.weld.Container.instance(Container.java:58) [:6.0.0.Final] > at org.jboss.weld.resolution.ResolvableBuilder.checkQualifier(ResolvableBuilder.java:209) [:6.0.0.Final] > at org.jboss.weld.resolution.ResolvableBuilder.addQualifier(ResolvableBuilder.java:174) [:6.0.0.Final] > at org.jboss.weld.resolution.ResolvableBuilder.addQualifierIfAbsent(ResolvableBuilder.java:184) [:6.0.0.Final] > at org.jboss.weld.manager.BeanManagerImpl.resolveObserverMethods(BeanManagerImpl.java:464) [:6.0.0.Final] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:604) [:6.0.0.Final] > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:598) [:6.0.0.Final] > at org.jboss.seam.jms.bridge.IngressMessageListener.onMessage(IngressMessageListener.java:45) > at org.hornetq.jms.client.JMSMessageListenerWrapper.onMessage(JMSMessageListenerWrapper.java:91) [:6.0.0.Final] > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:822) [:6.0.0.Final] > at org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:46) [:6.0.0.Final] > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:940) [:6.0.0.Final] > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [:6.0.0.Final] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_22] > This exception occurs when trying to fire an event with the contents of a JMS message. The message listener in this case is instantiated from the portable extension and receives the bean manager as an argument in the constructor. I am able to get as far as reading the data from JMS, but when firing the second event the above exception occurs. I'm not certain that this is a Weld problem, but it seem slike a good place to start based on the packages shown. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMINTL-20) Pluralizer plugin system for messages

by Ken Finnigan (JIRA)

Pluralizer plugin system for messages ------------------------------------- Key: SEAMINTL-20 URL: https://issues.jboss.org/browse/SEAMINTL-20 Project: Seam International Issue Type: Feature Request Components: Locales, Messages Reporter: Ken Finnigan Fix For: 3.0.0.Beta2 Pluralizing system that can suport defined plurals through use of @PluralText and @PluralCount, but also a provider based implementation of pluralizers for different languages, with a default pluralizer that adds "s" to words. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMREST-20) Provide better boot message

by Jozef Hartinger (JIRA)

Provide better boot message --------------------------- Key: SEAMREST-20 URL: https://issues.jboss.org/browse/SEAMREST-20 Project: Seam REST Issue Type: Feature Request Affects Versions: 3.0.0.Beta1 Reporter: Jozef Hartinger Priority: Minor The boot message should: - contain module version - should contain information about which optional parts of the module are enabled/disable (Catch integration, RestClient integration, Templating, etc...) - be only one - currently there are several messages printed by each of module's Extension (Templating support, Restclient support, etc...) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2275) Document on Seam iText charting

by Joshua Partogi (JIRA)

Document on Seam iText charting ------------------------------- Key: JBSEAM-2275 URL: http://jira.jboss.com/jira/browse/JBSEAM-2275 Project: JBoss Seam Issue Type: Patch Affects Versions: 2.0.0.GA Environment: JBoss 4.2.1.GA Reporter: Joshua Partogi Fix For: 2.0.1.GA Point 16.2 1. Write in doc to use the charting support, we need to add the jfreechart.jar and jcommon-*.jar in the project classpath. We can also add this is our build.xml 2. The key attribute is needed upon p:data component usage otherwise it will throw this exception java.lang.IllegalArgumentException: Null 'key' argument. at org.jfree.data.DefaultKeyedValues.setValue(DefaultKeyedValues.java:239) at org.jfree.data.DefaultKeyedValues2D.setValue(DefaultKeyedValues2D.java:337) at org.jfree.data.DefaultKeyedValues2D.addValue(DefaultKeyedValues2D.java:303). In examples, it is used in (the ones below are the fixed value): Barchart, Linechart, Series PieChart 1. Attributes: title — The chart title text. legend — A boolean value indicating whether or not the chart should include a legend. Default value is true is3D - A boolean value indicating that the chart should be rendered in 3D instead of 2D. labelLinkMargin - The link margin labelLinkPaint - The paint used for the label linking lines. labelLinkStroke - The stroke used for the label linking lines. labelLinksVisible - A flag that controls whether or not the label links are drawn. labelOutlinePaint - The paint used to draw the outline of the section labels labelOutlineStroke - The stroke used to draw the outline of the section labels labelShadowPaint - The paint used to draw the shadow for the section labels labelPaint - The color used to draw the section labels labelGap - The gap between the labels and the plot as a percentage of the plot width. labelBackgroundPaint - The color used to draw the background of the section labels. If this is null, the background is not filled. startAngle - The starting angle circular - A boolean value indicating whether whether to draw an ellipse or a perfect circle. direction - The direction for the pie segments. If value is not set "anticlockwise" then by default it is clockwise. sectionOutlinePaint - The outline paint for ALL sections (overrides list). sectionOutlineStroke - The outline stroke for ALL sections (overrides list). sectionOutlinesVisible - A flag that controls whether or not an outline is drawn for each section in the plot. baseSectionOutlinePaint - The base section outline paint baseSectionPaint - The base section paint baseSectionOutlineStroke - The base section outline stroke 2. Usage: <p:document xmlns:p="http://jboss.com/products/seam/pdf"> <p:piechart title="Pie Chart" circular="false" direction="anticlockwise" startAngle="30" labelGap="0.1" labelLinkPaint="red"> <p:series key="Prices"> <p:data key="2003" columnKey="2003" value="7.36" /> <p:data key="2004" columnKey="2004" value="11.50" /> <p:data key="2005" columnKey="2005" value="34.625" /> <p:data key="2006" columnKey="2006" value="76.30" /> <p:data key="2007" columnKey="2007" value="85.05" /> </p:series> </p:piechart> </p:document> -- 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

13 years, 3 months

5
5
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-32) No artifact for "Combined JAR (API & implementation)" in jboss repository

by Marek Nazarko (JIRA)

No artifact for "Combined JAR (API & implementation)" in jboss repository ------------------------------------------------------------------------- Key: SEAMSECURITY-32 URL: https://issues.jboss.org/browse/SEAMSECURITY-32 Project: Seam Security Issue Type: Bug Affects Versions: 3.0.0.Beta1 Reporter: Marek Nazarko Described on project front page "Combined JAR (API & implementation)" doesn't exists in repository. Maven tries to download it from http://repository.jboss.org/nexus/content/groups/public-jboss//org/jboss/... but this place is empty. "Individual JARs" works ok. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-25) Cannot login into idmconsole application

by Martin Gencur (JIRA)

Cannot login into idmconsole application ---------------------------------------- Key: SEAMSECURITY-25 URL: https://issues.jboss.org/browse/SEAMSECURITY-25 Project: Seam Security Issue Type: Bug Affects Versions: 3.0.0.Beta1 Reporter: Martin Gencur The application gets successfully deployed. When I try to log in with demo/demo credentials, the JBossAS console throws the following exception: 16:14:46,907 INFO [org.hibernate.validator.engine.resolver.DefaultTraversableResolver] Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver. 16:14:46,923 ERROR [org.jboss.seam.security.IdentityImpl] Login failed: org.jboss.seam.security.AuthenticationException: An Authenticator could be located at org.jboss.seam.security.IdentityImpl.authenticate(IdentityImpl.java:287) [:3.0.0.Beta1] at org.jboss.seam.security.IdentityImpl.login(IdentityImpl.java:217) [:3.0.0.Beta1] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_21] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_21] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_21] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_21] 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 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_21] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2011