[jboss-user] [JBoss Seam] - Section 28.5 in the manual...when?
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 : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123294#4123294 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123294 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Does Seam 1.2 go well with richfaces 3.1.2 or 3.1.3?
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=bb&op=viewtopic&p=4118498#4118498 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118498 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Seam 1.2.1 + POJO + @Interceptor: possible?
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 use the @Interceptor annotation without success.. My goal is to catch Hibernate exceptions when a method of some component annoted with @Transactional is called, some problem occured and the transaction is rollback, and to "convert" some of them to a business exception... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107891#4107891 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4107891 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Run JSF RI on WebSphere 6.1
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 the ejb3 technology preview currently available from ibm) - ear and war classloader have to be set to parent_last - components.xml: | | http://jboss.com/products/seam/components"; |xmlns:core="http://jboss.com/products/seam/core"; |xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; |xsi:schemaLocation="http://jboss.com/products/seam/core http://jboss.com/products/seam/core-1.2.xsd http://jboss.com/products/seam/components http://jboss.com/products/seam/components-1.2.xsd";> | | | | | | | | ressources.administrateur | ... | | | | | | | | | - hibernate.cfg.xml (partial) | http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd";> | | | | java:comp/env/jdbc/promopunch2 | com.saq.util.hibernate.dialect.DB28Dialect | | SAQPP | true | true | true | | true | after_statement | org.hibernate.transaction.WebSphereExtendedJTATransactionLookup | org.hibernate.transaction.JTATransactionFactory | | | ... | | | | web.xml (partial | | http://java.sun.com/xml/ns/j2ee"; |xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; |xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd";> |PromoPunchWeb | | | javax.faces.STATE_SAVING_METHOD | server | | | javax.faces.DEFAULT_SUFFIX | .xhtml | | | com.sun.faces.preferXHTML | true | | | facelets.LIBRARIES | /WEB-INF/promopunch.taglib.xml | | | | | org.ajax4jsf.VIEW_HANDLERS | com.sun.facelets.FaceletViewHandler | | | org.richfaces.SKIN | ruby | | | | | facelets.DEVELOPMENT | true | | | com.sun.faces.verifyObjects | true | | | com.sun.faces.validateXml | true | | | com.sun.faces.displayConfiguration | true | | | | Initialisation Promopunch (Avant Seam) | com.saq.pp.web.listener.ListenerInitPreSeam | | | JBoss Seam Listener | org.jboss.seam.servlet.SeamListener | | | JSF Listener | com.sun.faces.config.ConfigureListener | | | Initialisation Promopunch (Apres Seam) | com.saq.pp.web.listener.ListenerInitPostSeam | | | | | Empeche l'appel direct ÃÂ la page de login | Filtre Page Login | com.saq.pp.web.filter.FiltrePageLogin | | | | Filtre Seam | org.jboss.seam.web.SeamFilter | | | RichFaces | org.ajax4jsf.Filter | | | Verifie que l'application a bien ete initialisee | Filtre Application Initialisee | com.saq.pp.web.filter.FiltreApplicationInitialisee | | | Gestion des objets de session Promopunch | Filtre Gestion Session | com.saq.pp.web.filter.FiltreGestionSession | | | | | Filtre Page Login | /login/login.jsp | | | | Filtre Seam | /* | | | RichFaces | *.jsf | | | Filtre Application Initialisee | *.jsf | | | Filtre Gestion Session | *.jsf | | | | | Faces Servlet | javax.faces.webapp.FacesServlet | 1 | | | Seam Resource Servlet | org.jboss.seam.servlet.ResourceServlet | 2 | | | | Faces Servlet | *.jsf | | | Seam Resource Servlet | /seam/resource/* | | | | 403 | /pages/erreurs/erreur_403.jsf | | | 404 | /pages/erreurs/erreur_404.jsf | | | 500 | /erreur.jsp | | | java.lang.Throwable | /erreur.jsp | | | | index.html | | | | login | | HTTPS | /login/login.jsp | GET | POST | | | ToutLeMonde | ToutleMonde | | | CONFIDENTIAL | | | | ... | | | jdbc/promopunc
[jboss-user] [JBoss Seam] - Re: Seam 2.0 RC1: how to disable the ajax4jsf filter?
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 java.lang.ClassLoader.defineClass(ClassLoader.java:228) | at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:148) | at com.ibm.ws.classloader.CompoundClassLoader._defineClass(CompoundClassLoader.java:555) | at com.ibm.ws.classloader.CompoundClassLoader.findClass(CompoundClassLoader.java:506) | at com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:389) | at java.lang.ClassLoader.loadClass(ClassLoader.java:573) | at java.lang.ClassLoader.defineClassImpl(Native Method) | at java.lang.ClassLoader.defineClass(ClassLoader.java:228) | at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:148) | at com.ibm.ws.classloader.CompoundClassLoader._defineClass(CompoundClassLoader.java:555) | at com.ibm.ws.classloader.CompoundClassLoader.findClass(CompoundClassLoader.java:506) | at com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:389) | at java.lang.ClassLoader.loadClass(ClassLoader.java:573) | at java.lang.Class.forNameImpl(Native Method) | at java.lang.Class.forName(Class.java:163) | at com.sun.faces.util.Util.loadClass(Util.java:227) | at com.sun.faces.application.ApplicationImpl.newThing(ApplicationImpl.java:1003) | at com.sun.faces.application.ApplicationImpl.createComponent(ApplicationImpl.java:539) | at org.jboss.seam.jsf.SeamApplication.createComponent(SeamApplication.java:91) | at com.sun.faces.config.ConfigureListener.verifyObjects(ConfigureListener.java:1302) | at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:397) | at com.ibm.ws.wswebcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:641) | at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:298) | at com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:289) | at com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:90) | at com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157) | at com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:665) | at com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:618) | at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:335) | at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:551) | at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1301) | at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1138) | at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:569) | at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:817) | at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:950) | at com.ibm.ws.runtime.component.ApplicationMgrImpl$1.run(ApplicationMgrImpl.java:1484) | at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:3997) | at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:4094) | at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:245) | at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:1489) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) | at java.lang.reflect.Method.invoke(Method.java:615) | at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:62) | at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) | at java.lang.reflect.Method.invoke(Method.java:615) | at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:265) | at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1089) | at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:971) | at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:231) | at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:238) | at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833) | at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBe
[jboss-user] [JBoss Seam] - Re: Seam 2.0 RC1: how to disable the ajax4jsf filter?
simplybecause we don't use ajax4jsf in our project and this will remove a useless filter (for our project) and also remove the need to include richefaces* jar in our ear files. Maybo also sightly improve performance(?) and reduce the loength odf stacktraces ..lol IMHO, there should be an option in seam to simply disable the ajax4jsf filter View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091012#4091012 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091012 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: seam tries tio create a seam component from a class whic
Pete, for us, this is a critical/blocking bug and the status should be set to "blocker" in JIRA. The code is running well on seam 1.2.1, and this problem forces us to wait until seam 2.0.1 is out before migrating to seam 2.0... I'm sure they are lots of projects ou there that are using plain POJOs for persistence that will have the same problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091007#4091007 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091007 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Seam 2.0 RC1: how to disable the ajax4jsf filter?
In section 25.1.4 of the doc, it is explained how to configure the ajax4jsf filter (http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090837#4090837 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090837 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - seam tries tio create a seam component from a class which is
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 which is *not* a seam component
Is this a bug? is this a configuration problem?
The "Utilisateur" class si a plain POJO... (We do't use EJB3..)
Also, we use in
componente.xml
| @Name("utilisateurManager")
| @Scope(ScopeType.APPLICATION)
| @Startup
| public class UtilisateurManagerImpl extends ManagerHibernate implements
UtilisateurManager {
|@In
|private Session sessionHibernate;
|
|@Transactional(TransactionPropagationType.REQUIRED)
|public Utilisateur obtenirUtilisateurParCodeUsager(String codeUsager) {
| return (Utilisateur) sessionHibernate.get(Utilisateur.class,
codeUsager.toUpperCase());
|}
|
| [02/10/07 17:23:02:759 EDT] 0028 viewhandler E Error Rendering
View[/pages/accueil.xhtml]
| java.lang.IllegalArgumentException: Not an
entity class: com.saq.pp.metier.modele.Utilisateur
| at org.jboss.seam.Entity.forClass(Entity.java:208)
| at
org.jboss.seam.security.Identity.checkEntityPermission(Identity.java:665)
| at
org.jboss.seam.security.HibernateSecurityInterceptor.onLoad(HibernateSecurityInterceptor.java:35)
| at
org.hibernate.event.def.DefaultPreLoadEventListener.onPreLoad(DefaultPreLoadEventListener.java:18)
| at
org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:125)
| at
org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:854)
| at org.hibernate.loader.Loader.doQuery(Loader.java:729)
| at
org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236)
| at org.hibernate.loader.Loader.loadEntity(Loader.java:1860)
| at
org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:48)
| at
org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:42)
| at
org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3044)
| at
org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:395)
| at
org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:375)
| at
org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:139)
| at
org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:195)
| at
org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:103)
| at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:878)
| at org.hibernate.impl.SessionImpl.get(SessionImpl.java:815)
| at org.hibernate.impl.SessionImpl.get(SessionImpl.java:808)
| at
org.jboss.seam.persistence.HibernateSessionProxy.get(HibernateSessionProxy.java:181)
| at
com.saq.pp.metier.manager.UtilisateurManagerImpl.obtenirUtilisateurParCodeUsager(UtilisateurManagerImpl.java:41)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
|
(Line UtilisateurManagerImpl.java:41 correspond to the sessionHibernate.get(..)
statement)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090835#4090835
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4090835
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Run JSF RI on WebSphere 6.1
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=bb&op=viewtopic&p=4087569#4087569 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087569 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - How to programatically create a seam component in a filter?
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:
|
|
In the servlet filter class, I have:
| public void doFilter(ServletRequest req, ServletResponse resp,
FilterChain chain) throws IOException, ServletException {
| chain.doFilter(req, resp);
| Utilisateur cx = (Utilisateur)
Component.getInstance("test.utilisateur");
|}
|
This result in the following exception:
| java.lang.IllegalStateException: No application context active
| at org.jboss.seam.Component.forName(Component.java:1577)
| at org.jboss.seam.Component.getInstance(Component.java:1627)
| at org.jboss.seam.Component.getInstance(Component.java:1610)
| at org.jboss.seam.Component.getInstance(Component.java:1604)
| at com.saq.pp.web.filter.FiltreTest.doFilter(FiltreTest.java:70)
| at
com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
| at
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
| at
com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
| at
com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:761)
| at
com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:673)
| at
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:498)
| at
com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:464)
| at
com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
| at
com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:744)
| at
com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1433)
| at
com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:112)
| at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)
| at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383)
| at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:263)
| at
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
| at
com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
| at
com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
| at
com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
| at
com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
| at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
| at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
| at
com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
| at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
| at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
|
I have the same results with Component.getInstanceFromFactory()
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066695#4066695
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066695
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Problem with ajax4jsf resources with WebSphere v6.1.0.9
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: http://www-1.ibm.com/support/docview.wss?uid=swg24014758 I now have the "hibernate2" sample of seam 2.0beta that fully works on was v6.1.0.9 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4066138#4066138 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4066138 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Problem with ajax4jsf resources with WebSphere v6.1.0.9
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=bb&op=viewtopic&p=4065220#4065220 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065220 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Problem with ajax4jsf resources with WebSphere v6.1.0.9 and
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):
|
|
But this resource (it returns the javascript that holds the A4J function) is
never processed ("A4J" is not defined in firefox error console) by WAS due to 2
problems :
First problem:
It seems that on was v6.1.0.9, a request is routed to a filter only if a
servlet-mapping is defined for the URL. In my web.xml file, I have the
following for filters and servlets:
|
| Seam Filter
| org.jboss.seam.servlet.SeamFilter
|
|
| Seam Filter
| /*
|
|
| Faces Servlet
| javax.faces.webapp.FacesServlet
| 1
|
|
| Seam Resource Servlet
|
org.jboss.seam.servlet.SeamResourceServlet
| 2
|
|
| Faces Servlet
| *.seam
|
|
| Seam Resource Servlet
| /seam/resource/*
|
|
It seems that even if the URI match the pattern for the filter, the filter
never sees this request because (IMO), there is no servlet with a matchng
pattern
Adding the following lines in web.xml makes the
"/a4j.res/org.ajax4jsf.framework.ajax.AjaxScript" to be processed by the seam
filter
|
| Seam Resource Servlet
| /a4j.res/*
|
|
I will ask the IBM support and eventually open a PMR for this.
But even with this, the browser never receives the ajax4jsf javascript related
to the "/a4j.res/org.ajax4jsf.framework.ajax.AjaxScript" URI.
Second problem:
In the org.jboss.seam.servlet.SeamFilter.java at line 66, "bf.getUrlPattern()"
for the ajax4jsf filter returns "*.seam"
So as the requested resource ("/a4j.res/org.ajax4jsf.framework.ajax.AjaxScript"
) does not match the pattern, it is not processed by the ajax4jsf filter.
In org.jboss.seam.servlet.SeamFilter.java, adding the line
"bf.setUrlPattern(null);" in line 66 as follow, makes it work:
|if (filter instanceof AbstractFilter) {
| AbstractFilter bf = (AbstractFilter) filter;
|
| log.debug(" pattern=" + bf.getUrlPattern());---> display "*.seam"
| bf.setUrlPattern(null); ---> ugly hack
|
| if (bf.isMappedToCurrentRequestPath(request)) {
| filter.doFilter(request, response, this);
| } else {
| this.doFilter(request, response);
| }
|} else {
| filter.doFilter(request, response, this);
|}
|
Is this second problem a WebSphere problem? is it a configuration problem? is
it a bug in seam?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064800#4064800
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064800
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Batch process with seam: what is the best approach?
Done: http://jira.jboss.com/jira/browse/JBSEAM-1680 Thanks Gavin! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064677#4064677 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064677 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Batch process with seam: what is the best approach?
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
the classes into the common.jar module.
We have the need for batch processes, ie processesthat will run outside any
web/jee container, with a standard j2se jdk, from a plain java class, possibly
running for hours. Those processes will use the seam common components from the
common.jar file.
The high level algorithm is :
| - bootstrap the seam engine
| - for each business item to process (maybe tens of thousand or more...):
| - begin transaction
| - do some business stuff that update the database
| - commit
| - shutdown the seam engine
|
What is the best way to do that with seam? Is it possible to do this without
instanciating or faking a web container?, ie without having in the batch
classpath, jars like "servlet.jar" eand "j2ee.jar"? or something like the jboss
embedded container?
We looked at the SeamTest class as the "bootstrap" class, but SeamTest depends
on javax.faces.*, javax.servlet.* and org.testng.* classes and is fully
designed to test online components...
Or maybe the jboss embedded container is the way to go?
Thx for your guidance here.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064578#4064578
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064578
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - seam 1.2.1 on WAS: NoClassDefFoundError: org.jboss.system.Se
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 java.security.SecureClassLoader.defineClass(SecureClassLoader.java:148) | at com.ibm.ws.classloader.CompoundClassLoader._defineClass(CompoundClassLoader.java:526) | at com.ibm.ws.classloader.CompoundClassLoader.findClass(CompoundClassLoader.java:477) | at com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:382) | at java.lang.ClassLoader.loadClass(ClassLoader.java:573) | at java.lang.ClassLoader.defineClassImpl(Native Method) | at java.lang.ClassLoader.defineClass(ClassLoader.java:228) | at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:148) | at com.ibm.ws.classloader.CompoundClassLoader._defineClass(CompoundClassLoader.java:526) | at com.ibm.ws.classloader.CompoundClassLoader.findClass(CompoundClassLoader.java:477) | at com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:382) | at java.lang.ClassLoader.loadClass(ClassLoader.java:573) | at org.jboss.seam.util.Reflections.classForName(Reflections.java:159) | at org.jboss.seam.init.Initialization.addSpecialComponents(Initialization.java:774) | at org.jboss.seam.init.Initialization.init(Initialization.java:502) | at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33) | at com.ibm.ws.wswebcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:637) | at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:295) | at com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:285) | at com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:88) | at com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157) | at com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:655) | at com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:608) | at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:335) | at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:551) | at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1312) | at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1129) | at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:569) | at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:814) | at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:965) | at com.ibm.ws.runtime.component.ApplicationMgrImpl$1.run(ApplicationMgrImpl.java:1495) | at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:3995) | at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:4092) | at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:245) | at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:1500) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) | at java.lang.reflect.Method.invoke(Method.java:615) | at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:62) | at sun.reflect.GeneratedMethodAccessor41.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) | at java.lang.reflect.Method.invoke(Method.java:615) | at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:265) | at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1089) | at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:971) | at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:231) | at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:238) | at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833) | at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:802) | at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1080) | at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118) | at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:973) | at com.ibm.ws.management.connector.Admin
[jboss-user] [JBoss Seam] - Re: seam v2.0beta takes ages to start on WebSphere v6.1.0.9
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=bb&op=viewtopic&p=4063205#4063205 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4063205 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: seam v2.0beta takes ages to start on WebSphere v6.1.0.9
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 ejb-jar.xml files it finds (present on the classpath?). On production, our servers are even not allowed to do that! I'll wait for the status on this. If you think this is a WAS problem, just tell me with the relevant information. As you know Michael I have an acces to IBM to open PMRs if needed. Thx for your help and analysis and also for that great product View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062938#4062938 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062938 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: seam v2.0beta takes ages to start on WebSphere v6.1.0.9
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 of time on the internet to validate.what exactly? Is there a way to not let seam do that validation? I'm not using EJB3 but plain POJOs and there are no EJB in the application. There is only 2 seam "user" components. The ear is a clone of the "registration" sample (ie without the persistent stuff) and I'm trying to make seam 2.0 + facelets to work on WAS v6.1 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062762#4062762 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062762 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - seam v2.0beta takes ages to start on WebSphere v6.1.0.9
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 event:org.jboss.seam.preSetVariable.org.jboss.seam.ui.entityConverterStore.component | DEBUG [seam.Component] - instantiating Seam component: org.jboss.seam.core.events | DEBUG [seam.Component] - initializing new instance of: org.jboss.seam.core.events | DEBUG [seam.Component] - done initializing: org.jboss.seam.core.events | DEBUG [seam.Component] - instantiating Seam component: org.jboss.seam.core.events | DEBUG [seam.Component] - initializing new instance of: org.jboss.seam.core.events | DEBUG [seam.Component] - done initializing: org.jboss.seam.core.events | DEBUG [core.Events ] - Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.ui.entityConverterStore.component | DEBUG [util.DTDEntityResolver] - trying to resolve system-id [http://java.sun.com/dtd/ejb-jar_2_0.dtd] | WARN [init.Initialization ] - Couldn't parse META-INF/ejb-jar.xml for component types Operation timed out: connect:could be due to invalid address Nested exception: Operation timed out: connect:could be due to invalid address | DEBUG [util.DTDEntityResolver] - trying to resolve system-id [http://java.sun.com/dtd/ejb-jar_2_0.dtd] | WARN [init.Initialization ] - Couldn't parse META-INF/ejb-jar.xml for component types Operation timed out: connect:could be due to invalid address Nested exception: Operation timed out: connect:could be due to invalid address | DEBUG [util.DTDEntityResolver] - trying to resolve system-id [http://java.sun.com/dtd/ejb-jar_2_0.dtd] | WARN [init.Initialization ] - Couldn't parse META-INF/ejb-jar.xml for component types Operation timed out: connect:could be due to invalid address Nested exception: Operation timed out: connect:could be due to invalid address | INFO [seam.Component] - Component: org.jboss.seam.ui.graphicImage.graphicImageResource, scope: APPLICATION, type: JAVA_BEAN, class: org.jboss.seam.ui.graphicImage.GraphicImageResource | DEBUG [seam.Component] - instantiating Seam component: org.jboss.seam.core.events | ... | It seems it's trying to validate something against the ejb-jar_2_0.dtd file. It does this for most of the classes present in jboss-seam.jar and jboss-seam-ui.jar. Where does this come from? is there something missing in my classpath? is it related to seam or to WebSphere? is there a way to disable this validation? will I win to the lottery next saturday? That makes a lot of questions indeed... Any help appreciated View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062707#4062707 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062707 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Run JSF RI on WebSphere 6.1
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=bb&op=viewtopic&p=4062702#4062702 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062702 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: ClassCastException: org.jboss.seam.jsf.SeamApplication11
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. There is no need anymore of MyFaces and also no need for fancy Classloader configurations. I will let you know when this fix will be publicly available, I didn't test it with seam 1.3 (2.0?) but the problem were identical with both versions so I think it should work too View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058456#4058456 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058456 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Run JSF RI on WebSphere 6.1
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. There is no need anymore of MyFaces and also no need for fancy Classloader configurations. I will let you know when this fix will be publicly available, I didn't test it with seam 1.3 (2.0?) but the problem were identical with both versions so I think it should work too View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058455#4058455 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058455 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Run JSF RI on WebSphere 6.1
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=bb&op=viewtopic&t=107948 I have open a PMR with IBM for it and still wait for an answer from IBM View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052846#4052846 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052846 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Run JSF RI on WebSphere 6.1
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 : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052795#4052795 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052795 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Run JSF RI on WebSphere 6.1
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: http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP&q1=myfaces&uid=swg21243668&loc=en_US&cs=utf-8&lang=en Off Topic: BTW, Michael, your book on JBoss Seam is fantastic. I greatly recommend it to everyone. That book is clear, easy to read and is a must-have for anyone developping with seam. Thanks!! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052794#4052794 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052794 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: ClassCastException: org.jboss.seam.jsf.SeamApplication11
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=bb&op=viewtopic&p=4051502#4051502 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4051502 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: ClassCastException: org.jboss.seam.jsf.SeamApplication11
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 "utility" jar and have the war depends on it, and only have classes related to presentation in the war (view controllers/backing beans). This seems to not be possible if you want to uses seam annotation in any class in the utility jar, as jboss-seam.jar must be placed in the ear file directly has any other framework jar (log4j, etc..). and as you point it out, this does not work A workaround is to have an utility jar for the "business" classes and deploy it under the war WEB-INF/lib directoryarghh See my other posts in tha forum on that topic. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4046669#4046669 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4046669 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam on Websphere 6.x backed by DB2?
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 : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045812#4045812 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045812 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Seam on Websphere 6.x backed by DB2?
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 v6.1. Search on "MyFaces" in the was support page and find the paper from IBM explaining how to make MyFaces work with was v6.1 - You must use PARENT_LAST on BOTH ear and war classloader amd put jboss* libs in ot WEB-INF/lib View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045645#4045645 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045645 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: seam cannot reference EJB, why?
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 "seam backing beans and view controllers" in the web module (Within its own war classloader..)... Also the fact that everything must use the same classloader is really a show stopper, going against the J2EE modules architecture If someone knows how to make it working, with only jsf+seam+non-EJB3 POJO+hibernate with all our services/managers/persistent classes in a utility jar, and our view controllers (backing beans) in a war referencing the utility jar (Injecting our services and class model in the view controllers) , just tell us how todo it, i.e. where to put each jar and each config file (seam.properties, components.xml...) and how to configure the classloaders... In the meantime, we'll keep using spring+hibernate for our services/managers/persistent classes classes in a utility jar, and jsf+seam on the presentation side in a war, with seam injecting our spring-managed services/managers/persistent classes into seam components. Hibernate being only used in the utility jar and the Hibernate session being injected by spring Thx in advance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045643#4045643 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045643 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: ClassCastException: org.jboss.seam.jsf.SeamApplication11
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 to patch Hibernate to make it work (org.hibernate.JTATransactionFactory) to make it work due to a problem Hibernate tries to get the JTA Transaction Statusat some point in the sessioN/transaction lifecycle (pls search on hibernate for this one) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4045146#4045146 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4045146 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: ClassCastException: org.jboss.seam.jsf.SeamApplication11
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, jboss-seam.jar,myfaces-api-1.1.5.jar,myfaces-impl-1.1.5.jar under web-inf/lib - all other dependent libs (commons*, hibernate*, etc..) in ear with ref in the meta-inf/manifest.mf file of the warmodule - ear and war classloader set to PARENT_LAST If i remove the myfaces* libs (and so use the jsf was jsf implementation) or push down the myfaces* libs to the ear level, I have the ClassCast..classes imcompatibe...exception) It seems that it works *only* if the myfaces libs are at the "same level" as the jsf implementation libs (dont know how to express this..) and that the way seam initialises itself requires this. Maybe it's due to the way seam scans the classpath to find its resources (?) ... Any thoughts on this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043677#4043677 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043677 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - ClassCastException: org.jboss.seam.jsf.SeamApplication11 inc
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 PROTECTED] java.lang.ClassCastException: org.jboss.seam.jsf.SeamApplication11 incompatible with com.sun.faces.application.ApplicationImpl at com.ibm.ws.jsf.configuration.FacesConfigParser.createFacesFactories(FacesConfigParser.java:1019) at com.ibm.ws.jsf.configuration.FacesConfigParser.initializeConfiguration(FacesConfigParser.java:354) at com.ibm.ws.jsf.util.FacesConfigUtil._parseJSFConfiguration(FacesConfigUtil.java:128) at com.ibm.ws.jsf.util.FacesConfigUtil.parseJSFConfiguration(FacesConfigUtil.java:82) at com.sun.faces.util.Util.verifyFactoriesAndInitDefaultRenderKit(Util.java:497) at com.ibm.ws.jsf.configuration.FacesConfig.initialize(FacesConfig.java:96) Q: - Any idea for this exception (I'v tried lots of things to try to have it working, including playing with classloader...) - What is the requirement for seam on JSF: Does seam absolutely requires "MyFaces" as JSF implementation? or can I use WAS JSF 1.1 implementation bases on Sun RI? or more generally any JSF 1.1 compatible implementation? - Anyone there running seam 1.2.1 on WAS v6.1.0.7 with the builtin JSF implementation? thx file /WEB-INF/faces-config.xml: http://java.sun.com/dtd/web-facesconfig_1_1.dtd";> org.jboss.seam.jsf.SeamPhaseListener file /WEB-INF/web.xml: -- http://java.sun.com/xml/ns/j2ee"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd";> javax.faces.STATE_SAVING_METHOD server javax.faces.CONFIG_FILES /WEB-INF/faces-config.xml javax.faces.DEFAULT_SUFFIX .jsp com.sun.faces.NUMBER_OF_VIEWS_IN_SESSION 15 com.sun.faces.enableHighAvailability false com.sun.faces.COMPRESS_STATE false com.ibm.ws.jsf.JSP_UPDATE_CHECK true com.ibm.ws.jsf.LOAD_FACES_CONFIG_AT_STARTUP true com.sun.faces.config.ConfigureListener org.jboss.seam.servlet.SeamListener Faces Servlet javax.faces.webapp.FacesServlet -1 Faces Servlet /faces/* Faces Servlet *.faces View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043258#4043258 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043258 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
