September 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2057) Syntax highlighting

by Gavin King (JIRA)

Syntax highlighting ------------------- Key: JBSEAM-2057 URL: http://jira.jboss.com/jira/browse/JBSEAM-2057 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Gavin King Assigned To: Christian Bauer I would love some way to do syntax highlighting in code blocks. Would require some extra wiki syntax of some kind, maybe <pre highlight="java">...</pre> or something. RIFE has some code we can probably reuse. This will make our blogs and docs *so* much more readable. -- 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, 1 month

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4171) Wiki Forum:Deadlock found when trying to get lock

by Francisco Jose Peredo Noguez (JIRA)

Wiki Forum:Deadlock found when trying to get lock ------------------------------------------------- Key: JBSEAM-4171 URL: https://jira.jboss.org/jira/browse/JBSEAM-4171 Project: Seam Issue Type: Bug Components: Wiki Reporter: Francisco Jose Peredo Noguez Assignee: Christian Bauer A week ago I was writing a long answer to a forum thread... I previewed it, it was fine, I clicked to post it and got (and of course lost all my text): HTTP Status 400 - Request failed, please check the application log or contact the administrator (christian.bauer(a)gmail.com): 'com.mysql.jdbc.exceptions.MySQLTransactionRollbackException, Deadlock found when trying to get lock; try restarting transaction in com.mysql.jdbc.SQLError@1042' type Status report message Request failed, please check the application log or contact the administrator (christian.bauer(a)gmail.com): 'com.mysql.jdbc.exceptions.MySQLTransactionRollbackException, Deadlock found when trying to get lock; try restarting transaction in com.mysql.jdbc.SQLError@1042' description The request sent by the client was syntactically incorrect (Request failed, please check the application log or contact the administrator (christian.bauer(a)gmail.com): 'com.mysql.jdbc.exceptions.MySQLTransactionRollbackException, Deadlock found when trying to get lock; try restarting transaction in com.mysql.jdbc.SQLError@1042'). -- 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, 1 month

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2529) Incorporate some of the pictures used in presentations into the ref doc

by Pete Muir (JIRA)

Incorporate some of the pictures used in presentations into the ref doc ----------------------------------------------------------------------- Key: JBSEAM-2529 URL: http://jira.jboss.com/jira/browse/JBSEAM-2529 Project: JBoss Seam Issue Type: Task Components: Documentation Reporter: Pete Muir Assigned To: Christian Bauer Priority: Minor Especially the contexts diagram -- 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, 1 month

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3889) Easier RestEasy paths

by John Ament (JIRA)

Easier RestEasy paths --------------------- Key: JBSEAM-3889 URL: https://jira.jboss.org/jira/browse/JBSEAM-3889 Project: Seam Issue Type: Feature Request Components: Remoting Environment: JSF based apps Reporter: John Ament Assignee: Shane Bryzak The rest easy integration is missing a few important integrations that would make using it in applications considerably easier. - s:link integrated resource paths based on actions. If I have a restful service defines as: @Path("/viewimage") @Name("viewImage") public class ViewImage implements java.io.Serializable .... @GET @Path("/{username}/{filename}") public byte[] viewImage(@PathParam("username")String username,@PathParam("filename")String filename) I should be able to define an s:link something like... <s:link action="#{viewImage.viewImage}"> <f:param name="username" value="#{someBean.someValue}" /> <f:param name="filename" value="#{someBean.someOtherValue}" /> <h:outputText value="View Image" /> </s:link> Or even a specialized graphicImage implementation that does soemthing similar... <s:graphicImage action="#{viewImage.viewImage}"> <f:param name="username" value="#{someBean.someValue}" /> <f:param name="filename" value="#{someBean.someOtherValue}" /> </s:graphicImage> Second, the resource path configuration in web.xml should be optional. The seam filter should be able to pull out the resources without needing the resource servlet directly handling the values. -- 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, 1 month

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2598) Exception handling - Never log and handle an exception, do one or the other

by Shane Bryzak (JIRA)

Exception handling - Never log and handle an exception, do one or the other --------------------------------------------------------------------------- Key: JBSEAM-2598 URL: http://jira.jboss.com/jira/browse/JBSEAM-2598 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Shane Bryzak Fix For: 2.1.0.GA Either I see my exception in the log (because it is one of the VERY RARE silently recoverable exceptions - I would not know a single one) or it is handled by my exception handler. Actually, I should never see an exception in my log unless I say so in my exception handler. I've seen Shane doing some commits about this but he only made logging configurable in Exceptions.handle(), which runs AFTER SeamPhaseListener already dumps a log.error("Uncaught exception", e). So basically, you can now configure if you want an exception logged twice or just once. This is btw killing me in production because my log fills up with login-password failures if someone makes a typo. -- 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, 1 month

