[opencms-dev] opencms ftpd /w properties, a little problem with it and a request for testing

Ruben Malchow ruben at khm.de
Fri May 26 01:08:12 CEST 2006


hello list,

three topics rolled into one this time.

1.) NEW VERSION, INCLUDING ACCESS TO PROPERTIES ###################

i have just uploaded a new version of the opencms ftpd. it now includes 
the ability to access a resource's (or a structure's) properties through 
virtual files that have the same name as the referenced file, but a 
special suffix (which is configured by a module parameter called 
"suffix"). it this parameter is not set or set to an empty string, there 
will be no special properties files.

the property files are xml files that contain

-> resource properties (prefixed "resource.")

-> structure properties (prefixed "structure.")

-> a list of siblings (not currently used)

-> the resource id

-> the resource type id



2.) A LITTLE PROBLEM ################################################

now, the last thing is a bit of a problem. the good thing about it is 
that you can now download entire sites and upload them to a different 
opencms instance, and apart from the sibling structure it will be mostly 
the same, except for one big problem:

i tried this on

/sites/default/alkacon-documentation/documentation-xmlcontent

and when i delete the folder and upload it again, it will fail when 
setting the resource type id for

	simpleexample/simplecontent.html

because it is being set to xmlfile, and thus opencms will try to look at 
it as an xml file. the corresponding xml schema however is called

	simpleexample/simpleexample.xsd

and, when the client sorts alphabetically, is uploaded later. so it 
doesn't exist yet. thus, opencms barfs when trying to write 
simplecontent.html

when everything is there and i upload everything again, setting the 
resource type id succeeds, because then, the schema is there.

while this may be a good reason for joe desbonnet's idea of having a 
special "metadata" directory you can upload seperately and thus 
eliminating the problem with the inconvenient sort order, i was 
wondering if anyone else might have a different idea for solving this. 
having an entire virtual directory structure will be a pest, i reckon.

also, to avoid other possible problems with the order in which the files 
are uploaded by the client, it might be a good idea not to use multiple 
threads to upload several files simultanously.



3.) REQUEST FOR TESTING ################################################

i have heard reports of the opencms ftpd not working properly on some 
configurations, expecially involving eclipse on linux. and since i don't 
have the means of testing all combinations (shame on me) and still have 
the strong feeling it might be a CR/LF problem, i would like to ask 
anyone who is able to test any of the following configurations and 
report their findings:

	-> eclipse on linux, opencms on win32
	-> eclipse on linux, opencms on linux
	-> eclipse on win32, opencms on linux

with java 1.5.*, eclipse 3.1, opencms 6.2.* and the application server 
of your personal preference (i.e. tomcat 5.*).

please remember the crappy eclipse bug that makes it forget its 
credentials and always keep the eclipse site explorer open alongside the 
eclipse ftp/synchronize window:

Window -> Show View -> Other -> Target Management -> Site Explorer

there, you can go rightclick -> properties on your opencms ftp site and 
enter your credentials when eclipse forgets them.

thanks for your help!

#######################################################################

pling!

.rm









More information about the opencms-dev mailing list