April 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3568) Jee5 example doesn't work on WAS 6.1 without workaround

by Marek Novotny (JIRA)

Jee5 example doesn't work on WAS 6.1 without workaround ------------------------------------------------------- Key: JBSEAM-3568 URL: https://jira.jboss.org/jira/browse/JBSEAM-3568 Project: Seam Issue Type: Bug Environment: java 5, WAS 6.1.0.19 Reporter: Marek Novotny Fix For: 2.1.1.CR1 After customizing JEE5 example to WAS 6.1 and deploying on server, application doesn't work and in log is exception: [15.10.08 16:29:38:899 SELČ] 00000021 WebApp E Exception caught while initializing context com.sun.faces.config.ConfigurationException: It appears the JSP version of the container is older than 2.1 and unable to locate the EL RI expression factory, com.sun.el.ExpressionFactoryImpl. If not using JSP or the EL RI, make sure the context initialization parameter, com.sun.faces.expressionFactory, is properly set. at com.sun.faces.config.ConfigureListener.registerELResolverAndListenerWithJsp(ConfigureListener.java:545) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:211) at com.ibm.ws.wswebcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:916) at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:350) at com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:337) at com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:92) at com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157) at com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:666) at com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:619) at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:395) at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:611) at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1304) at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1165) at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:587) at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:832) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:950) at com.ibm.ws.runtime.component.ApplicationMgrImpl$1.run(ApplicationMgrImpl.java:1495) at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:4104) at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:4202) at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:245) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:1500) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:62) at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:265) at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1089) at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:971) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:231) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:238) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:802) at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1082) at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118) at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:975) at com.ibm.ws.management.application.sync.StartDeploymentTask.startDeployment(StartDeploymentTask.java:196) at com.ibm.ws.management.application.sync.StartDeploymentTask.fullAppUpdate(StartDeploymentTask.java:92) at com.ibm.ws.management.application.sync.StartDeploymentTask.performTask(StartDeploymentTask.java:81) at com.ibm.ws.management.application.sync.AppBinaryProcessor$AppBinThread.run(AppBinaryProcessor.java:896) at com.ibm.ws.management.application.sync.AppBinaryProcessor.postProcess(AppBinaryProcessor.java:633) at com.ibm.ws.management.application.sync.AppBinaryProcessor._onChangeCompletion(AppBinaryProcessor.java:441) at com.ibm.ws.management.application.sync.AppBinaryProcessor$2.run(AppBinaryProcessor.java:413) at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118) at com.ibm.ws.management.application.sync.AppBinaryProcessor.onChangeCompletion(AppBinaryProcessor.java:400) at com.ibm.ws.management.repository.FileRepository.postNotify(FileRepository.java:1776) at com.ibm.ws.management.repository.FileRepository.update(FileRepository.java:1320) at com.ibm.ws.management.repository.client.LocalConfigRepositoryClient.update(LocalConfigRepositoryClient.java:189) at com.ibm.ws.sm.workspace.impl.WorkSpaceMasterRepositoryAdapter.update(WorkSpaceMasterRepositoryAdapter.java:637) at com.ibm.ws.sm.workspace.impl.RepositoryContextImpl.update(RepositoryContextImpl.java:1882) at com.ibm.ws.sm.workspace.impl.RepositoryContextImpl.synch(RepositoryContextImpl.java:1829) at com.ibm.ws.sm.workspace.impl.WorkSpaceImpl.synch(WorkSpaceImpl.java:479) at com.ibm.ws.console.core.action.SyncWorkSpaceAction.execute(SyncWorkSpaceAction.java:239) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1486) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:510) at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1097) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1038) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145) at com.ibm.ws.console.core.servlet.WSCUrlFilter.setUpCommandAssistence(WSCUrlFilter.java:792) at com.ibm.ws.console.core.servlet.WSCUrlFilter.continueStoringTaskState(WSCUrlFilter.java:363) at com.ibm.ws.console.core.servlet.WSCUrlFilter.doFilter(WSCUrlFilter.java:229) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130) at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:834) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:682) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:566) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:486) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3440) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:815) at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1461) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:118) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473) -- 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, 5 months

