Le lundi 24 septembre 2007 à 23:01 -0500, John Goerzen a écrit : > Hi everyone, Hi,
Just a few words to add to Alain's answer. > > 1) There is a quite monolithic installer. Can I install Nuxeo onto > a standard Debian jboss/tomcat/whatever installation? If not, > what happens when an individual component, say jboss, has a security > bug? Does everything have to be upgraded? Nuxeo 5 is really a platform : a set of configurable and pluggable components. What you are testing is the defaut demo webapp packaging. Nuxeo modules can be deployed on JBoss 4.0.4/5 , but also GlassFish (partial support for now) and Eclipse RCP. The packaging system uses Maven. Using our maven plugin, you can assemble a custom application : - choosing what component you need - split application on several JVMs / ears > > 2) A critical part of this is accessing the system through automated > means. This is not going to be from Java, however. It seems that > there are many API points that require Java, but I can't find > anything such as XML-RPC, REST, SOAP, etc. interfaces that are > language-agnostic. If I wanted to, say, upload a new document and > set the name and source field, how could I do this in an automated > fashion without using Java? Because our first uses cases for using remote interfaces needed performances we first focused on EJB3 remoting. => Almost all services are accessibles via EJb remoting Nuxeo 5 also offers other remote interfaces : - WebServices : For now Nuxeo only exposes to simple SOAP WebServices. For the 5.2 release we will work on giving a SOAP facade for most services. - RestAPI Nuxeo 5 already exposes a set of RestAPI. For that we integrated restlets (restlet.org). Nuxeo provides bases classes for implementing Restlet that integrates with Nuxeo API (with or without Seam). => http://svn.nuxeo.org/trac/nuxeo/browser/org.nuxeo.ecm.platform/trunk/nuxeo-platform-ui-web/src/main/resources/OSGI-INF/restAPI-contrib.xml For examples, the rest Upload API is already used by the Firefox plugin to do the upload. Some extra restlet are available in the sandbox : http://svn.nuxeo.org/trac/nuxeo/browser/sandbox/nuxeo-platform-restPack/trunk There is also a java http client lib : http://svn.nuxeo.org/trac/nuxeo/browser/sandbox/nuxeo-http-client/trunk - Seam remoting : Thanks to Seam some of the methods of the ActionListeners are accessible via javascript/XMLHttpRequest. This is how D&D feature is handled in Nuxeo5 standard webapp. > 3) Can we define custom metadata fields? Of course, please see Nuxeo Book and sample projects. > What is the efficiency of > searching for a particular word within existing metadata fields? Well, this is exactly the purpose of the pluggable search service ... > Does each word occur in a row in an indexed database column? This is a real search engine, by default using Lucene via Compass. See Nuxeo Book for more details. > > 6) What are domains for? I can't seem to see that they offer any > functionality that can't be obtained through another workspace & > section. I must admit that for now a Domain is a kind of super workspace. For some project, Domains are used to bind a part of the user directory to a part of the content tree : eg : a commercial domain (internal users + clients users) and a internal domain => differents LDAP and SQL directories We plan to port a part of this configuration in the standard 5.2 webapp. > > 7) I get an exception (a cast exception for java.lang.long) whenever > attempting to modify a vocabularly. This is with 5.1.1.GA. > This didn't appear fixed in the BTS. Is there a workaround? We'll check this, thx for the feedback. > > 8) What is the scalability of the system, and where can I read > about server sizing? The service platform has been load tested for heavy document creating/injection process. The tests scripts are available in the public SVN. In a standard server (Bi Pro + 4 Go) you can expect to inject between 10 and 20 documents per secondes depending on the size of the attached files and the business logic (meta-data processing ....). Some simple documents injection (big set of meta-data but no blob), we have examples of injection at 80 doc/s. On the webapp side, we are doing the tests and optimisations for a few days now. Plublic results will be available soon. The main points are : - the sizing will heavily depend on you business logic => the type of document you use => the event listeners associated to it => the process associated to it - Nuxeo 5 can be splitted in several JVM/Server - A lot of heavy processing can be made async - We already have a lot of tools to help testing and tuning > > 9) URLs to the actual document content don't appear to remain static > when documents are moved to other folders. This should already be the case ! > Is there a way to get a > static link to a document (or a particular version) that will always > be constant, even if moved? The default URL pattern does not include versioning, but this is pluggable and we have already implemented it for client projects : URL => Business UID + version Id > > 10) How do I make it use USA date formats? (m/d/y) Should be a simple JSF configuration. > > 11) Can I define pulldown lists for fields other than Coverage? Yes, that what hierarchical vocabularies are made for. > > Thanks, > > -- John > > _______________________________________________ > ECM mailing list > [email protected] > http://lists.nuxeo.com/mailman/listinfo/ecm > _______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm
