Hi Matthew,

Thank you for the email.  After what you said I took another look at
the bluedragon.xml and not only had it changed the mapping name to
lower case, it had completely removed the <directory></directory> tag!
 I put it back in, and now it works.

I hadn't thought to look in the bluedragon.xml file because I was
operating on a remote server, and just kept making changes locally
then FTP'ing the file again.

Can anyone else reproduce the issue where it removes the
<directory></directory> tag completely?

Andrew.

2008/11/19 Matthew Woodward <[EMAIL PROTECTED]>:

> I just tried this on Windows using the Jetty version of OpenBD and it worked
> for me. I just did a simple test file that I included--here's the mapping
> info:
> <cfmappings>
>   <mapping name="/modelglue">
>     <directory>C:/</directory>
>     <name>/ModelGlue</name>
>   </mapping>
>  </cfmappings>
>
> Note that the mapping name that's an attribute of the mapping node becomes
> "/modelglue" (lowercase) when OpenBD restarts, but that doesn't affect how
> things work since the mapping check is case-insensitive.
>
> If yours is still mixed case, that could indicate you didn't restart OpenBD
> after adding the mapping because, at least in my experience on both Linux
> and now Windows, that will get changed to all lowercase when OpenBD
> restarts.
>
> I did a couple of other directory tests (i.e. things other than the C:/
> root) and it seems to work.
>
> Let me know if you're still having trouble and I'm sure we can get it sorted
> out.
>
> --
> Matt Woodward
> [EMAIL PROTECTED]
> http://www.mattwoodward.com/blog
>
> Please do not send me proprietary file formats such as Word, PowerPoint,
> etc. as attachments.
> http://www.gnu.org/philosophy/no-word-attachments.html
>
>

--~--~---------~--~----~------------~-------~--~----~
Open BlueDragon Public Mailing List
 http://groups.google.com/group/openbd?hl=en
 official blog @ http://blog.openbluedragon.org/
!! save a network - trim replies before posting !!
-~----------~----~----~----~------~----~------~--~---

Reply via email to