Section 28.5. Annotations for use with Seam JavaBean components in a J2EE
environment in the manual is still mostly TBD
Any chance this section will be complete soon?
thx and bravo for the great work..
View the original post :
No problem for us:
- Seam 1.2.1
- JSF RI 1.2_07
- RicgFaces 3.1.3
- facelets 1.1.13
- WebSphere 6.1.0.13
Also ok with RF 3.2.0, latest snapshot
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4118498#4118498
Reply to the post :
is it possible to use custom seam interceptor around invocation of methods of
Seam POJO Components?
In the Seam 1.2.1 manual, section 5.2, it is written You can even use Seam
interceptors with JavaBean components, not just EJB3 beans!
How to do that? is there some sample somewhere?
I tried to
Hie Joe
i plan to write a kind of bullet point list on how to make seam 1.2.1 work with
was v6.1.0.11 but we are very very busy now.
We also can't migrate to seam 2.0 because of bug seam-2029 which is blocking
for us
In the meantime, to anser your question:
- we use POJOs (we dind't want to try
Pete,
if i remove the richefaces*.jar, i got this exception ,even if we don't use
ajax4jsf...:
| java.lang.NoClassDefFoundError: org.ajax4jsf.component.html.HtmlLoadStyle
| at java.lang.ClassLoader.defineClassImpl(Native Method)
| at
using seam 2.0 RC1
In a seam component, we are using Hibernate to get an instance of a
persistent instance which is not a seam componnent and we receive an
IllegalArgumentException .
It seems that, after Hibernate perfoemed the sql select, seam tries to build
a seam component from a class
In section 25.1.4 of the doc, it is explained how to configure the ajax4jsf
filter (web:ajax4jsf-filter ...)
Is there a way to completely disable the ajax4jsf filter?
Thx
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4090837#4090837
Reply to the post :
Seam runs fine for us on websphere 6.1.0.11 + JSF RI 1.2_04Sp2 + facelets
1.1.12.
What is your specific problem?.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4087569#4087569
Reply to the post :
With seam 1.2.1, is it possible to create a seam component in a servlet filter?
If so how to do it?
In web.xml, I declare a filter after all other filters 9seam, jsf, etc...)
In components.xml:
|component name=test.utilisateur auto-create=true scope=session
Problems #1 and #2 solved! This is a known feature of WebSphere v6.1.
To make it run, it is necessary that the following Webcontainer custom property
be set to 'true': com.ibm.ws.webcontainer.invokefilterscompatibility
See this link for explanation:
Opened PMR at IBM for problem #1
Am I the only one to get this problem? anyone else with problem #2?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4065220#4065220
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4065220
We have an online application build around seam, POJOs and hibernate.
Our business seam components (managers + model classes) are isolated into a
separate jar file (common.jar), the view controler seam components (aka
backing beans) are directly held into the war module, the war module calling
Done: http://jira.jboss.com/jira/browse/JBSEAM-1680
Thanks Gavin!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4064677#4064677
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4064677
When testing the hibernate2 sample of seam 2.0 beta, on was v6.1.0.9, the
ajax4jsf resources URI are not routed to the aja4jsf filter.
Aja4jsf adds the following line in the pages with aja4jsf tags (ie pages
book.xhtml, main.xhml, register.xhtml):
| script type=text/javascript src=/my
Running seam 1.2.1 on WebSphere v6.1.0.9, I get this exception:
| java.lang.NoClassDefFoundError: org.jboss.system.ServiceMBeanSupport
| at java.lang.ClassLoader.defineClassImpl(Native Method)
| at java.lang.ClassLoader.defineClass(ClassLoader.java:228)
| at
Michael, the app is packaged in the classic ear/war way, if the proxy is
correctly configured, it works.
However, as Pete stated it, this parsing stuff is new with seam2 and I don't
think this is aceptable that, on startup, the application makes hundreds of
call on internet to validate all the
Thx. I'll test it when the next (beta?) release will be out.
Michael, I've sent you a minimal ear file to test seam 2.0beta on was v6.1.0.9
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4063205#4063205
Reply to the post :
The fix will be in fixpack 6.1.0.11. Estimated GA: August 31 2007
APAR id: PK47367
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4062702#4062702
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4062702
seam v2.0beta takes ages to start on WebSphere v6.1.0.9
I use seam 2.0 beta, JSF 1.2 RI + facelets, and seam takes ages to start
(1.5h+). In the log4j traces I see those messages related to a problem with a
DTD validation
| ...
| DEBUG [core.Events ] - Processing
Pete, this is org.jboss.seam.util.DTDEntityResolver.
Michael, yes it is ...but behind a proxy...and it does not appear to be
configured correctly (at least the properties in the JVM are not correctly set)
BUT. Even if it was correctly configured, I don't want to have seam connect
hundreds
I have good news for who is using seam with WebSphere v6.1
After having opened a PMR with IBM, they fixed the problem that caused the
ClassCastException.
I can now run jboss-seam 1.2.1 on WebSphere with the IBM JSF 1.1 implementation
of WebSphere v6.1.0.9, with the interim fix they send me.
I have good news for who is using seam with WebSphere v6.1
After having opened a PMR with IBM, they fixed the problem that caused the
ClassCastException.
I can now run jboss-seam 1.2.1 on WebSphere with the IBM JSF 1.1 implementation
of WebSphere v6.1.0.9, with the interim fix they send me.
I think you should set both ear and war classloaders to PARENT_LAST to be sure
that the web container picks the JSF implementation you have in WEB-INF/lib,
like for MyFaces. Check the related IBM technote here:
Oups I forgot: To my knowledge, JSF 1.2 needs servlet 2.5 which is part of
J2EE5...and websphere 6.1 only implements servlet 2.4 for J2EE 1.4
I don't know if you'll be able to make it work in WAS v6.1
View the original post :
Ok. looks similar to the problem we have with seam 1.2.1 +was v6.1.0 + JSF
Implementation from WAS (not MyFaces..).
have a look my previous post here :
http://www.jboss.com/index.html?module=bbop=viewtopict=107948
I have open a PMR with IBM for it and still wait for an answer from IBM
View the
Gavin and shushamen, FYI I've opned a PMR with IBM on this.
I'm waiting for feedback, I'll keep you informed
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4051502#4051502
Reply to the post :
cool, but the questions behind my problem were:
1) do you have to use MyFaqes instead of the JSF implementation of WAS (Is it
your case)?
2) Indeed, if you put all your code in the war, seam works, but this is not
acceptable to us. We have to separate our sevices/managers/model classes into a
oups...
I forgot the hibernate patch to make hibernate work with seam.
See bug HHH-2160 in hibernate
(http://opensource.atlassian.com/projects/hibernate/browse/HHH-2160)
This bug has been reported with was 6.0.2.15 + DB2 9.1, we also have it with
was 6.1.0.7 + db2 v8.2.7
View the original post
Alain, we reached the same point and this is a major point for us to NOT use
seam all the way (This is the only problem with seam we see in fact...)
The problem is the same if you use POJOs instead of EJB3 and try to isolate
those POJOs in an utiliy jar deployed in your ear, and keep only the
It works on was v6.1.0.7,
...but:
- You have to put all your code in a war (we were not able to make it work by
splitting the code between a war and an utility jar...if you know how to do,
tell us please )
- You have to use MyFaces instead of the the JSF 1.1 implementation included
with was
No. I didn't know there was a ejb3 feature pack for was...
In the related forum, it is said that it needs exactly was v6.1.0.3 ma ybe it's
your problem (we are in v6.1.0.7)
In fact we are using regular POJO + Hibernate 3.2.4 + @Transactional
annotations and plain standard jta transactions.
I had
I'm not 100% of your last statement, I finally made it to work with the
following config (but i'm not satisfied with it, mostly because of the
parent_last classloader on the war and the need to use myfaces...):
- have jboss-seam-ui.jar,
Hello,
I'm trying to setup a project with seam 1.2.1 on WebSphere v6.1.0.7.
WAS v6.1.0.7 has a JSF 1.1 implementation based on JSF Sun RI. When WAS tries
to start the application, I get the following exception:
WebAppE Extension processor failed to initialize in factory: [EMAIL
33 matches
Mail list logo
