March 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMFACES-104) Dynamic resource bundles

by Nicklas Karlsson (JIRA)

Dynamic resource bundles ------------------------ Key: SEAMFACES-104 URL: https://issues.jboss.org/browse/SEAMFACES-104 Project: Seam Faces Issue Type: Feature Request Reporter: Nicklas Karlsson It would be nice to be able to overload ResourceBundle. Preferrably at a level that would allow the user to take control over the faces validation and bean validation messages (e.g. load them from a DB) Ideas perhaps from http://john-ament.blogspot.com/2010/03/dyanmic-resourcebundles-in-cdi.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
1
0 / 0

[JBoss JIRA] Created: (SOLDER-86) Split up LoggerProducers

by Ken Finnigan (JIRA)

Split up LoggerProducers ------------------------ Key: SOLDER-86 URL: https://issues.jboss.org/browse/SOLDER-86 Project: Seam Solder Issue Type: Task Components: Logging Affects Versions: 3.0.0.CR2 Reporter: Ken Finnigan Assignee: Ken Finnigan Priority: Minor Split the existing LoggerProducers into one for each type of Producer. Such as: LoggerProducer TypedLoggerProducer TypedMessageBundleProducer -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
1
0 / 0

[JBoss JIRA] Created: (SEAMJMS-22) Remoting support

by John Ament (JIRA)

Remoting support ---------------- Key: SEAMJMS-22 URL: https://issues.jboss.org/browse/SEAMJMS-22 Project: Seam JMS Issue Type: Feature Request Components: Injection Reporter: John Ament Assignee: John Ament Based on the spring support in Apache ActiveMQ ( http://activemq.apache.org/spring-support.html ) we should provide support for remote JMS providers. I'm proposing to have remoting basics in the main impl, with impls providing remote support for ActiveMQ and HornetQ. Remoting support should handle local configuration (in memory?) and instances running in a separate VM. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Created: (SEAMJCR-15) Upgrade to Arquillian 1.0.0Alpha-5

by George Gastaldi (JIRA)

Upgrade to Arquillian 1.0.0Alpha-5 ---------------------------------- Key: SEAMJCR-15 URL: https://issues.jboss.org/browse/SEAMJCR-15 Project: Seam JCR Issue Type: Library Upgrade Reporter: George Gastaldi -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
2
0 / 0

[JBoss JIRA] Created: (SOLDER-85) Better separation of i18n and logging concerns

by Ken Finnigan (JIRA)

Better separation of i18n and logging concerns ---------------------------------------------- Key: SOLDER-85 URL: https://issues.jboss.org/browse/SOLDER-85 Project: Seam Solder Issue Type: Enhancement Components: Core, Documentation, Logging Affects Versions: 3.0.0.CR2 Reporter: Ken Finnigan Assignee: Ken Finnigan Fix For: 3.0.0.Final Currently we have the following classes within the api: org.jboss.seam.solder.log.Category org.jboss.seam.solder.log.Locale org.jboss.seam.solder.log.Suffix org.jboss.seam.solder.log.TypedCategory org.jboss.seam.solder.logging.Cause org.jboss.seam.solder.logging.FormatWith org.jboss.seam.solder.logging.LogMessage org.jboss.seam.solder.logging.Message org.jboss.seam.solder.logging.MessageBundle org.jboss.seam.solder.logging.MessageBundleInvocationHandler org.jboss.seam.solder.logging.MessageLogger org.jboss.seam.solder.logging.MessageLoggerInvocationHandler org.jboss.seam.solder.logging.Messages org.jboss.seam.solder.logging.StatusMessage And in the impl we have: org.jboss.seam.solder.log.LoggerExtension org.jboss.seam.solder.log.LoggerProducers org.jboss.seam.solder.log.TypedLogger org.jboss.seam.solder.log.TypedMessageBundle The proposal is the following: - Rename package in impl to be org.jboss.seam.solder.logging - Move TypedCategory from api to impl - Remove org.jboss.seam.solder.logging.StatusMessage, as this will be implemented within Seam i18n - Rename FormatWith to Formatter - Rename LogMessage to Log - Move/Rename packages to result in the following contents of the api: org.jboss.seam.solder.logging.Category org.jboss.seam.solder.logging.Cause org.jboss.seam.solder.logging.Log org.jboss.seam.solder.logging.MessageLogger org.jboss.seam.solder.logging.MessageLoggerInvocationHandler org.jboss.seam.solder.logging.Suffix org.jboss.seam.solder.messages.Formatter org.jboss.seam.solder.messages.Locale org.jboss.seam.solder.messages.Message org.jboss.seam.solder.messages.MessageBundle org.jboss.seam.solder.messages.MessageBundleInvocationHandler org.jboss.seam.solder.messages.Messages -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
4
0 / 0

