March 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2313) create a JBoss remote debug launch for Eclipse just like for NetBeans

by Dan Allen (JIRA)

create a JBoss remote debug launch for Eclipse just like for NetBeans --------------------------------------------------------------------- Key: JBSEAM-2313 URL: http://jira.jboss.com/jira/browse/JBSEAM-2313 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.0.0.GA Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.0.1.GA The NetBeans project is setup to remote debug JBoss on port 8787. However, Eclipse does not come with such a debug launch. Naturally if you use JBossTools, you are going to be able to do in-place debugging. However, there are some people that like to start JBoss AS from an external process, at which point it would be nice to be able to attach to it. This merely adds a launcher to the launch menu in Eclipse. -- 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

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2393) Query order by regexp fails when using lower/upper on a column

by Darryl Smith (JIRA)

Query order by regexp fails when using lower/upper on a column -------------------------------------------------------------- Key: JBSEAM-2393 URL: http://jira.jboss.com/jira/browse/JBSEAM-2393 Project: JBoss Seam Issue Type: Bug Components: Framework Affects Versions: 2.0.0.GA Reporter: Darryl Smith In o.j.s.framework.Query private static final Pattern ORDER_CLAUSE_PATTERN = Pattern.compile("^[\\w\\.,\\s]*$"); while this works with simple cases e.g. v.jobTitle asc it fails on lower(v.jobTitle) asc, is the proper way to order by a character field on many databases -- 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

3
6
0 / 0

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

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-2299?page=all ] Pete Muir closed JBSEAM-2299. ----------------------------- > 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.CR2 > > 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

18 years

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2264) @Observer with PostSetVariable produces Concurrent exceptions in a conversation scoped stateful bean

by Dan Hinojosa (JIRA)

@Observer with PostSetVariable produces Concurrent exceptions in a conversation scoped stateful bean ---------------------------------------------------------------------------------------------------- Key: JBSEAM-2264 URL: http://jira.jboss.com/jira/browse/JBSEAM-2264 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Environment: java 6_u03, jboss-4.2.1GA, jboss-seam-2.0.0.GA Reporter: Dan Hinojosa A method with an @Observer that listens to a postSetVariable event: @Name("myModule") @Scope(ScopeType.CONVERSATION) @Stateful public class MyModule implements ModuleLocal, ModuleRemote { @Observer("org.jboss.seam.postSetVariable.foo") public void process() { /* Do something */ } } produces a stack trace: [SeamPhaseListener] uncaught exception javax.el.ELException: javax.ejb.EJBTransactionRolledbackException: no concurrent calls on stateful bean 'jboss.j2ee:service=EJB3,name=MyModule' (EJB3 4.3.13) According to 3.1.10. Concurrency model of the 2.0.0 documentation: Finally, Seam enforces a single thread /per conversation per process/ model for the conversation context by serializing concurrent requests in the same long-running conversation context. The two 'per' is kind of confusing, but it seems that since Seam is serializing concurrent requests, this issue should not occur. Will create demo app shortly. -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2247) Error in resources-weblogic92/WEB-INF/web.xml included with jpa example

by first last (JIRA)

Error in resources-weblogic92/WEB-INF/web.xml included with jpa example ----------------------------------------------------------------------- Key: JBSEAM-2247 URL: http://jira.jboss.com/jira/browse/JBSEAM-2247 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: first last Target server: WLS 9.2.2 Built war using "ant weblogic92" Started examples server. Deployed war using console.. I get following error during deployment process when I try to activate changes: Error: failed to load java type corresponding to e=web-app@http://java.sun.com/xml/ns/javaee -- 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

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2279) duplicate seam component Id

by wu haixing (JIRA)

duplicate seam component Id --------------------------- Key: JBSEAM-2279 URL: http://jira.jboss.com/jira/browse/JBSEAM-2279 Project: JBoss Seam Issue Type: Bug Components: Wiki Affects Versions: 2.0.0.GA Environment: vista jdk-1.6.0_02 jboss-4.2.2.GA Reporter: wu haixing Assigned To: Christian Bauer Priority: Minor Here is the excepiton: 11:11:54,507 ERROR [[/wiki]] Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener java.lang.IllegalStateException: Two components with the same name and precedence: org.jboss.seam.remoting.gwt.gwtRemoteService I just delete jboss-seam-remoting.jar in the lib to get the application startup,but I not sure this is the solution -- 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

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2243) org.jboss.seam.persistence.HibernateSessionProxy does not implement org.hibernate.event.EventSource

by Bojan Cekrlic (JIRA)

