March 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-885) Restricting pages in pages.xml with wildcards

by Joshua Jackson (JIRA)

Restricting pages in pages.xml with wildcards --------------------------------------------- Key: JBSEAM-885 URL: http://jira.jboss.com/jira/browse/JBSEAM-885 Project: JBoss Seam Issue Type: Feature Request Components: Security Affects Versions: 1.1.6.GA Environment: JBoss AS 5.0.0.Beta1 Reporter: Joshua Jackson Priority: Optional If I have directory structure for pages as such: /department/home.xhtml /distributor/home.xhtml I'll be able to secure it in pages.xml with wildcards as such: <page view-id="/**/*"> <restrict /> </page> If I have directory structure as such: /order/purchase/home.xhtml /order/sales/home.xhtml I'll be able to secure it in pages.xml with wildcards as such: <page view-id="/order/purchase/*"> <restrict /> </page> Since with this pattern it only works if we define the role in <restrict> element as such: <page view-id="/order/purchase/*"> <restrict>#{s:hasRole('admin')}</restrict> </page> Also this pattern: <page view-id="/order/**/*"> <restrict /> </page> And this pattern: <page view-id="/**/**/*"> <restrict /> </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

19 years

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-334) Examples need changes to run on JBoss 5.x

by Stan Silvert (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-334?page=comments#action_12356850 ] Stan Silvert commented on JBSEAM-334: ------------------------------------- Yes, JBoss 5.x and JBoss 4.2 use the same JSF impl. > Examples need changes to run on JBoss 5.x > ----------------------------------------- > > Key: JBSEAM-334 > URL: http://jira.jboss.com/jira/browse/JBSEAM-334 > Project: JBoss Seam > Issue Type: Bug > Components: Examples > Affects Versions: 1.0.1 > Reporter: Stan Silvert > > The examples need to be updated so that they can deploy and run on JBoss 5.x. > JBoss 5.x ships with the RI JSF 1.2 implementation. To get the examples to run on JBoss 5.x, you need to remove this from web.xml: > <listener> > <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class> > </listener> > For JBoss 5.x, the listener for JSF 1.2 is added automatically, so you don't need to put it in web.xml. > Also, there are some third party libraries such as cglib that do not ship with JBoss 5.x. I was able to get the examples to run on JBoss 5.x by adding Seam's thridparty-all.jar to the server/default/lib directory. However, that's probably not the best way to handle the problem. -- 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

19 years

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1016) Change visibility of some methods in ExceptionFilter

by Leszek Kowalski (JIRA)

Change visibility of some methods in ExceptionFilter ---------------------------------------------------- Key: JBSEAM-1016 URL: http://jira.jboss.com/jira/browse/JBSEAM-1016 Project: JBoss Seam Issue Type: Feature Request Environment: Seam 1.2.0Patch1 Reporter: Leszek Kowalski It would be really nice if visibility of methods endWebRequestAfterException and rollbackTransactionIfNecessary could be changed from private to protected, so ExceptionFilter could be subclassed easily (for example to add some custom code if an exception occurs). -- 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

19 years

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-930) calendar input control disappears behind dropdown

by Guy Veraghtert (JIRA)

calendar input control disappears behind dropdown ------------------------------------------------- Key: JBSEAM-930 URL: http://jira.jboss.com/jira/browse/JBSEAM-930 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.1.7.CR1 Environment: IE 6 Reporter: Guy Veraghtert The calendar javascript has an issue when it comes to popups appearing on top of dropdown fields. It doesn't matter what z-index you set, DIVs will not popup on top of the dropdowns because it is being rendered by windows controls. The only way to do it is to popup using iframes and have the DIV reside inside the iframe. see also http://www.sharepointblogs.com/mkruger/archive/2006/10/03/13261.aspx -- 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

19 years

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-781) Identity.login is reporting a login failure with a SEVERITY_INFO

by Keith Naas (JIRA)

Identity.login is reporting a login failure with a SEVERITY_INFO ---------------------------------------------------------------- Key: JBSEAM-781 URL: http://jira.jboss.com/jira/browse/JBSEAM-781 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.1.5.GA Reporter: Keith Naas A login failure should be either a SEVERITY_ERROR or configurable. For instance, line 191 would be FacesMessages.instance().addFromResourceBundle(FacesMessage.SEVERITY_ERROR, "org.jboss.seam.loginFailed", "Login failed", ex); -- 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

