[JIRA] Commented: (NXP-1503) Nuxeo Remote Api replaces application classloader

2007-09-03 Thread Filipchik Alexander (JIRA NUXEO)

[ 
http://jira.nuxeo.org/browse/NXP-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_25239
 ] 

Filipchik Alexander commented on NXP-1503:
--

May be problem can be solved, by adding a parent classloader to the new one. 
I.e. you have to put current  thread classloader as parent to new created. It 
allow to save current classloader hierarchy.

 Nuxeo Remote Api replaces application classloader
 -

 Key: NXP-1503
 URL: http://jira.nuxeo.org/browse/NXP-1503
 Project: Nuxeo Enterprise Platform 5
  Issue Type: Bug
  Components: Runtime
Affects Versions: 5.1.0.GA
Reporter: Filipchik Alexander
Assignee: Bogdan Stefanescu
Priority: Blocker
   Original Estimate: 1 week, 2 days
  Remaining Estimate: 1 week, 2 days

 I trying to use Nuxeo Remote api to create bridge between me web-application 
 and Nuxeo Server.
 My web-application starts under Tomcat Application Server, and uses Spring 
 Web.
 To interact with Nuxeo i need to use Nuxeo Remote. 
 So i put all necessary common libs in tomcat/common/libs directory.
 My webb-application is situated in tomcat/webapp/ directory.
 What i get, when tomcat starts:
 when i trying to configure Nuxeo Runtime (runtime = new SimpleRuntime(home); 
 Framework.initialize(runtime); deployConfiguration();) i lost my current 
 classloader.
 Since all beans is loaded by Spring Classloader (or i can too write own 
 Classloader for my needs) - this process interrupts.
 Nuxeo libs is situated in common libs dir, so they are loaded by tomcat level 
 classloader. This classloader don't know about classes in my application.
 So Spring throwing ClassNotFound Exceptions for classes, that situated in 
 application!!!
 I investigate Nuxeo code and found 5 classes where classloader is changed.
 It is:
 org.nuxeo.ecm.core.schema.TypeService
 org.nuxeo.runtime.jboss.adapter.deployment.XMLComponentDeployer
 org.nuxeo.runtime.jboss.osgi.JBossOSGiAdapter
 org.nuxeo.runtime.launcher.RuntimeLoader
 org.nuxeo.runtime.launcher.StandaloneBundleLoader
 If you need to load classes with you own classloader - you must restore 
 default, when loading is finished.
 Only XMLComponentDeployer restores default classloader
 Please, review this bug as soon as possible, because it  prejudices using 
 Nuxeo Remoting.
 In my mind - there are so much functionality and libs in Nuxeo Remote 
 interface, it must be lightweight.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


___
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets


[JIRA] Created: (NXP-1515) Userspace

2007-09-03 Thread Julien Lepage (JIRA NUXEO)
Userspace
-

 Key: NXP-1515
 URL: http://jira.nuxeo.org/browse/NXP-1515
 Project: Nuxeo Enterprise Platform 5
  Issue Type: Question
Reporter: Julien Lepage
Assignee: Thierry Delprat


Hi,
Can i have more information about user's space which is located 
domain/userdatas/username ? Indeed, i can't find the  user-data-type.xml (i 
have greped this file and UserDataRoot but no find)
Thanks, 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


___
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets


[JIRA] Created: (NXP-1516) XML formatting lost when saving local theme file

2007-09-03 Thread JIRA NUXEO
XML formatting lost when saving local theme file


 Key: NXP-1516
 URL: http://jira.nuxeo.org/browse/NXP-1516
 Project: Nuxeo Enterprise Platform 5
  Issue Type: Improvement
Affects Versions: 5.1.0.GA
Reporter: Thibaut SoulciƩ
Assignee: Jean-Marc Orliaguet


on two lines...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


___
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets


[JIRA] Created: (NXP-1518) Layout system

2007-09-03 Thread Anahide Tchertchian (JIRA NUXEO)
Layout system
-

 Key: NXP-1518
 URL: http://jira.nuxeo.org/browse/NXP-1518
 Project: Nuxeo Enterprise Platform 5
  Issue Type: Task
Reporter: Anahide Tchertchian
Assignee: Anahide Tchertchian
 Fix For: 5.2 M1


Form automatic generation using an XML configuration.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


___
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets


[JIRA] Commented: (NXP-1518) Layout system

2007-09-03 Thread Anahide Tchertchian (JIRA NUXEO)

[ 
http://jira.nuxeo.org/browse/NXP-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_25287
 ] 

Anahide Tchertchian commented on NXP-1518:
--

Layout service
==

Layout service: component that handles a registry of named layouts and
associated api to access them.

API:

getLayout(id, mode)

...

A layout definition:

layout id=dublincore
  !-- optional source used to organize widget calls --
  source/source
  widget id=title type=text
labels
  !-- default label (no mode specified) --
  labellabel.dublincore.title/label
  label mode=edit/label
