search

slarson / wholebrain

Automatically exported from code.google.com/p/wholebrain
0 stars 0 forks source link

Uploaded OBJs don't appear in the data tree, don't appear again on client reload #524

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Launch latest client (0.7.7.9-SNAPSHOT) against latest server (1.1.4-SNAPSHOT)
2.Upload OBJ via debug menu (manipulation state checked on)
3.OBJ appears in WBC space

What is the expected output? What do you see instead?
Even though the OBJ appears, no record of it appears under ("mesh models").  
Worse, upon closing and reopening the client, the objs that were uploaded do 
not even appear in the 3d view.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by stephen....@gmail.com on 12 Aug 2010 at 1:40

GoogleCodeExporter commented 9 years ago 
Also, picking OBJs imported this way frequently leads to the following 
exception being thrown: 

--08/12/10 06:45:04 WARN  wbc.util.PickUtil [AWT-EventQueue-0]:
 tried to get selected relevant from tangible manager but returned null!
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
    at org.wholebrainproject.wbc.observers.ApplicationObserver3D.update(ApplicationObserver3D.java:49)
    at java.util.Observable.notifyObservers(Observable.java:142)
    at org.wholebrainproject.wbc.app.Application.changed(Application.java:509)
    at org.wholebrainproject.wbc.app.Application.changed(Application.java:503)
    at org.wholebrainproject.wbc.app.Application.stopCamera(Application.java:722)
    at org.wholebrainproject.wbc.view.listeners.View3DListener.mouseReleased(View3DListener.java:251)
    at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:232)
    at java.awt.Component.processMouseEvent(Component.java:5517)
    at java.awt.Component.processEvent(Component.java:5282)
    at java.awt.Component.dispatchEventImpl(Component.java:3984)
    at java.awt.Component.dispatchEvent(Component.java:3819)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
    at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

Original comment by stephen....@gmail.com on 12 Aug 2010 at 1:46

GoogleCodeExporter commented 9 years ago 
On second review, the nullpointerexception is probably irrelevant to the 
problem.

Checking out locahost:8182/tangibles/meshmodels reveals that the server is not 
reporting back the new .objs that have been uploaded as tangibles.  This is 
after making sure that wbcserver.properties had all the permissions set to true 
that deal with the recent code modifications to allow a server to freeze 
uploads.

Original comment by stephen....@gmail.com on 12 Aug 2010 at 1:57

GoogleCodeExporter commented 9 years ago 
I exported the server state on my local machine after having uploaded these 
OBJs and I see that datawrapper entries are correctly created.  However, when I 
search for references to the data wrapper URIs, I don't find any.  This leads 
me to believe that perhaps we have broken the process of creating the 
TangibleState during upload

Original comment by stephen....@gmail.com on 12 Aug 2010 at 2:32

GoogleCodeExporter commented 9 years ago 
Remember that insert/add/update/change/delete/remove operations are disabled on 
dev-. 

This is the content of the email I sent to Stephen, Chris, and Jesus on Jul 27:

******************
I have installed a new server on dev- that supports the fine-grained control of 
write operations on the server. This and the procedure for enabling/disabling 
them are described in our wiki at

http://wiki.wholebraincatalog.org/wiki/How_to_Deploy_a_WBC_Server#Controlling_Se
rver_Write_Operations

All write operations are initially set to disabled. 

There could be some unintended consequences of this capability. If so, let me 
know and I will fix it.
******************

Original comment by davlit0...@gmail.com on 12 Aug 2010 at 6:42

GoogleCodeExporter commented 9 years ago 
Based on conversation today, I will give David Little more information on the 
appropriate behavior of the ContentResource.

Original comment by stephen....@gmail.com on 13 Aug 2010 at 10:39

GoogleCodeExporter commented 9 years ago 
Closing a whole raft of issues because they are not relevant to the web version 
any more

Original comment by stephen....@gmail.com on 7 Mar 2011 at 10:31