December 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2160) seam-gen templates use a mix of tabs and spaces

by Gavin King (JIRA)

seam-gen templates use a mix of tabs and spaces ----------------------------------------------- Key: JBSEAM-2160 URL: http://jira.jboss.com/jira/browse/JBSEAM-2160 Project: JBoss Seam Issue Type: Task Components: Tools Affects Versions: 2.0.0.GA Reporter: Gavin King Priority: Minor We need to pick one, and use it consistently in all templates. -- 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, 5 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2350) Content Compression with GWTService overriding Container (tomcat/jetty)

by darren hartford (JIRA)

Content Compression with GWTService overriding Container (tomcat/jetty) ----------------------------------------------------------------------- Key: JBSEAM-2350 URL: http://jira.jboss.com/jira/browse/JBSEAM-2350 Project: JBoss Seam Issue Type: Task Environment: jboss 4.2.1, Seam 2.0.0.GA (GWT 1.4.60) Reporter: darren hartford See forum reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110587 The GWTService class is doing Content Compression/HTTP. This is not documented in the normal reference/user guides. Discussion points: 1) Should Seam handle content compression (for GWT service remoting) that overrides the container (tomcat) settings. 2) If Seam does handle content compression, should it be configurable for different environments (Local LAN with poor desktops (set high), versus Dialup with fast desktop (set low)), and be able to disable content compression for wire debugging purposes. -- 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, 5 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2290) Tooling to create GWT Interface jar from @Name/@WebRemote annotations

by darren hartford (JIRA)

Tooling to create GWT Interface jar from @Name/@WebRemote annotations --------------------------------------------------------------------- Key: JBSEAM-2290 URL: http://jira.jboss.com/jira/browse/JBSEAM-2290 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.0.0.GA Environment: seam-remoting, GWT Reporter: darren hartford Create tooling support to automatically generate a separate GWT Interface jar. By default/convention, an interface class needs to be created for consumption by a GWT Web Application that conforms with the (ejb3, other?) implementation (for mapping purposes). Tooling support to automatically create this would reduce errors and improve maintenance and ease-of-integration of both server-side and GWT web app side. Recommend tooling support for: seam-gen ant maven2 For example: server impl: ============ package com.domain.app; @Stateless //seam/gwt remoting support - should be name of GWT Service class @Name("com.domain.app.gwt.client.QueryGwtService") public class QueryGwt implements QueryGwtLocal { public String gwtTest(){ return "test ok"; } } //-------------------- package com.domain.app; @Local public interface QueryGwtLocal { //Seam-gwt remoting through the interface, not the session bean @WebRemote public String gwtTest(); } ============== The above server implementation with SEAM annotations will always need the following interfaces for GWT: =================== package com.domain.app.gwt.client; public interface QueryGwtService extends RemoteService{ public String gwtTest(); } //---------------- package com.domain.app.gwt.client; public interface QueryGwtServiceAsync{ public void gwtTest(AsyncCallback callback); } ================== -- 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, 5 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2302) Query Parser adding Where clause conditions to Non Where clauses

by Terry (JIRA)

Query Parser adding Where clause conditions to Non Where clauses ---------------------------------------------------------------- Key: JBSEAM-2302 URL: http://jira.jboss.com/jira/browse/JBSEAM-2302 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Environment: Any Reporter: Terry When using EntityQuery's getEjbql() and getRestrictions() override methods; and if ejbql in getEjbql() contains any clause after the WHERE clause - such as GROUP BY, the query parses appends restrictions to GROUP BY clause rather than to the WHERE clause. It seems, that EntityQuery expects WHERE to be last clause in ejbql. -- 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, 6 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2029) Identity.checkEntityPermission() fails for entities mapped using orm.xml or .hbm.xml

by Pete Muir (JIRA)

Identity.checkEntityPermission() fails for entities mapped using orm.xml or .hbm.xml ------------------------------------------------------------------------------------ Key: JBSEAM-2029 URL: http://jira.jboss.com/jira/browse/JBSEAM-2029 Project: JBoss Seam Issue Type: Bug Components: Security Affects Versions: 2.0.0.CR1 Reporter: Pete Muir Assigned To: Shane Bryzak Fix For: 2.0.1.GA Entity.forClass() isn't a great way to determine the entity's Class and should be done through PersistenceProvider -- 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, 6 months

4
24
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2306) Can't create Quartz Cron job at startup

by NSA (JIRA)

