http://issues.jabsorb.org/show_bug.cgi?id=70
Summary: Let JSONRPCServlet serve up the jsonrpc.js client
Product: jabsorb
Version: unspecified
URL: http://lists.jabsorb.org/pipermail/jabsorb-dev/2010-
May/000495.html
Status: NEW
Severity: enhancement
Priority: medium
Component: server
AssignedTo: [email protected]
ReportedBy: [email protected]
CC: [email protected]
Currently, in order to use jabsorb, users must add both jsonrpc.js and
jabsorb.jar to their projects. If they upgrade, they often have to replace
both files.
The jsonrpc.js file could be included in jabsorb.jar. Then the
org.jabsorb.JSONRPCServlet could serve up the internal jsonrpc.js file (e.g.
<script type="text/javascript" src="/JSON-RPC?client=js"></script>).
Advantages:
- Easier upgrade path for users: they simply replace jabsorb.jar. If changes
were made to the jsonrpc.js resource within the jar, these will automatically
be included.
- Versioning of jsonrpc.js in the repository.
- Backwards compatible with the "old way." Using an external copy of
jsonrpc.js would still work.
Notes:
- In order to allow browser caching to work correctly, the servlet would need
to return the correct Last-Modified header value (the release date of the
.jar?) when responding to requests for the client.
- The minified version of jsonrpc.js could also be included (or generated) too.
--
Configure bugmail: http://issues.jabsorb.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.
_______________________________________________
Jabsorb-dev mailing list
[email protected]
http://lists.jabsorb.org/mailman/listinfo/jabsorb-dev