5
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3750) CHART : only display a couple of label on x-axis instead of all

by yan langlois (JIRA)

CHART : only display a couple of label on x-axis instead of all --------------------------------------------------------------- Key: JBSEAM-3750 URL: https://jira.jboss.org/jira/browse/JBSEAM-3750 Project: Seam Issue Type: Feature Request Components: PDF Reporter: yan langlois It would be great to have the possibility to diplay only a couple of label on a chart (x-axis). for example : display months instead of days (like in this chart : http://www.jfree.org/jfreechart/images/PriceVolumeDemo1.png) -- 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, 5 months

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3615) Test seam-gen against a full real world database model

by Francisco Jose Peredo Noguez (JIRA)

Test seam-gen against a full real world database model ------------------------------------------------------ Key: JBSEAM-3615 URL: https://jira.jboss.org/jira/browse/JBSEAM-3615 Project: Seam Issue Type: Feature Request Reporter: Francisco Jose Peredo Noguez Test seam-gen against a full real world database model, so reduce its shortcomings (recursion, inheritance, complex primary keys,etc) in an easier way. I propose the use of the models in The Data Model Resource Book, Vol. 1 (http://www.amazon.com/gp/product/0471380237) or in The Data Model Resource Book, Vol. 2 (http://www.amazon.com/Data-Model-Resource-Book-Vol/dp/0471353485). -- 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, 5 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3475) Seamspace example - InvalidStateException at friend request

by Jozef Hartinger (JIRA)

Seamspace example - InvalidStateException at friend request ----------------------------------------------------------- Key: JBSEAM-3475 URL: https://jira.jboss.org/jira/browse/JBSEAM-3475 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.CR1 Environment: JDK 5, 6 JBoss AS 4.2.3 Reporter: Jozef Hartinger I am getting InvalidStateException when trying to submit an introduction message at friend request. -- 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, 5 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1572) Make s:decorate behave more similarly to ui:decorate (h:panelGrid-friendly)

by Alex Savitsky (JIRA)

Make s:decorate behave more similarly to ui:decorate (h:panelGrid-friendly) --------------------------------------------------------------------------- Key: JBSEAM-1572 URL: http://jira.jboss.com/jira/browse/JBSEAM-1572 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Alex Savitsky Priority: Minor ui:decorate preserves its children, while s:decorate groups them as one instead. This makes s:decorate unusable for form fields laid out using h:panelGrid, as there's no way to separate the field label from the field itself (they are grouped together). -- 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, 5 months

9
23
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3710) For JavaBeans, investigate moving MEI functionality into @PostActivte/@PrePassivate

by Pete Muir (JIRA)

For JavaBeans, investigate moving MEI functionality into @PostActivte/@PrePassivate ----------------------------------------------------------------------------------- Key: JBSEAM-3710 URL: https://jira.jboss.org/jira/browse/JBSEAM-3710 Project: Seam Issue Type: Feature Request Components: Core Reporter: Pete Muir Priority: Critical Fix For: 2.1.1.CR2 This is possible only in JavaBeans as the HttpSession is passed as an arguement to the sessionWillPassivate/sessionWillActivate call, and we can store the conversationId in @AroundInvoke method. In EJBs, the passivation/activation happens independently of the HttpSession. This should be a performance improvement, @PrePassivate (serialize out entities) will be called just as much, but @PostActivate will be called a lot less. -- 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, 5 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2093) Optimize getting Id in Seam code for better performance

by Mikhail Grushinskiy (JIRA)

Optimize getting Id in Seam code for better performance ------------------------------------------------------- Key: JBSEAM-2093 URL: http://jira.jboss.com/jira/browse/JBSEAM-2093 Project: JBoss Seam Issue Type: Feature Request Reporter: Mikhail Grushinskiy This sequence of calls (used in PersistenceProvider) is quite slow Entity.forClass(bean.getClass()).getIdentifier(bean); 1) Entity.forClass() is reading annotations using JDK 5 methods (JDK 5 annotation reading is not that fast). Can it be cached? 2) JDK 5 reflection is used to get bean id (which is slower than optmized reflection with cglib) 3) There could be other reasons as well. I think repetitive calling of this sequence under profiler will give better picture. from PersistenceProvider.java /** * Get the value of the entity identifier attribute. * * @param bean a managed entity instance */ public Object getId(Object bean, EntityManager entityManager) { return Entity.forClass( bean.getClass() ).getIdentifier(bean); } /** * Get the name of the entity * * @param bean * @param entityManager */ public String getName(Object bean, EntityManager entityManager) { return Entity.forClass(bean.getClass()).getName(); } /** * Get the value of the entity version attribute. * * @param bean a managed entity instance */ public Object getVersion(Object bean, EntityManager entityManager) { return Entity.forClass( bean.getClass() ).getVersion(bean); } -- 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, 5 months

