July 2009 - seam-issues - Jboss List Archives

[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

14 years, 2 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

14 years, 2 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

14 years, 2 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

14 years, 2 months

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

14 years, 2 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

14 years, 2 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2997) EL does not resolve varargs methods properly

by Tobias Hill (JIRA)

EL does not resolve varargs methods properly -------------------------------------------- Key: JBSEAM-2997 URL: http://jira.jboss.com/jira/browse/JBSEAM-2997 Project: Seam Issue Type: Bug Components: EL Affects Versions: 2.0.1.GA Reporter: Tobias Hill Seems EL does not resolve vararg methods properly. Examples: 1) #{component.setData()} does not find method setData(Object... items) on component-bean. 2) #{component.setData('foo')} actually does find method setData(Object... items) on component-bean. 3) #{component.setData('foo', bar)} where bar is not a String, does _not_ find method setData(Object... items) on component-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

14 years, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4047) Bean should be annotated as asynchronous in Seam Reference Guide

by Brian Dill (JIRA)

Bean should be annotated as asynchronous in Seam Reference Guide ---------------------------------------------------------------- Key: JBSEAM-4047 URL: https://jira.jboss.org/jira/browse/JBSEAM-4047 Project: Seam Issue Type: Task Reporter: Brian Dill -- 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

14 years, 2 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4284) Wrong pageflow name in case of nested conversation

by Vesa Hiltunen (JIRA)

Wrong pageflow name in case of nested conversation -------------------------------------------------- Key: JBSEAM-4284 URL: https://jira.jboss.org/jira/browse/JBSEAM-4284 Project: Seam Issue Type: Bug Affects Versions: 2.1.2.GA Reporter: Vesa Hiltunen I tried to start nested conversation with new pageflow as follows: <s:link value="DoIt" action="/pages/myPage.xhtml"> <s:conversationPropagation type="nested" pageflow="myPageflowName" /> </s:link> Seam did not find pageflow because it is looking for pageflow named as: d.myPageflowName Request parameter was: conversationPropagation=nested.myPageflowName It looks like method getPropagationFromRequestParameter(Map parameters) in org.jboss.seam.core.ConversationPropagation contains a bug. Method assumes that string "nested." was "nest." Current code: else if (value.startsWith("nest")) { propagationType = PropagationType.NEST; if ( value.length()>5 ) { pageflow = value.substring(5); } } One way to fix the code: else if (value.startsWith("nest")) { propagationType = PropagationType.NEST; if ( value.length()>7 ) { pageflow = value.substring(7); } } -- 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

14 years, 2 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3883) URL rewriting broken for view-id of redirects in exceptions

by Stephen Friedrich (JIRA)

URL rewriting broken for view-id of redirects in exceptions ----------------------------------------------------------- Key: JBSEAM-3883 URL: https://jira.jboss.org/jira/browse/JBSEAM-3883 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Reporter: Stephen Friedrich When a configured exception handler redirects to a view-id, then the URL for that view-id is not processed by Seam's URL rewriting filter. As a result you cannot re-write the URL for your login page if you want to redirect to the login page when a ViewExpiredSException occurs. The problem is that the RewriteFilter is deeper in the filter chain than the ExceptionFilter, so at the time when the exception filter is handling an exception no RewritingResponse is on the chain of wrapped responses. Norman RIchards suggested to split incoming and outgoing rewriting and place it at opposite ends of the filter chain. -- 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

14 years, 2 months

4
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2009