June 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-4814) MAX_ROWS reached error message instead displays MAX_COLUMNS

by Derek MacDonald (JIRA)

MAX_ROWS reached error message instead displays MAX_COLUMNS ----------------------------------------------------------- Key: JBSEAM-4814 URL: https://issues.jboss.org/browse/JBSEAM-4814 Project: Seam 2 Issue Type: Bug Components: Excel Affects Versions: 2.2.2.Final Reporter: Derek MacDonald Priority: Minor Fix For: 2.3.0.ALPHA When the 65535 row limit of a spreadsheet is reached, the generated exception's message mistakenly displays the limit as 255. org/jboss/seam/excel/jxl/JXLExcelWorkbook.java Line 130: 129 if (currentRowIndex >= MAX_ROWS) { 130 throw new ExcelWorkbookException(Interpolator.instance() 131 .interpolate("Excel only supports {0} rows", MAX_COLUMNS)); 132 } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-4821) Typos in documentation

by Jozef Hartinger (JIRA)

Typos in documentation ---------------------- Key: JBSEAM-4821 URL: https://issues.jboss.org/browse/JBSEAM-4821 Project: Seam 2 Issue Type: Bug Components: Documentation Issues Affects Versions: 2.2.2.Final Reporter: Jozef Hartinger Assignee: Marek Novotny Priority: Minor Fix For: 2.3.0.ALPHA Annotations.xml: spell check failed on 'annotationed' Annotations.xml: spell check failed on 'precendence' Annotations.xml: spell check failed on 'signalling' Cache.xml: spell check failed on 'depoyment' ClusteringAndEJBPassivation.xml: spell check failed on 'addressses' ClusteringAndEJBPassivation.xml: spell check failed on 'Ejb' (should be EJB) ClusteringAndEJBPassivation.xml: spell check failed on 'infrastruture' ClusteringAndEJBPassivation.xml: spell check failed on 'prematurally' ClusteringAndEJBPassivation.xml: spell check failed on 'reassociate' (should be re-associate) ClusteringAndEJBPassivation.xml: spell check failed on 'thise' ClusteringAndEJBPassivation.xml: spell check failed on 'tranfered' ClusteringAndEJBPassivation.xml: spell check failed on 'transfered' ClusteringAndEJBPassivation.xml: spell check failed on 'unserializing' (should be deserializing) Concepts.xml: spell check failed on 'absense' Concepts.xml: spell check failed on 'automagically' Concepts.xml: spell check failed on 'dependecies' Concepts.xml: spell check failed on 'Javabeans' (should be JavaBeans) Concepts.xml: spell check failed on 'precedece' Concepts.xml: spell check failed on 'precendence' Concepts.xml: spell check failed on 'programatically' Concepts.xml: spell check failed on 'threadsafeness' Concepts.xml: spell check failed on 'visable' Configuration.xml: repeated instance(s) of 'be'. Configuration.xml: spell check failed on 'aggrevating' Configuration.xml: spell check failed on 'compoenent' Configuration.xml: spell check failed on 'thar' Controls.xml: spell check failed on 'contol' Controls.xml: spell check failed on 'occured' Conversations.xml: spell check failed on 'could't' Conversations.xml: spell check failed on 'overriden' Conversations.xml: spell check failed on 'thats' Dependencies.xml: spell check failed on 'libraies' Drools.xml: spell check failed on 'alse' Events.xml: spell check failed on 'propreties' Excel.xml: spell check failed on 'childrens' Excel.xml: spell check failed on 'ths' Excel.xml: spell check failed on 'verically' Getting_Started_With_JBoss_Tools.xml: spell check failed on 'arguements' Getting_Started_With_JBoss_Tools.xml: spell check failed on 'deloyed' Getting_Started_With_JBoss_Tools.xml: spell check failed on 'engieneer' Glassfish.xml: repeated instance(s) of 'the'. I18n.xml: spell check failed on 'hexidecimal' Itext.xml: repeated instance(s) of 'to'. Itext.xml: spell check failed on 'definied' Jbpm.xml: spell check failed on 'jDPL' Mail.xml: spell check failed on 'asynchrounously' Mail.xml: spell check failed on 'musn't' Persistence.xml: repeated instance(s) of 'be'. Persistence.xml: spell check failed on 'loosly' Persistence.xml: spell check failed on 'persisence' Persistence.xml: spell check failed on 'vaues' Preface.xml: repeated instance(s) of 'and'. Remoting.xml: spell check failed on 'containining' Rss.xml: spell check failed on 'elemenents' Security.xml: spell check failed on 'chosing' Security.xml: spell check failed on 'ompletely' Security.xml: spell check failed on 'omputers' Security.xml: spell check failed on 'overriden' Security.xml: spell check failed on 'permisison' Security.xml: spell check failed on 'precendence' Security.xml: spell check failed on 'relevent' Security.xml: spell check failed on 'Thie' Security.xml: spell check failed on 'trival' Security.xml: spell check failed on 'ublic' Security.xml: spell check failed on 'umans' Security.xml: spell check failed on 'uring' Security.xml: spell check failed on 'utomated' Testing.xml: spell check failed on 'Javadoc' Testing.xml: spell check failed on 'testng' (should be TestNG) Text.xml: spell check failed on 'Javadoc' Tools.xml: repeated instance(s) of 'the'. Tutorial.xml: repeated instance(s) of 'of'. Tutorial.xml: repeated instance(s) of 'the'. Tutorial.xml: spell check failed on 'achive' Tutorial.xml: spell check failed on 'attibute' Tutorial.xml: spell check failed on 'configration' Validation.xml: spell check failed on 'Hiberate' Validation.xml: spell check failed on 'higlighting' Weblogic.xml: repeated instance(s) of 'the'. Webservices.xml: spell check failed on 'defauls' Websphere.xml: spell check failed on 'annd' Websphere.xml: spell check failed on 'cutomized' Websphere.xml: spell check failed on 'ejb' Wicket.xml: spell check failed on 'automagically' Wicket.xml: spell check failed on 'iinstrumentation' Xml.xml: repeated instance(s) of 'the'. Xml.xml: spell check failed on 'namespaced' -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMFACES-165) @Inject for Validators doesn't work with MyFaces

