Thanks for all the work that you are doing and I appreciate you being open to this idea.
First a bit of a caveat. My experience with web apps is limited to testing them and I have to confess that I may not be much of a help in comments regarding the deployment of Jythoninc web apps mainly because I've never developed any. I have some understanding about tomcat and jboss configuration but that’s about where it ends. Although with the work on django I might start dabbling.
That being said, I'd like to improve portability of the tools/apps that I develop. A best case scenario is just installing the needed files on a new system and double click on the jar (like the installer). So for example, presume that you have developed 'aTool' that would be useful to others. These co-workers do not have Jython installed and may never have even heard of Jython which means that you will be using the Jython standalone jar; which does not include a registry file. The easiest way to do that currently seems to be, well.... not so easy. See: http://wiki.python.org/jython/JythonFaq/DistributingJythonScripts. If you don't have Java development experience the task can be daunting at best. What I'm suggesting is a way such an environment variable or something that could be set to point to stuff you need for your app. To use a real example.
Currently I have a classpath that looks like:
All of these are needed. But if I want to give what I done to co-workers so they can use 'aTool', its a real headache... and a MASSIVE jar file. Never mind updates to scripts or jar changes. Ok so this is still pretty java specific so lets add some python and change it so I have a JythonImports setting that is for example:
This setting would be read at startup so that import CustomJythonModules * or from org.this.myJavaStuff import * would just work.
Obviously the name JythonImports is just an example maybe jythonpath or something else would be better.
I guess I'm looking for a hybrid setting that is a combo of pythonPath and classpath that can be use by the standalone jar (and web apps) and not require a lot of work to move things from a development environment to a deployment / distribution. The benefits would be easier distribution / deployment of code, easier to debug and test, easier to modify or change individual components, and finally but hardly last improved ease of use. I don’t believe this would impact any backward compatibility.
Did this clarify anything or just confuse the issue further.
From: Leo Soto M. [mailto:leo.soto@...]
Sent: Thursday, July 31, 2008 3:02 PM
To: Moore, Greg
Cc: Nicholas Riley; jython-dev@...; jython-users@...
Subject: Re: [Jython-dev] Jython settings - input requested
On Thu, Jul 31, 2008 at 3:39 PM, Moore, Greg <Greg_W_Moore@...> wrote:
> For my 2 cents worth, I like your suggestions and think they will help
> clarify things going forward. I'm wondering if having something like,
> for example, 'JythonImports' setting the that could be used to specify
> where external libraries are so they can be found when using standalone
> Jython or in a web application environment. Something kinda like a
> classpath but could also include python modules as well as java.
Hi Greg, and thanks for your feedback. I'd like if you can expand a
bit more about what would be possible with this new setting so we
understand how it will be different than what "python.path" currently
I'm very interested on web deployment of Jython projects, so any
feedback/ideas on that topic will be appreciated, but maybe we should
start another thread for that...
Leo Soto M.
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.