May 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3850) begin-conversation flush-mode="MANUAL" doesn't actualy apply MANUAL flushMode

by Uros Majeric (JIRA)

begin-conversation flush-mode="MANUAL" doesn't actualy apply MANUAL flushMode ----------------------------------------------------------------------------- Key: JBSEAM-3850 URL: https://jira.jboss.org/jira/browse/JBSEAM-3850 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.SP1 Environment: Seam 2.1.0.SP1 JBoss AS 4.2.2 Java 6 Reporter: Uros Majeric Priority: Critical If I put <begin-conversation join="true" flush-mode="MANUAL"/> in some.page.xml it starts me a conversation but flushMode isn't MANUAL. I tried with <action execute="#{actionBean.startConversation}"/> wich is anotated with: @Begin(join = true, flushMode = FlushModeType.MANUAL). In that case ti work's fine. -- 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

15 years, 1 month

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4184) Implement servlet-booking example

by Pete Muir (JIRA)

Implement servlet-booking example --------------------------------- Key: JBSEAM-4184 URL: https://jira.jboss.org/jira/browse/JBSEAM-4184 Project: Seam Issue Type: Feature Request Components: Examples Reporter: Pete Muir Assignee: Dan Allen Fix For: 3.0.0.BETA1 http://anonsvn.jboss.org/repos/seam/examples/trunk/servlet-booking/ This example will show Seam in a servlet-only environment, including using JPA -- 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

15 years, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2809) s:inputPassword

by Pete Muir (JIRA)

s:inputPassword --------------- Key: JBSEAM-2809 URL: http://jira.jboss.com/jira/browse/JBSEAM-2809 Project: JBoss Seam Issue Type: Feature Request Components: JSF Controls Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.1.0.BETA1 Extension of h:inputSecret. Renders two input fields. Attaches a validator by default that checks both fields are the same. Use like <s:inputPassword value="#{identity.password}" /> Advantages: No backing bean logic required, validation done at correct point -- 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, 1 month

7
22
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4182) EntityList generated by seam-gen lost the compatibility with 2.0.x versions

by Marcos Sousa (JIRA)

EntityList generated by seam-gen lost the compatibility with 2.0.x versions --------------------------------------------------------------------------- Key: JBSEAM-4182 URL: https://jira.jboss.org/jira/browse/JBSEAM-4182 Project: Seam Issue Type: Bug Components: Tools Affects Versions: 2.1.0.GA Environment: Windows or linux platform. Eclipse and Jboss Tools 3 Reporter: Marcos Sousa The generated EntityList by seam-gen in the previews versions (2.0.x) isn't compatible with Seam 2.1.x. Basically the problem is in the query building because the method "getRestrinctions" changed the returned type that causes a ClassCastException. -- 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

15 years, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4010) Document various approaches to Wicket instrumentation

by Clint Popetz (JIRA)

Document various approaches to Wicket instrumentation ----------------------------------------------------- Key: JBSEAM-4010 URL: https://jira.jboss.org/jira/browse/JBSEAM-4010 Project: Seam Issue Type: Task Components: Wicket Reporter: Clint Popetz Assignee: Clint Popetz Fix For: 2.1.2.CR1 -- 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

15 years, 1 month

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4031) JavassistInstrumentor throws ClassNotFoundException when scanning annotations

by Paul Mooney (JIRA)

JavassistInstrumentor throws ClassNotFoundException when scanning annotations ----------------------------------------------------------------------------- Key: JBSEAM-4031 URL: https://jira.jboss.org/jira/browse/JBSEAM-4031 Project: Seam Issue Type: Bug Components: Wicket Reporter: Paul Mooney A ClassNotFoundException is thrown when the javassistInstrumentor encounters annotations that are not in the classpath. This happens when : -Using the seam-instrument-wicket plugin -scanAnnotations is true -Classes that match the 'includes' patterns have a TYPE targetted annotation which is defined in the project, or in an artifact that is not a dependency of the plugin. This seems to happen because dependencies of the project, and the project's classes are not in the classpath of the seam-instrument-wicket plugin. Possible Solutions: 1. Somehow put all of the project's dependencies and classes in the plugin's classpath when it runs. or 2. Replace all calls to 'CtClass.getAnnotations()' inside of JavassistInstrumentor with 'CtClass.getAvailableAnnotations()' which only loads Annotations on the classpath and does not throw a ClassNotFoundException. -- 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

15 years, 1 month

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4139) Maven Instrument Plugin - Compile dependencies fixed

by Cruz Fernandez (JIRA)

Maven Instrument Plugin - Compile dependencies fixed ---------------------------------------------------- Key: JBSEAM-4139 URL: https://jira.jboss.org/jira/browse/JBSEAM-4139 Project: Seam Issue Type: Patch Components: Wicket Affects Versions: 2.1.1.GA Environment: The Maven instrumentation Reporter: Cruz Fernandez In a maven builded project, instrumenting at build time the wicket classes is something necesary (as maven always puts compiled classes in WEB-INF/classes). The seam-instrument-wicket plugin needs to be put in "compile" scope (for getting the "provided" dependencies that are needed in compile time). Probably fixes issue : JBSEAM-4031, https://jira.jboss.org/jira/browse/JBSEAM-4031 as the maven project must have the annotation dependencies for compilations (I suppose the org.jboss.seam is included in the project of Paul Mooney) -- 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

