well, yes we do... however, it we were not getting that far...
@RequestMapping(method = POST)
ModelAndView create(@Valid @ModelAttribute Foo foo, BindingResult binder) {
if...
Type: Posts; User: Blair; Keyword(s):
well, yes we do... however, it we were not getting that far...
@RequestMapping(method = POST)
ModelAndView create(@Valid @ModelAttribute Foo foo, BindingResult binder) {
if...
ok, we are trying out spring 3 rc1 and have run into some interesting behavior.
The first is a bit of a warning to people using binder.setValidator, if you are returning some object of different...
Anyone seen anything apart from the "Spring Richclient's Future" note on http://spring-rich-c.sourceforge.net/1.0.0/index.html?
Maybe the display tag library is what you are after.
or just making the Controller you are currently using a bit smarter.
I'm pretty sure that validation doesn't i18n so well in richclient.
use the ImageIO write method
http://java.sun.com/j2se/1.5.0/docs/api/javax/imageio/ImageIO.html#write(java.awt.image.RenderedImage,%20java.lang.String,%20java.io.OutputStream)
to write to a...
That was it :). Thanks!
I remember being able to use the archetype from home, but couldn't at work. Thanks!
I was pretty sure that spring richclient was in the standard maven repo at
http://repo1.maven.org/maven2
I've had a look at it now, and it isn't there.
so - the question I've got is.... Was...
I just went to use the archetype and found it was gone, in fact, the whole of Richclient was missing. :confused:
The overhead of the interceptor is really really small. Almost any other way would be complex or slower, or most likely both.
oh, its off topic, but what is XmlBeanFactory for? Is it for systems with limited resources (does it use less memory)? or what?
It has to have a use apart from confusing people who haven't looked...
Oh, NOW I remember....
this was a tricky one!
XMLBeanFactory DOESN'T do AOP, you need to use ApplicationContext
the transaction annotations didn't fire up and thats what caused the error.
...
I got it going :) - but it was long enough ago I can't remember what I was doing wrong.
I should have posted back.
The Spring Security subproject (ACEGI) is normally the way of handling it,
http://acegisecurity.org/
Not the most simple thing to set up, but well worth it in the end.
Which release of spring? I'm using spring 2 rc4 (now).
Can you post your applicationContext.xml? (or whichever your spring config file is)
Oh yeah, and what error are you getting?
--- Blair
I'm going to make a guess and say that the datasource you have doesn't have a connection pool.
it doesn't sound like a hibernate or mapping problem now, What does your controller and jsp page look like?
in the mean time ... you can get around it by creating the TransactionAttributeSourceAdvisor with its constructor.
replace <tx:annotation-driven /> with
<bean...
what is the code being used to persist it look like?
try....
query name="ItemImpl.findItemByKeywords">
<![CDATA[from ItemImpl as item inner join item.itemMeta as meta inner join meta.keywords as keywords where keywords.name in ( :params )]]>...
so, what is the query -
AssessmentItemImpl.findItemByKeywords
It all works now.
I've had a look at the docs and now understand why its like that, but I'd never have found it on my own, so thanks! You have been very helpful.
--- Blair
ok, this is from a prevous thread, but I have more information about whats going on. Hopefully someone can see whats going wrong, I've tried to be very careful and clear in each step.
It looks...
ENP:
You have to start a transaction before you can use getCurrentSession().
If your using spring2, the annotation way of handleing transactions is very cool.
I'd help you through it, but...
<bean class="org.springframework.transaction.interceptor.TransactionAttributeSourceAdvisor">
<constructor-arg index="0" ref="transactionInterceptor"/>
</bean>
So it gets...