January 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2446) Document how to set up the classpath and directory structure for Seam integration testing with Embedded JBoss

by Pete Muir (JIRA)

Document how to set up the classpath and directory structure for Seam integration testing with Embedded JBoss ------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2446 URL: http://jira.jboss.com/jira/browse/JBSEAM-2446 Project: JBoss Seam Issue Type: Task Components: Documentation, Test Harness Affects Versions: 2.0.1.CR1 Reporter: Pete Muir Fix For: 2.0.1.GA We currently have no docs on what jars you need on the classpath, and that seam.properties is required for your jar to be deployed -- 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

16 years, 11 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1883) Deleting a tree of wiki nodes does not update the Lucene index

by Christian Bauer (JIRA)

Deleting a tree of wiki nodes does not update the Lucene index -------------------------------------------------------------- Key: JBSEAM-1883 URL: http://jira.jboss.com/jira/browse/JBSEAM-1883 Project: JBoss Seam Issue Type: Bug Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Deletes of subtrees are done via database cascades, I need to query all identifiers before a delete (cheap with nested set) and remove them from the Lucene index. -- 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

16 years, 11 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2397) Implement trash feature for WikiFiles

by Christian Bauer (JIRA)

Implement trash feature for WikiFiles ------------------------------------- Key: JBSEAM-2397 URL: http://jira.jboss.com/jira/browse/JBSEAM-2397 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer WikiFile instances should not be deleted immediately, should be moved into a special "Trash" area. First implement moving of WikiFiles between directories, requires implementation of "select everything in a directory subtree" and "recreate that directory subtree". The idea is that everything goes into the same Trash area and we add a timestamp suffix to all WikiFile names to make them unique there. WikiComments are not affected, they are attached to the WikiFile by parent identifier, so they are ultimately removed when the WikiFile is cleared from the Trash. -- 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

16 years, 11 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2454) Pages raises event "org.jboss.seam.notLoggedIn", Documentation uses "org.jboss.seam.security.notLoggedIn"

by Thomas März (JIRA)

Pages raises event "org.jboss.seam.notLoggedIn", Documentation uses "org.jboss.seam.security.notLoggedIn" --------------------------------------------------------------------------------------------------------- Key: JBSEAM-2454 URL: http://jira.jboss.com/jira/browse/JBSEAM-2454 Project: JBoss Seam Issue Type: Bug Components: Documentation, Security Affects Versions: 2.0.1.CR1 Reporter: Thomas März Priority: Minor org.jboss.seam.navigation.Pages protected void notLoggedIn() { Events.instance().raiseEvent("org.jboss.seam.notLoggedIn"); FacesMessages.instance().addFromResourceBundleOrDefault( FacesMessage.SEVERITY_WARN, "org.jboss.seam.NotLoggedIn", "Please log in first" ); } Documentation: http://docs.jboss.com/seam/2.0.1.CR1/reference/en/html/security.html#d0e7094 http://docs.jboss.com/seam/2.0.1.CR1/reference/en/html/security.html#d0e7997 -- 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

16 years, 11 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2320) Query#refresh() should generate an event

by Dan Allen (JIRA)

Query#refresh() should generate an event ---------------------------------------- Key: JBSEAM-2320 URL: http://jira.jboss.com/jira/browse/JBSEAM-2320 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 2.0.0.GA Reporter: Dan Allen Priority: Minor Fix For: 2.0.x It is very useful to know when a query is refreshed, either because a parameter is dirty or because some other part of the application forced it to refresh itself. This message passing is extremely important when working in a caching situation. I am thinking something like: org.jboss.seam.queryRefreshed perhaps we pass the ejbql or the Query component as an parameter to the event -- 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

16 years, 11 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Resolved: (JBSEAM-2299) Seam Generate Entities creates edit field for @Version annotated fields

