Standalone File Server using REST

• Key: TRANSACTION-27
• Type: New Feature
• Status: Open
• Priority: Minor
• Assignee: Unassigned
• Reporter: Oliver Zeigermann

Description

Before implementing JTA we need a standalone file server that decouples it from the Applikation server. Main reason is that file access is not allowed from inside JEE (is that right) and a.c.t locks might block the whole container. Having such a server using a REST like inferface would solve that problem. This might be out of scope, though?!

Comments

[Oliver Zeigermann]

A meaningful JTA implementation that runs inside an application server would require an external process that manages the file system as this is not allowed from inside the application server. Maybe it is from inside a JCA implementation. Aynway, having an external server decouples c.a.t from the app server which is good anyway.

[Alexander T]

Hi. I'm a long time lurker here, and I really would like to see some JTA happening. I believe that a lot of resource adapters handle file access and locks, take for instance Apache Jackrabbit, who already seem to have file transactions. Developing a HTTP communication protocol between the container and transaction manager would be a bit overkill if you ask me.