December 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1745) SpringTransaction fails with HibernateJpaDialect and FlushMode.MANUAL

by Darryl Smith (JIRA)

SpringTransaction fails with HibernateJpaDialect and FlushMode.MANUAL ---------------------------------------------------------------------- Key: JBSEAM-1745 URL: http://jira.jboss.com/jira/browse/JBSEAM-1745 Project: JBoss Seam Issue Type: Bug Components: Spring Reporter: Darryl Smith When using flushMode = MANUAL with org.springframework.orm.jpa.vendor.HibernateJpaDialect, the flushMode is changed to AUTO when beginning transaction SessionImpl.setFlushMode(FlushMode) line: 1286 HibernateSessionProxy.setFlushMode(FlushMode) line: 381 SeamHibernateJpaDialect(HibernateJpaDialect).beginTransaction(EntityManager, TransactionDefinition) line: 60 JpaTransactionManager.doBegin(Object, TransactionDefinition) line: 326 JpaTransactionManager(AbstractPlatformTransactionManager).getTransaction(TransactionDefinition) line: 350 SpringTransaction.begin() line: 74 Unless the transaction definition is set to readOnly spring will change the flushMode to manual HibernateJpaDialect:45 -------------------------------- public Object beginTransaction(EntityManager entityManager, TransactionDefinition definition) throws PersistenceException, SQLException, TransactionException { super.beginTransaction(entityManager, definition); Session session = getSession(entityManager); FlushMode flushMode = session.getFlushMode(); FlushMode previousFlushMode = null; if (definition.isReadOnly()) { // We should suppress flushing for a read-only transaction. session.setFlushMode(FlushMode.MANUAL); previousFlushMode = flushMode; } else { // We need AUTO or COMMIT for a non-read-only transaction. if (flushMode.lessThan(FlushMode.COMMIT)) { session.setFlushMode(FlushMode.AUTO); previousFlushMode = flushMode; } } return new SessionTransactionData(session, previousFlushMode); } Perhaps SpringTransaction should set should pass readOnly transaction def to Spring when the flushMode is manual. Current Workaround: use DefaultJpaDialect -- 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

16 years, 7 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2423) checkEntityPermission only checks one method

by Andrew (JIRA)

checkEntityPermission only checks one method -------------------------------------------- Key: JBSEAM-2423 URL: http://jira.jboss.com/jira/browse/JBSEAM-2423 Project: JBoss Seam Issue Type: Bug Components: Security Affects Versions: 2.0.1.CR1 Environment: JPA on tomcat6 Reporter: Andrew Priority: Critical If an entity has more than one method marked as @PrePersist, only one method is used to check for security. All methods should be considered and the result "anded" together. Code in the Identity bean only checks for a @Restrict on the first method found. In my case, I extend an object with a @PrePersist with no @Restrict. My entity has a method: @PrePersist @PreUpdate @PreRemove @Restrict public void beforeChange() {} (everything is restricted except for read access) According to the PrePersist documentation, multiple PrePersist methods are valid. There are workarounds, but this is dangerous code. If it were not for my unit tests it could have slipped through. The seam documentation does not mention this limitation I marked this as critical as it creates security holes in the application. Here is the relevant code: public void checkEntityPermission(Object entity, EntityAction action) { isLoggedIn(true); PersistenceProvider provider = PersistenceProvider.instance(); Class beanClass = provider.getBeanClass(entity); if (beanClass != null) { String name = Seam.getComponentName(entity.getClass()); if (name == null) name = beanClass.getName(); Method m = null; switch (action) { case READ: m = provider.getPostLoadMethod(beanClass); break; case INSERT: m = provider.getPrePersistMethod(beanClass); break; case UPDATE: m = provider.getPreUpdateMethod(beanClass); break; case DELETE: m = provider.getPreRemoveMethod(beanClass); } Restrict restrict = null; if (m != null && m.isAnnotationPresent(Restrict.class)) { restrict = m.getAnnotation(Restrict.class); } else if (entity.getClass().isAnnotationPresent(Restrict.class)) { restrict = entity.getClass().getAnnotation(Restrict.class); } if (restrict != null) { if (Strings.isEmpty(restrict.value())) { checkPermission(name, action.toString(), entity); } else { checkRestriction(restrict.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

16 years, 7 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-866) Ajax4JSF integration for Wiki

by Gavin King (JIRA)

Ajax4JSF integration for Wiki ----------------------------- Key: JBSEAM-866 URL: http://jira.jboss.com/jira/browse/JBSEAM-866 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Gavin King The following features should use Ajax4JSF instead of navigation or full page submits. * Preview panel should be dynamically rendered as user types in the edit box * Edit page and edit directory should use an ajax include instead of navigation * The operations in the edit directory box should use partial submit/render * Login should be implemented using a partial submit/render -- 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

16 years, 7 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2386) pages.xml redirect should accept plain URLs

by Christian Bauer (JIRA)