by Dan Allen (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-2299?page=all ] Dan Allen resolved JBSEAM-2299. ------------------------------- Resolution: Done > Seam Generate Entities creates edit field for @Version annotated fields > ----------------------------------------------------------------------- > > Key: JBSEAM-2299 > URL: http://jira.jboss.com/jira/browse/JBSEAM-2299 > Project: JBoss Seam > Issue Type: Bug > Components: Tools > Affects Versions: 2.0.0.GA > Reporter: Thorsten Kunz > Assigned To: Dan Allen > Priority: Minor > Fix For: 2.0.1.GA > > Attachments: JBSEAM-2299-v1.txt, JBSEAM-2299-v2.txt, JBSEAM-2299-v3.txt > > > When you have an entity with a @Version annotation present (which is the default if you create it with "Seam Entity") and then run "Seam Generate Entities" on the project and select "use existing entities" the resulting CRUD pages will allow the version field to be edited. So you won't be able to create entities because the set accessor for the version was declared private in the entity. This renders the CRUD pages useless. > I think this field should not be editable in the first place. > Cheers, Thorsten -- 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

16 years, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2426) seam-gen components.xml templates have incorrect event id for notLoggedIn redirect

by Andrew Atkinson (JIRA)

seam-gen components.xml templates have incorrect event id for notLoggedIn redirect ---------------------------------------------------------------------------------- Key: JBSEAM-2426 URL: http://jira.jboss.com/jira/browse/JBSEAM-2426 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.1.CR1 Reporter: Andrew Atkinson Fix For: 2.0.1.GA The components.xml seam-gen templates have an incorrect or outdated event id: <event type="org.jboss.seam.security.notLoggedIn"> <action execute="#{redirect.captureCurrentView}"/> </event> should be <event type="org.jboss.seam.notLoggedIn"> <action execute="#{redirect.captureCurrentView}"/> </event> -- 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

16 years, 11 months

4
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2458) UIAttachment uses incorrect field name to get document type

by Dan Allen (JIRA)

UIAttachment uses incorrect field name to get document type ----------------------------------------------------------- Key: JBSEAM-2458 URL: http://jira.jboss.com/jira/browse/JBSEAM-2458 Project: JBoss Seam Issue Type: Bug Components: Mail Affects Versions: 2.0.1.CR1 Reporter: Dan Allen Assigned To: Dan Allen Fix For: 2.0.1.GA Attachments: JBSEAM-2458-v1.txt The UIAttachment class uses reflection to get the document type from DocumentData. When DocumentData was refactored to use the field name documentType rather than docType, the reflection code did not get updated in this class. -- 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

16 years, 11 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2466) Support custom entity beans as JBPM process variables

by Marcus Schmidke (JIRA)

Support custom entity beans as JBPM process variables ----------------------------------------------------- Key: JBSEAM-2466 URL: http://jira.jboss.com/jira/browse/JBSEAM-2466 Project: JBoss Seam Issue Type: Feature Request Components: BPM Affects Versions: 2.0.0.GA Reporter: Marcus Schmidke In a non-Seam-EJB3-environment it is possible to configure jBPM such that EJB3 entity beans can be used as process variables. It would be nice if that would be even supported by Seam's jBPM support. Why doesn't it work today? The reason is in the way you combine jBPM and EJB3: - reference jBPM's hibernate.cfg.xml from persistence.xml such that the EJB3 PersistenceManager knows not only about EJB3 entities but also about jBPM entities - tell jBPM not to use it's own SessionFactory, but to get it from JNDI - tell jBPM not to create Hibernate sessions on it's own but inject the current Hibernate Session from PersistenceManager The last point is the problem with Seam. The injection has to be done manually every time a jbpmContext is created (via jbpmContext.setSession()), and Seam does not offer any hook to do this when it takes control over jbpmContext management. -- 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

16 years, 11 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2411) Create a JPA weblogic 10.0 examples resource and build scripts.

by Jay Balunas (JIRA)

Create a JPA weblogic 10.0 examples resource and build scripts. --------------------------------------------------------------- Key: JBSEAM-2411 URL: http://jira.jboss.com/jira/browse/JBSEAM-2411 Project: JBoss Seam Issue Type: Task Components: Examples Affects Versions: 2.0.1.CR1 Reporter: Jay Balunas Assigned To: Jay Balunas There are some differences between weblogic 9.2 and 10.0 and they should have their own resource setup in the JPA examples. This will go along with the updated reference guide on weblogic 10 integration. -- 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

16 years, 11 months

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