August 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3006) web:character-encoding-filter and UTF-8 not working

by Bruno Orcha Garcￃﾭa (JIRA)

web:character-encoding-filter and UTF-8 not working ---------------------------------------------------- Key: JBSEAM-3006 URL: http://jira.jboss.com/jira/browse/JBSEAM-3006 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.GA Reporter: Bruno Orcha Garcￃﾭa web:character-encoding-filter is not working. When submitting UTF-8 characters in a h:inputText (for example), the string contains invalid characters, due a bad encoding interpretation. This issue should be fixed configuring the web:character-encoding-filter to UTF-8 in component.xml, but this is not working. This filter should be the first, in the seam filter stack?. Using a filter in web.xml it's the unique solution that works currently. -- 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

13 years, 6 months

5
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1839) Use HSQL to store Quartz jobs when deployed on JBoss AS

by Michael Yuan (JIRA)

Use HSQL to store Quartz jobs when deployed on JBoss AS ------------------------------------------------------- Key: JBSEAM-1839 URL: http://jira.jboss.com/jira/browse/JBSEAM-1839 Project: JBoss Seam Issue Type: Feature Request Reporter: Michael Yuan Assigned To: Michael Yuan Fix For: 2.0.0.GA Right now, Quartz jobs are stored "in-memory" and hence cannot be auto-started when the server reboots. The user can use persistence job stores by using a custom quartz property file. However, in JBoss AS, we should store jobs in the HSQL DB by default: * In the dispatcher component, we can have a "jboss=true" attribute * If this attribute is true, the QuartzDispatcher will setup Quartz tables for this particular app in the HSQL at startup, and then use the HSQL DB as persistent job store. This way, when the application deploys again, all the jobs for this application will be auto-started again. -- 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

13 years, 7 months

4
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2353) Quartz asynchronous events shceduled to fire while the server is shutdown fire before seam is initialized when the server is started.

by Yona Appletree (JIRA)

Quartz asynchronous events shceduled to fire while the server is shutdown fire before seam is initialized when the server is started. ------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2353 URL: http://jira.jboss.com/jira/browse/JBSEAM-2353 Project: JBoss Seam Issue Type: Bug Components: Async Environment: Jboss 4.2.2.GA; Quartz scheduler. Reporter: Yona Appletree Fix For: 2.0.0.GA When the QuartzDispatcher is created, it causes any event scheduled to fire in the past to fire immediately (in a separate thread). Since QuartzDispatcher is marked @Startup, it may start before other components. If the handler of an event fired on startup relies on another component marked @Startup, it may not exist by the time the event is fired, and will therefore cause an error. I have a found a partial workaround for this issue, documented in the referenced forum thread. -- 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

13 years, 7 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1869) Example of Control Set for Quartz SEAM Interation

by Piergiuseppe Spinelli (JIRA)

Example of Control Set for Quartz SEAM Interation ------------------------------------------------- Key: JBSEAM-1869 URL: http://jira.jboss.com/jira/browse/JBSEAM-1869 Project: JBoss Seam Issue Type: Task Components: Examples Affects Versions: 2.0.0.BETA1 Environment: Any OS. JBoss2_0B project. Reporter: Piergiuseppe Spinelli Priority: Optional The attached sample is an attept to create a control interface to SEAM asynchronous method using Quartz as scheduling engine. I was asked to do this in the related forum thread: I am not sure it is near to the desired functionalities, but it could be used as a starting point (or possibly as a negative sample). The sample is very raw and I have used SEAM too short to be sure I did not make to stupid things, but if the idea is useful, I am sure other people will improve it. Notes: - The sample use quartz integrated in SEAM as it currently is: a support to asynchronous method - Quartz is used with its in-memory db, the persistent status is kept by the application usign custom Entities - Since I am a newby in SEAM, I preferred to make some custom classes for supporting CRUD operations since it was difficult to me to get the SEAM framework to do more that the simple things showed in the samples TODO: - it could be better to use some well known components library for the interface instead that my custom controls (i.e Trinidad) - the entities I made to keep the application status use a table schema very similar to the quartz schema: it could be a good idea in a future to be able to use some entity model over the quartz schema - it would be usefull to add the feature to upload the classes to be scheduler directly by the web interface, mayby using a classloader chain for supporting hot versioning. -- 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

