and is there some sort of work around?
--
View this message in context:
http://old.nabble.com/Tapestry---hibernate-problem-tp2666p26667111.html
Sent from the Tapestry - User mailing list archive at Nabble.com
Hi all,
I have a little problem.
I'm using hibernate criteria to fetch list of objects that I want to display
in loop component. (enclosed in my commentModule component)
Criteria criteria = getManager().createCriteria(CommentBean.class);
criteria.setFetchMode(user,FetchMode.JOIN);
this
Hi,
Looks more like an issue with your criteria. Have you tried to use
FetchMode.EAGER instead?
Christian
Bojan Cincur schrieb:
Hi all,
I have a little problem.
I'm using hibernate criteria to fetch list of objects that I want to display
in loop component. (enclosed in my commentModule
Hi,
You should check your mapping to be sure the many-to-one relationship
between comment and user is correct, and verify your database table
comment contains an existing foreign key to the user table.
Best thing to do is to run your Criteria in a JUnit test.
Nicolas.
Bojan Cincur a écrit
://old.nabble.com/Tapestry---hibernate-problem-tp2666p26667111.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e
to null/t:eventlink/p
pt:eventlink event=deletedelete/t:eventlink/p
pt:eventlink event=setToTransientset to
transient/t:eventlink/p
/body
/html
--
View this message in context:
http://www.nabble.com/T5%3A-tapestry-hibernate-problem-when-setting-%40Persist%28%22entity%22%29
to transient/
t:eventlink/p
/body
/html
--
View this message in context:
http://www.nabble.com/T5%3A-tapestry-hibernate-problem-when-setting-%40Persist%28%22entity%22%29-to-a-transient-object-tp18996169p18996169.html
Sent from the Tapestry - User mailing list archive at Nabble.com
.hibernate.HibernateModule.build(Logger, List,
RegistryShutdownHub) (at HibernateModule.java:117) (for service
'HibernateSessionSource'): tried to access field
org.hibernate.cfg.Configuration.xmlHelper from class
org.hibernate.cfg.AnnotationConfiguration
--
View this message in context:
http://www.nabble.com/tapestry-hibernate
hi,
the HibernateEntityValueEncoder creates ValueEncoder for every
contributed Entity class that's nice... but if i submit a page with a
select component that used a list of entities to generate the selection
model i will receive an exception if no option was selected! this is
because the
Hi all,
I have a dynamic form where the user can set a dynamic number of passengers.
The html looks like:
table jwcid=@For
source=ognl:passengerList
value=ognl:currentPassengerId
width=100%
Hi Grigoris
I will assume that your form is surrounding the @For component.
Advices:
* remove the updatePassenger it will confuse things.
* persist passengerList in the session
* populate passengerList on pageBeginRender
* add a keyExpression to the For component
* then save all the
in my appModule.java, i changed :
public void contributeHibernateSessionSource(
OrderedConfigurationString configuration) {
configuration.add(my, org.ts.domain.bo);
}
2007/10/26, Donyee [EMAIL PROTECTED]:
I got errors when i use T5.06-hibernate, and my app works
I got errors when i use T5.06-hibernate, and my app works fine when i use
T5.05!
Also i changed the html to tml, sl4j...
Error:
No service implements the interface org.apache.tapestry.ioc.Configuration.
Error invoking service builder method
Hi,
i have tried the tapestry-hibernate package to handle my hibernate
sessions. I have setup the package in maven and add the hibernate
Session to all constructors of my services.
I started with my CustomerService getting and setting my customerbeans
(each of them having a Set of
Hi,
i have tried the tapestry-hibernate package to handle my hibernate
sessions. I have setup the package in maven and add the hibernate
Session to all constructors of my services.
I started with my CustomerService getting and setting my customerbeans
(each of them having a Set of
you shouldn't persist any object from hibernate
@ApplicationState
private Customer _customer;
same object will be referenced in you second request,
and the second request will have different session,
tapestry-hibernate integration is still basic,
and for now you should just change
16 matches
Mail list logo