by Christian Kaltepoth (JIRA)

@Inject for Validators doesn't work with MyFaces ------------------------------------------------ Key: SEAMFACES-165 URL: https://issues.jboss.org/browse/SEAMFACES-165 Project: Seam Faces Issue Type: Bug Components: Validation & Conversion Affects Versions: 3.0.1 Environment: Tomcat 7.0.8, MyFaces 2.0.5, Weld 1.1.0 Reporter: Christian Kaltepoth @Inject doesn't work for validators when using MyFaces. The fields are always null. If I run the application with Mojarra instead of MyFaces everything works fine. I'm note completely sure if it is a Seam Faces or a MyFaces issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3355) SeamExpressionEvaluator gobbles up exceptions

by Wolfgang Schwendt (JIRA)

SeamExpressionEvaluator gobbles up exceptions ---------------------------------------------- Key: JBSEAM-3355 URL: https://jira.jboss.org/jira/browse/JBSEAM-3355 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.BETA1 Reporter: Wolfgang Schwendt Priority: Critical Rev 8710 of org.jboss.seam.bpm.SeamExpressionEvaluator introduced a serious bug. If the invocation of the method expression (me.invoke(...)) throws an exception such as org.jboss.seam.security.AuthorizationException, the SeamExpressionEvaluator afterwards tries to evaluate the EL expression as a value expression. This of course results in a second exception thrown: PropertyNotFoundException. Consequently, the list "exceptions" has size > 2 (rather than just size==1), which results in SeamExpressionEvaluator throwing an ELException that does not wrap the exception which originally caused the method expression invocation to fail. The bug was introduced because, compared with earlier versions, the try/catch-blocks for the method expression and value expression evaluation were changed and are now wrong. This is serious because it breaks the handling of any application exception thrown while evaluating the EL method expression, such as AuthorizationException. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (SOLDER-109) Add a converter API to Solder

by George Gastaldi (JIRA)

