>
> Christoph I understand why this happens, I was simply asking if there
was a
> better way to do this using some struts session magic or such. Seems
there
> isn't so I'll just do it the old long winded way.
>
If you want to store attached entities in session you can make your
actions Sessio
> Inside an Interceptor I'm getting an exception
>
> java.lang.IllegalStateException: Cannot create a session after the
response
> has been committed
> I have access to the ActionInvocation as this is passed into
doIntercept()
> public String doIntercept(ActionInvocation invocation) throws Excep
> The error message comes from the IllegalArgumentException thrown by
> java.io.File.createTempFile() - it doesn't feature in the Struts
> distribution at all. Because there's no entry in
> struts-messages.properties for
> struts.messages.upload.error.IllegalArgumentException it gets added to
On 07/01/2016 09:42, Christoph Nenning wrote:
Please create a jira issue for that.
I see one was done yesterday along with a fix, also resolving the
related issue when a file field in a form is empty.
https://issues.apache.org/jira/browse/WW-4583
> > Please create a jira issue for that.
>
> I see one was done yesterday along with a fix, also resolving the
> related issue when a file field in a form is empty.
>
> https://issues.apache.org/jira/browse/WW-4583
>
That's great!
So you can either wait for next release or use a snapshot build
Just to make sure - you are POSTing the object back to the action and THEN
merging the entity correct? Not just calling the merge function in the
action from the page? Sorry, I had to ask because it sort of sounds like
that is what you are saying. I am using Struts2 and JPA and I routinely
post obj
In the case of non-versioned domain models or cases where you aren't concerned
with state collisions, the traditional lookup/render/lookup/merge workflow
works quite well.
The problem though comes into play when you are concerned about versioned
models and more importantly, controlling state
Just my two cents, you can avoid the lookup by using a JPQL UPDATE query.
If used to update a single record you avoid the lookup. If versioning is an
issue this may not be ideal (still you could manually set the version),
also if you expect to reuse objects you lose the ability to proxy, if those
a
8 matches
Mail list logo