[JBoss JIRA] Created: (SEAMREST-35) Backport ResourceHome and ResourceQuery components

by Jozef Hartinger (JIRA)

Backport ResourceHome and ResourceQuery components -------------------------------------------------- Key: SEAMREST-35 URL: https://issues.jboss.org/browse/SEAMREST-35 Project: Seam REST Issue Type: Feature Request Reporter: Jozef Hartinger Provide functionality similar to Seam 2's ResourceHome and ResourceQuery components http://docs.jboss.org/seam/latest-2.2/reference/en-US/html/webservices.ht... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Created: (SEAMREST-30) Cannot use @DefaultBean for default ClientExecutor

by Jozef Hartinger (JIRA)

Cannot use @DefaultBean for default ClientExecutor -------------------------------------------------- Key: SEAMREST-30 URL: https://issues.jboss.org/browse/SEAMREST-30 Project: Seam REST Issue Type: Bug Components: Client Affects Versions: 3.0.0.Beta1 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Priority: Minor Fix For: Future Cannot use @DefaultBean for default ClientExecutor. Otherwise the deployment fails on GlassFish. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
1
0 / 0

[JBoss JIRA] Created: (SOLDER-74) @DefaultBean producer methods broken on GlassFish

by Jozef Hartinger (JIRA)

@DefaultBean producer methods broken on GlassFish ------------------------------------------------- Key: SOLDER-74 URL: https://issues.jboss.org/browse/SOLDER-74 Project: Seam Solder Issue Type: Bug Components: Core Affects Versions: 3.0.0.Beta3 Reporter: Jozef Hartinger Priority: Critical org.jboss.arquillian.impl.event.FiredEventException: java.lang.RuntimeException: Could not inject members at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:68) at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115) at org.jboss.arquillian.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:127) at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:206) at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:225) at org.jboss.arquillian.junit.Arquillian$MultiStatementExecutor.execute(Arquillian.java:297) at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:221) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:163) at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:186) at org.jboss.arquillian.junit.Arquillian$MultiStatementExecutor.execute(Arquillian.java:297) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:182) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:127) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at org.junit.runner.JUnitCore.run(JUnitCore.java:136) at org.jboss.arquillian.junit.JUnitTestRunner.execute(JUnitTestRunner.java:69) at org.jboss.arquillian.protocol.servlet_3.ServletTestRunner.doGet(ServletTestRunner.java:84) at javax.servlet.http.HttpServlet.service(HttpServlet.java:735) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) 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:818) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:719) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1008) 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: Could not inject members at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:104) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.enrich(CDIInjectionEnricher.java:52) at org.jboss.arquillian.impl.handler.TestCaseEnricher.callback(TestCaseEnricher.java:42) at org.jboss.arquillian.impl.handler.TestCaseEnricher.callback(TestCaseEnricher.java:32) at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) ... 50 more Caused by: java.lang.NullPointerException at org.jboss.seam.solder.bean.defaultbean.AbstractDefaultProducerBean.getReceiver(AbstractDefaultProducerBean.java:74) at org.jboss.seam.solder.bean.defaultbean.AbstractDefaultProducerBean.create(AbstractDefaultProducerBean.java:65) at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:67) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:669) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:751) at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:138) at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:872) at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:884) at org.jboss.weld.manager.SimpleInjectionTarget$1.proceed(SimpleInjectionTarget.java:120) at org.glassfish.weld.services.InjectionServicesImpl.aroundInject(InjectionServicesImpl.java:134) at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:50) at org.jboss.weld.manager.SimpleInjectionTarget.inject(SimpleInjectionTarget.java:114) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectNonContextualInstance(CDIInjectionEnricher.java:114) at org.jboss.arquillian.testenricher.cdi.CDIInjectionEnricher.injectClass(CDIInjectionEnricher.java:93) ... 54 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2588) s:conversationPropagation breaks a4j:commandButton