Add a converter API to Solder ----------------------------- Key: SOLDER-109 URL: https://issues.jboss.org/browse/SOLDER-109 Project: Seam Solder Issue Type: Feature Request Reporter: George Gastaldi Solder could provide a converter API as http://static.springsource.org/spring/docs/3.1.x/spring-framework-referen... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (SEAMREST-19) ValidationInterceptor not triggered on GF

by Jozef Hartinger (JIRA)

ValidationInterceptor not triggered on GF ----------------------------------------- Key: SEAMREST-19 URL: https://issues.jboss.org/browse/SEAMREST-19 Project: Seam REST Issue Type: Bug Components: Bean Validation Affects Versions: 3.0.0.Alpha3 Environment: GF 3.1b37 JDK6U23 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Seam Tasks example - the ValidationInterceptor is not triggered. Probably a bug in GF. Need to write a test for that. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (SEAMFACES-126) Throw an some kind of unauthorized exception when auth fails, rather than returning a 401 response

by Brian Leathem (JIRA)

Throw an some kind of unauthorized exception when auth fails, rather than returning a 401 response -------------------------------------------------------------------------------------------------- Key: SEAMFACES-126 URL: https://issues.jboss.org/browse/SEAMFACES-126 Project: Seam Faces Issue Type: Enhancement Components: Security, View Configuration Reporter: Brian Leathem Fix For: 3.0.1 If authorization fails, and the user is not logged in, Faces looks for a @LoginViewId to redirect to, and returns a 401 response if none is found. A similar story applies for the @AccessDeniedViewId It would be better to instead throw an exception, that Seam Catch can intercept. If not intercepted, this exception would eventually lead to a 401 response. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (SEAMCRON-15) CL issues on redeployment

by Peter Royle (JIRA)

CL issues on redeployment ------------------------- Key: SEAMCRON-15 URL: https://issues.jboss.org/browse/SEAMCRON-15 Project: Seam Cron Issue Type: Bug Reporter: Peter Royle Assignee: Peter Royle Diablo-D3 gets it on every redeployment (from Eclipse to JBoss AS 6) and I have seen it once (using NetBeans redeploying after sitting overnight). The sumptom is the 'Singleton is not set' error. In a conversation about this Stuart Douglas explained how I can solve this: (04:42:51 PM) stuartdouglas: something that did just occur to me is that weld will probably not work very well in this new thread anyway, unless you set the TCCL to the correct one (04:43:07 PM) PeteRoyle: TCCL? (04:43:16 PM) stuartdouglas: Thread Context Class Loader (04:43:28 PM) stuartdouglas: weld uses it a lot, even for stuff that should not need it to be set (04:43:51 PM) stuartdouglas: so if it is not set you end up with highly informative 'Singleton is not set' errors (04:44:30 PM) PeteRoyle: Ahah! I've been getting those sporadically on redeployment (04:44:45 PM) PeteRoyle: But to do with scheduling, not asynch (04:44:49 PM) PeteRoyle: (so far) (04:45:20 PM) stuartdouglas: those are pretty much always due to the wrong class loader being set as the TCCL (04:45:54 PM) stuartdouglas: also the only beans that will be accessible is @ApplicationScoped and @Dependant (04:46:10 PM) stuartdouglas: unless you put in some non-portable code to set up the contexts (04:46:11 PM) PeteRoyle: Is there a typical cure for that which doesn (04:46:29 PM) PeteRoyle: ''t require knowledge of how classloading works? (04:47:34 PM) stuartdouglas: not really, it depends where you get the errors, it should only be a problem when you start trying to use threads that you have spawned yourself to interact with weld (04:48:31 PM) stuartdouglas: for @Async the solution is to set the TCCL to the same as the original threads TCCL, and set it back in a finally block (04:49:11 PM) stuartdouglas: and it should really be run as a PriviliedAction, because a security manager might not let you set it (04:50:22 PM) marekn [~mnovotny@nat/redhat/x-wgsrrhabedyogdbb] entered the room. (04:50:39 PM) PeteRoyle: I get what you're saying, but I'm not sure how to do that stuff (04:50:54 PM) PeteRoyle: (setting the TCCL and running as PrivAction) (04:51:57 PM) stuartdouglas: https://github.com/stuartwdouglas/jboss-as/blob/master/weld/src/main/java... (04:52:11 PM) stuartdouglas: https://github.com/stuartwdouglas/jboss-as/blob/master/weld/src/main/java... (04:52:43 PM) stuartdouglas: note that SecurityActions is package private, otherwise any class can use it to set the TCCL (04:53:42 PM) stuartdouglas: basically it just wraps Thread.currentThread().set/getContextClassLoader (04:54:38 PM) PeteRoyle: Should I copy this code into Cron, (or Solder) to make it portable? (04:55:09 PM) stuartdouglas: it needs to be copied each time (04:55:38 PM) stuartdouglas: otherwise any code can get/set the TCCL (04:56:02 PM) kevinpollet [~kevinpoll(a)217.112.54.72] entered the room. (04:56:56 PM) PeteRoyle: OK so do I set the TCCL as the first thing in the new thread? (04:56:59 PM) amitev [~amitev(a)212.25.36.84] entered the room. (04:57:06 PM) stuartdouglas: yes (04:57:11 PM) PeteRoyle: (frm within the thread, say inside the run() method)? (04:57:17 PM) stuartdouglas: yes (04:57:34 PM) PeteRoyle: and unset it from a finally block from the original thread which screate the new thread (04:57:52 PM) PeteRoyle: screate=created (04:58:21 PM) stuartdouglas: yes, although you can just set it to null rather than saving and restoring the existing TCCL (04:59:01 PM) stuartdouglas: otherwise if you are using a thread pool the TCCL can hang around after redeployment, which results in a memory leak (04:59:47 PM) PeteRoyle: actually it looks like all the examples in WeldContainer do both those things in the same thread. Can I unset the TCCL at the end of the run() method (in a finally)? (04:59:58 PM) maschmid [~maschmid@nat/redhat/x-fjnivohxvbmhnpfw] entered the room. (05:00:00 PM) stuartdouglas: yes (05:00:06 PM) PeteRoyle: ok (05:00:33 PM) stuartdouglas: oops, sorry, I mis-read your earlier question (05:00:50 PM) stuartdouglas: you should only manipulate it inside the run method (05:00:57 PM) PeteRoyle: ok gotchya -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (SEAMCRON-2) Implement asynchronous method invocation for managed beans