pages.xml redirect should accept plain URLs ------------------------------------------- Key: JBSEAM-2386 URL: http://jira.jboss.com/jira/browse/JBSEAM-2386 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Christian Bauer Priority: Minor Instead of: <rule if-outcome="redirectToDocument"> <redirect view-id="/wiki.xhtml"> <param name="nodeId" value="#{documentHome.instance.id}"/> </redirect> </rule> I'd like to be able to do: <rule if-outcome="redirectToDocument"> <redirect url="#{wiki:renderURL(documentHome.instance)}"/> </rule> which would give me a nice URL without rewriting acrobatics. -- 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

16 years, 7 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2291) Hot deploy pages.xml

by Pete Muir (JIRA)

Hot deploy pages.xml -------------------- Key: JBSEAM-2291 URL: http://jira.jboss.com/jira/browse/JBSEAM-2291 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.GA Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.0.1.GA Ability to hot deploy pages.xml and *.page.xml -- 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

16 years, 7 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1591) Redo ui example as a 'real life' example

by Pete Muir (JIRA)

Redo ui example as a 'real life' example ---------------------------------------- Key: JBSEAM-1591 URL: http://jira.jboss.com/jira/browse/JBSEAM-1591 Project: JBoss Seam Issue Type: Feature Request Components: Examples Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir Assigned To: Pete Muir Lets have an example that has a purpose, rather than some mismash of control demonstrations. 80% of it is about a person and their interests, so lets build some sort of 'My Profile' app (very simple, no security etc.) - maybe a registration2 app? -- 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

16 years, 7 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1416) Make it clear in the documentation that Session scope concurrency is only handled when interception is enabled

by Mike Quilleash (JIRA)

Make it clear in the documentation that Session scope concurrency is only handled when interception is enabled -------------------------------------------------------------------------------------------------------------- Key: JBSEAM-1416 URL: http://jira.jboss.com/jira/browse/JBSEAM-1416 Project: JBoss Seam Issue Type: Task Components: Documentation Affects Versions: 1.2.1.GA Environment: Any Reporter: Mike Quilleash The concurrency section of the documentation says that seam automatically makes session scoped components threadsafe. Quote: Since the session context is multithreaded, and often contains volatile state, session scope components are always protected by Seam from concurrent access. However the implementation of this uses an interceptor so components that disable interception (InterceptionType.NEVER) will not benefit from this and threadsafety will have to be built into the component itself. This should be documented as the above states that they are ALWAYS protected. -- 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

16 years, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2042) quartz example doesn't report errors

by Norman Richards (JIRA)

