August 2012 - seam-issues - Jboss List Archives

[JBoss JIRA] (JBSEAM-5016) Working SeamTest with Arquillian+TestNG

by Marek Schmidt (JIRA)

Marek Schmidt created JBSEAM-5016: ------------------------------------- Summary: Working SeamTest with Arquillian+TestNG Key: JBSEAM-5016 URL: https://issues.jboss.org/browse/JBSEAM-5016 Project: Seam 2 Issue Type: Enhancement Components: Test Harness Affects Versions: 2.3.0.BETA2 Reporter: Marek Schmidt Assignee: Marek Schmidt Fix For: The future Make SeamTest work with arquillian-testng-container -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
1
0 / 0

[JBoss JIRA] (JBSEAM-5015) PrioritizableConverter has a type on @FacesConverter name

by Rafael Benevides (JIRA)

Rafael Benevides created JBSEAM-5015: ---------------------------------------- Summary: PrioritizableConverter has a type on @FacesConverter name Key: JBSEAM-5015 URL: https://issues.jboss.org/browse/JBSEAM-5015 Project: Seam 2 Issue Type: Enhancement Components: Core Reporter: Rafael Benevides On PrioritizableConverter@FacesConverter(value="org.jboss.sema.ui.PrioritizableConverter") seam was write sema. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
2
0 / 0

[JBoss JIRA] (JBSEAM-4962) Generation of Seam Reference Guide sometime throws ConcurrentModificationException

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-4962: ------------------------------------- Summary: Generation of Seam Reference Guide sometime throws ConcurrentModificationException Key: JBSEAM-4962 URL: https://issues.jboss.org/browse/JBSEAM-4962 Project: Seam 2 Issue Type: Bug Components: Build Affects Versions: 2.3.0.BETA2, 2.3.0.BETA1 Reporter: Marek Novotny Fix For: 2.3.0.CR1 That happens more frequently on Jenkins than on my local build. {noformat} [ERROR] Failed to execute goal org.jboss.maven.plugins:maven-jdocbook-plugin:2.2.0:generate (jdocbook:generate) on project seam-reference-guide: Execution jdocbook:generate of goal org.jboss.maven.plugins:maven-jdocbook-plugin:2.2.0:generate failed. ConcurrentModificationException -> [Help 1] {noformat} We probably need to upgrade to the latest maven-jdocbook-plugin from 2.2.0 to 2.3.x? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
5
0 / 0

[JBoss JIRA] (SOLDER-334) NullPointerException in ImplicitHttpServletObjectsProducer.getCookies if not Cookies

by Thomas Frühbeck (JIRA)

Thomas Frühbeck created SOLDER-334: -------------------------------------- Summary: NullPointerException in ImplicitHttpServletObjectsProducer.getCookies if not Cookies Key: SOLDER-334 URL: https://issues.jboss.org/browse/SOLDER-334 Project: Solder Issue Type: Bug Affects Versions: 3.1.0.Final Reporter: Thomas Frühbeck If no Cookies in Request, request.getCookies() returns null. > @Produces > @RequestScoped > protected List<Cookie> getCookies() { > return Arrays.asList(getHttpServletRequest().getCookies()); > } When using the Producer, there is no possibility to identify, if cookies are set or not, the proxy will not be null: So by simply invoking : @Inject private List<Cookie> cookies; public void handleInit(@Observes HttpServletRequest request) { log.info("handling Request: "+request.getRequestURI()); if (cookies != null) { for (Cookie cookie : cookies) { System.out.println("Found Cookie: "+cookie); } ... I get: description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.NullPointerException java.util.Arrays$ArrayList.<init>(Arrays.java:2842) java.util.Arrays.asList(Arrays.java:2828) org.jboss.solder.servlet.http.ImplicitHttpServletObjectsProducer.getCookies(ImplicitHttpServletObjectsProducer.java:93) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:601) org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:264) org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52) org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137) org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:260) org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:170) org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstance(MethodInjectionPoint.java:137) org.jboss.weld.bean.ProducerMethod$1.produce(ProducerMethod.java:133) org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:299) org.jboss.weld.context.AbstractContext.get(AbstractContext.java:107) org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:90) org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:104) org.jboss.weld.proxies.Collection$Iterable$List$1103886743$Proxy$_$$_WeldClientProxy.iterator(Collection$Iterable$List$1103886743$Proxy$_$$_WeldClientProxy.java) at.tfr.web.SolderEventHandler.handleInit(SolderEventHandler.java:28) at.tfr.web.SolderEventHandler$Proxy$_$$_WeldClientProxy.handleInit(SolderEventHandler$Proxy$_$$_WeldClientProxy.java) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:601) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-4980) Use registration to javax.faces.event.PostConstructApplicationEvent instead of relying on ServletContextListener

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-4980: ------------------------------------- Summary: Use registration to javax.faces.event.PostConstructApplicationEvent instead of relying on ServletContextListener Key: JBSEAM-4980 URL: https://issues.jboss.org/browse/JBSEAM-4980 Project: Seam 2 Issue Type: Bug Components: JSF Integration Affects Versions: 2.3.0.BETA2, 2.3.0.BETA1 Reporter: Marek Novotny Assignee: Marek Novotny Fix For: 2.3.0.CR1 Use registration to javax.faces.event.PostConstructApplicationEvent instead of relying on ServletContextListener for initializing of JSF 2 integration. JSF2 specifically addresses this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
5
0 / 0