19 years

4
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1035) Documentation uses taskInstanceListByType instead of ...ForType

by Arjan van Bentem (JIRA)

Documentation uses taskInstanceListByType instead of ...ForType --------------------------------------------------------------- Key: JBSEAM-1035 URL: http://jira.jboss.com/jira/browse/JBSEAM-1035 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 1.2.0.GA Environment: All Reporter: Arjan van Bentem Priority: Minor The documentation uses a few references to taskInstanceListByType, which should in fact read taskInstanceListForType, like <h:dataTable value="#{taskInstanceListByType['todo']}" var="task"> should be <h:dataTable value="#{taskInstanceListForType['todo']}" var="task"> When using the first, the logs show org.jboss.seam.Component seam component not found: taskInstanceListByType This only applies to the documentation; the example code is correct. -- 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

19 years

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-247) Inject microcontainer components

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-247?page=comments#action_12356815 ] Ales Justin commented on JBSEAM-247: ------------------------------------ We (MC team) are working on splitting MC into smaller fine grained artifacts. So that other projects could use MC more easily - standalone, IoC part, ... But using MC's XML configuration for Seam, that's Gavin's (Seam team) decision. I'm definitelly for unification of bean configuration accross JBoss projects. > Inject microcontainer components > -------------------------------- > > Key: JBSEAM-247 > URL: http://jira.jboss.com/jira/browse/JBSEAM-247 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Ales Justin > > We should be able to set up components using JBoss MC, and inject them into Seam components. -- 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

19 years

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-247) Inject microcontainer components

by Joshua Jackson (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-247?page=comments#action_12356813 ] Joshua Jackson commented on JBSEAM-247: --------------------------------------- Does this mean in the future the component XML configuration will be like Microcontainer style? If it does I think it is great because IMHO it is less verbose and we can get common configuration through out our Seam apps project. > Inject microcontainer components > -------------------------------- > > Key: JBSEAM-247 > URL: http://jira.jboss.com/jira/browse/JBSEAM-247 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Ales Justin > > We should be able to set up components using JBoss MC, and inject them into Seam components. -- 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

19 years

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-334) Examples need changes to run on JBoss 5.x

by Joshua Jackson (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-334?page=comments#action_12356806 ] Joshua Jackson commented on JBSEAM-334: --------------------------------------- I tried to make it work on JBoss 5.0.0.Beta1, and deployed it on JBoss 4.2.0.CR1 it doesn't work. AFAIK JBoss 5.0.0.Beta1 and JBoss 4.2.0.CR1 uses the same JSF RI library. > Examples need changes to run on JBoss 5.x > ----------------------------------------- > > Key: JBSEAM-334 > URL: http://jira.jboss.com/jira/browse/JBSEAM-334 > Project: JBoss Seam > Issue Type: Bug > Components: Examples > Affects Versions: 1.0.1 > Reporter: Stan Silvert > > The examples need to be updated so that they can deploy and run on JBoss 5.x. > JBoss 5.x ships with the RI JSF 1.2 implementation. To get the examples to run on JBoss 5.x, you need to remove this from web.xml: > <listener> > <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class> > </listener> > For JBoss 5.x, the listener for JSF 1.2 is added automatically, so you don't need to put it in web.xml. > Also, there are some third party libraries such as cglib that do not ship with JBoss 5.x. I was able to get the examples to run on JBoss 5.x by adding Seam's thridparty-all.jar to the server/default/lib directory. However, that's probably not the best way to handle the problem. -- 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

19 years

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-412) EJB 2 integration

by Joshua Jackson (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-412?page=comments#action_12356802 ] Joshua Jackson commented on JBSEAM-412: --------------------------------------- If this is supported I think it will be great as there are still many legacy apps are still using EJB2. Will it be supported through 1. Spring EJB support Abstract class 2. EJB3 3. Directly through Seam > EJB 2 integration > ----------------- > > Key: JBSEAM-412 > URL: http://jira.jboss.com/jira/browse/JBSEAM-412 > Project: JBoss Seam > Issue Type: Feature Request > Components: EJB3 > Reporter: Gavin King > Assigned To: Gavin King > > At least let EJB2 session beans be discovered and injected. -- 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

19 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues March 2007