July 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1608) Seam application can not start because of faces-config configuration in seam-ui.jar

by Joshua Jackson (JIRA)

Seam application can not start because of faces-config configuration in seam-ui.jar ------------------------------------------------------------------------------------ Key: JBSEAM-1608 URL: http://jira.jboss.com/jira/browse/JBSEAM-1608 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.0.BETA1 Environment: Glassfish build b53-rc Reporter: Joshua Jackson Fix For: 2.0.0.CR1 Here is the stacktrace: Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener javax.faces.FacesException: Can't parse configuration file: jar:file:/D:/javastuff/glassfish/domains/domain1/applications/j2ee-apps/seam/seam_war/WEB-INF/lib/jboss-seam-ui.jar!/META-INF/faces-config.xml: Error at line 12 column 18: The content of element type "validator" must match "(description*,display-name*,icon*,validator-id,validator-class,attribute*,property*)". at com.sun.faces.config.ConfigureListener.parse(ConfigureListener.java:1438) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:348) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4515) at org.apache.catalina.core.StandardContext.start(StandardContext.java:5176) at com.sun.enterprise.web.WebModule.start(WebModule.java:324) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:973) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:957) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:688) at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1576) at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1217) at com.sun.enterprise.web.WebContainer.loadJ2EEApplicationWebModules(WebContainer.java:1142) at com.sun.enterprise.server.TomcatApplicationLoader.doLoad(TomcatApplicationLoader.java:141) at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:243) at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:336) at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:210) at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:645) at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:918) at com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:902) at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:458) at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:173) at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308) at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:223) at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298) at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132) at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108) at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:905) at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:577) at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:621) at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:744) 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:375) at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:358) at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:464) 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.GeneratedMethodAccessor17.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:90) at $Proxy1.invoke(Unknown Source) at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304) at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174) at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:145) at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:537) at java.lang.Thread.run(Thread.java:595) -- 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

17 years, 5 months

5
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1607) s:graphicImage should use a more unique URL

by Shane Bryzak (JIRA)

s:graphicImage should use a more unique URL ------------------------------------------- Key: JBSEAM-1607 URL: http://jira.jboss.com/jira/browse/JBSEAM-1607 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.0.BETA1 Reporter: Shane Bryzak Assigned To: Pete Muir When using s:graphicImage the image URL looks something like this: /seam/resource/graphicImage/org.jboss.seam.ui.GraphicImageStore.41.png The problem here is that when the container is restarted, the index is reset to 0 which means that browsers may use a cached version of a previously loaded image (which may be the wrong image). I suggest that we use a UID value for this instead to guarantee uniqueness. -- 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

17 years, 5 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1744) s:convertEntity fails with an java.lang.IllegalArgumentException: Unknown entity: my.Entity_$$_javassist_3

by Matthias M. (JIRA)

s:convertEntity fails with an java.lang.IllegalArgumentException: Unknown entity: my.Entity_$$_javassist_3 ---------------------------------------------------------------------------------------------------------- Key: JBSEAM-1744 URL: http://jira.jboss.com/jira/browse/JBSEAM-1744 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Environment: EJB3, Seam 2.0.0.BETA1, Hibernate Reporter: Matthias M. <s:convertEntity/> fails on 'getAsObject' with an IllegalArgumentException The code which is responsible for this bug is identified : The method forClass(...) returns a new Entity with the given parameter set - should be the correctly resolved 'entityClass'. <code> public class Entity extends Model { .......... public static Entity forClass(Class clazz) { if ( !Contexts.isApplicationContextActive() ) { throw new IllegalStateException("No application context active"); } Class entityClass = Seam.getEntityClass(clazz); if (entityClass==null) { throw new IllegalArgumentException("Not an entity class: " + clazz.getName()); } String name = getModelName(entityClass); Model model = (Model) Contexts.getApplicationContext().get(name); if ( model==null || !(model instanceof Entity) ) { Entity entity = new Entity(clazz); Contexts.getApplicationContext().set(name, entity); return entity; } else { return (Entity) model; } } ............. </code> -- 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

17 years, 5 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1538) BaseSeamTest should not be dependant on JBoss Embedded

by Darryl Smith (JIRA)

BaseSeamTest should not be dependant on JBoss Embedded ------------------------------------------------------ Key: JBSEAM-1538 URL: http://jira.jboss.com/jira/browse/JBSEAM-1538 Project: JBoss Seam Issue Type: Feature Request Components: Test Harness Affects Versions: 1.3.0.ALPHA Reporter: Darryl Smith With the addition of EntityTransaction and HibernateTransaction BaseSeamTest should support environments where JBoss Embedded is not present. -- 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

17 years, 5 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1740) Still has dependencies on Sun's EL RI, breaks security checks

by None None (JIRA)

Still has dependencies on Sun's EL RI, breaks security checks ------------------------------------------------------------- Key: JBSEAM-1740 URL: http://jira.jboss.com/jira/browse/JBSEAM-1740 Project: JBoss Seam Issue Type: Bug Components: EL Affects Versions: 1.2.1.GA Environment: JBoss AS 4.2.1 Reporter: None None Seam 1.2.1 is supposed to not have dependencies on the Sun EL reference implementation. In fact they do depend: org.jboss.seam.util.EL and org.jboss.seam.jsf.SeamELFunctionMapper include the Sun packages. Strangely enough, the entire system works without the Sun JARs until it gets to a security check, like s:hasRole, in a @Restrict annotation. This means that the entire security system isn't usable in this environment. The solution is to remove those dependencies. I think there should be a patch release for this; this is a fatal problem to any app which requires those security restrictions, and probably is not difficult to fix. What is strange is that all the rest of EL is working, so this small bit of code is only triggering during security checks. -- 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

17 years, 5 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1728) Missing HTMLLink source code from jboss-seam-2.0.0.BETA1 package

by Wise Guy (JIRA)

Missing HTMLLink source code from jboss-seam-2.0.0.BETA1 package ---------------------------------------------------------------- Key: JBSEAM-1728 URL: http://jira.jboss.com/jira/browse/JBSEAM-1728 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.BETA1 Environment: jboss-seam-2.0.0.BETA1 Reporter: Wise Guy I had to debug the HtmlLink class and couldn't find the source code. Obviously previous version of the archive contain the file while the BETA1 contains the doc. A search for HtmlLink in my Seam folder returns: HtmlLink.java -> jboss-seam-1.2.1.GA\src\ui\org\jboss\seam\ui HtmlLink.java -> jboss-seam-1.3.0.ALPHA\src\ui\org\jboss\seam\ui HtmlLink.html -> jboss-seam-2.0.0.BETA1\doc\ui\apidocs\org\jboss\seam\ui\component\html HtmlLink.html -> jboss-seam-2.0.0.BETA1\doc\ui\apidocs\org\jboss\seam\ui\component\html\class-use Is this supposed to be like that? -- 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

17 years, 5 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1684) Clean up icefaces stuff in the seam-gen build

by Gavin King (JIRA)

Clean up icefaces stuff in the seam-gen build --------------------------------------------- Key: JBSEAM-1684 URL: http://jira.jboss.com/jira/browse/JBSEAM-1684 Project: JBoss Seam Issue Type: Task Components: Tools Affects Versions: 2.0.0.CR1 Reporter: Gavin King Priority: Blocker Fix For: 2.0.0.CR1 The ICEFaces patch to the build script contains a bunch of useless targets like icefacesCheck, check-icefaces, cond-if, cond-else with log messages in broken english. Also, icefaces war projects are broken, since the correct build.xml does not get copied. Also, we now have *four* copies of the project build script to maintain. What a mess! -- 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

17 years, 5 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1450) Pass Quartz Triggers directly in @Asynchronous methods

by Michael Yuan (JIRA)