7
18
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4067) ELSupport.coerceToType modifies BigDecimal Values

by Pete Muir (JIRA)

ELSupport.coerceToType modifies BigDecimal Values ---------------------------------------------------- Key: JBSEAM-4067 URL: https://jira.jboss.org/jira/browse/JBSEAM-4067 Project: Seam Issue Type: Bug Components: EL Reporter: Pete Muir Assignee: Norman Richards Priority: Critical See https://issues.apache.org/bugzilla/show_bug.cgi?id=43656 -- 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, 6 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4078) Jar locking during of component initialization on Windows

by Andrey Lomakin (JIRA)

Jar locking during of component initialization on Windows --------------------------------------------------------- Key: JBSEAM-4078 URL: https://jira.jboss.org/jira/browse/JBSEAM-4078 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Environment: Windows 2000, Java(TM) SE Runtime Environment (build 1.6.0_13-b03), GlassFish v3 Prelude (build b28c) Reporter: Andrey Lomakin JARs that contain components.xml are locked till server shutdown and can not be removed after application undeploy on Windows. As I understend following snippet of code in method org.jboss.seam.init.Initialization#initComponentsFromXmlDocuments: InputStream stream = url.openStream(); log.debug("reading " + url); try { installComponentsFromXmlElements(XML.getRootElement(stream), replacements); } finally { Resources.closeStream(stream); } should be replaced by URLConnection connection = url.openConnection(); connection.setUseCaches(false); InputStream stream = url.openStream(); // and so on... If cashes will not be switched of file will be opened but never closed. Returned instance of InputStream interface is sun.net.www.protocol.jar.JarURLConnection,JarURLInputStream that closes opened jar file only if cashes are not used. class JarURLInputStream extends java.io.FilterInputStream { 103 JarURLInputStream (InputStream src) { 104 super (src); 105 } 106 public void close () throws IOException { 107 try { 108 super.close(); 109 } finally { 110 if (!getUseCaches()) { 111 jarFile.close(); 112 } 113 } 114 } 115 } -- 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, 6 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4028) way to outject someting in to the CURRENT conversation even if a new one is started before the context is flushed

by David Schlotfeldt (JIRA)

way to outject someting in to the CURRENT conversation even if a new one is started before the context is flushed ----------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4028 URL: https://jira.jboss.org/jira/browse/JBSEAM-4028 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.2.GA Reporter: David Schlotfeldt If you outject and then create a new nested conversation the outjected variable ends up in the nested conversation. This is because ServerConversatoinContext keeps the "additions" to it separate from the actual context variables -- just in the case it needs to "rollback". When the render response phase takes place ServerConversationContext "commits" the new additions. The "key" of each addition is determined at that time. The key of entries is prefixed with the conversation id to allow Seam to determine what conversation it is for. It would be nice if when one could outject the variable into the conversation that was current when it was outjected. This could easily be done by storing the conversation id that was current in the "additions" information and using it instead of the current conversation id when flushed. This of course is a change that could cause many issues for people so I propose an attribute is added to @Out called "conversation-at-flush=[true|false]" with the default value of true. If you want the outject to be in the converation current when outjected you set this attribute to false. Just to point out an issue I could see happen if not kept in mind when implementing: A nested conversation could in theory start, things outjected, and then the nested conversation ended before flush takes place. When flush does happen we need to filter out those outjects from the nested conversation that had conversation-at-flush=false since that conversation was ended. This simply means checking the conversation id is still active before making the addition/removal. -- 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, 6 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2009