/labels
descriptionfoo/description
helpbar/help
!-- translate labels, description, help... --
translatetrue/translate
!-- field with schema, field name and optional id --
fields
  field schema=dublincore name=title id=text
/fields
!-- if a mode is given, it overwrites the layout mode ;
  no expressions allowed for now (?) --
modeview/mode
!-- jsf properties to apply when rendering the document ;
 EL expressions accepted --
properties
  property name=renderedtrue/property
  property name=required#{!currentUser.administrator}/property
  !-- other common components attributes: onclick, etc...--
  property name=styleClassdataInputText/property
/properties
!-- properties for a given mode --
properties
  modeedit/mode
  modecreate/mode
  property name=renderedfalse/property
/properties
  /widget
  widget id=subjects type=list
fields
  field schema=dublincore name=subjects
/fields
properties
  property name=directorysubject/property
/properties
  /widget
  !-- widget for lists/sub fields --
  widget id=files type=complexList
fields
  field schema=files name=files
/fields
subwidget id=file type=file
  subfields
subfield name=content id=blob
subfield name=filename id=filename
  /subfields
/subwidget
  /widget
/layout


Usage in xhtml file:

nx:widget widget=widget document=document mode=mode /

The specific component handler used to manage widgets will put components
defined in the widget type definition in the tree at creation time.
It will derive from the CompositeFaceletTagHandler.

Specific tag handlers can be defined to do specific work (properties setting
for instance).

When a source is mentioned, it is used as if it was defined using a
ui:decorate tag.

Widget type definition:

widget type=text
  handler-classorg.nuxeo.ecm.platform.layout.WidgetTagHandler/handler-class
  !-- optional component description using default implementation --
  components mode=view
component id=text
  component-type.../component-type
  renderer-type.../renderer-type
  handler-class.../handler-class
  source.../source
/component
  /components
  components mode=edit
component id=text
  component-type/component-type
  renderer-type/renderer-type
  handler-class/handler-class
  source/source
/component
component id=message
  
/component
  /components
/widget


Link to document types
==

Documents types can be configured to use registered layouts.
This will be added to a type definition:

type id=Root coretype=Root
  labelServer Root/label
  icon/icons/folder.gif/icon
  ...
  layoutClusters
!-- default cluster (no mode specified) --
cluster
  layoutdublincore/layout
/cluster
!-- do not display --
cluster mode=create
  layoutdublincore/layout
  layoutfile/layout
/cluster
  /layoutClusters
/type

Document layout service api:

getLayout(document, mode)

nx:cluster document=document name=default mode=edit /
will call recursively nx:layout document=document name=layout_id
mode=edit / for each layout in given cluster.
This will call recursively the associated nx:widget tags.

Layout can be generated using the old layout system for compatibility
purposes, or generated automatically using the schema definition (?).


 Layout system
 -

 Key: NXP-1518
 URL: http://jira.nuxeo.org/browse/NXP-1518
 Project: Nuxeo Enterprise Platform 5
  Issue Type: Task
Reporter: Anahide Tchertchian
Assignee: Anahide Tchertchian
 Fix For: 5.2 M1


 Form automatic generation using an XML configuration.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


___
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets


[JIRA] Commented: (NXP-1518) Layout system

2007-09-03 Thread Florent Guillaume (JIRA NUXEO)

[ 
http://jira.nuxeo.org/browse/NXP-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_25288
 ] 

Florent Guillaume commented on NXP-1518:


In general I prefer to use name=... instead of id=..., as id often has a 
special meaning for XML.

Also instead of:
  field schema=files name=files/ 
I'd use:
  field schema=filesfiles/field 
And actually we should tend to make schemas disappear, and use prefixes 
instead, so:
  fieldf:files/field
Like also:
  field id=textdc:title/field
(I'm not sure what the id is for here, is it for JSF?)

(Same for subfields, avoid schemas and use prefixes)



 Layout system
 -

 Key: NXP-1518
 URL: http://jira.nuxeo.org/browse/NXP-1518
 Project: Nuxeo Enterprise Platform 5
  Issue Type: Task
Reporter: Anahide Tchertchian
Assignee: Anahide Tchertchian
 Fix For: 5.2 M1


 Form automatic generation using an XML configuration.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


___
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets


[JIRA] Commented: (NXP-1518) Layout system

2007-09-03 Thread Florent Guillaume (JIRA NUXEO)

[ 
http://jira.nuxeo.org/browse/NXP-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_25289
 ] 

Florent Guillaume commented on NXP-1518:


Also subwidget - subWidget, etc.



 Layout system
 -

 Key: NXP-1518
 URL: http://jira.nuxeo.org/browse/NXP-1518
 Project: Nuxeo Enterprise Platform 5
  Issue Type: Task
Reporter: Anahide Tchertchian
Assignee: Anahide Tchertchian
 Fix For: 5.2 M1


 Form automatic generation using an XML configuration.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira


___
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets