[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
[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
[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
[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
[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