October 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2038) Documentation of xml namespace component configuration not consistent with example

by Matt Drees (JIRA)

Documentation of xml namespace component configuration not consistent with example ---------------------------------------------------------------------------------- Key: JBSEAM-2038 URL: http://jira.jboss.com/jira/browse/JBSEAM-2038 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 2.0.0.CR1 Reporter: Matt Drees Priority: Minor As an example of a component that can be configured in components.xml, the documentation has: <pay:payment-home new-instance="#{newPayment}" created-message="Created a new payment to #{newPayment.payee}" /> However, the SeamPay example has: <pay:payment-home name="paymentHome" new-instance="#{newPayment}" created-message="Created a new payment to #{newPayment.payee}" /> I think I tried it once a few months ago, and the the first doesn't work. -- 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

17 years, 3 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2097) mapping events to cache updates.

by Gavin King (JIRA)

mapping events to cache updates. -------------------------------- Key: JBSEAM-2097 URL: http://jira.jboss.com/jira/browse/JBSEAM-2097 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Would be really nice to be able to say: <event type="...."> <evict-cache region="...."/> </event> Perhaps we could even go so far as: <event type="...."> <reset variable="...."/> </event> to reset context variables (though this one is more arguable). -- 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

17 years, 3 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2100) Allow same parameter more than once in a single restriction

by Diego Ballve (JIRA)

Allow same parameter more than once in a single restriction ----------------------------------------------------------- Key: JBSEAM-2100 URL: http://jira.jboss.com/jira/browse/JBSEAM-2100 Project: JBoss Seam Issue Type: Patch Components: Framework Affects Versions: 2.0.0.CR2 Reporter: Diego Ballve Priority: Minor Attachments: QueryParser.diff Sometimes you need to compare a restriction parameter w/ many fields in the same restriction. In those cases, I feel that it makes more sense to have multiple comparisons than to write something like :param IN (select1, select2, ...). The attached patch allows that, registering the same value binding once per restriction but allowing it to appear multiple times. -- 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

17 years, 3 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2096) conversationStack and conversationList don't get refreshed

by Norman Richards (JIRA)

conversationStack and conversationList don't get refreshed ---------------------------------------------------------- Key: JBSEAM-2096 URL: http://jira.jboss.com/jira/browse/JBSEAM-2096 Project: JBoss Seam Issue Type: Bug Reporter: Norman Richards Priority: Minor Fix For: 2.0.0.GA The changes here seem to be causing problems: http://fisheye.jboss.com/changelog/JBoss?cs=MAIN:gavin:20070708211336 I'm not sure if this affects other components, but the changes the values to be cached in page scope. This causes a problem if an action causes a conversation to begin but doesn't navigate to a new view. We should either revert the changes or perhaps change these components to EVENT scope. (I'm not sure if there are any issues moving to EVENT scope. If there are, then these should revert to being @Unwrap 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

17 years, 3 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2076) let EL access qualified @Factory and @Out names

by Matt Drees (JIRA)

let EL access qualified @Factory and @Out names ----------------------------------------------- Key: JBSEAM-2076 URL: http://jira.jboss.com/jira/browse/JBSEAM-2076 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Matt Drees Priority: Minor I can use "dot" qualified component names in EL. (I.e, I can use #{org.jboss.seam.security.identity.username} in my page instead of #{identity.username}). However, I can't do the same for @Factory variables (and presumably other kinds of non-component context variables). I'd like to. :-) -- 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

17 years, 3 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2063) raise an event on logout

by Matt Drees (JIRA)

raise an event on logout ------------------------ Key: JBSEAM-2063 URL: http://jira.jboss.com/jira/browse/JBSEAM-2063 Project: JBoss Seam Issue Type: Feature Request Reporter: Matt Drees Priority: Minor I'd like a "org.jboss.seam.postLogout" or maybe "org.jboss.seam.postSessionInvalidate" to observe. (I need to redirect the user to our single signin/out server). -- 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

17 years, 3 months

2
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-326) Dynamic view-id in Pageflow

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-326?page=comments#action_12381887 ] Pete Muir commented on JBSEAM-326: ---------------------------------- Note to self - should be just a call to Expressions - attached patch really bad ws issues. > Dynamic view-id in Pageflow > --------------------------- > > Key: JBSEAM-326 > URL: http://jira.jboss.com/jira/browse/JBSEAM-326 > Project: JBoss Seam > Issue Type: Feature Request > Components: BPM > Affects Versions: 1.1.0.BETA1 > Environment: seam cvs as of 8/2/2006 > Reporter: John Conner > Assigned To: Pete Muir > Fix For: 2.0.1.GA > > Attachments: pageflow-dynamic-view-id, pageflow-dynamic-view-id > > > I have a need where I would like to have an el expression in the view-id of a pageflow. I've looked a bit at themes; and while I might be able to do what I want by replacing the template.xhtml dynamically, I don't (at least initial) like indirection. > I believe the patch for this functionality is reletively trivial. Altough, I very well could have missed something. Basically, I modified the Page.getViewId() method to evaulate the value returned and replace any el expressions. > I also modified the Number Guess example to use this feature. > I have attached an initial patch as a proof of concept if it is of any interest to the Seam developers. > -- JC -- 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

17 years, 3 months

1
0
0 / 0

[jbossseam-issues] Multiple Datasources with Seam-Generated POJO entities, creates all tables in both datasources

by Ian Darwin

Summary of previous posts: http://lists.jboss.org/pipermail/jboss-user/2007-January/036530.html http://lists.jboss.org/pipermail/jboss-user/2007-January/032850.html Both give a general how-to story http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071027#4071027 http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034669#4034669 Both give partial examples, ending with Code: @PersistenceContext(unitName="db1-PU") private EntityManager db1EntityManager; There are two problems: 1) The seam-gen created code doesn't use an explicit EntityManager, but just an @Entity-annotated POJO for the model and two helper classes, ClassNameHome (extends EntityHome<ClassName>) and ClassNameList extends EntityQuery, neither of which has an EntityManager field. Annotating the various classes with the PersistenceContext does not help. Secondly, perhaps as a result, all the entities get created in both databases. Third, how can we make sure that import.sql is only applied against one of the datasources? TIA Ian Darwin

17 years, 3 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1647) Document concept of disinjection

by Matt Drees (JIRA)

Document concept of disinjection -------------------------------- Key: JBSEAM-1647 URL: http://jira.jboss.com/jira/browse/JBSEAM-1647 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.BETA1 Reporter: Matt Drees Priority: Minor The documentation doesn't talk about disinjection. It surprised me quite a bit when I read the source code for BijectionInterceptor to find that all @In attributes get nulled after method invocation. -- 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

17 years, 3 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2080) Security documentation should use "insert" instead of "assert" terminology

by Matt Drees (JIRA)

Security documentation should use "insert" instead of "assert" terminology -------------------------------------------------------------------------- Key: JBSEAM-2080 URL: http://jira.jboss.com/jira/browse/JBSEAM-2080 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Reporter: Matt Drees Priority: Optional The security documentation contains phrases like "asserted into the working memory". While drools used to use "assert" to put stuff in the working memory, now it uses "insert". So, it makes sense (to me, anyway) to match the change in terminology. -- 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

17 years, 3 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues October 2007