by Dan Allen (JIRA)

Implement asynchronous method invocation for managed beans ---------------------------------------------------------- Key: SEAMCRON-2 URL: https://issues.jboss.org/browse/SEAMCRON-2 Project: Seam Cron Issue Type: Feature Request Reporter: Dan Allen Assignee: Peter Royle Fix For: 3.0.0.Alpha1 Implement thread pool-based asynchronous method invocation for managed (non-EJB) beans. This feature allows developers to mark a method for background execution using an annotation. {code:java} public class BeanWithAsyncMethod { @Asynchronous public void doLongOperation() { ... } } {code} To be forward thinking, we should put the @Asynchronous annotation (and related) and the dispatcher interface in Solder so that we can have different providers. For instance, Seam JMS could alternatively be used to execute the method over JMS to provide guaranteed execution instead of Seam Cron's default thread pool approach. You can use similar functionality from Seam 2 as a reference: http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/src/main/... We may consider offering the task control (Future) that EJB 3.1 provides, though you can create that as a separate issue if you deem it follow-up work. See: http://download.oracle.com/javaee/6/tutorial/doc/gkkqg.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBSEAM-4815) clean up icefaces example

by judy guglielmin (JIRA)

clean up icefaces example -------------------------- Key: JBSEAM-4815 URL: https://issues.jboss.org/browse/JBSEAM-4815 Project: Seam 2 Issue Type: Task Components: Examples Affects Versions: 2.2.2.Final Environment: ICEfaces-1.8.3, jsf1.2 various application servers Reporter: judy guglielmin Assignee: judy guglielmin Fix For: 2.3.0.ALPHA to ensure ice:dataTable has ice:columns as children, and the import.xml has an extra space at the bottom of the file which causes grief in some of the application servers. Mostly for going forwards with (not-released) versions of ICEfaces. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 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 June 2011