[Treebase-guts] [ treebase-Bugs-2960910 ] Phylowidget does not run

[SourceForge.net <no...@so...>]

Bugs item #2960910, was opened at 2010-02-28 18:32
Message generated for change (Settings changed) made by vgapeyev
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1126676&aid=2960910&group_id=248804

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: ui
Group: None
Status: Open
Priority: 9
Private: No
Submitted By: William Piel (sfrgpiel)
>Assigned to: Vladimir Gapeyev (vgapeyev)
Summary: Phylowidget does not run

Initial Comment:
Using dev server, I'm unable to look at any trees (clicking the magnifying glass, which is supposed to fire-up phylowdiget, fails to work). Causes "Error. Click for details" with the result "The application failed to run"

----------------------------------------------------------------------

Comment By: Vladimir Gapeyev (vgapeyev)
Date: 2010-03-01 16:53

Message:
I am trying to understand what is going on here... 

Apparently, before I and Jon showed up, the arrangement was to run the
"publish" script, which would take Phylowidget.jar and place it inside the
exploded WAR, at treebase-web/test/phylowidget.  This location already
contains several jars (core.jar,itext.jar,jgrapht-jdk1.5.jar,pdf.jar),
which are also required by the client (see
treebase-web/src/main/webapp/WEB-INF/pages/newPhylowidget.jsp).  These jars
come packed inside treebase-web.war

So, why can't we just put Phylowidget.jar inside the WAR archive,
alongside the other 4 jars?  


----------------------------------------------------------------------

Comment By: Rutger Vos (rvos)
Date: 2010-03-01 11:12

Message:
This is almost certainly because PhyloWidget.jar isn't in the right
location. This jar is unlike all the others in the project because it is a
client side applet that is run in a browser window, which means the web
server needs to make this jar available to the client. Apparently, the new
dev/prod/stage server configuration hasn't taken this into account. Since
only Jon has access to the server itself I suppose he's the only one who
can fix it.

----------------------------------------------------------------------

Comment By: Rutger Vos (rvos)
Date: 2010-03-01 11:12

Message:
Thanks for reporting this bug.  We'll look into it as soon as possible.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1126676&aid=2960910&group_id=248804