November 2006 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-100) Unify datasource configuration factory with E-EJB3

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-100?page=all ] Gavin King updated JBSEAM-100: ------------------------------ Component/s: Core > Unify datasource configuration factory with E-EJB3 > -------------------------------------------------- > > Key: JBSEAM-100 > URL: http://jira.jboss.com/jira/browse/JBSEAM-100 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Christian Bauer > Priority: Trivial > Attachments: JBSEAM-100.zip > > > The org.jboss.resource.adapter.jdbc.local.LocalTxDataSource does the same as org.jboss.seam.microcontainer.DataSourceFactory - they are slightly different in configuration only. > For example: > - connectionUrl vs. connectionURL > - getDatasource vs. getDataSource > - etc. > One internal difference is the CachedConnectionManager. It is injected into the LocalTxDataSource, but instantiated in the seam.microcontainer.DataSourceFactory. > I think we should either unify, or better, kick out one of those two. -- 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

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-409) WebSessionContext.flush causing out of memory

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-409?page=all ] Gavin King updated JBSEAM-409: ------------------------------ Component/s: Portal Fix Version/s: 1.1.0.CR1 Assignee: Gavin King Priority: Critical (was: Major) > WebSessionContext.flush causing out of memory > --------------------------------------------- > > Key: JBSEAM-409 > URL: http://jira.jboss.com/jira/browse/JBSEAM-409 > Project: JBoss Seam > Issue Type: Bug > Components: Portal > Affects Versions: 1.1.0.BETA1 > Reporter: jarkko Lietolahti > Assigned To: Gavin King > Priority: Critical > Fix For: 1.1.0.CR1 > > -- 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

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-404) Improved exception handling rules

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-404?page=all ] Gavin King updated JBSEAM-404: ------------------------------ Summary: Improved exception handling rules (was: Exception handling rules) > Improved exception handling rules > --------------------------------- > > Key: JBSEAM-404 > URL: http://jira.jboss.com/jira/browse/JBSEAM-404 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Louis Coetzee > > Seam provides the @Redirect annotation for use on Exception classes. It provides an attribute to specify the target viewId to redirect to once the exception has been thrown. It would be good if this view Id can be specified dynamically. > e.g. > @Name("napException") > @ApplicationException(rollback=true) > @Redirect(viewId = "#{napException.viewId}") > public class NAPException extends Exception implements Serializable { > or in xml > <from-view-id>/xxx.jsp</from-view-id> > <from-exception>com.myapp.NAPException</from-exception> > <to-view-id>/error.jsp</to-view-id> > <redirect/> -- 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

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-123) Make EL be testable

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-123?page=all ] Gavin King closed JBSEAM-123. ----------------------------- Fix Version/s: 1.1.0.BETA2 Resolution: Done Assignee: Gavin King Was already done. > Make EL be testable > ------------------- > > Key: JBSEAM-123 > URL: http://jira.jboss.com/jira/browse/JBSEAM-123 > Project: JBoss Seam > Issue Type: Feature Request > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1.0.BETA2 > > > Currently, we cannot execute any EL expression outside a real running myfaces. Mocking doesn't work. This is a big problem for jBPM pageflows, which are currently totally untestable. > Perhaps we can use commons-el directly? -- 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

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-404) Exception handling rules

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-404?page=all ] Gavin King updated JBSEAM-404: ------------------------------ Component/s: Core > Exception handling rules > ------------------------ > > Key: JBSEAM-404 > URL: http://jira.jboss.com/jira/browse/JBSEAM-404 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Louis Coetzee > > Seam provides the @Redirect annotation for use on Exception classes. It provides an attribute to specify the target viewId to redirect to once the exception has been thrown. It would be good if this view Id can be specified dynamically. > e.g. > @Name("napException") > @ApplicationException(rollback=true) > @Redirect(viewId = "#{napException.viewId}") > public class NAPException extends Exception implements Serializable { > or in xml > <from-view-id>/xxx.jsp</from-view-id> > <from-exception>com.myapp.NAPException</from-exception> > <to-view-id>/error.jsp</to-view-id> > <redirect/> -- 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

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-355) Constructor injection of component dependencies

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-355?page=all ] Gavin King updated JBSEAM-355: ------------------------------ Component/s: Core > Constructor injection of component dependencies > ----------------------------------------------- > > Key: JBSEAM-355 > URL: http://jira.jboss.com/jira/browse/JBSEAM-355 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Christian Bauer > Priority: Minor > > Take the registration example. The 'user' component is instantiated by Seam when JSF first looks for 'user' in a page. It is then put in the SESSION context (think CONVERSATION for other use cases of what I'm proposing). Seam uses the default constructor to instantiate the component. > Now imagine that some attributes of User are immutable and that the only way to set their values is through a different constructor. Also imagine that these values are actually present when Seam instantiates the 'user' component, e.g. in the current CONVERSATION. I'd like to tell Seam to call my constructor and use EL to bind the arguments. > Without this feature, immutable properties need to have public setter methods that I call later in an action method to wire in the required attributes manually. -- 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

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-427) contactlist example nonfunctional with JSF 1.2 RI

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-427?page=all ] Gavin King closed JBSEAM-427. ----------------------------- Resolution: Rejected You need to set up the ELResolver, as per the documentation. I have tested the example, it works fine. > contactlist example nonfunctional with JSF 1.2 RI > ------------------------------------------------- > > Key: JBSEAM-427 > URL: http://jira.jboss.com/jira/browse/JBSEAM-427 > Project: JBoss Seam > Issue Type: Bug > Reporter: Chuck Adams > > I'm using the JSF 1.2 RI in JBoss, and to get any example to run, I have to move el-api.jar and el-impl.jar to the jsf-libs directory and remove them from the war, or else the ConfigureListener bombs. No big deal, once I do that, the booking example works fine. > The same isn't the case for the contactlist example however: the search page works, but view and edit just bring up a blank contact. When I switched back to myfaces, it worked perfectly (even though I forgot to set jbossHasMyFacesLifecycleBug back to true) -- 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

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-497) NPE in Pages.createPage

