January 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-215) Create an XML schema or DTD for pageflow

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-215?page=all ] Gavin King updated JBSEAM-215: ------------------------------ Fix Version/s: 1.1.5.GA (was: 1.1.1.GA) > Create an XML schema or DTD for pageflow > ---------------------------------------- > > Key: JBSEAM-215 > URL: http://jira.jboss.com/jira/browse/JBSEAM-215 > Project: JBoss Seam > Issue Type: Feature Request > Components: BPM > Reporter: Gavin King > Assigned To: Gavin King > Priority: Critical > Fix For: 1.1.5.GA > > Attachments: pageflow-1.0.xsd > > > like it says -- 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

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-641) typos in a file in jboss-seam-ui.jar in Seam 1.1.0.GA distribution

by Ian White (JIRA)

typos in a file in jboss-seam-ui.jar in Seam 1.1.0.GA distribution ------------------------------------------------------------------ Key: JBSEAM-641 URL: http://jira.jboss.com/jira/browse/JBSEAM-641 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.1.0.GA Environment: All Reporter: Ian White Priority: Minor In the faces-config.xml in the META-INF directory in seam-seam-ui.jar there are 4 occurences of boolean. My Intellij IDEA complains about them. Should they be Boolean instead ? -- 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

18 years, 2 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-665) Seam throws NPE when a component with a @Name is specified in components.xml

by Mike Quilleash (JIRA)

Seam throws NPE when a component with a @Name is specified in components.xml ---------------------------------------------------------------------------- Key: JBSEAM-665 URL: http://jira.jboss.com/jira/browse/JBSEAM-665 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.0.GA Environment: Win XP Pro Java 1.5.0 Tomcat 6.0.7 Reporter: Mike Quilleash Example line in components.xml <component class="com.xxx.ElementDetail"/> Class ElementDetail does not have a @Name (which it should) but class Initialization method installComponentFromXmlElement() throws an NPE on this line. name = clazz.getAnnotation(Name.class).value(); Would be nice to check for the null condition and throw a more descriptive exception of the problem. e.g Name nameAnnotation = clazz.getAnnotation( Name.class ); if ( nameAnnotation == null ) throw new IllegalArgumentException( "Component class " + class.getName() + " requires a @Name annotation or it's components.xml reference requires a name attribute" ); name = nameAnnotation.value(); -- 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

18 years, 2 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-570) The persistence manager doesnt find EJB3 entities when testclasses and ejbs are separated

by Alexandre Touret (JIRA)

The persistence manager doesnt find EJB3 entities when testclasses and ejbs are separated ----------------------------------------------------------------------------------------- Key: JBSEAM-570 URL: http://jira.jboss.com/jira/browse/JBSEAM-570 Project: JBoss Seam Issue Type: Bug Components: EJB3 Affects Versions: 1.1.0.CR2 Environment: JBOSS AS 4.0.5GA JDK 1.5 Reporter: Alexandre Touret Hello, I m currently testing Seam. The samples bundled (expecially BookingUnitTest) with the distribution work but notin my environment: 1- I splitted the sample in order to "be mavenized" 2- I changed the database to postgreSQL 3- add one more table 4- move queries to namedqueries Maven separates classes build directory and test build directory. I have this directory layout: target/classes --> EJB builds target/test-classes /ejb-container testcases classes built /micro-container /resources files When I start a test which seems like BookingTest (in sample booking) everything works fine, but when I start BookingUnitTest, the persistencemanager doesnt find the entity I have this error: javax.persistence.PersistenceException: org.hibernate.hql.ast.QuerySyntaxException: Hotel is not map ped [from Hotel] at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl. java:567) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:79) at org.jboss.seam.example.booking.test.BookingUnitTest.testHotelBooking(BookingUnitTest.java:61) Caused by: org.hibernate.hql.ast.QuerySyntaxException: Hotel is not mapped [from Hotel] at org.hibernate.hql.ast.util.SessionFactoryHelper.requireClassPersister(SessionFactoryHelper.java: 158) at org.hibernate.hql.ast.tree.FromElementFactory.addFromElement(FromElementFactory.java:87) at org.hibernate.hql.ast.tree.FromClause.addFromElement(FromClause.java:70) at org.hibernate.hql.ast.HqlSqlWalker.createFromElement(HqlSqlWalker.java:267) at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromElement(HqlSqlBaseWalker.java:3049) at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromElementList(HqlSqlBaseWalker.java:2938) at org.hibernate.hql.antlr.HqlSqlBaseWalker.fromClause(HqlSqlBaseWalker.java:688) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:544) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281) Regards, Alexandre Touret -- 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

18 years, 2 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-662) s:formattedText for wikitext rendering

by Gavin King (JIRA)

s:formattedText for wikitext rendering -------------------------------------- Key: JBSEAM-662 URL: http://jira.jboss.com/jira/browse/JBSEAM-662 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.1.GA We need built-in rendering of wiki/forum text. Built a parser using ANTLR. -- 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

18 years, 2 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-635) Pageflow started in render response phase using <start-page>doesn't work

by Richard Leherpeur (JIRA)

