[JBossCache] - Re: Could a recent version be uploaded to the maven2 reposit
by fabrefactor
Niels:
I, too, would like to see this sent to central (repo1.maven.org).
In it's absence, I'll note the following POM works for us and JBC 1.4.0.SP1:
| <project>
| <modelVersion>4.0.0</modelVersion>
| <groupId>jboss</groupId>
| <artifactId>jboss-cache</artifactId>
| <version>1.4.0.SP1</version>
| <dependencies>
| <dependency>
| <groupId>jboss</groupId>
| <artifactId>jboss-system</artifactId>
| <version>4.0.3</version>
| </dependency>
| <dependency>
| <groupId>jboss</groupId>
| <artifactId>jboss-jmx</artifactId>
| <version>4.0.3</version>
| </dependency>
| <dependency>
| <groupId>jboss</groupId>
| <artifactId>jboss-common</artifactId>
| <version>4.0.3</version>
| </dependency>
| <dependency>
| <groupId>jboss</groupId>
| <artifactId>jboss-minimal</artifactId>
| <version>4.0.3</version>
| </dependency>
| <dependency>
| <groupId>concurrent</groupId>
| <artifactId>concurrent</artifactId>
| <version>1.3.4</version>
| </dependency>
| <dependency>
| <groupId>jgroups</groupId>
| <artifactId>jgroups-all</artifactId>
| <version>2.2.9.2</version>
| </dependency>
| </dependencies>
| </project>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006071#4006071
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006071
19 years, 2 months
[JBoss Seam] - Re: pagination problem, advice needed
by liudan2005
Thanks Gavin. I've had a look at Query and it looks great. However, my situation is a bit more complicated. What I need is a way to to paginating the collocation based property of my entities. Here is my code:
| <h:dataTable value="#{persons}" var="person" >
| <h:outputText value="#{person.name}" />
| <h:outputText value="#{person.age}" />
| <h:dataTable value="#{person.reviews}" var="review" >
| <h:outputText value="#{review.title}" />
| </h:dataTable>
|
| <h:dataTable value="#{person.calls}" var="call" >
| <h:outputText value="#{call.duration}" />
| </h:dataTable>
| <h:dataTable>
|
As you can see, Query is good for paginating #{persons}. But for #{person.reviews}, I don't see a easy way of doing it. I have many entities that require this kind of multi-level pagination. Can you give any advices on this? Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006070#4006070
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006070
19 years, 2 months
[JBoss Seam] - Re: PersistenceException during testNG unit test
by asookazian
problem resolved by moving persistence.xml around into various folders in Eclipse.
now getting HibernateException: could not find datasource. I am referencing the persistence unit (Entity Manager) as follows:
@Configuration(beforeTestClass=true)
| public void init()
| {
| emf = Persistence.createEntityManagerFactory("RSDB");
| }
|
| The name of the datasource file is "loantrack-ds.xml" and is as follows:
|
| <?xml version="1.0" encoding="UTF-8"?>
|
| <datasources>
| <local-tx-datasource>
| <jndi-name>jdbc/RespaJbossDS</jndi-name>
| <jndi-name>java:jdbc/RespaJbossDS</jndi-name>
| <connection-url>jdbc:JSQLConnect://d-rtl-db-01:2233/database=RSDB/user-name=process-jboss/password=pjss986sPROD</connection-url>
| <driver-class>com.jnetdirect.jsql.JSQLDriver</driver-class>
| <user-name>process-jboss</user-name>
| <password>pjss986sPROD</password>
| </local-tx-datasource>
| </datasources>
|
| persistence.xml as follows:
|
| <?xml version="1.0" encoding="UTF-8"?>
| <persistence>
| <persistence-unit name="RSDB">
| <provider>org.hibernate.ejb.HibernatePersistence</provider>
| <jta-data-source>java:jdbc/RespaJbossDS</jta-data-source>
| <properties>
| <property name="hibernate.hbm2ddl.auto" value="update"/>
| <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"/>
| </properties>
| </persistence-unit>
| </persistence>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006067#4006067
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006067
19 years, 2 months
[JBoss Seam] - Re: Conversations
by lightbulb432
Thanks, that description cleared that up.
Let's say you have a conversation with several methods (one method called per request) and I use FlushMode.COMMIT/AUTO. If the first few requests in the conversation access a NEVER or NOT_SUPPORTED action method, and the next request accesses a REQUIRES (or similar) action method, would the persistence context be flushed when that REQUIRES method successfully returns?
Or would changes be flushed after every request because of the fact that there's always a transaction?
anonymous wrote : use two transactions per request; the first spans the beginning of the update model values phase until the end of the invoke application phase; the second spans the render response phase
How do the transactions from the quote above relate to the transactions specified by the transaction attributes?
If somebody could please lay this all out for me that'd be wonderful...I've been reading the Seam and Hibernate sections on transactions, but now I just need to ask a human...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006062#4006062
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006062
19 years, 2 months