Here are the files (cut down, but still showing the error).
The application template:
|
| http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
| http://www.w3.org/1999/xhtml";
| xmlns:ui="http://java.sun.com/jsf/facelets";
| xmlns:s="http://jboss.com/products/seam/ta
I followed your suggestion except that I changed the name of the param from
manager to orderManager in the both the param tag and the included file. The
page displays correctly but invoking an action via
|
|
triggers the following exception
| Exception during request processing:
|
I am trying to reuse a facelets file in various use cases with a different
stateful session bean managing each use case.
In order to do that the beans outject themselves as "manager". For example:
| @Stateful @Name("auditOrderManager") public class AuditOrderManager {
| @Out AuditOrder
Solved
The missing piece was changing the JNDI name pattern in components.xml to
reflect the name of the old application (tukan).
Thanks for listening ;-).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083817#4083817
Reply to the post :
http://www.jbos
The demoManager is created using seam-gen's new-conversation target. The xhtml
page (as generated) has buttons for beginning and ending a conversation and for
incrementing a value, which is shown on the page. The bean has the
corresponding methods. Again, this is the raw product from the new-con
I'm trying to add Seam to an old EJB2 application so that we can do new
development in Seam and gradually port the old stuff into Seam.
I starting by merging the deployment directory of an "empty" Seam application,
SeamApp, (created with seam-gen new-project) into the exploaded deployment
legac
The exception is apparently just a manifestation of an earlier non-application
exception, (that caused the stateful session bean to be destroyed, I assume).
That exception occurred in fact due to a missing view in the database.
View the original post :
http://www.jboss.com/index.html?module=bb&
This exception has been happening on and off during the development.
The project is now in testing and inexplicably it started appearing again, both
on the test environment and the develoment environment, and not only on the
current version but also on 4 previous cvs versions, spanning 2 weeks,
Here is the mapped property for which the lazyloading appear to fail:
@OneToMany(cascade={CascadeType.PERSIST, CascadeType.MERGE})
| public List getKriterien() {
| return kriterien;
| }
|
| public void setKriterien(List kriterien) {
| this.k
I've isolated the cause if this to a call to an entitybean method, which
accesses mapped property (A list mapped to another table). If I call this
method from an action, it works. But when I call it during rendering, it fails
with the above Exception. Appearantly this is a problem with lazy load
I should have mentioned that I've got this error from time to time before, but
it has gone away without my intervention, (which makes it a bit scary). A
previous post on this error mentions its random appearance. I would be curious
to know ith there has been any progress on nailing down its caus
Caused by: javax.ejb.EJBTransactionRolledbackException:
javax.persistence.TransactionRequiredException: No active JTA transaction on
joinTransaction call
I get the above exception seemingly randomly. At least a cannot associate it
with anything. I have two versions of my project (a day or so o
Hello Seamers
I'm doing a pilot Seam application for my employer, which already uses
Hibernate and Spring. We like the ease of use, but we are wrestling with some
questions.
1. We would like to factor out any reusable "business logic" into a service
layer, possibly in a different EAR. It is cl
13 matches
Mail list logo