[JBoss JIRA] (JBSEAM-4998) Drools does not work with Java7

by Ramkumar Pillai (JIRA)

Ramkumar Pillai created JBSEAM-4998: --------------------------------------- Summary: Drools does not work with Java7 Key: JBSEAM-4998 URL: https://issues.jboss.org/browse/JBSEAM-4998 Project: Seam 2 Issue Type: Bug Components: Drools Environment: Jboss AS7 Reporter: Ramkumar Pillai https://issues.jboss.org/browse/JBRULES-3163 Drool 5.1.1 has a Defect whicis is not working on JVM 1.7, the same issue is closed in Rools not yet Fixed in Seam BOM file -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-4512) BPM task does not rollback

by Jason E (JIRA)

BPM task does not rollback -------------------------- Key: JBSEAM-4512 URL: https://jira.jboss.org/jira/browse/JBSEAM-4512 Project: Seam Issue Type: Bug Components: BPM Affects Versions: 2.2.0.GA Environment: Testing this on Windows XP. Deploying to JBoss AS 4.2.2 Reporter: Jason E I have made a simple change to the ShipAction.java class in the dvdstore example that ships with Seam. Here is the change //@EndTask public String ship() { order.ship(track); TaskInstance ti = ManagedJbpmContext.instance().getTaskInstance(taskInstance.getId()); taskInstance.end(); if(true) throw new RuntimeException("TESTING"); return "admin"; } I commented out the end task annotation and I am ending the task via the TaskInstance API. When I throw the Runtime exception the changes to the ORDERS entity bean (i.e. updating the tracking number) rolls back. The problem is that the task instance change (i.e. ending the task) does not rollback. It appears that jBPM is flushing its changes in another db transaction. This seems like a bug since I would expect the ending of my task to also rollback. This seems like the desired behavior. This was the only change I made to the dvdstore example that ships with Seam 2.2.0.GA so it should be easy to reproduce. Thanks! Jason -- 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

12 years, 5 months

7
18
0 / 0

[JBoss JIRA] (SEAMFACES-249) Transaction not closed when using view parameters

by Bryn Cooke (JIRA)

Bryn Cooke created SEAMFACES-249: ------------------------------------ Summary: Transaction not closed when using view parameters Key: SEAMFACES-249 URL: https://issues.jboss.org/browse/SEAMFACES-249 Project: Seam Faces Issue Type: Bug Environment: Linux, Tomcat7, Mojarra 2.1.11, Seam Faces 3.1.0 Reporter: Bryn Cooke When using the view parameters the transaction created by the TransactionPhaseListener in the render response phase is not closed. This results in the transaction being marked as close on commit and in our web site we run out of connections to the database. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
2
0 / 0

[JBoss JIRA] (JBSEAM-4933) Create war and ear maven archetype to simulate generate general seam2 project

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-4933: ------------------------------------- Summary: Create war and ear maven archetype to simulate generate general seam2 project Key: JBSEAM-4933 URL: https://issues.jboss.org/browse/JBSEAM-4933 Project: Seam 2 Issue Type: Task Components: Tools Reporter: Marek Novotny Assignee: Marek Novotny Fix For: 2.3.0.BETA2 We need quick Seam 2 project template creation for Web and Enterprise Applications. This would be achieved by creating EAR and WAR Seam2 archetype. They should be based on previous generated project templates from Seam Generator. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-86) Scheme setting for pages in @ViewConfig

by Bill Elliot (JIRA)

Scheme setting for pages in @ViewConfig --------------------------------------- Key: SEAMSECURITY-86 URL: https://issues.jboss.org/browse/SEAMSECURITY-86 Project: Seam Security Issue Type: Feature Request Affects Versions: 3.0.0.Final Reporter: Bill Elliot Is there a way in Seam 3 to do like in the Page definitions of Seam 2 to specify the Scheme (HTTP/HTTPS) to use for a specific page? I need to be able to place the login and password changing screens into HTTPS for increased security and best practices. This could likely be done in the Pages definition under a @ViewConfig. Possibly adding a new annotation @Scheme("HTTPS"). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

4
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2012