quartz example doesn't report errors ------------------------------------ Key: JBSEAM-2042 URL: http://jira.jboss.com/jira/browse/JBSEAM-2042 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.0.CR1 Reporter: Norman Richards Priority: Minor Fix For: 2.0.1.GA It would be nice if we could capture/report scheduler errors. In this case I accidentally entered the 12th business day of the week. 10:27:31,007 ERROR [STDERR] org.quartz.SchedulerException: Based on configured schedule, the given trigger will never fire. 10:27:31,008 ERROR [STDERR] at org.quartz.core.QuartzScheduler.scheduleJob(QuartzScheduler.java:698) 10:27:31,008 ERROR [STDERR] at org.quartz.impl.StdScheduler.scheduleJob(StdScheduler.java:255) 10:27:31,008 ERROR [STDERR] at org.jboss.seam.async.QuartzDispatcher.scheduleWithQuartzService(QuartzDispatcher.java:218) 10:27:31,008 ERROR [STDERR] at org.jboss.seam.async.QuartzDispatcher.scheduleInvocation(QuartzDispatcher.java:125) 10:27:31,008 ERROR [STDERR] at org.jboss.seam.async.QuartzDispatcher.scheduleInvocation(QuartzDispatcher.java:45) 10:27:31,008 ERROR [STDERR] at org.jboss.seam.async.AsynchronousInterceptor.aroundInvoke(AsynchronousInterceptor.java:38) 10:27:31,008 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) 10:27:31,008 ERROR [STDERR] at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106) 10:27:31,008 ERROR [STDERR] at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:155) 10:27:31,008 ERROR [STDERR] at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:91) 10:27:31,008 ERROR [STDERR] at org.jboss.seam.example.quartz.PaymentProcessor_$$_javassist_4.schedulePayment(PaymentProcessor_$$_javassist_4.java) 10:27:31,009 ERROR [STDERR] at org.jboss.seam.example.quartz.PaymentController.saveAndScheduleNthBusinessDay(PaymentController.java:68) 10:27:31,009 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 10:27:31,009 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 10:27:31,009 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 10:27:31,009 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) 10:27:31,009 ERROR [STDERR] at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) 10:27:31,009 ERROR [STDERR] at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) 10:27:31,009 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) 10:27:31,009 ERROR [STDERR] at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:46) 10:27:31,009 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) 10:27:31,009 ERROR [STDERR] at org.jboss.seam.persistence.ManagedEntityIdentityInterceptor.aroundInvoke(ManagedEntityIdentityInterceptor.java:48) 10:27:31,009 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) 10:27:31,009 ERROR [STDERR] at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31) 10:27:31,009 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) 10:27:31,009 ERROR [STDERR] at org.jboss.seam.transaction.TransactionInterceptor$1.work(TransactionInterceptor.java:38) 10:27:31,009 ERROR [STDERR] at org.jboss.seam.util.Work.workInTransaction(Work.java:40) 10:27:31,009 ERROR [STDERR] at org.jboss.seam.transaction.TransactionInterceptor.aroundInvoke(TransactionInterceptor.java:32) 10:27:31,009 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) 10:27:31,009 ERROR [STDERR] at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) 10:27:31,010 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) 10:27:31,010 ERROR [STDERR] at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106) 10:27:31,010 ERROR [STDERR] at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:155) 10:27:31,010 ERROR [STDERR] at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:91) 10:27:31,010 ERROR [STDERR] at org.jboss.seam.example.quartz.PaymentController_$$_javassist_3.saveAndScheduleNthBusinessDay(PaymentController_$$_javassist_3.java) 10:27:31,010 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 10:27:31,010 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 10:27:31,010 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 10:27:31,010 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) 10:27:31,010 ERROR [STDERR] at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:328) 10:27:31,010 ERROR [STDERR] at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:341) 10:27:31,010 ERROR [STDERR] at org.jboss.el.parser.AstPropertySuffix.invoke(AstPropertySuffix.java:58) 10:27:31,010 ERROR [STDERR] at org.jboss.el.parser.AstValue.invoke(AstValue.java:96) 10:27:31,010 ERROR [STDERR] at org.jboss.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) 10:27:31,010 ERROR [STDERR] at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68) 10:27:31,010 ERROR [STDERR] at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:77) 10:27:31,010 ERROR [STDERR] at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) 10:27:31,010 ERROR [STDERR] at javax.faces.component.UICommand.broadcast(UICommand.java:383) 10:27:31,010 ERROR [STDERR] at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:447) 10:27:31,010 ERROR [STDERR] at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752) 10:27:31,011 ERROR [STDERR] at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97) 10:27:31,011 ERROR [STDERR] at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) 10:27:31,011 ERROR [STDERR] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) 10:27:31,011 ERROR [STDERR] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) 10:27:31,011 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) 10:27:31,011 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 10:27:31,011 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) 10:27:31,011 ERROR [STDERR] at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) 10:27:31,011 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) 10:27:31,011 ERROR [STDERR] at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) 10:27:31,011 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) 10:27:31,011 ERROR [STDERR] at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) 10:27:31,011 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) 10:27:31,011 ERROR [STDERR] at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) 10:27:31,011 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) 10:27:31,011 ERROR [STDERR] at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:44) 10:27:31,011 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) 10:27:31,011 ERROR [STDERR] at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:150) 10:27:31,011 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) 10:27:31,012 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 10:27:31,012 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) 10:27:31,012 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) 10:27:31,012 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 10:27:31,012 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) 10:27:31,012 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) 10:27:31,012 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) 10:27:31,012 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) 10:27:31,012 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) 10:27:31,012 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) 10:27:31,012 ERROR [STDERR] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) 10:27:31,012 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) 10:27:31,012 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) 10:27:31,012 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) 10:27:31,012 ERROR [STDERR] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) 10:27:31,012 ERROR [STDERR] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) 10:27:31,012 ERROR [STDERR] 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

16 years, 8 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2374) Update to latest Trinidad version in seamdiscs example.

by Alexander Seitz (JIRA)

Update to latest Trinidad version in seamdiscs example. ------------------------------------------------------- Key: JBSEAM-2374 URL: http://jira.jboss.com/jira/browse/JBSEAM-2374 Project: JBoss Seam Issue Type: Task Components: Examples Affects Versions: 2.0.0.GA Reporter: Alexander Seitz Priority: Minor It would be nice to update the seamdiscs example to the latest version of Trinidad (1.2.4). The benefit would be that it supports ajax-based sorting and paging so only the table is reloaded on this events and not the complete page. I tried it for my own, it works so far but when using the latest Trinidad 1.2.4 libs I get the following errors: 2007-12-13 11:29:23,574 ERROR [STDERR] 13.12.2007 11:29:23 org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderKit createResponseWriter SCHWERWIEGEND: No RenderingContext has been created. Also, lazy loading for Richfaces tables would be nich ;-) -- 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

16 years, 8 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2046) Seam allows out of date pages.xml schema

by Stuart Douglas (JIRA)

Seam allows out of date pages.xml schema ---------------------------------------- Key: JBSEAM-2046 URL: http://jira.jboss.com/jira/browse/JBSEAM-2046 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Stuart Douglas Priority: Minor Seam does not provide any notification when an out of date schema or DTD is used in pages.xml, the file is transparently downloaded from the jboss website with every time a page is viewed, resulting in a major performance degradation. Seam should provide some indication to the developer that this is happening (probably throw an exception, I cannot think of any use case where you would want this behavior ). -- 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

16 years, 8 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2007