15 years, 1 month

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4178) Seam 2.1.1GA on Glassfish generates an exception depending on where the end-conversation is placed in a pages.xml

by Arshad Mahmood (JIRA)

Seam 2.1.1GA on Glassfish generates an exception depending on where the end-conversation is placed in a pages.xml ----------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4178 URL: https://jira.jboss.org/jira/browse/JBSEAM-4178 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Environment: JD 1.6 Seam 2.1.1.GA Glassfish 2.1 Reporter: Arshad Mahmood I have an application with an edit page named edit.xhtml, it has a form and submit buttion which executes the following action #{currencyAction.save}. The currencyAction is an EJB Stateful session bean. I am coming across a weird error when the action is execute:- If my pages.xml is as follows, everything works as expected (i.e. the bean is saved and I get redirected to the view page).  <param name="currencyId" value="#{currencyAction.currencyId}" />  <begin-conversation join="true" />  <navigation from-action="#{currencyAction.save}"> <end-conversation before-redirect="true" /> <rule if-outcome="persisted"> <redirect view-id="/settings/currencies/view.xhtml"> <param name="currencyId" value="#{currencyAction.currencyId}" /> </redirect> </rule> </navigation> ** BUT **, if I change the end-conversation to be within the if-outcome then I get an exception. I.e. if the pages,xml is changed to  <navigation from-action="#{currencyAction.save}"> <rule if-outcome="persisted"> <end-conversation before-redirect="true" /> *** CHANGE HERE **** <redirect view-id="/settings/currencies/view.xhtml"> <param name="currencyId" value="#{currencyAction.currencyId}" /> </redirect> </rule> </navigation> The exception is as follows:- [#|2009-05-15T10:08:58.045+0100|INFO|sun-appserver2.1|javax.enterprise.system.container.ejb|_ThreadID=24;_ThreadName=TP-Processor12;| javax.ejb.TransactionRolledbackLocalException: Exception thrown from bean; nested exception is: java.lang.IllegalArgumentException: EntityManagerFactory not found in JNDI : java:comp/env/smartkidsBSEMF java.lang.IllegalArgumentException: EntityManagerFactory not found in JNDI : java:comp/env/smartkidsBSEMF at org.jboss.seam.persistence.ManagedPersistenceContext.getEntityManagerFactoryFromJndiOrValueBinding(ManagedPersistenceContext.java:245) at org.jboss.seam.persistence.ManagedPersistenceContext.initEntityManager(ManagedPersistenceContext.java:78) at org.jboss.seam.persistence.ManagedPersistenceContext.getEntityManager(ManagedPersistenceContext.java:107) at sun.reflect.GeneratedMethodAccessor423.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) The bean values are persisted to the database, but then this exception is raised. -- 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

15 years, 1 month

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4181) Seam Test fails with error "MessagingType 'org.quartz.Job' not found in resource deployment >>>> jboss.jca:service=RARDeployment, >>>> name='jms-ra.rar'"

by Gary Hu (JIRA)

Seam Test fails with error "MessagingType 'org.quartz.Job' not found in resource deployment >>>> jboss.jca:service=RARDeployment, >>>> name='jms-ra.rar'" ---------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4181 URL: https://jira.jboss.org/jira/browse/JBSEAM-4181 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.SP1 Reporter: Gary Hu Seam test fails with the error "MessagingType 'org.quartz.Job' not found in resource deployment >>>> jboss.jca:service=RARDeployment, >>>> name='jms-ra.rar'" when running quartz scheduler integration similar to the tutorial http://www.jboss.org/jbossejb3/docs/tutorial/jca/inflow/quartz/quartz.html The error could be reproduced using seam quartz example. The code is something similar to: @MessageDriven(activationConfig = { @ActivationConfigProperty(propertyName = "cronTrigger", propertyValue = "0 0/360 * * * ?") }) @ResourceAdapter("quartz-ra.rar") @Name("processor") @AutoCreate public class PaymentProcessor implements org.quartz.Job{ ... } The code above can be deployed to JBoss AS without problem. But Seam test will fail with the error mentioned above. -- 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

15 years, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4177) TestNG integration tests do not support setting of cookies

by Brendan Farragher (JIRA)

TestNG integration tests do not support setting of cookies ---------------------------------------------------------- Key: JBSEAM-4177 URL: https://jira.jboss.org/jira/browse/JBSEAM-4177 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.1.GA Environment: Ubuntu Linux 8.04, JBoss AS 4.2.3 Reporter: Brendan Farragher There is no support for setting cookies inside of a TestNG integration test case. I do not know if this issue is related to: https://jira.jboss.org/jira/browse/JBSEAM-795 -- 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

15 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2009