September 2010 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-4706) Forum email notification comment does not correspond to the real content

by Julien Kronegg (JIRA)

Forum email notification comment does not correspond to the real content ------------------------------------------------------------------------ Key: JBSEAM-4706 URL: https://jira.jboss.org/browse/JBSEAM-4706 Project: Seam Issue Type: Bug Components: Wiki Environment: Forum thread email notification feature as of 2010.09.08. Reporter: Julien Kronegg Assignee: Christian Bauer Priority: Minor I recently received the following forum email notification message: Hello Julien, you received a response to your posting on the Seam community forum, posted by xiaox xiaox: The DNA testing took a calendar year to come back -- with "inconclusive"plus size Cocktail Dresses results. For months and months, the state funding needed to pay for "mitigation," investigators who prepare long before opening statements for a death penalty plus size cocktail dresseshearing, never showed up, Trenticosta said. Woman was beaten but alive when set on fire Click here to reply... The response link is http://seamframework.org/Community/HowtoAvoidMethodOrGetterToBeCalledSeve... and the corresponding comment text is: This is abit late but why not do the below? <c:set var="_personName" value="#{createExample.person.name}"/> within the jsf page? I used it to reduce the call to the backing bean when a jsf page is first rendered but it is not perfect as partial re-rendering of a page may cause issues. Cheers. I expected to have the "<c:set var..." message as the comment in the email notification body, instead of the stuff about DNA testing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 5 months

2
1
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

15 years, 5 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

15 years, 5 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

15 years, 5 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

15 years, 5 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

15 years, 5 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

15 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-4576) Upgrade Javassist to new version - current version has memory leaks

by Marek Novotny (JIRA)

Upgrade Javassist to new version - current version has memory leaks ------------------------------------------------------------------- Key: JBSEAM-4576 URL: https://jira.jboss.org/jira/browse/JBSEAM-4576 Project: Seam Issue Type: Task Components: Core Affects Versions: 2.2.0.GA, 2.2.0.CR1 Reporter: Marek Novotny Assignee: Marek Novotny Fix For: 2.2.1.CR2 The problem is caused by the current javassist usage pattern of calling ProxyFactory.createClass().newInstance() which currently (due to the broken cache), always creates a new class for the proxy. And once this class gets classloaded, you cannot easily get rid of it from the ClassLoaders class map. There were also a few problems with deserialization, mainly because it did drop the assigned MethodHandler and used the DefaultMethodHandler instead. Storing a static reference cause a problem for garbage collection, because the MethodHandler set directly into the ProxyFactory can never get freed. Patches from Mark Struberg is available at http://github.com/struberg/javassist -- 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

1
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4204) Hot redeploy is broken w/ JBoss AS 5

by Fred Bricon (JIRA)

Hot redeploy is broken w/ JBoss AS 5 ------------------------------------ Key: JBSEAM-4204 URL: https://jira.jboss.org/jira/browse/JBSEAM-4204 Project: Seam Issue Type: Bug Components: Hot Deploy Affects Versions: 2.1.2.CR2, 2.1.1.GA, 2.0.2.SP1 Environment: Vista, Eclipse Ganymede 3.4.2, JBoss Tools 3.0.1.GA, JBoss 5.0.1.GA Reporter: Fred Bricon Hi It seems hot deployement doesn't work on JBoss 5.0.1.GA : when editing (and saving) xhtml files, JBoss Tools correctly publish the files to the JBoss AS deploy directory, but changes are not picked up. I tested projects created from the JBoss Tools wizards : - booking (2.0.2.SP1 from the examples menu) - simple 2.0.2.SP1 project - simple 2.1.1.GA project - simple 2.1.2.CR2 project A simple seam-less dynamic web project, is correctly hot redeployed via JBoss Tools. [Others|http://seamframework.org/Community/HotDeployAndJBoss5] have experienced this problem. I couldn't say if it's a Seam or an AS5 issue for sure, but I vote for the former. regards, Fred Bricon -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3581) Chatroom example throws NameNotFoundException on AS 5

by Jozef Hartinger (JIRA)

Chatroom example throws NameNotFoundException on AS 5 ----------------------------------------------------- Key: JBSEAM-3581 URL: https://jira.jboss.org/jira/browse/JBSEAM-3581 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.3.CR1, 2.1.0.GA Environment: JDK 5 JBoss AS 5.0.0.CR2 Reporter: Jozef Hartinger I am getting "javax.naming.NameNotFoundException: chatroomTopic not bound" when deploying the example on AS 5. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2010