Very cool - thanks for giving me the reason when it's okay to bend these rules
re: Assets not needing transactional business stuff
On 25/05/2012, at 9:43 PM, Geoff Callender wrote:
> Arno is spot on. The spec is being motherly, but in practice if you're
> uploading assets, as opposed to saving
Arno is spot on. The spec is being motherly, but in practice if you're
uploading assets, as opposed to saving something that must be considered part
of a transaction, then there's no harm done in writing to the file system.
Everybody does it! Here's an example:
http://jumpstart.doublen
626 pages of spec... and you reply with section number and some copy and paste.
I am grateful Arno, thank you!
On 25/05/2012, at 5:45 PM, Arno Haase wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> JEE application servers typically do not actually prevent you from
> accessing the fi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
JEE application servers typically do not actually prevent you from
accessing the file system, and the spec does not require them to. So
if it works with your specific app server / jee stack, you are home free.
The spec prohibits accessing the file sys
To answer my own question (correctly I hope),
This collapsed war (the EJB jars packaged within WAR) thing means for my simple
wants, tapestry to pass a URL to a servlet which has access to the filesystem.
It's as simple as that - the servlet is the "gateway" to the filesystem.
Cheers
Chris
On
Hi Tapestry Users,
In April there was a thread about AssetFactory help [1] and it mentioned that
the J2EE spec states that you should not read or write to the file system.
Reading up on the collapsed ear from openejb's website [2] they say (sic) "not
quite j2ee but truly jee6".
Although openejb
