Hi Catrina
just to update you on this issue.
With your help we have now reproduced the problem, and identified the
code change that introduced it.
We are now examining the conflicting requirements, (which motivated the
suspect code change) and looking at the design of this feature. Given
that you have a workaround, using "?filename as a sp:varName object", we
have a preference to continue our internal design discussion for a
little longer, before deciding on the way forward.
thanks
Jeremy
On 8/15/2011 11:01 AM, Catrina wrote:
I see the problem. Our scripts use the following method when using a
variable for a property (wrap the variable name with curly braces):
{?variableName}
Your script examples use the following method:
?filename as a sp:varName object
Is my method shown above no longer supported? Examples in the
TopBraid project still show similar methods as mine do so I'm a little
confused. Did we miss something being removed?
~Catrina
On Aug 15, 12:48 pm, Scott Henninger<[email protected]>
wrote:
Catrina; Is there any processing of the variable between its creation and when
it is used in the input/output module. At this point, we can't reproduce what
you are reporting.
Attached is a test case that works as expected. If you can modify this to fail
as your script does, then we should be able to isolate the issue. Follow these
steps:
1. Create a project named NewProject
2. Run the ExportToRDF script
3. Run the ImportRDFFromWorkspace script
You can look at these scripts in SPARQLMotion. The first will create a file
path with various camel case and space formats. This creates the filepath
correctly. The second uses the same pathname, bound from the the same
BindBySelect query.
-- Scott
On 8/15/11 8:12 AM, Catrina wrote:A similar issue occurs when using a variable in the
sml:sourceFilePath property and Import modules. In this example, I set a variable for
the project workspace's directory and another for the input xml file. But, when the
sml:ImportXMLFile module attempts to import the file, it's trying to get a file out
of the directory where the script resides and the file separators in my variables are
resolved to underscores. These problems cause an issue for a large number of our
scripts. All of which worked prior to TB 3.5.x. Thanks, Catrina On Aug 15, 7:34 am,
Catrina<[email protected]>wrote:When using the various Export
SPARQLMotion modules, it is common for us to set the sml:targetFilePath property with
a variable storing the absolute path in the project's workspace. However, in
TopBraid 3.5.1, all of these values appear to be getting resolved incorrectly with
underscores in place of the file separator. This issue has caused every SPARQLMotion
script containing an export module to break. For example, my variable is set to
something like the following: - logFile = /MyProject/MyLogs/Log_TESTING.txt However,
the text file was written to:
/WhereeverTheScriptResides/_MyProject_MyLogs_Log_TESTING.txt Thanks, Catrina
unnamed1.ttl
2KViewDownload
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
