@Romain, it works as well as the end user deems fit at the end of the
day - There is such a thing as a stable snapshot, that is one that
passes all the tests that has ever been written so far, and all the end
user tests that they have for their own app. There is definitely no
black and white ru
I have a client that makes a call to a remote EJB method and then terminates
within a very short period of time. If the EJB method is synchronous,
everything works fine. If the EJB is annotated with @Asynchronous, the call
doesn't seem to be processed on the server unless I introduce a short sleep
Andy,
Yes, I am aware of that. We started using the SNAPSHOTs after we got a (for
us) critical bugfix on trunk.
The fix was in the trunk only four hours after we reported the bug which, by
the way, we found quite impressive. But we underestimated the effort (and
thus time) it takes to roll a relea
Hi jieryn,
This has got me thinking along the lines of using 'lineEndings' in the
maven-assembly-plugin, which is designed to address exactly this issue.
It means splitting out tar.gz and zip assembly.xml's to two separate files
(possibly component based), which will be some additional work. I wi
You should let the JPA provider manage the @Version field, don't try and
change it or read it yourself or you'll always get this error. It's
controlled internally by the provider and is to do with optimistic locking.
If you want to manage your own entity version the, i.e. versioned data row,
then
