March 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-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-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-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

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1065) Entity Query should support multiple value bindings on restrictions.

by sal something (JIRA)

Entity Query should support multiple value bindings on restrictions. -------------------------------------------------------------------- Key: JBSEAM-1065 URL: http://jira.jboss.com/jira/browse/JBSEAM-1065 Project: JBoss Seam Issue Type: Bug Components: Framework Affects Versions: 1.2.0.GA Reporter: sal something Entity Query should support multiple value bindings on restrictions. The use case would be the 'between' statement, as of now Entity Query will throw an exception using a 'between' statement: Caused by: java.lang.IllegalArgumentException: there should be exactly one value binding in a restriction: applicationDeadline between #{vacancyBrowseSearch.appDeadlineStartDate} and #{vacancyBrowseSearch.appDeadlineEndDate} at org.jboss.seam.framework.Query.parseEjbql(Query.java:145) at org.jboss.seam.framework.EntityQuery.createQuery(EntityQuery.java:100) at org.jboss.seam.framework.EntityQuery.getResultList(EntityQuery.java:41) -- 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

9
17
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-909) RCFaces compatibility

by Daniel Wiell (JIRA)

RCFaces compatibility --------------------- Key: JBSEAM-909 URL: http://jira.jboss.com/jira/browse/JBSEAM-909 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.1.6.GA Environment: JBoss Seam 1.1.6, JSF 1.1 RI (or MyFaces 1.1.5), Facelets 1.1.11, RCFaces 1.0b3 (or nightly from 20070221), Tomcat 5.5.20 Reporter: Daniel Wiell 1. Download RCFaces-facelets-starter-kit-v1-0b3.war (http://downloads.sourceforge.net/rcfaces/RCFaces-facelets-starter-kit-v1-...). 2. Deploy it in Tomcat. 3. Try the app - sorting the table works fine. 4. Build the "hibernate" example in Seam 1.1.6. 5. Copy over the jar files from the hibernate webapp to the "RCFaces-facelets-starter-kit" webapp, excluding the MyFaces jars and removing any dublicates. 6. Add "SeamListener" and "Seam Redirect Filter" to web.xml. 7. Add "SeamPhaseListener" to faces-config.xml. 8. Copy the components.xml and remove "bookingDatabase". 8. Redeploy the app. 9. Try it - when sorting you get the following stacktrace: java.lang.IllegalStateException: No phase id bound to current thread (make sure you do not have two SeamPhaseListener instances installed) at org.jboss.seam.contexts.PageContext.getPhaseId(PageContext.java:153) at org.jboss.seam.contexts.PageContext.isRenderResponsePhase(PageContext.java:165) at org.jboss.seam.contexts.PageContext.getCurrentReadableMap(PageContext.java:76) at org.jboss.seam.contexts.PageContext.get(PageContext.java:66) at org.jboss.seam.contexts.Contexts.lookupInStatefulContexts(Contexts.java:160) at org.jboss.seam.Component.getInstance(Component.java:1635) at org.jboss.seam.jsf.SeamVariableResolver.resolveVariable(SeamVariableResolver.java:53) at com.sun.facelets.el.LegacyELContext$LegacyELResolver.getValue(LegacyELContext.java:134) at com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:65) at com.sun.el.parser.AstValue.getValue(AstValue.java:106) at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:192) at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71) at com.sun.facelets.el.LegacyValueBinding.getValue(LegacyValueBinding.java:56) at org.rcfaces.core.internal.component.BasicComponentEngine.getInternalProperty(BasicComponentEngine.java:149) at org.rcfaces.core.internal.component.BasicComponentEngine.getValue(BasicComponentEngine.java:402) at org.rcfaces.core.internal.component.CameliaGridComponent.getValue(CameliaGridComponent.java:418) at org.rcfaces.core.internal.component.CameliaGridComponent.getDataModel(CameliaGridComponent.java:401) at org.rcfaces.renderkit.html.internal.renderer.DataGridRenderer$TableRenderContext.<init>(DataGridRenderer.java:2624) at org.rcfaces.renderkit.html.internal.renderer.DataGridRenderer$TableRenderContext.<init>(DataGridRenderer.java:2691) at org.rcfaces.renderkit.html.internal.renderer.DataGridRenderer.createTableContext(DataGridRenderer.java:677) at org.rcfaces.renderkit.html.internal.service.DataGridService.writeJs(DataGridService.java:242) at org.rcfaces.renderkit.html.internal.service.DataGridService.service(DataGridService.java:171) at org.rcfaces.core.internal.config.ServicesRegistryImpl.afterPhase(ServicesRegistryImpl.java:121) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:254) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:110) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:213) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:29) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) 10. Comment out the "SeamPhaseListener" and retry - now it works again. It's too bad, since RCFaces seems like a really great component library. -- 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

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

14 years, 1 month

5
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues March 2007