April 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1126) Generate-entities creates a class with the error

by Alex Narinsky (JIRA)

Generate-entities creates a class with the error ------------------------------------------------ Key: JBSEAM-1126 URL: http://jira.jboss.com/jira/browse/JBSEAM-1126 Project: JBoss Seam Issue Type: Bug Components: EJB3 Affects Versions: 1.2.1.GA, 1.2.0.GA Reporter: Alex Narinsky Priority: Minor I am using generate-entities. Prior to version 1.2 this worked fine. Starting from version 1.2 one generated class contains the error - double definition of one "In" element. Please, see the text below @Name("moviesHome") public class MoviesHome extends EntityHome<Movies> { @In(create = true) ContactsHome contactsHome; @In(create = true) ProjectsHome projectsHome; @In(create = true) ContactsHome contactsHome; -- 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

12 years, 3 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1167) hot-deploy changes broke hibernate tools integration (and possible also testng)

by Max Andersen (JIRA)

hot-deploy changes broke hibernate tools integration (and possible also testng) ------------------------------------------------------------------------------- Key: JBSEAM-1167 URL: http://jira.jboss.com/jira/browse/JBSEAM-1167 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 1.2.1.GA Reporter: Max Andersen Priority: Critical .classpath in seam-gen previously pointed to test-build where hibernate tools could pick up a META-INF/persistence.xml file. Now it points to build/model and is actually never used because all src output is explicitly set. Thus no proper persistence unit is defined in eclipse now. -- 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

12 years, 3 months

6
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-855) Client-API for Monitoring Download Progress of large amounts of data

by Stefan Frank (JIRA)

Client-API for Monitoring Download Progress of large amounts of data --------------------------------------------------------------------- Key: JBSEAM-855 URL: http://jira.jboss.com/jira/browse/JBSEAM-855 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Reporter: Stefan Frank Assigned To: Shane Bryzak Priority: Optional If you transport larger chunks of data via remoting, it is currently not possible to monitor the download progress. The effect is, that you can only display an unqualified busy-animation to the user. We implement this manually right now, by breaking down the date into smaller chunks and then reporting back the progress based on the downloaded chunks vs. the total number. of chunks. An enhancement would be to have: - a possibility to register a callback for progres on the client - a feature to have the data(especially collections) chopped up automatically and sent in smaller chunks (maybe some annotations as hint?!) This would make it possible to display a proper progress-bar on the client and report back, that the download is still running. -- 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, 4 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-731) <restrict> in components.xml

by Gavin King (JIRA)

<restrict> in components.xml ---------------------------- Key: JBSEAM-731 URL: http://jira.jboss.com/jira/browse/JBSEAM-731 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Gavin King Assigned To: Gavin King Fix For: 1.2.0.BETA1 I guess we should allow you to restrict access to a component or method via a declaration in components.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

13 years, 4 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-986) Seam Remoting - support subscribing to a JMS Queue

by Shane Bryzak (JIRA)

Seam Remoting - support subscribing to a JMS Queue -------------------------------------------------- Key: JBSEAM-986 URL: http://jira.jboss.com/jira/browse/JBSEAM-986 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Affects Versions: 1.2.0.GA Reporter: Shane Bryzak Assigned To: Shane Bryzak Priority: Minor Seam Remoting currently supports subscribing to a JMS topic, however doesn't support subscribing to a queue. This would be useful for things such as progress updates, etc. -- 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, 4 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1229) Remoting exception with JMS subscription

by Alex Mateescu (JIRA)