org.jboss.seam.persistence.HibernateSessionProxy does not implement org.hibernate.event.EventSource --------------------------------------------------------------------------------------------------- Key: JBSEAM-2243 URL: http://jira.jboss.com/jira/browse/JBSEAM-2243 Project: JBoss Seam Issue Type: Patch Components: Core, EJB3 Affects Versions: 2.0.0.GA Reporter: Bojan Cekrlic When using the following search pattern: FullTextEntityManager fullTextEntityManager = org.hibernate.search.jpa.Search.createFullTextEntityManager(em); MultiFieldQueryParser parser = new MultiFieldQueryParser(new String[]{"username", "description"}, new SloAnalyzer()); org.apache.lucene.search.Query query = parser.parse( this.qs ); javax.persistence.Query hibQuery = fullTextEntityManager.createFullTextQuery( query, User.class ); The code dies with something in the lines of "FullTextHibernateSessionProxy cannot be cast to EventSource". This happens because of constructor in org.hibernate.search.impl.FullTextSessionImpl: public FullTextSessionImpl(org.hibernate.Session session) { this.session = (Session) session; this.eventSource = (EventSource) session; this.sessionImplementor = (SessionImplementor) session; } The quick solution is to fix org.jboss.seam.persistence.HibernateSessionProxy (which is extended by FullTextHibernateSessionProxy) to implement org.hibernate.event.EventSource and add the following code: public void delete(String arg0, Object arg1, boolean arg2, Set arg3) { ((EventSource) delegate).delete(arg0, arg1, arg2, arg3); } public void forceFlush(EntityEntry arg0) throws HibernateException { ((EventSource) delegate).forceFlush(arg0); } public ActionQueue getActionQueue() { return ((EventSource) delegate).getActionQueue(); } public Object instantiate(EntityPersister arg0, Serializable arg1) throws HibernateException { return ((EventSource) delegate).instantiate(arg0, arg1); } public void merge(String arg0, Object arg1, Map arg2) throws HibernateException { ((EventSource) delegate).merge(arg0, arg1, arg2); } public void persist(String arg0, Object arg1, Map arg2) throws HibernateException { ((EventSource) delegate).persist(arg0, arg1, arg2); } public void persistOnFlush(String arg0, Object arg1, Map arg2) { ((EventSource) delegate).persistOnFlush(arg0, arg1, arg2); } public void refresh(Object arg0, Map arg1) throws HibernateException { ((EventSource) delegate).refresh(arg0, arg1); } public void saveOrUpdateCopy(String arg0, Object arg1, Map arg2) throws HibernateException { ((EventSource) delegate).saveOrUpdateCopy(arg0, arg1, arg2); } I have not gone into details if any of these methods need to do EL interpolation or not, but my first hunch tells me that either no or it's not important for this usage scenario. -- 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

3
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2244) SpringTransaction doesn't pass the exception stack to the exception handler

by dapeng wang (JIRA)

SpringTransaction doesn't pass the exception stack to the exception handler --------------------------------------------------------------------------- Key: JBSEAM-2244 URL: http://jira.jboss.com/jira/browse/JBSEAM-2244 Project: JBoss Seam Issue Type: Feature Request Components: Spring Affects Versions: 2.0.0.GA Reporter: dapeng wang Fix For: 2.0.1.GA currently if a tx will be rollbacked, the SpringTransaction class kind of swallow the root cause in the following code Code: catch (TransactionSystemException e) { log.error("Exception cause:", e); throw new SystemException(e.getMessage()); } catch (UnexpectedRollbackException e) { log.error("Exception cause:", e); throw new RollbackException(e.getMessage()); } The problem is that the SystemException and RollbackException defined in JTA seem not to be able to take the case exception. But it is essential to pass the whole cause exception in SystemException and RollbackException instead of only a text message. My use case is the following: JSF delete action method tries to delete a row in the db. When the tx commits, it discovers the row can not be deleted because of foreign key constraint. I would like to have the ConstraintViolationException wrapped in the RollbackException, so that I have a chance to handle this exception later with the exception handler. In the current implmenetation, the RollbacklException with only text message and no cause stack will later be wrapped as an IllegalStateException, which is not helpful for exception handling at all. Please make the cause exception somehow accessible (ThreadLocal, or Seam Event Context), so that the error handling mechanism has a chance to do an exception handling. -- 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

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2151) Document and use com.ibm.ws.webcontainer.invokefilterscompatibility with ajax4jsf in hibernate2/jpa examples

by Pete Muir (JIRA)

Document and use com.ibm.ws.webcontainer.invokefilterscompatibility with ajax4jsf in hibernate2/jpa examples ------------------------------------------------------------------------------------------------------------ Key: JBSEAM-2151 URL: http://jira.jboss.com/jira/browse/JBSEAM-2151 Project: JBoss Seam Issue Type: Task Components: Examples Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Priority: Trivial Fix For: 2.0.1.GA -- 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
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2132) consult class attribute on component XML declaration with namespace

by Dan Allen (JIRA)

consult class attribute on component XML declaration with namespace ------------------------------------------------------------------- Key: JBSEAM-2132 URL: http://jira.jboss.com/jira/browse/JBSEAM-2132 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR2 Reporter: Dan Allen Assigned To: Dan Allen Priority: Critical Fix For: 2.0.1.GA When a component template class is being configured (such as EntityHome, EntityQuery, etc), the class attribute should be considered prior to deriving the class name from the namespace info + XML element name. Doing so prevents the case where two components are being configured for the same name when the developer intends only to use it for configuration. Case in point: Let's say I create a class that extends EntityHome to provide some extra behavior. @Name("myEntityHome") public class MyEntityHome extends EntityHome { } Now I want to configure the properties of this class in components.xml <framework:entity-home name="myEntityHome" class="org.example.model.MyEntityHome"> <framework:created-message>You created it! Yeah!</framework:created-message> <framework:updated-message>You updated it! Yeah!</framework:updated-message> <framework:deleted-message>You deleted it! Yeah!</framework:deleted-message> </framework:entity-home> If the class attribute is not consulted, it will look for a @Name annotation on org.jboss.seam.framework.EntityHome rather than org.example.model.MyEntityHome. When it doesn't find one on the built-in class, it tries to create a new component definition. Why would I want to use XML namespace tags in this case? Simple. Tag completion and property recognition support. Note that this works if the class resolved from XML namespace + element name is the same as the component class. In the case when the component class extends the built-in class, you get this 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

18 years

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