Can't create Quartz Cron job at startup --------------------------------------- Key: JBSEAM-2306 URL: http://jira.jboss.com/jira/browse/JBSEAM-2306 Project: JBoss Seam Issue Type: Bug Components: Async Affects Versions: 2.0.0.GA Environment: Windows, JBoss 4.2.1 GA Reporter: NSA I've set up an ObserveInitilization class as suggested by Pete Muir here: http://in.relation.to/Bloggers/DoingSomethingAtStartupWithSeam It looks like this: @Name("observeInitialization") public class ObserveInitialization { @In(create=true) Updater updater; @Observer("org.jboss.seam.postInitialization") public void start() { initialize(30 * 1000l); } @Asynchronous public void initialize(@Duration long durationInMilliseconds) { updater.update(new Date(), "0 0/3 * * * ?"); } } The Updater class looks like this: @Name("updater") public class Updater { @In private EntityManager entityManager; @Logger private Log log; @Asynchronous public void update(@Expiration Date start, @IntervalCron String cron) { //... } } The issue is this code calls ThreadPoolDispatcher.scheduleWithExecutorService, which casts the return value of createSchedule to a TimerSchedule. Because I'm using an @IntervalCron the return value of createSchedule is a CronSchedule which extends Schedule, but not TimerSchedule, so I get a ClassCastException: 09:14:59,387 ERROR [[/admin]] Exception sending context initialized event to listener instance of cl ass org.jboss.seam.servlet.SeamListener java.lang.ClassCastException: org.jboss.seam.async.CronSchedule at org.jboss.seam.async.ThreadPoolDispatcher.scheduleInvocation(ThreadPoolDispatcher.java:47) at org.jboss.seam.async.ThreadPoolDispatcher.scheduleInvocation(ThreadPoolDispatcher.java:29) 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 org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:155) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:91) at org.jboss.seam.async.ThreadPoolDispatcher_$$_javassist_6.scheduleInvocation(ThreadPoolDispatcher _$$_javassist_6.java) at org.jboss.seam.async.AsynchronousInterceptor.aroundInvoke(AsynchronousInterceptor.java:38) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:155) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:91) at com.company.Updater_$$_javassist_5.update(Updater_$$_javassist_5.java) at com.company.ObserveInitialization.initialize(ObserveInitialization.java:29) I compared this to the Quartz example packaged with Seam. That example also calls createSchedule but as a parameter to QuartzDispatcher.scheduleWithQuartzService which accepts a Schedule, thus no ClassCastException. -- 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, 6 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2415) Allow caching of created SelectItem Lists

by Damian Harvey (JIRA)

Allow caching of created SelectItem Lists ----------------------------------------- Key: JBSEAM-2415 URL: http://jira.jboss.com/jira/browse/JBSEAM-2415 Project: JBoss Seam Issue Type: Feature Request Reporter: Damian Harvey Rendering of drop-down menus (h:selectOneMenu) can be slow in JSF pages when working with large lists that can appear often (eg. countries - 246 items). It would be nice to be able to cache the resulting list from s:selectItems so that it can be used again in subsequent pages/requests. -- 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, 6 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2356) Give the ability to extend the list of EL functions supportem by Seam EL resolver

by Olivier Thierry (JIRA)

Give the ability to extend the list of EL functions supportem by Seam EL resolver ---------------------------------------------------------------------------------- Key: JBSEAM-2356 URL: http://jira.jboss.com/jira/browse/JBSEAM-2356 Project: JBoss Seam Issue Type: Feature Request Components: EL Affects Versions: 2.0.0.GA Reporter: Olivier Thierry There is no easy way to use a custom EL function for example in a resource bundle. There are two EL functions today (s:hasRole and s:hasPermissions) which are hard-coded in org.jboss.seam.el.SeamFunctionMapper class. It would be nice to have the possibility to extend the list of these EL functions with our custom ones, without having to modify Seam source 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

16 years, 6 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2171) Converter implementations for java 1.5 atomic classes

by Dennis Byrne (JIRA)

Converter implementations for java 1.5 atomic classes ----------------------------------------------------- Key: JBSEAM-2171 URL: http://jira.jboss.com/jira/browse/JBSEAM-2171 Project: JBoss Seam Issue Type: Feature Request Components: Core Environment: head Reporter: Dennis Byrne Assigned To: Dennis Byrne Attachments: AtomicBooleanConverter.java, AtomicIntegerConverter.java, AtomicLongConverter.java I am having some political problems getting this into Tomahawk (which is living in a java 1.4 world). The work is here and it's tested. I think this would be a good addition to Seam, considering that Seam has done so much w/ the other stuff that came out in 1.5. I intend to document this, so please advise on what the protocol is. Also, I looked around the code base and couldn't find a faces-config to register these. -- 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, 6 months

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1811) DefaultActionListener is not call when using s:link

by Andy Bosch (JIRA)

DefaultActionListener is not call when using s:link --------------------------------------------------- Key: JBSEAM-1811 URL: http://jira.jboss.com/jira/browse/JBSEAM-1811 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.2.1.GA Environment: Jboss 4.0.5 GA and JBoss 4.2.0 Reporter: Andy Bosch In JSF in faces-config.xml you can create your own actionlistener with <action-listener> com.company.MyActionListener </action-listener> This actionlistener will be executed each time, a commandLink or commandButton is pressed. When using s:link or s:button the actionlistener is not called. -- 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, 6 months

4
11
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