[jboss-user] [JBoss Seam] - Pb Initializing database on app startup with postInitializat
I launch a method on application startup using the
org.jboss.seam.postInitialization event. It work fine except if I access the
database (and I need to) :
using seam managed entity manager :
@In
| private EntityManager em;
|
| @Observer(org.jboss.seam.postInitialization)
| private void setupAFewThings() throws ComentSystemException {
| MyObject w = new MyObject() ;
| w.setName(test_name) ;
| em.getTransaction().begin();
| em.persist(w) ;
| em.getTransaction().commit();
| }
or manually creating a new entity manager like this :
@Observer(org.jboss.seam.postInitialization)
| private void setupAFewThings() throws ComentSystemException {
| MyObject w = new MyObject() ;
| w.setName(test_name) ;
| EntityManagerFactory emf =
Persistence.createEntityManagerFactory(myDatabase);
| EntityManager em = emf.createEntityManager();
| em.getTransaction().begin();
| em.persist(w) ;
| em.getTransaction().commit();
| }
I get the same error (java.lang.IllegalStateException: JTA EntityManager
cannot access a transactions) :
anonymous wrote : 16:26:18,530 ERROR [[/coment_demo]] Exception lors de l'envoi
de l'évènement contexte initialisé (context initialized) à l'instance de classe
d'écoute (listener) org.jboss.seam.servlet.SeamListener
| java.lang.IllegalStateException: JTA EntityManager cannot access a
transactions
| at
org.hibernate.ejb.AbstractEntityManagerImpl.getTransaction(AbstractEntityManagerImpl.java:316)
| at
com.sopinspace.coment.core.WorkflowManager.addDefaultWorkflow(WorkflowManager.java:53)
| at
com.sopinspace.coment.core.WorkflowManager.create(WorkflowManager.java:62)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
| at
org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
Any help ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4081692#4081692
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4081692
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Login Redirection not propagating GET parameters
maybe we will have to post an issue in JIRA ... View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4072924#4072924 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072924 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Login Redirection not propagating GET parameters
Using current CSV : after configuration the login redirection event listeners, I get the login-required feature all right but GET parameters to the original page are not propagated to the page after authentification. anonymous wrote : [...] attempts to access a restricted view while not logged in will be remembered, so that upon the user successfully logging in they will be redirected to the originally requested view, with any page parameters that existed in the original request. For instance, on the seam-booking example : main page is protected again unlogged access : trying to access http://localhost:8080/seam-booking/main.seam?testparam=test will redirect to authentification page, but after a successful authentification, the get parameter is not propagated : http://localhost:8080/seam-booking/main.seam?cid=11 is that a bug of am I missing something ? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4072370#4072370 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072370 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Startup exception: Ajax4jsfFilter
After updating seam jars to current CVS, I'm hitting the same pb ... Anybody solved that one ? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4072008#4072008 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4072008 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - hibernate validation decorators pb in 2.0.0.B1
Hi, I'd like to draw you attention on an issue that seems to occur since release 2.0.0.B1 with hibernate decorators on seam components : see : http://jira.jboss.org/jira/browse/JBSEAM-1626 View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4065702#4065702 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4065702 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: hibernate validation decorators pb in 2.0.0.B1
thanks for the reply ... I'll try to be more precise in the future. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4065899#4065899 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4065899 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - remoting error in 2.0.0.B1 (No application context active)
After upgrading to 2.0.0.B1 I get an error (see below) in a remoting call. For some reason, I only get the error when a parameter of the call is the js conterpart of an entity object created on the js side. Any help ? anonymous wrote : java.lang.IllegalStateException: No application context active | at org.jboss.seam.Component.forName(Component.java:1690) | at org.jboss.seam.remoting.wrapper.BeanWrapper.setElement(BeanWrapper.java:40) | at org.jboss.seam.remoting.CallContext.createWrapperFromElement(CallContext.java:45) | at org.jboss.seam.remoting.ExecutionHandler.unmarshalCalls(ExecutionHandler.java:147) | at org.jboss.seam.remoting.ExecutionHandler.handle(ExecutionHandler.java:58) | at org.jboss.seam.remoting.Remoting.getResource(Remoting.java:113) | at org.jboss.seam.servlet.SeamResourceServlet.doGet(SeamResourceServlet.java:69) | at org.jboss.seam.servlet.SeamResourceServlet.doPost(SeamResourceServlet.java:78) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) | at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:63) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.jboss.seam.web.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:44) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) | at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:87) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:63) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:46) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:127) | at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:277) | at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:40) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:140) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) | at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) | at java.lang.Thread.run(Thread.java:595) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4059920#4059920 Reply to the post :
[jboss-user] [JBoss Seam] - Re: remoting error in 2.0.0.B1 (No application context activ
The problem seems to occur only when an argument of a remote procedure call
is an instance of an entity created on the client side by : var customer =
Seam.Component.newInstance(customer);
eg :
the entity object :
anonymous wrote : @Entity
| @Name(testObject)
| @Scope(CONVERSATION)
| public class TestObject {
| @Id
| private String stringId;
|
| public String getStringId() {
| return stringId;
| }
|
| public void setStringId(String stringId) {
| this.stringId = stringId;
| }
| }
in a seam component :
anonymous wrote : @Stateful
| @Name(testManager)
| @Scope(ScopeType.CONVERSATION)
| public class TestManager implements Manager {
| public void testOnly(TestObject test) {
| System.out.println(!!);
| System.out.println(test);
| }
| }
in js code :
anonymous wrote : function sayHelloCallback(result) { }
| testManager = Seam.Component.getInstance(testManager) ;
| testObject = Seam.Component.newInstance(testObject) ;
| testManager.testAttachTest(testObject,sayHelloCallback) -- error
|
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4059953#4059953
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4059953
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: remoting error in 2.0.0.B1 (No application context activ
I forgot the @WebRemote in
@WebRemote
public void testOnly(TestObject test) {
I reported this issue in JIRA :
http://jira.jboss.org/jira/browse/JBSEAM-1599
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4059959#4059959
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4059959
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - problem instrumenting hibernate classes with seam 2.0.0B1 (p
I was using the code below in my build.xml to instrument my entity classes to
get the full advantage of hibernate's lazy property loading feature :
target name=instrument
| taskdef name=instrument classpathref=build.classpath
classname=org.hibernate.tool.instrument.cglib.InstrumentTask
| /taskdef
| instrument
| fileset dir=${jar.dir}
| include name=**/entity/**/*.class /
| /fileset
| /instrument
| /target
Since I upgraded to seam 2.0.0B1 I get this error :
anonymous wrote : instrument:
| [instrument] starting instrumentation
|
| BUILD FAILED
| java.lang.NoSuchMethodError:
net.sf.cglib.core.ClassNameReader.getClassInfo(Lorg/objectweb/asm/ClassReader;)[Ljava/lang/String;
|
If I replace the thirdparty-all.jar file with the previous one (the one shipped
with previous versions of seam), the error is gone again and instrumentation
works.
Maybe something is wrong with that jar ?
Regards,
Zdal
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4060082#4060082
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4060082
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - 2 problems after upgrading to 2.0.0.BETA1
After upgrading all libs and config files to seam 2.0.0.BETA1, I'm facing two
problems :
- I'm unable to access seam components from non jsf servlets (despite the
web:context-filter url-pattern=/servlet/*/ configuration ... I get a
java.lang.IllegalStateException: No application context active at
org.jboss.seam.Component.forName(Component.java:1690) exception
- a validation on a backing bean property using the @AssertTrue hibernate
validator does not work anymore (@Email is still ok)
Here are my 3 main configurations files ... maybe some mistake I made (?)
components.xml
anonymous wrote : ?xml version=1.0 encoding=UTF-8?
| components xmlns=http://jboss.com/products/seam/components;
| xmlns:core=http://jboss.com/products/seam/core;
| xmlns:drools=http://jboss.com/products/seam/drools;
| xmlns:security=http://jboss.com/products/seam/security;
| xmlns:mail=http://jboss.com/products/seam/mail;
| xmlns:transaction=http://jboss.com/products/seam/transaction;
| xmlns:persistence=http://jboss.com/products/seam/persistence;
| xmlns:web=http://jboss.com/products/seam/web;
| xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
| xsi:schemaLocation=http://jboss.com/products/seam/core
http://jboss.com/products/seam/core-2.0.xsd
| http://jboss.com/products/seam/drools
http://jboss.com/products/seam/drools-2.0.xsd
| http://jboss.com/products/seam/security
http://jboss.com/products/seam/security-2.0.xsd
| http://jboss.com/products/seam/persistence
http://jboss.com/products/seam/persistence-2.0.xsd
| http://jboss.com/products/seam/web
http://jboss.com/products/seam/web-2.0.xsd
| http://jboss.com/products/seam/transaction
http://jboss.com/products/seam/transaction-2.0.xsd
| http://jboss.com/products/seam/mail
http://jboss.com/products/seam/mail-2.0.xsd
| http://jboss.com/products/seam/components
http://jboss.com/products/seam/components-2.0.xsd;
|
| core:init debug=@debug@ jndi-pattern=@jndiPattern@ /
|
|core:manager concurrent-request-timeout=500
| conversation-timeout=12
| conversation-id-parameter=cid/
|
| core:pages no-conversation-view-id=/index.xhtml /
|
| !-- Seam-managed persistence context with JPA --
| persistence:managed-persistence-context name=em auto-create=true
| persistence:persistence-unit-jndi-namejava:/@[EMAIL
PROTECTED]/persistence:persistence-unit-jndi-name
| /persistence:managed-persistence-context
|
| core:resource-bundle
| core:bundle-names
| myapp-messages
| myapp-internals-messages
| /core:bundle-names
| /core:resource-bundle
|
| core:locale-selector cookie-enabled=true /
|
| core:transactionListener /
|
| web:multipart-filter create-temp-files=true
| max-request-size=100/
|
| security:identity authenticate-method=#{login.login}/
|
|
|
|
|
|
|
|
| !-- integrate custom servlet with seam contexts --
| web:context-filter url-pattern=/cm_servlets/* /
|
|drools:rule-base name=securityRules
|drools:rule-files
|/META-INF/security.drl
|/drools:rule-files
|/drools:rule-base
|
| transaction:ejb-transaction/
|
|
web.xml
anonymous wrote :
| ?xml version=1.0 encoding=UTF-8?
|
| web-app version=2.4 xmlns=http://java.sun.com/xml/ns/javaee;
| xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
| xsi:schemaLocation=http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_2_4.xsd;
|
| !-- Ajax4jsf --
|
| context-param
| param-nameorg.ajax4jsf.VIEW_HANDLERS/param-name
| param-valuecom.sun.facelets.FaceletViewHandler/param-value
| /context-param
|
| context-param
| param-nameorg.ajax4jsf.SKIN/param-name
| param-valueblueSky/param-value
| /context-param
|
|!-- Seam --
|
|
| listener-classorg.jboss.seam.servlet.SeamListener/listener-class
|
|
|
| filter-nameSeam Filter/filter-name
| filter-classorg.jboss.seam.servlet.SeamFilter/filter-class
|
|
| filter-mapping
| filter-nameSeam Filter/filter-name
| url-pattern*.cm/url-pattern
| /filter-mapping
|
|
| servlet-nameSeam Resource Servlet/servlet-name
| servlet-classorg.jboss.seam.servlet.ResourceServlet/servlet-class
|
|
|servlet-mapping
| servlet-nameSeam Resource Servlet/servlet-name
| url-pattern/seam/resource/*/url-pattern
|/servlet-mapping
[jboss-user] [JBoss Seam] - Re: 2 problems after upgrading to 2.0.0.BETA1
any help / hint ? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4059580#4059580 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4059580 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - No application context active error in remoting request wi
I'm still stuck with my problem : being unable to access seam components from within a remoting request. All worked fine using seam 1.3* but since the 2.0.0B1 upgrade I get the error : anonymous wrote : 17:31:19,595 ERROR [ExecutionHandler] Error unmarshalling calls from request | java.lang.IllegalStateException: No application context active | at org.jboss.seam.Component.forName(Component.java:1690) | at org.jboss.seam.remoting.wrapper.BeanWrapper.setElement(BeanWrapper.java:40) | at org.jboss.seam.remoting.CallContext.createWrapperFromElement(CallContext.java:45) | at org.jboss.seam.remoting.ExecutionHandler.unmarshalCalls(ExecutionHandler.java:147) | at org.jboss.seam.remoting.ExecutionHandler.handle(ExecutionHandler.java:58) | at org.jboss.seam.remoting.Remoting.getResource(Remoting.java:113) | at org.jboss.seam.servlet.SeamResourceServlet.doGet(SeamResourceServlet.java:69) | at org.jboss.seam.servlet.SeamResourceServlet.doPost(SeamResourceServlet.java:78) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) | at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:63) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) | at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:87) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:63) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:46) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:127) | at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:277) | at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:40) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:140) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) | at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) | at java.lang.Thread.run(Thread.java:595) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4059653#4059653 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4059653 ___ jboss-user mailing list jboss-user@lists.jboss.org
[jboss-user] [JBoss Seam] - Re: seam 1.2.1 - 1.3 (CVS.20070531) causes wrong content en
any suggestion on this one ? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4052006#4052006 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4052006 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: seam 1.2.1 - 1.3 (CVS.20070531) causes wrong content en
Thanks of lot for the tip. It seems to work ; I say seems because I still have to test my application to make sure it has not broken anything somewhere else. Still, this use to work (serving UTF-8 encoded js static file trough Seam Filter) in seam 1.2.1 ... it might a bug that it does not work anymore (?) in 1.3. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4052091#4052091 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4052091 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: bug with s:fileUpload on IE6 (fine with FF or IE7)
thanks for the info Gavin. I finally managed to port my application to seam CVS jboss 4.2.0. The s:fileUpload component works on IE6 with those versions. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4050937#4050937 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4050937 ___ 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 - 1.3 (CVS.20070531) causes wrong content encodi
Since the port to 4.2 and seam 1.3 (CVS.20070531), I've a problem serving my UTF-8 encoded static js files that were ok with 4.0.5 and seams 1.2.1. The problem is also not there if I use a simple war file serving those static files in jboss 4.2. That's why I think the problem might come from seam. A simple UTF-8 javascript file with BOM at the beginning of the file is served with the machine's encoding (iso-8859-1 in my case). To reproduce the problem (inside the booking example) : 1. get the file from http://www.relationblog.com/ecrire/tools/fckeditor/editor/lang/en.js and put it in seam.home/examples/booking/view/js 2. deploy 3. go to http://localhost:8080/seam-booking/js/en.js : the file encoding is wrong and you can see the 3 BOM characters at the beginning of the file that should not be displayed View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4051005#4051005 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4051005 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: bug with s:fileUpload on IE6 (fine with FF or IE7)
I made some progess (I guess) upgrading to jboss-seam-CVS.20070531 using seam-gen to generate a project and comparing all the files in WEB-INF and META-INF to ajust them ... but I still get another error on application startup ... any help very much appreciated ... anonymous wrote : 11:38:48,248 INFO [Component] Component: org.jboss.seam.core.Dispatcher, scope: EVENT, type: JAVA_BEAN, class: org.jboss.seam.core.Dispatcher | 11:38:48,248 ERROR [[/]] Exception lors de l'envoi de l'évènement contexte initialisé (context initialized) à l'instance de classe d'écoute (listener) org.jboss.seam.servlet.SeamListener | java.lang.RuntimeException: Could not create Component: org.jboss.seam.core.Dispatcher | at org.jboss.seam.init.Initialization.addComponent(Initialization.java:887) | at org.jboss.seam.init.Initialization.installComponents(Initialization.java:818) | at org.jboss.seam.init.Initialization.init(Initialization.java:498) | at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:29) | at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3854) | at org.apache.catalina.core.StandardContext.start(StandardContext.java:4359) | at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:761) | at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:741) | at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297) | at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.apache.catalina.core.StandardContext.init(StandardContext.java:5310) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297) | at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(TomcatDeployer.java:301) | at org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeployer.java:104) | at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:375) | at org.jboss.web.WebModule.startModule(WebModule.java:83) | at org.jboss.web.WebModule.startService(WebModule.java:61) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.GeneratedMethodAccessor709.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at
[jboss-user] [JBoss Seam] - Re: bug with s:fileUpload on IE6 (fine with FF or IE7)
Apparently there is a problem (?) with the dispatcher component because commenting out : core:dispatcher / in components.xml solved my problem ... View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4050469#4050469 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4050469 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: bug with s:fileUpload on IE6 (fine with FF or IE7)
thanks a lot for your reply. I'll try it with the nightly builds ... but can I still use jboss 4.0.5 with the nightly builds ? should I also update the faces jar (from myfaces to sun's jar) ? (it could be great to test the register2 page in the seamspace example ... I get the bug with this page also on seam 1.2.1) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4050024#4050024 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4050024 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - problem using seam exception handling mecanism
I'm having trouble using the seam handling mecanism (using seam 1.2.1) :
I've added this in pages.xml
exception
| end-conversation/
| redirect view-id=/error.xhtml /
| /exception
I did set core:init debug=false jndi-pattern=@jndiPattern@ / in
components.xml and
param-namefacelets.DEVELOPMENT/param-nameparam-valuefalse/param-value
in web.xml
If i manually throw an exception in my code, the page just gets reloaded (no
redirect) and a face message Transaction failed is set
If I try to create (and the throw) a custom exception like this :
@Redirect(viewId=/error.xhtml, end=true)
| @ApplicationException(rollback=true)
| public class MyException extends RuntimeException {
I get the exact same behaviour : no redirect, only the Transaction failed
faces message.
I'm pretty sure the exceptionFilter is on because I have this in my log on
application start :
anonymous wrote : 10:35:13,297 INFO [SeamFilter] Initializing filter:
org.jboss.seam.servlet.multipartFilter
| 10:35:13,297 INFO [SeamFilter] Initializing filter:
org.jboss.seam.servlet.contextFilter
| 10:35:13,297 INFO [SeamFilter] Initializing filter:
org.jboss.seam.servlet.exceptionFilter
| 10:35:13,297 INFO [SeamFilter] Initializing filter:
org.jboss.seam.servlet.redirectFilter
Can anyone give me a hint a what could be wrong ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4050029#4050029
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4050029
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: bug with s:fileUpload on IE6 (fine with FF or IE7)
I deployed my application on 4.2.0 all right. Then I upgraded to jboss-seam-CVS.20070531 following the steps in : http://www.michaelyuan.com/blog/2007/05/29/seam-book-examples-updated-to-jboss-as-420-ga/ but then when I deploy my application I get : anonymous wrote : 19:15:55,938 INFO [EJBContainer] STARTED EJB: org.jboss.seam.core.TransactionListener ejbName: TransactionListener | 19:15:55,942 INFO [EJB3Deployer] Deployed: file:/home/me/lib/jboss-4.2.0.GA/server/default/deploy/my_app_dev.ear/jboss-seam.jar | 19:15:55,945 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/my_app_dev.ear/my_app_dev.war/ | 19:15:56,335 ERROR [STDERR] java.lang.UnsupportedOperationException | 19:15:56,336 ERROR [STDERR] at com.sun.faces.config.ConfigureListener$InitFacesContext.getViewRoot(ConfigureListener.java:1690) | 19:15:56,336 ERROR [STDERR] at com.sun.faces.util.MessageFactory.getMessage(MessageFactory.java:113) | 19:15:56,336 ERROR [STDERR] at com.sun.faces.util.MessageUtils.getExceptionMessageString(MessageUtils.java:277) | 19:15:56,336 ERROR [STDERR] at com.sun.faces.util.Util.createInstance(Util.java:477) | 19:15:56,336 ERROR [STDERR] at com.sun.faces.util.Util.createInstance(Util.java:436) | 19:15:56,336 ERROR [STDERR] at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:617) | 19:15:56,336 ERROR [STDERR] at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:503) | 19:15:56,336 ERROR [STDERR] at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:402) | 19:15:56,336 ERROR [STDERR] at org.jboss.web.jsf.integration.config.JBossJSFConfigureListener.contextInitialized(JBossJSFConfigureListener.java:69) | 19:15:56,336 ERROR [STDERR] at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3854) | 19:15:56,336 ERROR [STDERR] at org.apache.catalina.core.StandardContext.start(StandardContext.java:4359) | 19:15:56,336 ERROR [STDERR] at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:761) | 19:15:56,336 ERROR [STDERR] at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:741) | 19:15:56,337 ERROR [STDERR] at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553) | 19:15:56,337 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | 19:15:56,337 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | 19:15:56,337 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | 19:15:56,337 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) | 19:15:56,337 ERROR [STDERR] at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297) | 19:15:56,337 ERROR [STDERR] at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) | 19:15:56,337 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | 19:15:56,337 ERROR [STDERR] at org.apache.catalina.core.StandardContext.init(StandardContext.java:5310) | 19:15:56,337 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | 19:15:56,337 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | 19:15:56,337 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | 19:15:56,337 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) | 19:15:56,337 ERROR [STDERR] at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297) | 19:15:56,337 ERROR [STDERR] at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) | 19:15:56,337 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | 19:15:56,337 ERROR [STDERR] at org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(TomcatDeployer.java:301) | 19:15:56,337 ERROR [STDERR] at org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeployer.java:104) | 19:15:56,337 ERROR [STDERR] at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:375) | 19:15:56,337 ERROR [STDERR] at org.jboss.web.WebModule.startModule(WebModule.java:83) | 19:15:56,337 ERROR [STDERR] at org.jboss.web.WebModule.startService(WebModule.java:61) | 19:15:56,337 ERROR [STDERR] at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | 19:15:56,338 ERROR [STDERR] at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | 19:15:56,338 ERROR [STDERR] at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) | 19:15:56,338 ERROR [STDERR] at
[jboss-user] [JBoss Seam] - Re: bug with s:fileUpload on IE6 (fine with FF or IE7)
I found a page in the seamspace example called register2 that uses the s:fileUpload and I get the same behaviour than with my example ... meaning the upload does not happen in IE6 (ok with FF or IE7) anyone on this problem ? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4047836#4047836 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4047836 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - bug with s:fileUpload on IE6 (fine with FF or IE7)
I have a problem with the s:fileUpload component on IE 6. (using JBoss 4.0.5 /
seam 1.2.1.GA).
Everything is fine on Firefox or on IE 7 but when using it with IE 6 : when
hitting submit, the form (consisting of only one input file created with
s:fileUpload) gets cleared and no submission occurs.
h:form id=upload enctype=multipart/form-data
| s:fileUpload data=#{upload.file1} fileName=#{upload.fileName1}
accept=#{upload.supportedMimetypes}/
| h:commandButton value=upload action=#{upload.upload} /
| s:link id=cancel value=Cancel action=#{upload.cancel} /
| /h:form
|
Is this a known bug ? Is there any workaround because I must confess this
renders the fileUpload component completely unusable ...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4047301#4047301
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4047301
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: question : avoid conversation id parameter for RESTful a
Thanks for your reply ... You're right, the RESTful nature of my application is not the only reason why I want to get rid of the cid when a redirect (from pages.xml) occurs ... I also want to make sure of the uniqueness of the urls (for many reasons, including the indexation of the site by search engine). That's why I don't want the cid=xx in urls, at least for some of my pages ... View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4040446#4040446 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4040446 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - question : avoid conversation id parameter for RESTful appli
I'm trying to create a RESTful application (starting from the blog example) but
I'm having problem trying to get rid of the cid parameter :
Using this in pages.xml
page view-id=/login.xhtml
| navigation
| rule if=#{identity.loggedIn}
| redirect view-id=/workspace.xhtml /
| /rule
| /navigation
| /page
Everything is fine in the server (no long running conversation is started) but
after login, I'm redirected to /workspace.xhtml?cid=3 instead of
/workspace.xhtml ...
any hint on how to get rid of this cid parameter ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4040129#4040129
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4040129
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Question : seam and fine grain url control (regular expr
petemuir wrote : Use the urlrewrite filter (see the wiki in cvs for an example) or a page action. I think a page action is not sufficient for what I'm trying to do ... I'm sorry but I dont know what that wiki in cvs is (?) ... but maybe you're talking about http://tuckey.org/urlrewrite/ ? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4039742#4039742 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4039742 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Question : seam and fine grain url control (regular expressi
Hi, Is there a way to control urls way beyond the standard file name - url current mapping ? For instance if I have a page named users.xhtml along with a backing bean and I want that page to be served as /users/myusername/ to access my userspace instead of /users?username=myusername ? Is there a way to do that ? (This is really a need when migrating a legacy app to seam.) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038263#4038263 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038263 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - ejq-ql subquery in seam
this might be a little off topic since it's an ejb-ql question but I'm using it inside seam and I think maybe my error will be obvious to some of you. I'm simply trying to execute a simple (test) subquery like this : select t from MyObject t order by ( select 1 ) but I get the error : anonymous wrote : Caused by: org.hibernate.hql.ast.QuerySyntaxException: unexpected AST node: query [select t from com.[...].MyObject t order by ( select 1 ) ] any hint ? (I guess I'm doing some stupid mistake somewhere ...) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4037874#4037874 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4037874 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - access the seam managed PersistenceContext in a @Startup obj
I'm trying to access the seam managed persistence context inside a seam POJO declared as @Startup. When the object is created the inject seam managed persistence context is null @In | private EntityManager em; | Is there a way to do that (basically I need to schedule some maintenance related operations at startup time ... and those operations must access the database ...) ? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4037995#4037995 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4037995 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: captcha
it seems that there is already such thing (simple mathematical questions) inside JCaptcha ... see : com.octo.captcha.text.math.MathCaptcha Maybe a simple change of the current integration would be enough ... (I cannot read those captchas either ...) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4038042#4038042 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4038042 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Back...
Stack must not be null error when using ajax4jsf with seam another reported having the same problem ... maybe worth a look http://www.jboss.com/index.html?module=bbop=viewtopict=105872 I've changed a little bit of the page that was triggering the problem ... basically removing usage of richfaces ... and the problem seems gone ... I confess I'm a little bit confused about it ... View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4037099#4037099 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4037099 ___ jboss-user mailing list [EMAIL PROTECTED] https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re:
I had the problem with FF. But : i've changed a little bit of the page that was triggering the problem ... basically removing usage of richfaces ... and the problem seems gone ... I confess I'm a little bit confused about it ... View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4037101#4037101 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4037101 ___ jboss-user mailing list [EMAIL PROTECTED] https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re:
anyone having the same problem ? any idea ? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4035682#4035682 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4035682 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Stack must not be null error when using ajax4jsf with seam
I'm using ajax4jsf inside seam 1.2.1 and I get an error :
javax.servlet.ServletException: Stack must not be null when I click on a a4j
checkbox button
anonymous wrote : h:selectBooleanCheckbox
id=displayCheck value=#{myManager.updateDisplay}
| a:support event=onchange
reRender=results /
| /h:selectBooleanCheckbox
This happens only the first time I access the page (that basically displays a
list that can be viewed two ways (according to the state of the boolean)) : if
I reload the page I don't get the error anymore and everything is fine.
With previous releases of seam, I had, at the exact same time, the id must not
be null error and found out on ajax4jsf forums that this was due to a bug
fixed in seam 1.2.1. But it seems to me there is still some kind of a problem
...
Here is the complete stack trace :
anonymous wrote : 16:52:44,071 ERROR [ExceptionFilter] uncaught exception
| javax.servlet.ServletException: Stack must not be null
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:152)
| at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63)
| at
org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60)
| at
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
| at
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
| at
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
| at
org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57)
| at
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
| at
org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79)
| at
org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49)
| at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84)
| at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at
org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96)
| at
org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220)
| at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at
org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at
org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
|
Any idea of what can be wrong ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4035053#4035053
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4035053
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - error loading http://jboss.com/products/seam/pages-1.1.dtd
Hi, This morning (for us in Europe) the jboss website was down during a few hours ... as a result, a seam project would not start because of the error : anonymous wrote : java.lang.RuntimeException: org.dom4j.DocumentException: Error on line 1 of document http://jboss.com/products/seam/pages-1.1.dtd : The markup declarations contained or pointed to by the document type declaration must be well-formed. Nested exception: The markup declarations contained or pointed to by the document type declaration must be well-formed. | at org.jboss.seam.core.Pages.getDocumentRoot(Pages.java:836) | at org.jboss.seam.core.Pages.parse(Pages.java:794) | at org.jboss.seam.core.Pages.initialize(Pages.java:106) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) checking the page http://jboss.com/products/seam/pages-1.1.dtd I got :anonymous wrote : | !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN | | Cannot connect to database. as a reply. Of course this is a real problem ... I don't want to be unable to restart my jboss server because the jboss web server is down ... is there a way to be independent from that ? Thanks in advance, Z. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4032319#4032319 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4032319 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: error loading http://jboss.com/products/seam/pages-1.1.d
the last one : jboss-seam-1.2.1.GA (btw, this version 1.2.1 still writes Welcome to Seam 1.2.0.PATCH1 on load ;-) ) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4032327#4032327 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4032327 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: error loading http://jboss.com/products/seam/pages-1.1.d
same problem if I start my jboss server with my seam application without having my laptop connected to the internet : anonymous wrote : Caused by: org.dom4j.DocumentException: jboss.com Nested exception: jboss.com | at org.dom4j.io.SAXReader.read(SAXReader.java:484) | at org.dom4j.io.SAXReader.read(SAXReader.java:343) | at org.jboss.seam.util.XML.getRootElement(XML.java:16) | at org.jboss.seam.core.Pages.getDocumentRoot(Pages.java:832) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4032332#4032332 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4032332 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: error loading http://jboss.com/products/seam/pages-1.1.d
Thanks a lot ... it did the trick ... and I understood the problem ... I'll be more careful during the next seam version change ;-) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4032345#4032345 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4032345 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - lazy property loading ?
Is there a way to lazily load entity properties in seam ?
I'd like to load a large collection of objects without loading a (potentially
large) content inside every one of them ...
I've tried :
@Lob
| @Basic(fetch = FetchType.LAZY)
| public String getContent() {
| return content;
| }
But that does not seem to have any effect ...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4032378#4032378
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4032378
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Persistence Context vs. Seam-managed persistence context JPA
I'm kind of new to Java JPA and Hibernate and after having read the Seam documentation, all the persistence options in Seam are kind of complex for a first start ... If I understand it right (also looking at the examples in Seam), there is 3 way to achieve Java persistence in Seam : - direct use of Persistence Context (the booking example) - using Seam-managed persistence - with JPA (blog/jta example) - with Hibernate (hibernate, hibernate2 example) I have 2 questions : - what would you advice for a first start using Seam inside JBoss ? - what would you advice for an advanced usage of persistence using Seam inside JBoss ? - what are the relative advantages of the different solutions ? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4031068#4031068 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4031068 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: Persistence Context vs. Seam-managed persistence context
Thanks for your reply ! Do you advice Seam managed EntityManager because it's simpler ? more powerful ? both ? Is it an advice for a newcomer (then for me ;-)) ? Or an advanced user (then for me in a few times ;-)) ? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4031132#4031132 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4031132 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration Deployment] - using apache as jboss frontend and fine tuning url contexts
Hi, I'm using apache as a frontend for JBoss and I use mod_jk as the connector. However, I'm not really happy with having my two applications accessed by : http://mysite.com/application1 and http://mysite.com/application2 What I want (and have been unable to setup properly so far) is to access my first application with http://mysite.com/ and my second application with http://mysite.com/application2 I've tried with mod_rewrite but failed ... has anyone some ideas/pointers ? Thanks in advance. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4027440#4027440 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4027440 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration Deployment] - Re: using apache as jboss frontend and fine tuning url conte
actually, using mod_rewrite I've been able to almost achieve what I'm trying to
do :
| RewriteCond %{REQUEST_URI} !^/application2 [NC]
| RewriteRule ^/(.*) /application1/$1 [L,P]
|
| JkMount /* ajp13
|
The only problem is that all the links in application1 point to
/application1/mypage.jsp ... so after only one navigation my url becomes :
http://mysite.com/application1/mypage.jsp
Any hints ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4027444#4027444
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4027444
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - feature request on @webremote decorator arguments in remotin
A while ago, I posted a feature request into JIRA about the way @Webremote functions are decorated to prevent unwanted fields to be accessible in javascript on the client side ... Basically the idea is to filter the fields you want instead of the fields you dont want ...(more details, including the reasons to do so in the feature request page [see below]) http://jira.jboss.org/jira/browse/JBSEAM-975 Maybe some of you would be willing to give me some feedback about it ... View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4027081#4027081 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4027081 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - Re: concurrent access to SFSB using SEAM Remoting
Thanks for you answer. Looking at the code inside the Conversation Manager we saw that if there is a concurrent call to a locked conversation context : a new temporary one is created : log.debug(No stored conversation, or concurrent call to the stored conversation); | initializeTemporaryConversation(); | This lead to our problem since the concurrent-request-timeout is set to 1 sec by default. Setting this parameter to 20s did the trick : each request would wait enough time for the previous request to be completed. in components.xml : core:manager concurrent-request-timeout=2 ... Maybe you could add a note in section 3.1.10. Concurrency model mentioning this parameter ... In our case, it was really strange to have a new temporary (and empty !) conversation created to handle requests from a long running conversation ... maybe it solves some of your use-cases (?) ... View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4022318#4022318 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4022318 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Seam] - concurrent access to SFSB using SEAM Remoting
We encountered a problem accessing a simple SFSB from a javascript call using
seam remoting.
Concurrent js calls to a single conversational SFSB produces multiple instances
of SFSB each being added to a newly created conversation context which is not
what one would expect.
We reproduced it with a minor modification to the chatroom example.
We simply changed the sendMessage function (in ChatRoomAction.java) like this
(adding a 10s delay to simulate a long process) :
public void sendMessage(String message) {
| publish( new ChatroomEvent(message, username, message) );
| try {
|Thread.sleep(1) ;
| } catch (InterruptedException e) {
|e.printStackTrace();
| }
| }
|
This breaks the chatroom example : repeated inputs lead to the creation of new
chatroomAction SFSBs that don't hold the user object (and are located within
new conversation contexts).
This is the ouput in the chatroom :
anonymous wrote : testuser connected.
| testuser a
| null a
| testuser a
| null a
|
Thanks for any help.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4021160#4021160
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4021160
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