Pass Quartz Triggers directly in @Asynchronous methods ------------------------------------------------------ Key: JBSEAM-1450 URL: http://jira.jboss.com/jira/browse/JBSEAM-1450 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Michael Yuan Assigned To: Michael Yuan Fix For: 1.3.0.BETA1 We should write a QuartzTriggerSchedule class to wrap a Quartz Trigger. It would allow the user to build their own triggers and then use @Trigger trigger to pass to a async method. We can provide that in addition to the current support for fixed interval and cron jobs. -- 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

17 years, 5 months

4
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1736) WS and seam:conversationId

by Stefano Zaccaria (JIRA)

WS and seam:conversationId -------------------------- Key: JBSEAM-1736 URL: http://jira.jboss.com/jira/browse/JBSEAM-1736 Project: JBoss Seam Issue Type: Bug Components: WS Affects Versions: 2.0.0.BETA1 Environment: Windows Vista, JBOSS 4.2.0 and SEAM 2.0.0.BETA1 Reporter: Stefano Zaccaria Fix For: 2.0.0.CR1 After had worked with JBSEAM-1714 issue, now I'm trying the web service with gSOAP client. Of that thanks still Shane e Gavin! It work well until I trying to read the "conversationId" from the header message SOAP. In fact the gSOAP reject the tag "seam:conversationId" at runtime so I couldn't read it. I create the gSOAP webservice client through the WSDL generate from JBOSSWS, and I've noticed that there isn't a description about header. Maybe this could be the problem. In the seam reference in the chapter 20 is wrote: "Unfortunately, because web services may be consumed by a variety of web service clients written in a variety of languages, it is up to the developer to implement conversation ID propagation between individual web services that are intended to be used within the scope of a single conversation. JBoss" Now I understand that I duty management my self this parameter, but I want to know how to describe it in the WDSL generated. Thanks! -- 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

17 years, 5 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1732) File download dialog (providing source) instead of a page

by Stephan Heffner (JIRA)

File download dialog (providing source) instead of a page --------------------------------------------------------- Key: JBSEAM-1732 URL: http://jira.jboss.com/jira/browse/JBSEAM-1732 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.2.1.GA Environment: AS 4.0.5.GA + EJB 3, Seam 1.2.1.GA Firefox 2 (Linux, Mac & Windows) IE 7 (XP SP 2) Reporter: Stephan Heffner Sometimes after a restart of the JBoss Server, accessing our Seam based application results in a file download dialog instead of the redirection to the login page. Restarting the server again solved this usually. To get a better understanding whats going on, I activated Charles in my Firefox and get the attached session Infos. The redirect happens and the page data will be send, but the last response is this: <!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:s="http://jboss.com/products/seam/taglib" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html" xmlns:rich="http://richfaces.ajax4jsf.org/rich" template="layout/template_no_sidebar.xhtml"> <ui:define name="main"> <h:form id="login"> <rich:panel styleClass="loginPanel"> <f:facet name="header">Login</f:facet> <p>Bitte melden Sie Sich an:</p> <s:decorate template="/layout/display.xhtml"> <ui:define name="label">Username</ui:define> <h:inputText id="username" value="#{identity.username}"/> </s:decorate> <s:decorate template="/layout/display.xhtml"> <ui:define name="label">Passwort</ui:define> <h:inputSecret id="password" value="#{identity.password}"/> </s:decorate> <s:decorate template="/layout/display.xhtml"> <ui:define name="label"></ui:define> <h:selectBooleanCheckbox id="rememberMe" value="#{identity.rememberMe}"/> <h:outputLabel for="rememberMe">Auf diesem Computer merken</h:outputLabel> </s:decorate> <div class="actionButtons"> <h:commandButton value="Login" action="#{identity.login}"/> </div> </rich:panel> </h:form> </ui:define> </ui:composition> As you can see, the server sends the source instead of a rendered page. Any ideas what's going on? Stephan -- 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

17 years, 5 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2007