In the Forums, chris11kgf wonders about Maya 2008 export to Collada: "Hi, I was wondering if anyone has had success exporting a Maya 2008 file on Mac to collada for use in Wonderland v0.5. I downloaded and installed the CG.framework from NVIDIA and the ColladaExporter3.05B. Then, in Maya I checked load and autoload on COLLADA.bundle under Window>>Settings/Preferences>>PlugInManager. From there, I was able to export files into .dae format. I tried a simple model of some spheres and cubes and then a more complex model of an urban village. Also, saw the free transform post from earlier and tried that on my models. Unfortunately, neither of my models were viewable. I tried scaling larger (1.0, 5.0, 10.0) but still was unable to see model..."

userlab is working with Wonderland + JavaFX: "Hi everyone, I was wondering with the addition of JavaFX into the JVM family is there any project/work using JavaFX within Wonderland virtual worlds or is there plans on using the JavaFX platform in the future? I would be interested in starting a discussing and hearing all your thoughts on the + and - on using JavaFX in this context and maybe where we can take best advantage of its features. Just to get started I've thought it would be nice to have the client side UI written in JavaFX, for this would have the following benefits; - The UI could run within a browser and then be dragged off to be independent of that browser. (IE only) - The interface could be easily extended by none Java developers and be more rich in look-and-feel. - If the client side kept close to the core JavaFX library then it could run wherever the FX platform is or goes... (i.e. Desktop/Web/Mobile/TV/Blu-ray)..."

And ipsi asks about Options for Securing Client when Server has no wsp:Policy information?: "I have a web application running under Glassfish V2 UR2 (Java 1.5), and as part of that Application I need to call a remote web service. As far as I'm aware, that web service doesn't have any wsp:Policy information in the WSDL, and so I need an alternate way to secure it. The less code I have to write, the better. I've seen information regard wsit-security and {serviceName}Service.xml files, so I'm wondering if it would be as simple as taking the WSDL, adding all the required policy information (including the signed/encrypted parts and such), essentially including all the policy information that would normally be on the server side, and just allowing Metro/WSIT to pick that up. If that's possible, that'd be fantastic. For what it's worth, I did try that, but it didn't seem to find the wsit-client.xml file..."