<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.17023" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=427110311-05042010><FONT face=Arial
color=#0000ff size=2>Hi Gleb</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=427110311-05042010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=427110311-05042010><FONT face=Arial
color=#0000ff size=2>OpenCmsVfsFile accepts only relative paths to files that
exist on your OpenCms system, and you cannot disable the existence
check, as far as I know. You can however use an OpenCmsVfsFile
field to refer to an external file by pointing to a VFS
file of type "pointer" (called "External link" in the "New" dialog). A
file of type "pointer" is simply a file that holds a reference to
any URL, and if you access the pointer, you will be redirected to that URL. I
would suggest using this approach if you're mostly pointing to local files, and
rarely external files.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=427110311-05042010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=427110311-05042010><FONT face=Arial
color=#0000ff size=2>If you're often pointing to external files, then
you probably want to convert the OpenCmsVfsFile field to an
OpenCmsString field. For getting this job done while preserving your
data, my best suggestion would be to write a
custom JSP that modifies your xmlcontent files. (You will of
course have to change your XSD file(s) as well, but that part should be
quite straight-forward.)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=427110311-05042010><SPAN
class=427110311-05042010><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left>
<DIV dir=ltr align=left><SPAN class=427110311-05042010><FONT face=Arial
color=#0000ff size=2>Note: the administration panel has a tool under "Content
tools" called "Repair XML content", which will repair xmlcontent files
according to their XSD file(s). Unfortunately it cannot be used in your
case, as all your data for that field would be lost. (You could have
used it if you were converting the opposite way though, changing an
OpenCmsString field into an OpenCmsVfsFile
field.)</FONT></SPAN></DIV></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=427110311-05042010><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=427110311-05042010><FONT face=Arial
color=#0000ff size=2>Best regards,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=427110311-05042010><FONT face=Arial
color=#0000ff size=2>Paul</FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> opencms-dev-bounces@opencms.org
[mailto:opencms-dev-bounces@opencms.org] <B>On Behalf Of </B>gleb
makarov<BR><B>Sent:</B> 5. april 2010 12:46<BR><B>To:</B>
opencms-dev@opencms.org<BR><B>Subject:</B> [opencms-dev] external links in
OpenCmsVfsFile<BR></FONT><BR></DIV>
<DIV></DIV>Hello everyone,<BR>
<META content=Word.Document name=ProgId>
<META content="Microsoft Word 12" name=Generator>
<META content="Microsoft Word 12" name=Originator><LINK
href="file:///D:%5CGLEBA%7E2.MAK%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"
rel=File-List><LINK
href="file:///D:%5CGLEBA%7E2.MAK%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"
rel=themeData><LINK
href="file:///D:%5CGLEBA%7E2.MAK%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"
rel=colorSchemeMapping>
<STYLE>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 2.0cm 42.5pt 2.0cm 3.0cm; mso-header-margin: 35.4pt; mso-footer-margin: 35.4pt; mso-paper-source: 0; }
P.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0cm 0cm 10pt; LINE-HEIGHT: 115%; FONT-FAMILY: "Calibri","sans-serif"; mso-style-unhide: no; mso-style-qformat: yes; mso-style-parent: ""; mso-pagination: widow-orphan; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-theme-font: minor-bidi; mso-fareast-language: EN-US
}
LI.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0cm 0cm 10pt; LINE-HEIGHT: 115%; FONT-FAMILY: "Calibri","sans-serif"; mso-style-unhide: no; mso-style-qformat: yes; mso-style-parent: ""; mso-pagination: widow-orphan; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-theme-font: minor-bidi; mso-fareast-language: EN-US
}
DIV.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0cm 0cm 10pt; LINE-HEIGHT: 115%; FONT-FAMILY: "Calibri","sans-serif"; mso-style-unhide: no; mso-style-qformat: yes; mso-style-parent: ""; mso-pagination: widow-orphan; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-theme-font: minor-bidi; mso-fareast-language: EN-US
}
.MsoChpDefault {
mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-theme-font: minor-bidi; mso-fareast-language: EN-US; mso-style-type: export-only; mso-default-props: yes
}
.MsoPapDefault {
MARGIN-BOTTOM: 10pt; LINE-HEIGHT: 115%; mso-style-type: export-only
}
DIV.Section1 {
page: Section1
}
</STYLE>
<BR>I have a problem with external links in xmlcontent. There is an
OpenCmsVfsFile field type in xmlcontent files. It`s description in the
xml scheme is <xsd:element name="Image" type="OpenCmsVfsFile" /> When I
try to enter there a file name (path to file) form the different domain name
(<A href="http://servername/..">http://servername/..</A>), system shows
an error ‘Invalid reference, the resource can not be found’. <BR><BR>I`d like
to know if there is a way to update this scheme and change the field type
without data loss (for example change VfsFile to String).<BR><BR>Or is it
possible to disable verification of the OpenCmsVfsFile field type when saving
xmlcontent file?<BR><BR>I can`t update all xml schemes and templates manually
because of their huge amount.<BR><BR>Thank you in advance. <BR><BR>-- <BR>Best
regards,<BR>Gleb Makarov<BR></BLOCKQUOTE></BODY></HTML>