Pageflow started in render response phase using <start-page>doesn't work ------------------------------------------------------------------------ Key: JBSEAM-635 URL: http://jira.jboss.com/jira/browse/JBSEAM-635 Project: JBoss Seam Issue Type: Bug Components: BPM Affects Versions: 1.1.0.GA Environment: Jboss 4.0.5GA Reporter: Richard Leherpeur With the following pageflow definition: <?xml version="1.0"?> <pageflow-definition name="test"> <start-page name="start"> <transition to="isUserLoggedIn"/> </start-page> <decision name="isUserLoggedIn" expression="#{loginAction.isUserLoggedIn}"> <transition name="true" to="page1" /> <transition name="false" to="page2" /> </decision> ... </pageflow-definition> When the flow is started in a SFSB by calling a method definied like: @Begin public void init() { ... Pageflow.instance().begin(this.getPageflow()); } The pageflow is not starting properly. There are no errors messages in the logs but the application defined error page is displayed. Now, if the previous code is followed by: Pageflow.instance().navigate(facesContext, null); then the flow starts fine and reach the first page. But then it seems that the flow lost the conversation and it is not possible to access the SFSB that started the conversation anymore. I believe a comment about this usecase is made in org.jboss.seam.core.Pageflow in the method: public void begin(String pageflowDefinitionName) { if ( log.isDebugEnabled() ) { log.debug("beginning pageflow: " + pageflowDefinitionName); } processInstance = PageflowHelper.newPageflowInstance( getPageflowProcessDefinition(pageflowDefinitionName) ); //if ( Lifecycle.getPhaseId().equals(PhaseId.RENDER_RESPONSE) ) //{ //if a pageflow starts during the render response phase //(as a result of a @Create method), we know the navigation //handler will not get called, so we should force the //pageflow out of the start state immediately //TODO: this is not actually completely true, what about <s:actionLink/> //pi.signal(); //} setDirty(); Events.instance().raiseEvent("org.jboss.seam.beginPageflow." + pageflowDefinitionName); storePageflowToViewRootIfNecessary(); } -- 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

18 years, 2 months

2
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-639) @Startup + @Create causes exception

by Gavin King (JIRA)

@Startup + @Create causes exception ----------------------------------- Key: JBSEAM-639 URL: http://jira.jboss.com/jira/browse/JBSEAM-639 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.0.GA Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.1.1.GA https://na1.salesforce.com/500300000031hRp -- 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

18 years, 2 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-659) conflicting jar files

by mohammad norouzi (JIRA)

conflicting jar files --------------------- Key: JBSEAM-659 URL: http://jira.jboss.com/jira/browse/JBSEAM-659 Project: JBoss Seam Issue Type: Bug Components: Framework Affects Versions: 1.1.0.GA Environment: Win2003, JDK 5, Eclipse IDE, Apache Tomcat 5.5 Reporter: mohammad norouzi the JAXB packages in the Seam are not latest version and unfortunately are not seperated as an individual jar file, and we need latest version of JAXB (v2.0) in our project, so when we use our needed version it conflicts with the version inside the ejb-jar-all.jar file included in JBoss Seam. the only temporary workaround is to removing JAXB packages from that jar file. -- 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

18 years, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-657) dateFormat-parameter on SelectDate-UIComponent

by Kasper Sø￸rensen (JIRA)

dateFormat-parameter on SelectDate-UIComponent ---------------------------------------------- Key: JBSEAM-657 URL: http://jira.jboss.com/jira/browse/JBSEAM-657 Project: JBoss Seam Issue Type: Patch Components: JSF Affects Versions: 1.1.0.GA Environment: All Reporter: Kasper Sø￸rensen Priority: Minor The SelectDate-UIComponent always use the same dateFormat. I will be patching the component to make this parameterized. -- 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

18 years, 2 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-656) The JPA example fails to deploy in Glassfish

by Michael Yuan (JIRA)

The JPA example fails to deploy in Glassfish -------------------------------------------- Key: JBSEAM-656 URL: http://jira.jboss.com/jira/browse/JBSEAM-656 Project: JBoss Seam Issue Type: Bug Reporter: Michael Yuan Fix For: 1.1.1.GA The JPA example deploys fine in JBoss and Tomcat but failed in Glassfish. It complains that the jndi name pattern is not set when initializing the SeamListener. Could this be an issue with the JSF RI? Here is the stack trace: You must specify org.jboss.seam.core.init.jndiPattern or use @JndiName: login at org.jboss.seam.Component.getJndiName(Component.java:344) at org.jboss.seam.Component.<init>(Component.java:220) at org.jboss.seam.Component.<init>(Component.java:205) at org.jboss.seam.init.Initialization.addComponent(Initialization.java:735) at org.jboss.seam.init.Initialization.addComponents(Initialization.java:667) at org.jboss.seam.init.Initialization.init(Initialization.java:419) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4236) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4760) at com.sun.enterprise.web.WebModule.start(WebModule.java:292) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:833) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:817) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:662) at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1479) at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1143) at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:171) at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:275) at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:954) at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:941) at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:448) at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:160) at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:296) at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:203) at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:285) at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:119) at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:95) at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:871) at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:541) at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:585) at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:719) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:353) at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:336) at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:448) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784) at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:77) at $Proxy1.invoke(Unknown Source) at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:297) at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:133) at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:517) at java.lang.Thread.run(Thread.java:613) -- 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

18 years, 2 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2007