I think the SSO is a big issue when we suggest clients to adopt Seam. I try
the CAS SSO and rewrite Authenticator and Pages classes
according to CAS wiki but it does not work properly. Even I can use SSO in
two Seam applications, the seam application does not work same as
before. The reason seems that Seam can not handle
navigation(pages.xml/x.page.xml) correctly any more. For example, when I
login a simple CRUD Seam application and create a new entity, after I click
save button, the entity is created successfully but I am not navigated to
the Entity.xhtml and stayed at the same edit page. When I click list page,
and click View/Edit link of the entity, the entity's information is not
shown at the corresponding fields. They are all empty.
In fact, the CAS SSO adds some filters in web.xml. Does them affect Seam's
navigation? After I remove CAS SSO configuration, all works fine.
SSO is a common requirement of many clients. Can somebody help to figure out
what happened? Thanks.
JBoss Solution Architect
RedHat Service Center, P.R.China
I got a doubt about the support to Drools 5 announced on Seam 2.2.0 release
notes (and posts on blogs all over the internet, like the In Relation
"We've also moved our Drools <http://www.jboss.org/drools/> support from
Drools 4 to Drools 5"
Maybe I'm misunderstanding exactly what Seam team intended to say, but I got
In SVN, there's another branch, called Seam_2_2_Drools5, and there's a lot
of commits trying to integrate Seam and the Drools 5 API. On the otherhand,
the branch Seam_2_2 really doesn't seems to support this API (KnowledgeBase
and other new stuff).
It looks like I still have to use the old drools 4 api to make Seam 2.2.0
work with Drools.
Am I wrong?
Graduando do Departamento de Ciência da Computação
Universidade Federal do Rio de Janeiro
I would like to implement REQUIRES_NEW as a transaction type for the
@Transactional annotation. My basic plan is:
- Create a TransactionManager component that can be installed into
components.xml, and give the option to configure the JNDI location of
the JTA TransactionManager.
- modify the Work.workInTransaction method to check if the existing
transaction need to be suspended, as if so use the TransactionManager
component to suspend and resume the transaction.
I can't help thinking that there is some problem with this approach,
otherwise someone else would have already done it.
I also know that TransactionManager is not supposed to be used by the
application, does anyone know if this will cause problems?
I would also like to implement the ability to control seam global
transactions based on a flag in pages.xml, so they can be disabled for
specific views. Would anyone have any objections to this?
I have tried to find Maven versions of Seam and required libraries in
order to fix https://jira.jboss.org/jira/browse/JBIDE-4813.
I have succeeded to find versions of the required libraries in
<SEAM_HOME>/build/root.pom.xml, but haven't succeeded to find the
version of Seam (root.pom.xml contains @seam.version@). I have also
tried to find the version of Seam within the jboss-seam.jar file. For
EAP 5.0, the jboss-seam.jar file contains the 2.2.0.EAP version that
isn't any Maven version.
Is it possible to find the Maven version of Seam within any Seam