January 2008 - 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

11 years, 6 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

11 years, 6 months

6
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB

by Siarhei Dudzin (JIRA)

MDB activated too early to use Seam components as a standard EJB ---------------------------------------------------------------- Key: JBSEAM-2286 URL: http://jira.jboss.com/jira/browse/JBSEAM-2286 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: Siarhei Dudzin Priority: Critical As specified in the forum reference I have an MDB which uses a SLSB (also declared as Seam component) with business logic. If I deploy the application and there are already messages in the queue I get the following exception: javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted to invoke a Seam component outside the an initialized application at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138) at $Proxy111.onMessage(Unknown Source) Looks like the MDB processing the message before Seam is initialized? This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate business logic if I want to re-use the same functionality of the SLSB in Seam. I could use the solution from http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me to use vendor-specific API. -- 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

11 years, 6 months

13
22
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1279) use ExceptionFilter in Remoting

by Keith Naas (JIRA)

use ExceptionFilter in Remoting ------------------------------- Key: JBSEAM-1279 URL: http://jira.jboss.com/jira/browse/JBSEAM-1279 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Affects Versions: 1.2.1.GA Reporter: Keith Naas Assigned To: Shane Bryzak Currently, the Remoting resource class swallows all exceptions. Because of this, it is not possible to gracefully handle security restrictions in WebRemote methods from the client. Two ideas: # Simply bubble the Exception all the way up through the ResourceServlet. If the ResourceServlet throws the exception, the ExceptionFilter should pick up on it. The XHR would then receive the proper error code as defined in the pages.xml and could properly redirect the user to the correct login page. # Have the ResourceServlet trap for NotLoggedInException's or NotAuthorizedException's and return the respective HTTP status code. The XHR would then receive the error code and be able to redirect the user to the correct login page. -- 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, 6 months

5
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2092) Nothing mentioned about dependency on commons-* libraries

by Jacek Zebrowski (JIRA)

Nothing mentioned about dependency on commons-* libraries --------------------------------------------------------- Key: JBSEAM-2092 URL: http://jira.jboss.com/jira/browse/JBSEAM-2092 Project: JBoss Seam Issue Type: Task Components: Documentation Affects Versions: 2.0.0.CR2, 2.0.0.CR1 Reporter: Jacek Zebrowski As in the title. -- 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, 8 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2403) Cant build Seam from the CR1 download

by Chris Lowe (JIRA)

Cant build Seam from the CR1 download ------------------------------------- Key: JBSEAM-2403 URL: http://jira.jboss.com/jira/browse/JBSEAM-2403 Project: JBoss Seam Issue Type: Bug Environment: Windows XP, Redhat Developer Studio RC1 Reporter: Chris Lowe Getting the following exception when trying to build Seam 2.0.1 CVS on Win XP [java] [ERROR] Error on generate component [java] org.ajax4jsf.builder.config.ParsingException: I/O error on parsing config file [java] at org.ajax4jsf.builder.config.BuilderConfig.parseConfig(BuilderConfig.java:387) [java] at org.ajax4jsf.builder.mojo.GenerateMojo.createConfig(GenerateMojo.java:253) [java] at org.ajax4jsf.builder.mojo.GenerateMojo.execute(GenerateMojo.java:92) [java] at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:4 20) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExe cutor.java:539) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(Default LifecycleExecutor.java:480) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExec utor.java:459) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(Def aultLifecycleExecutor.java:311) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifec ycleExecutor.java:278) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor .java:143) [java] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330) [java] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) [java] at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25 ) [java] at java.lang.reflect.Method.invoke(Method.java:597) [java] at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) [java] at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) [java] at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) [java] at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [java] Caused by: java.net.MalformedURLException: unknown protocol: c [java] at java.net.URL.<init>(URL.java:574) [java] at java.net.URL.<init>(URL.java:464) [java] at java.net.URL.<init>(URL.java:413) [java] at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntit yManager.java:650) [java] at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVe rsionDetector.java:186) [java] at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configurati on.java:771) [java] at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configurati on.java:737) [java] at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) [java] at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser .java:1205) [java] at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserI mpl.java:522) [java] at org.apache.commons.digester.Digester.parse(Digester.java:1605) [java] at org.ajax4jsf.builder.config.BuilderConfig.parseConfig(BuilderConfig.java:384) [java] ... 20 more -- 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, 8 months

5
17
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1957) Improve handling of JBoss Embedded in Seam

by Pete Muir (JIRA)

Improve handling of JBoss Embedded in Seam ------------------------------------------ Key: JBSEAM-1957 URL: http://jira.jboss.com/jira/browse/JBSEAM-1957 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.CR1 Reporter: Pete Muir Assigned To: Pete Muir -- 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, 8 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2355) Move Seam onto vanilla build of JBoss Embedded

by Pete Muir (JIRA)

Move Seam onto vanilla build of JBoss Embedded ---------------------------------------------- Key: JBSEAM-2355 URL: http://jira.jboss.com/jira/browse/JBSEAM-2355 Project: JBoss Seam Issue Type: Task Components: Test Harness Affects Versions: 2.0.0.GA Reporter: Pete Muir Assigned To: Pete Muir Priority: Critical -- 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, 8 months

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

12 years, 8 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

12 years, 8 months

4
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2008