> Using Roo for Swing. Interesting.
Indeed. How hard would it be to replace the web layer with a desktop app?
Further, how hard would it be for Roo to generate RESTful services and a...
Type: Posts; User: duckbill; Keyword(s):
> Using Roo for Swing. Interesting.
Indeed. How hard would it be to replace the web layer with a desktop app?
Further, how hard would it be for Roo to generate RESTful services and a...
http://static.springsource.org/spring/docs/2.5.x/reference/xsd-config.html#xsd-config-body-schemas-util-constant
Have you considered the option of adding a @PostRemove method that would save a history entry (another entity) of the target entity once it is deleted?
Cheers,
Jukka
Hibernate validator 4.0 (JSR-303) support (for ddl generation) is only available through the upcoming Hibernate 3.5+. http://opensource.atlassian.com/projects/hibernate/browse/HHH-4428
I would go with jTDS (but the dialect as above). Just make sure the jtds jar is in your classpath, and that the db properties resemble the ones below.
Driver = net.sourceforge.jtds.jdbc.Driver...
Have you checked the hibernate dialect property in persistence.xml for typos?
org.hibernate.dialect.SQLServerDialect
A Roo-generated app will by default instruct Hibernate to generate the schema at runtime (i.e. when running tests or deploying the app). This is controlled by the "hibernate.hbm2ddl.auto" property in...
I personally don't see any problem in having persistence methods in an Entity, simply because we're not doing much there but delegating to the EntityManager. So concerns are separated for the most...
DataBinder.initDirectFieldAccess();
DataBinder.setAllowedFields(new String[] {"id", "version", ...})
This is probably something Roo could manage.
Personally, I'm not too worried about exposing...
DataBinder.initDirectFieldAccess()?
--
Jukka
bazza80, if you want a DAO layer, why not just replace the EntityManager in your Entities with a dedicated DAO object? This way you can have your DAO layer that fits perfectly into the Roo-generated...
Hi,
I have previously downloaded STS 2.1 SR01 with the Groovy plugin. Unfortunately the Groovy pluging is causing me trouble and I'm now seeking to download a non-groovy version of STS.
The...
Thanks, I'll track ROO-182's development.
Hi Stefan,
Thanks for your reply.
That's true, got so carried away with all the new stuff that I forgot to utilize the usual layered design. A simple service bean would indeed do the work...
Hi,
Another issue I'm facing with Roo's rich Entity model:
How do I go about marking static methods transactional? I would like to be able to use the declarative way (i.e. @Transactional)...
Hi,
I find the non-anemic entity model (that Roo generates by default via aspectj) very nice and simple. The one feature I miss from a repository-based approach, however, is the automatic...
Hi,
For starters, I have to say that Roo looks really promising.
Unfortunately I have a problem with importing a Roo-generated (Roo 1.0.0RC1) project into STS (2.1.0RC1). This is described...
Either add a custom destroy-method to your bean that cleans up the background thread upon context stop or implement the DisposableBean interface accordingly.
Just a wild guess, but
Does the PurchaseOrderService interface contain the exact same printText() method as it appears in the impl class?
If not, the dynamic transaction proxy (which I think...