The reason for that is that the live article assume that in the --data-dir
you have a can.ex2 file as well as the other one. And for you, you didn't
share the ParaViewData dir.
Seb
On Thu, Oct 24, 2013 at 9:54 AM, Pawel Kwiecien wrote:
> Hi Seb,
> I'm experimenting with ParaViewWeb based on th
Hi Pawel,
I think for 1) you put a data-dir that contains too much files hence a
complain about a text message too large.
For 2, you can change to command line with an argument that contain the
file to load instead of a directory.
Seb
On Sun, Oct 20, 2013 at 9:27 PM, Pawel Kwiecien wrote:
>
Hi Pawel,
if you run "java -jar JettySessionManager-Server-1.0.jar" with no argument
you should see what the configuration file should be. I guess, you may need
to provide a valid pw.factory.proxy.adapter as well as a valid path for the
creation of a file for pw.factory.proxy.adapter.file.
It is
Hi Pawel,
yes it is possible, one way to do that is to use a Session Manager like the
following one. But you can build your own if need be.
Seb
http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/jetty_session_manager
On Thu, Oct 3, 2013 at 8:53 AM, Pawel Kwiecien wrot
Hi all,
I'm exploring ParaViewWeb included in ParaView 4.0. As described in the
documentation (http://www.paraview.org/Wiki/ParaViewWeb), I can run it
locally like that
./bin/pvpython lib/site-packages/paraview/web/pv_web_visualizer.py
--content www --port 8080 --data-dir $PARAVIEW_DATA
My quest