[JBoss Seam] - Problems ending long running conversation
by billahome
We have been trying to end conversations, and then immediately begin them, with little success. I am beginning to wonder if there are problems with Seam 1.2.1 GA in this area. Any advice would be welcome.
We notice (for instance) that if we have something like this in pages.xml
<page view-id="/a.xhtml">
<begin-conversation join="true" />
<navigation from-action="#{myBean.myAction}">
<end-conversation/>
<redirect view-id="/b.xhtml" />
<page view-id="/b.html">
<begin-conversation join="true" />
that when someone navigates from page a via myBean.myAction to b, that the conversation really doesn't end - neither the conversation-id nor the conversation context is changed by the above (except for perhaps by myBean.myAction). Is this the expected behavior? If so, how does one get a new conversation in this case?
Bill Alexander
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100769#4100769
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100769
16Â years, 6Â months
[JBossWS] - problem on jboss-4.2.0.GA not if upgraded with jbossws1.2.0.
by Pires da Silva
Hello,
Executing my web service under jboss4.2.0-GA on Linux, I get:
(meaning jboss-4.2.0.GA is just unzipped, all required war etc copied under appropriate directories)
but when using jboss-4.2.0.GA + upgrading it from jbossws1.2.0.SP1 it is working.
java.lang.NoSuchMethodError: javax.xml.soap.SOAPElement.getElementQName()Ljavax/xml/namespace/QName;
at org.jboss.ws.core.soap.SOAPElementImpl.getChildElements(SOAPElementImpl.java:504)
at org.jboss.ws.core.soap.SOAPBodyImpl.faultIterator(SOAPBodyImpl.java:181)
at org.jboss.ws.core.soap.SOAPBodyImpl.getFault(SOAPBodyImpl.java:168)
at org.jboss.ws.core.soap.SOAPMessageImpl.isFaultMessage(SOAPMessageImpl.java:326)
at org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:244)
at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:448)
at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75)
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.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.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)
Catherine Pires da Silva
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100762#4100762
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100762
16Â years, 6Â months
[JBoss Seam] - Seam with 2 datasources (Postgres+MySQL)
by manuel_fidalgo
Hello, Im working with SEAM 1.2.1 and I have two datasources: one is from a Postgres database (and works fine) and the other one is for a MySQL database ('WP7Datasource', which doesn't work).
The problem is that when I start JBoss i get this error:
16:58:20,968 INFO [SessionFactoryImpl] building session factory
17:08:39,718 WARN [ServiceController] Problem starting service persistence.units:ear=medieq-aqua.ear,jar=medieq-aqua.jar,unitName=WP7Datasource
javax.persistence.PersistenceException: org.hibernate.MappingException: could not instantiate id generator
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:695)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:127)
at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:264)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
...
Caused by: org.hibernate.MappingException: could not instantiate id generator
at org.hibernate.id.IdentifierGeneratorFactory.create(IdentifierGeneratorFactory.java:98)
at org.hibernate.mapping.SimpleValue.createIdentifierGenerator(SimpleValue.java:152)
at org.hibernate.impl.SessionFactoryImpl.(SessionFactoryImpl.java:192)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1218)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:688)
... 147 more
Caused by: org.hibernate.MappingException: Dialect does not support sequences
at org.hibernate.dialect.Dialect.getSequenceNextValString(Dialect.java:570)
at org.hibernate.id.SequenceGenerator.configure(SequenceGenerator.java:65)
at org.hibernate.id.SequenceHiLoGenerator.configure(SequenceHiLoGenerator.java:43)
at org.hibernate.id.IdentifierGeneratorFactory.create(IdentifierGeneratorFactory.java:94)
....
the datasources are defined here:
<?xml version="1.0" encoding="UTF-8"?>
| <datasources>
| <local-tx-datasource>
| <jndi-name>medieqDatasource</jndi-name>
| <connection-url>
| jdbc:postgresql://localhost:5432/medieqdev
| </connection-url>
| <driver-class>org.postgresql.Driver</driver-class>
| <user-name>****</user-name>
| <password>****</password>
| <connection-property name="char.encoding">
| UTF-8
| </connection-property>
| <transaction-isolation>
| TRANSACTION_READ_COMMITTED
| </transaction-isolation>
| <min-pool-size>25</min-pool-size>
| <max-pool-size>100</max-pool-size>
| <blocking-timeout-millis>5000</blocking-timeout-millis>
| <idle-timeout-minutes>15</idle-timeout-minutes>
| <prepared-statement-cache-size>
| 75
| </prepared-statement-cache-size>
| </local-tx-datasource>
|
| <!-- add datasource for UMLS MYSQL database (Manuel Fidalgo)-->
| <local-tx-datasource>
| <jndi-name>WP7Datasource</jndi-name>
| <connection-url>jdbc:mysql://localhost/umls</connection-url>
| <driver-class>com.mysql.jdbc.Driver</driver-class>
| <user-name>***</user-name>
| <password>***</password>
| <connection-property name="char.encoding">UTF-8</connection-property>
| <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
| <min-pool-size>25</min-pool-size>
| <max-pool-size>100</max-pool-size>
| <blocking-timeout-millis>5000</blocking-timeout-millis>
| <idle-timeout-minutes>15</idle-timeout-minutes>
| <prepared-statement-cache-size>75</prepared-statement-cache-size>
| <metadata> <type-mapping>mySQL</type-mapping></metadata>
| </local-tx-datasource>
| </datasources>
and the persistence.xml is this:
<persistence>
| <persistence-unit name="medieqDatasource">
| <provider>org.hibernate.ejb.HibernatePersistence</provider>
| <jta-data-source>java:/medieqDatasource</jta-data-source>
| <properties>
| <!-- create-drop -->
| <property name="hibernate.hbm2ddl.auto" value="validate"/>
| <property name="hibernate.show_sql" value="true"/>
| <!-- These are the default for JBoss EJB3, but not for HEM: /-->
| <property name="hibernate.cache.provider_class" value="org.hibernate.cache.HashtableCacheProvider"/>
| <property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.JBossTransactionManagerLookup"/>
| <property name="jboss.entity.manager.factory.jndi.name" value="java:/medieqEntityManagerFactory"/>
| </properties>
| </persistence-unit>
|
| <!-- MySQL UMLS database Manuel Fidalgo -->
| <persistence-unit name="WP7Datasource">
| <provider>org.hibernate.ejb.HibernatePersistence</provider>
| <jta-data-source>java:/WP7Datasource</jta-data-source>
| <properties>
| <property name="hibernate.hbm2ddl.auto" value="validate" />
| <property name="hibernate.cache.use_query_cache" value="true" />
| <property name="hibernate.show_sql" value="true" />
| <property name="hibernate.dialect" value="org.hibernate.dialect.MySQL5Dialect" />
| <property name="hibernate.connection.username" value="***" />
| <property name="hibernate.connection.password" value="***" />
| <property name="hibernate.connection.driver_class" value="com.mysql.jdbc.Driver" />
| <property name="hibernate.connection.url" value="jdbc:mysql://localhost/umls" />
| <property name="jboss.entity.manager.factory.jndi.name" value="java:/WP7EntityManagerFactory" />
| <property name="hibernate.jdbc.use_get_generated_keys" value="false" />
| </properties>
| </persistence-unit>
| </persistence>
Both databases are working and I can connect to them via JDBC. I have no entities for the MySQL database but is should work...I think that the problem is that the configuration forces MySQL to use id generators and it doesnt work but I don't know why it uses this generators and if I could turn off this feature (only for MySQL)... Any help will be apreciated...
thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4100758#4100758
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4100758
16Â years, 6Â months