Remoting exception with JMS subscription ---------------------------------------- Key: JBSEAM-1229 URL: http://jira.jboss.com/jira/browse/JBSEAM-1229 Project: JBoss Seam Issue Type: Bug Components: Remoting Affects Versions: 1.2.1.GA Environment: JEMS Installer 1.2 ejb3 profile, JBoss Portal 2.6.0ALPHA1, JBoss Seam 1.2.1GA running on Fedora Core 6, Firefox 1.5 Reporter: Alex Mateescu Assigned To: Shane Bryzak Priority: Minor I am deploying an EAR with multiple (the number is probably irrelevant) JARs and WARs that use Seam Remoting and subscribe to a JMS topic. The subscribe calls work fine, they send the correct topic name and receive a token. On the first poll, though, there is an exception: 2007-04-23 14:08:29,602 ERROR [org.jboss.seam.remoting.Remoting] Error java.lang.IllegalArgumentException: Invalid token argument - token not found in Session Context. [undefined] at org.jboss.seam.remoting.messaging.SubscriptionRegistry.getSubscription(SubscriptionRegistry.java:179) at org.jboss.seam.remoting.messaging.PollRequest.poll(PollRequest.java:45) at org.jboss.seam.remoting.PollHandler.handle(PollHandler.java:83) at org.jboss.seam.remoting.Remoting.getResource(Remoting.java:110) at org.jboss.seam.servlet.ResourceServlet.doGet(ResourceServlet.java:68) at org.jboss.seam.servlet.ResourceServlet.doPost(ResourceServlet.java:77) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) Upon closer inspection, the polling request looks like this: <envelope><body><poll token="c312b1bb-d996-46e4-a8d7-6f35caa99d73" timeout="10"/><poll token="undefined" timeout="10"/></body></envelope> which is the cause of the exception. Subsequent calls look fine: <envelope><body><poll token="c312b1bb-d996-46e4-a8d7-6f35caa99d73" timeout="10"/><poll token="3922899d-1e6b-4bc1-96ab-3713f4460446" timeout="10"/></body></envelope> I think the error was there before, when using Seam 1.1.0GA, but it was random. I may be wrong, but now it is always there. Of course, remoting works fine after the initial call. -- 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, 4 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-728) Support "outside" authentication

by Gavin King (JIRA)

Support "outside" authentication -------------------------------- Key: JBSEAM-728 URL: http://jira.jboss.com/jira/browse/JBSEAM-728 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Gavin King Assigned To: Shane Bryzak Fix For: 1.2.0.BETA1 If the container has already authenticated the user outside of Seam, we should be able to still use Seam authorization. -- 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, 4 months

7
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1250) Socket write error with Seam JMS Remoting

by Scott McNab (JIRA)

Socket write error with Seam JMS Remoting ----------------------------------------- Key: JBSEAM-1250 URL: http://jira.jboss.com/jira/browse/JBSEAM-1250 Project: JBoss Seam Issue Type: Bug Components: Remoting Affects Versions: 1.2.1.GA, 1.2.0.GA Environment: WindowsXP, JBossAS 4.2.0.CR1 Reporter: Scott McNab Assigned To: Shane Bryzak Full details are given in the corresponding forum topic, however a summary is: * Client-side javascript subscribes to a JMS topic by calling Seam.Remoting.subscribe(). * The client then navigates to a new page. * Approximately 30 seconds later, a SocketException (socket write error) occurs on the server within Seam Remoting (presumably because my Seam poll-timeout is set to 30 seconds). This occurs consistently with JBoss running under Windows, but does not seem to occur when the server is run on Linux. It is also not affected by browser type (i.e. it happens when using Firefox or IE). This bug did not occur previously when the same code was running with Seam 1.0.1.GA. -- 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, 4 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-729) support container authorization

by Gavin King (JIRA)

support container authorization ------------------------------- Key: JBSEAM-729 URL: http://jira.jboss.com/jira/browse/JBSEAM-729 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Gavin King Assigned To: Shane Bryzak Fix For: 1.2.0.BETA1 We should re-authenticate on each request, so that you can use container authorization as well as Seam authorization, -- 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, 4 months

8
19
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-827) ICEfaces components are rendering during non RENDER_RESPONSE phase

by Gregory Dick (JIRA)

ICEfaces components are rendering during non RENDER_RESPONSE phase ------------------------------------------------------------------- Key: JBSEAM-827 URL: http://jira.jboss.com/jira/browse/JBSEAM-827 Project: JBoss Seam Issue Type: Bug Components: ICE Faces Integration Environment: SEAM+ICEfaces Reporter: Gregory Dick Assigned To: Gregory Dick During the INVOKE_APPLICATION phase of application operations that are printing to PDF, SEAM is directly rendering facelets output, and ICEfaces components are mistakenly rendering at this time. -- 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

5
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2007