January 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2476) Verify and attempt to use EAR/WAR ANTLR lib rather than weblogic 10's lib for examples in reference doc

by Jay Balunas (JIRA)

Verify and attempt to use EAR/WAR ANTLR lib rather than weblogic 10's lib for examples in reference doc ------------------------------------------------------------------------------------------------------- Key: JBSEAM-2476 URL: http://jira.jboss.com/jira/browse/JBSEAM-2476 Project: JBoss Seam Issue Type: Task Components: Examples Affects Versions: 2.0.1.GA Environment: Weblogic 10.3.TP Reporter: Jay Balunas Priority: Minor Current reference guide chapter for weblogic uses the ClassicQueryTranslatorFactory for the hibernate properties in persistence.xml file. This is listed as required because Weblogic ships with an older version of the ANTLR libraries. First verify the ANTLR version. If that is still a problem there may be a way to set a preference in the classloaders for libraries deployed in the EAR/WAR. Using ClassicQueryTranslatorFactory causes performance issues with hibernate. -- 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, 10 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2461) startup attribute missing from components-2.0.xsd for component

by Dan Allen (JIRA)

startup attribute missing from components-2.0.xsd for component --------------------------------------------------------------- Key: JBSEAM-2461 URL: http://jira.jboss.com/jira/browse/JBSEAM-2461 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.CR1 Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.0.1.GA Attachments: JBSEAM-2461-v1.txt For some reason the startup attribute is not present in the list of acceptable attributes for a <component> tag. -- 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, 10 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2462) attribute namefor meldware-user administrator property is wrong in XSD

by Dan Allen (JIRA)

attribute namefor meldware-user administrator property is wrong in XSD ---------------------------------------------------------------------- Key: JBSEAM-2462 URL: http://jira.jboss.com/jira/browse/JBSEAM-2462 Project: JBoss Seam Issue Type: Bug Components: Mail Affects Versions: 2.0.1.CR1 Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.0.1.GA meldware-user attribute for administrator property is listed as admin in XSD -- 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, 10 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2460) getValidator incorrectly references converterId in Param.java

by Dan Allen (JIRA)

getValidator incorrectly references converterId in Param.java ------------------------------------------------------------- Key: JBSEAM-2460 URL: http://jira.jboss.com/jira/browse/JBSEAM-2460 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.CR1 Reporter: Dan Allen Assigned To: Dan Allen Fix For: 2.0.1.GA Simple typo. Should be validatorId but is converterId. -- 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, 10 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2467) add supported-locale elements to faces-config.xml

by Dan Allen (JIRA)

add supported-locale elements to faces-config.xml ------------------------------------------------- Key: JBSEAM-2467 URL: http://jira.jboss.com/jira/browse/JBSEAM-2467 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.0.1.CR1 Reporter: Dan Allen Assigned To: Dan Allen Fix For: 2.0.1.GA Adding the <supported-locale> elements to faces-config.xml make it simple to create a drop-down list to be used with the locale switcher component. Java has built in support for rendering locale-specific labels for the languages, which makes it even all the more appropriate. This allows you to create the following UI component: Language: <h:selectOneMenu value="#{localeSelector.localeString}" valueChangeListener="#{localeSelector.select}" onchange="submit();"> <f:selectItems value="#{localeSelector.supportedLocales}"/> </h:selectOneMenu> -- 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, 10 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2470) core.jar needed for Drools support in seam-gen projects

by Dan Allen (JIRA)

core.jar needed for Drools support in seam-gen projects ------------------------------------------------------- Key: JBSEAM-2470 URL: http://jira.jboss.com/jira/browse/JBSEAM-2470 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.1.CR1 Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.0.1.GA core.jar should definitely be deployed along with seam-gen projects. The only reason a seam-gen application runs property on JBoss AS is because the core.jar class files are bundled within jasper-jdt.jar that is located in JBoss server/lib. This is purely coincidence and leads to immediate breakage on non JBoss servers. The core.jar simple needs to be added to the exploded archive. -- 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, 10 months

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

16 years, 10 months

3
6
0 / 0

[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

16 years, 10 months

3
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

16 years, 10 months

4
9
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

16 years, 10 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2008