by Fijai Cairo (JIRA)

s:conversationPropagation breaks a4j:commandButton -------------------------------------------------- Key: JBSEAM-2588 URL: http://jira.jboss.com/jira/browse/JBSEAM-2588 Project: JBoss Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.0.1.GA Environment: Firefox OSX 10.51, JBoss AS 4.22, JAVA 1.5.0_13-b05-237 Reporter: Fijai Cairo <a4j:commandButton styleClass="btn" id="contactButton#{accountHolder}" oncomplete="UIControl('contactForm', 'contact', 'identification');" reRender="contactBlock#{accountHolder},uiSec" actionListener="#{accountOpen.submitContactInfo}" value="Continue" > <a4j:actionparam name="holder" value="getSuffix()" noEscape="true"/> <s:conversationPropagation type="join" /> </a4j:commandButton> Renders the following: Notice that the onclick handler is rendered before the input is rendered and causes a document.getElementById("contactButton1") has no properties javascript error. <div id="contactContinueSection1" style="padding: 10px 10px 10px 10px; display: block"> <script language="JavaScript" type="text/javascript"> //<![CDATA[ document.getElementById('contactButton1').onclick = new Function("event", "{if (document.getElementById){var form = document.getElementById('contactForm1');var input = documen t.createElement('input');if (document.all){ input.type = 'hidden';input.name = 'conversationPropagat ion';input.value = 'join';}else if (document.getElementById) {input.setAttribute('type', 'hidden');i nput.setAttribute('name', 'conversationPropagation');input.setAttribute('value', 'join');}form.appen dChild(input);return true;}}"); //]]> </script> <input id="contactButton1" name="contactButton1" onclick="A4J.AJAX.Submit('_viewRoot','contactForm1',event,{'parameters':{'holder':getSuffix(),'conversationPr opagation':'join','contactButton1':'contactButton1'} ,'actionUrl':'/BaisiPrototype/AE/primary.jspv?j avax.portlet.faces.DirectLink=true','oncomplete':function(request,event,data){UIControl('contactForm ', 'contact', 'identification');}} );return false;" value="Continue" class="btn" type="button" /> </div> Without <s:conversationPropagation type="join" />, the onclick handler is rendered as an attribute of the button as ff: <div id="contactContinueSection1" style="padding: 10px 10px 10px 10px; display: block"><input id="contactButton1" name="contactButton1" onclick="A4J.AJAX.Submit('_viewRoot','contactForm1',event,{'parameters':{'holder':getSuffix(),'contactButton1 ':'contactButton1'} ,'actionUrl':'/BaisiPrototype/AE/primary.jspv?javax.portlet.faces.DirectLink=tru e','oncomplete':function(request,event,data){UIControl('contactForm', 'contact', 'identification');} } );return false;" value="Continue" class="btn" type="button" /> -- 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

15 years

3
4
0 / 0

[JBoss JIRA] Created: (SEAMREST-28) Provide a Java SE example (JAX-RS client)

by Jozef Hartinger (JIRA)

Provide a Java SE example (JAX-RS client) ----------------------------------------- Key: SEAMREST-28 URL: https://issues.jboss.org/browse/SEAMREST-28 Project: Seam REST Issue Type: Feature Request Components: Client, Examples Reporter: Jozef Hartinger Verify that Seam REST can be run in SE environment (with Weld SE) and provide a client application that runs in a standalone mode (Java SE). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
4
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 March 2011