by Ryan Dewell (JIRA)

NPE in Pages.createPage ----------------------- Key: JBSEAM-497 URL: http://jira.jboss.com/jira/browse/JBSEAM-497 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.0.BETA2 Reporter: Ryan Dewell This did not exist in 1.1.0 beta 1 or previous versions. It appears to be related to the new per-view configuration file instead of monolithic pages.xml. We have our own custom, restful, view handler on top Seam/JSF. ---- java.lang.NullPointerException at org.jboss.seam.core.Pages.createPage(Pages.java:212) at org.jboss.seam.core.Pages.getPage(Pages.java:201) at org.jboss.seam.core.Pages.getConvertedParameters(Pages.java:363) ---- Presumably this NPE can occur any time replaceExtension returns null. So a simple fix might be: ---- InputStream stream = null; String replaced = replaceExtension(viewId, ".page.xml"); if (replaced != null) stream = Resources.getResourceAsStream( replaced.substring(1) ); if (stream == null){ [...... 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

18 years, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-392) Add XML resolver from Hibernate so classpath:// prefix works

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-392?page=all ] Gavin King closed JBSEAM-392. ----------------------------- Fix Version/s: 1.1.0.BETA2 Resolution: Done Assignee: Gavin King I did this in BETA2 > Add XML resolver from Hibernate so classpath:// prefix works > ------------------------------------------------------------ > > Key: JBSEAM-392 > URL: http://jira.jboss.com/jira/browse/JBSEAM-392 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Christian Bauer > Assigned To: Gavin King > Priority: Minor > Fix For: 1.1.0.BETA2 > > > In a Hibernate XML mapping file you can load an XML entity declaration from the classpath. The same resolver should be used in Seam. -- 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

18 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-413) Support <foo>value</foo> as well as <property name="foo">value</property> in components.xml

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-413?page=comments#action_12346916 ] Gavin King commented on JBSEAM-413: ----------------------------------- The way we should handle this is by supporting XML namespaces. For example, there should be a DTD for a core: namespace which defines the properties of all the builtin components. And a jms: namespace, and a theme: namespace. Want to work on that next? > Support <foo>value</foo> as well as <property name="foo">value</property> in components.xml > ------------------------------------------------------------------------------------------- > > Key: JBSEAM-413 > URL: http://jira.jboss.com/jira/browse/JBSEAM-413 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1.0.CR1 > > -- 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

18 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2006