April 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4117) Seam-gen generate EntityList with RESTRICTIONS which do not work for other JPA providers

by Julien Kronegg (JIRA)

Seam-gen generate EntityList with RESTRICTIONS which do not work for other JPA providers ---------------------------------------------------------------------------------------- Key: JBSEAM-4117 URL: https://jira.jboss.org/jira/browse/JBSEAM-4117 Project: Seam Issue Type: Bug Components: Tools Reporter: Julien Kronegg Each EntityList generated by Seam-gen contains RESTRICTIONS like: "lower(myEntity.myField) like lower(concat(#{myEntityList.myEntity.myField, '%'))" -- 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

15 years, 8 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2629) looking up content by user on seamframework.org

by Keith Naas (JIRA)

looking up content by user on seamframework.org ----------------------------------------------- Key: JBSEAM-2629 URL: http://jira.jboss.com/jira/browse/JBSEAM-2629 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Environment: Firefox 2.0.0.12 Reporter: Keith Naas Assigned To: Christian Bauer Priority: Trivial I would like to be able to see the content that I have created/modified or be able to search for it. I was trying to find a post that I made earlier today and so I typed in my username into the search field, clicked Find and waited for it to display in the results list, but alas it did not. Maybe the lastModifiedBy or createdBy could be indexed along with the content and dates? The member page could also display a list of content created/modified by that user. -- 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

15 years, 8 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4086) Migrate sfwk.org production database to UTF8

by Christian Bauer (JIRA)

Migrate sfwk.org production database to UTF8 -------------------------------------------- Key: JBSEAM-4086 URL: https://jira.jboss.org/jira/browse/JBSEAM-4086 Project: Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assignee: Christian Bauer The production database of seamframework.org was created without UTF8 support. The wiki throws exceptions if someone enters non-latin-1 characters. Migration is not really trivial in MySQL, need to look into a 10-line DBUnit export/import script. -- 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

15 years, 8 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4009) Email me when a message is posted in a forum thread I did posts

by Julien Kronegg (JIRA)

Email me when a message is posted in a forum thread I did posts --------------------------------------------------------------- Key: JBSEAM-4009 URL: https://jira.jboss.org/jira/browse/JBSEAM-4009 Project: Seam Issue Type: Feature Request Components: Wiki Affects Versions: 2.1.1.GA Reporter: Julien Kronegg Assignee: Christian Bauer There are now a lot of posts done on Seam forum. If you are not a regular user (e.g. you read the forum every 2-3 days), following threads in which you posted some messages is very difficult. It would be very convenient if the Wiki sends emails to the users which posted emails in a given thread when a new message is posted. This should: - improve the response time (because the users are aware of the new message very quickly) - decrease the amount of messages without answers - encourage users to post messages to the forum AFAIK, the Wiki now sends messages only to the user which created the thread, so sending an email for each post should not be very difficult. -- 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

15 years, 8 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4089) Allow for custom LogProviders

by Bob Thule (JIRA)

Allow for custom LogProviders ----------------------------- Key: JBSEAM-4089 URL: https://jira.jboss.org/jira/browse/JBSEAM-4089 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.1.GA Reporter: Bob Thule Please see forum: http://www.seamframework.org/Community/CustomLogProvider org.jboss.seam.log.Logging finds a log provider by: static LogProvider getLogProvider(String category, boolean wrapped) { return isLog4JAvailable ? new Log4JProvider(category, wrapped) : new JDKProvider(category, wrapped); } This does not allow users to supply a custom log provider. There are two reasons I can see for wanting to use a custom log provider: 1. To allow an alternative logging api, such as SLF4J. (for SLF$j, the current work-around for this is to use an log4j-to-slf4j bridge jar) 2. To allow custom work to be done, such as when error is called, to looking for an object in the contexts and to add a message to that object. i.e. public void error(String message, Exception e) { ((ErrorLog)Contexts.getSessionContext().get("errorLog")).add(message, e); if (level>=ERROR) logImp.error(message, e); } -- 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

15 years, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2873) Add ui for getting feed with or without comments

by Max Andersen (JIRA)

Add ui for getting feed with or without comments ------------------------------------------------ Key: JBSEAM-2873 URL: http://jira.jboss.com/jira/browse/JBSEAM-2873 Project: JBoss Seam Issue Type: Bug Components: Wiki Reporter: Max Andersen Assigned To: Christian Bauer -- 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

15 years, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3748) Adopt SLF4J to avoid expensive logging

by Anthony Whitford (JIRA)