4
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2601) Exception handling - Improve the exception reporting with more context information

by Shane Bryzak (JIRA)

Exception handling - Improve the exception reporting with more context information ---------------------------------------------------------------------------------- Key: JBSEAM-2601 URL: http://jira.jboss.com/jira/browse/JBSEAM-2601 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Shane Bryzak Fix For: 2.1.0.GA Once we clean up #{exception} and #{handledException} (remove one...), we need to add more context information. I don't know how to do that so I don't have any recommendation how this could be implemented - only that I heard that Tapestry has good exceptions. What I need (especially now in production) is more information about the request that triggered the exception. For example, I want to be able to reproduce the exception by executing the same GET/POST request. So this needs to include request header/parameter information and information about the server-side state (is it a new session, etc). I need to be able to access that information in my exception handler and for production optionally have it logged. Without this, I need to rely on user error reports which so far have not resulted in a single bugfix of the wiki, because I can't reproduce what the users are doing. -- 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, 1 month

5
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2296) @DataModelSelection makes tests impossible

by Christian Bauer (JIRA)

@DataModelSelection makes tests impossible ------------------------------------------ Key: JBSEAM-2296 URL: http://jira.jboss.com/jira/browse/JBSEAM-2296 Project: JBoss Seam Issue Type: Bug Components: Test Harness Reporter: Christian Bauer @Name("testBean") @Scope(ScopeType.CONVERSATION) @AutoCreate public class TestBean { @DataModel private List<String> names; public List<String> getNames() { return names; } public void setNames(List<String> names) { this.names = names; } @DataModelSelection private String name; public String getName() { return name; } public void setName(String name) { this.name = name; } public void init() { this.names = new ArrayList<String>(); this.names.add("A"); this.names.add("B"); this.names.add("C"); } } The test: @Test public void test() throws Exception { new FacesRequest() { protected void invokeApplication() throws Exception { TestBean testBean = (TestBean)getInstance("testBean"); testBean.init(); testBean.setName("B"); System.out.println("#### NAME IS: " + testBean.getName()); assert testBean.getName().equals("B"); } }.run(); } This test fails and prints the selected name as "A". If you remove @DataModelSelection, it prints the correct "B". -- 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, 1 month

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1469) @In for GWT clients

by Gavin King (JIRA)

@In for GWT clients ------------------- Key: JBSEAM-1469 URL: http://jira.jboss.com/jira/browse/JBSEAM-1469 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Reporter: Gavin King Assigned To: Shane Bryzak Fix For: 1.3.0.GA The GWT code to call a server-side component is *really* ugly. You should be able to get a Seam component just by injecting it into your GWT client-side object. -- 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, 1 month

7
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-982) Make SeamText parser more flexible

by Christian Bauer (JIRA)

Make SeamText parser more flexible ---------------------------------- Key: JBSEAM-982 URL: http://jira.jboss.com/jira/browse/JBSEAM-982 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer We need a more flexible seam-text.g - possibly several stages with an AST in the middle. This is needed for - generating PDF output from seam text - implementing a diff algorithm -- 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, 1 month

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3939) Seam's Resteasy implementation does not support multiple applications using resteasy on same server

by John Sublette (JIRA)

Seam's Resteasy implementation does not support multiple applications using resteasy on same server --------------------------------------------------------------------------------------------------- Key: JBSEAM-3939 URL: https://jira.jboss.org/jira/browse/JBSEAM-3939 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Environment: SEAM 2.1.1.GA with seam-resteasy patch described in https://jira.jboss.org/jira/browse/JBSEAM-3449, and RestEasy 1.0.1.GA. Running 2 Resteasy applications on Tomcat server. Reporter: John Sublette Priority: Minor Seam's Resteasy implementation does not support multiple applications using resteasy on same server. Problem is with ResteasyDispatcher.onStartup() where there is a call to ResteasyProviderFactory.setInstance() that register's the provider factory. When the second application calls this, it sets the static variable - thus overwriting the first application's. I have patched it to set a custom ResteasyProviderFactory subclass based on ThreadLocalResteasyProviderFactory instead. This subclass is a STATELESS Seam object that grabs the web-app appropriate providerFactory through a Seam Component.getInstance() call (injection may have worked too). -- 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, 1 month

3
10
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2009