13 years, 7 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-975) constraint by inclusion on remote calls object fields

by Zalder R (JIRA)

constraint by inclusion on remote calls object fields ----------------------------------------------------- Key: JBSEAM-975 URL: http://jira.jboss.com/jira/browse/JBSEAM-975 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Reporter: Zalder R Assigned To: Shane Bryzak Priority: Optional I think it could be nice to define the fields of the objects returned in a "WebRemote call" with an "include" parameter (instead of the current exclude parameter). For instance : now you have : @WebRemote(exclude = {"secret"}) it would be nice to be able to define : @WebRemote(include = {"fieldIreallyNeed1", "fieldIreallyNeed2"}) The reasons for this are many : - security : if the object structure varies over time, you would not want the new fields to be available on the client side by default - in some cases it's a lot more lightweight (both in the code and in the volume of data sent) to define a minimum set of fields you want instead of the fields you don't want -- 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

13 years, 7 months

5
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-984) Progressbar for async methods

by Pete Muir (JIRA)

Progressbar for async methods ----------------------------- Key: JBSEAM-984 URL: http://jira.jboss.com/jira/browse/JBSEAM-984 Project: JBoss Seam Issue Type: Feature Request Components: Core, Remoting Affects Versions: 1.2.0.GA Reporter: Pete Muir Priority: Minor I think a fairly common use case is: * Call action * call async method to do a lengthy action * return to page * update progress bar and say when done based on async method I think we could wrap this all up: * user raises an event in the async method indicating completeness * remoting/ui component polls seam to update progress -- 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

13 years, 7 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3282) API for pluging and adding thirdparty suport to enhance Seam Remoting

by Francisco Jose Peredo Noguez (JIRA)

API for pluging and adding thirdparty suport to enhance Seam Remoting --------------------------------------------------------------------- Key: JBSEAM-3282 URL: https://jira.jboss.org/jira/browse/JBSEAM-3282 Project: Seam Issue Type: Feature Request Components: Remoting Reporter: Francisco Jose Peredo Noguez Assignee: Shane Bryzak Give us choice, expose an API to customize Seam Remoting (if it is available then it needs detailed documentation, or at least introductory documentation), so that if for some reason this never makes it in to Seam trunk, at least it becomes real easy to create some sort of plug-in to do it. -- 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

13 years, 7 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2215) Interface.js too large

by Robin Young (JIRA)

Interface.js too large ---------------------- Key: JBSEAM-2215 URL: http://jira.jboss.com/jira/browse/JBSEAM-2215 Project: JBoss Seam Issue Type: Bug Components: Remoting Affects Versions: 2.0.0.GA Reporter: Robin Young Assigned To: Shane Bryzak The interface.js file produced includes type definitions for EVERY seam component in my system and takes a couple of seconds to serve. The url is "/seam/resource/remoting/interface.js?navigationSystemService" and is generated by and s:remote tag. I have added exclude parameters to my WebRemote annotations and this restricts the data sent back back but does nothing to limit the interface.js file produced. Is there any way to slim this down and thus improve the speed of my site? -- 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

13 years, 7 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1056) Comet requests for Seam Remoting

by Niels Hoogeveen (JIRA)

Comet requests for Seam Remoting -------------------------------- Key: JBSEAM-1056 URL: http://jira.jboss.com/jira/browse/JBSEAM-1056 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Environment: any Reporter: Niels Hoogeveen Assigned To: Shane Bryzak Since JBossAS-4.2.0.CR1 supports Tomcat 6 a "servlet" of type CometProcessor, which allows for comet style http access, is available. In principle this would allow for a non-polling/long-polling solutions for eg. the JMS example. -- 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

13 years, 7 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1470) Seam event bus integration for remoting

by Gavin King (JIRA)

Seam event bus integration for remoting --------------------------------------- Key: JBSEAM-1470 URL: http://jira.jboss.com/jira/browse/JBSEAM-1470 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Reporter: Gavin King Assigned To: Shane Bryzak Both js and GWT clients should be able to do Events.instance().raiseEvent(....) and have it processed on the server side. They should also be able to have @Observer methods, or do Events.instance().addListener(...), and get event notifications over Seam Remoting's push functionality. -- 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

13 years, 7 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2008