Adopt SLF4J to avoid expensive logging -------------------------------------- Key: JBSEAM-3748 URL: https://jira.jboss.org/jira/browse/JBSEAM-3748 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.1.CR1 Reporter: Anthony Whitford Please consider adopting SLF4J as the core logging facade over Apache Commons Logging. When used properly, SLF4J provides improved performance and readability: Using ACL, evaluation of the logging messages still occur unless they are wrapped using code guards. For example, the following statement: log.debug("found in method context: " + name); still fragments memory by constructing the debug message even if debug is not enabled. The developer must use a code guard like: if ( log.isDebugEnabled() ) log.debug("found in method context: " + name); The guard will help circumvent the evaluation of the debug message, but the developer needs to take the initiative to add the code guard and this adds cyclomatic complexity. See: http://commons.apache.org/logging/commons-logging-1.1.1/guide.html#JCL%20... With SLF4J, the above can be simplified to: log.debug("found in method context: {}", name); The framework will delay evaluation of the debug message until after it checks if debug is enabled. If it is not, the message is not constructed, saving memory, and with limited hassle on the developer. Lazy programmers tend to avoid adding the code guards, especially when there is limited logging. SLF4J provides an opportunity to be efficient with less hassle. I would really like to see Seam adopt it as their core logging framework. (With the emphasis on performance, the 2.1 branch seems like a good opportunity.) Note that Hibernate has already adopted SLF4J. -- 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

15 years, 8 months

4
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2656) Watch a topic by email (or RSS?)

by Pete Muir (JIRA)

Watch a topic by email (or RSS?) -------------------------------- Key: JBSEAM-2656 URL: http://jira.jboss.com/jira/browse/JBSEAM-2656 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Pete Muir Assigned To: Christian Bauer This is necessary, especially for our non-core contributors who want to work on particular topics but don't have the resources to monitor the whole forum -- 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

15 years, 8 months

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4102) LoggingFilter throws NPE

by Christian Bauer (JIRA)

LoggingFilter throws NPE ------------------------ Key: JBSEAM-4102 URL: https://jira.jboss.org/jira/browse/JBSEAM-4102 Project: Seam Issue Type: Bug Components: Core Reporter: Christian Bauer Assignee: Christian Bauer Fix For: 2.1.2.GA LoggingFilter.java uses a) deprecated Identity.getUsername(); b) which throws NPE sometimes (seen on sfwk.org production log) 11:22:36,043 ERROR [[default]] Servlet.service() for servlet default threw exception java.lang.NullPointerException at org.jboss.seam.security.Identity.getUsername(Identity.java:653) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:50) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.wiki.core.ui.WikiUrlSessionIdFilter.doFilter(WikiUrlSessionIdFilter.java:86) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:562) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) Should obtain Credentials instance first, then check null, then username, then check null. -- 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

15 years, 8 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4107) Make app server deployment options more intuitive in seam gen

by John Ament (JIRA)

Make app server deployment options more intuitive in seam gen ------------------------------------------------------------- Key: JBSEAM-4107 URL: https://jira.jboss.org/jira/browse/JBSEAM-4107 Project: Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.1.2.CR1 Environment: Nightly build for 2.1.2 from trunk opensuse 11.1 x86_64 Reporter: John Ament Priority: Trivial seam setup could be a bit more intuitive when it comes to selecting default app server for deployment. Currently it is requesting: [input] Enter your JBoss AS home directory [C:/Program Files/jboss-4.2.3.GA] [C:/Program Files/jboss-4.2.3.GA] /opt/jboss/jboss-5.0.1.GA-1 [input] Enter your JBoss AS domain [default] [default] all [input] Enter your GlassFish V2 or V3 home directory (Ignore if you aren't deploying to GlassFish) [C:/Program Files/glassfish-v2.1] [C:/Program Files/glassfish-v2.1] [input] Enter your GlassFish domain (Ignore if you aren't deploying to GlassFish) [domain1] [domain1] Instead, maybe it could prompt with the following questions: Select your default app server [jboss] [glassfish] [tomcat] jboss Enter your JBoss AS home directory [] /path/to/jboss/install Enter your JBoss AS domain [] default Similar prompts for glassfish as well (and maybe only make tomcat available if you're deploying a war file?) I think by adding this, it would be easier to integrate additional app servers into the seam options. Of course, the flip side is that by doing this you're limited to a single app server deployment mode. For IT it's not a bad approach (since they're usually app server specific anyways). To alleviate this problem though, maybe add a new seam target add-appserver ? It can prompt for the same things I listed above. -- 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

15 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2009