Recent changes to bugs

Error In Tutorial Example (LoggingAspect)

Anonymous — Thu, 26 Oct 2006 18:25:57 -0000

Source code for MyTransformation.tl depicted on the
page
http://www.fxl-project.com/html/fxl_eclipse_plugin.htm
generates errors as illustrated in patch attached.

Used plugin version 1.2.6

1.2.5.5 beta package broken on windows

anatoly techtonik — Wed, 25 Oct 2006 13:19:55 -0000

Downloaded archive fails to unpack. It is probably
because some of the pathnames inside are too long.
Namely the problem occurs somewhere within this directory:

\plugins\de.siemens.fxl.sll.examples.generator_1.2.1\de.siemens.fxl.sll.examples.generator_1.2.1

I guess this is because wrong double directory packaging.

Getting automatically the "Save As" Screen

Christian Feininger — Thu, 18 May 2006 09:21:01 -0000

If you are editing a transformation in your eclipse
project, where FXL support is enabled and also FXL
Builder is enabled and you already assigned the
transformation in a pipe, then you get sometimes if
you save the transformation, the "Save as" Screen. You
have to click it away before you can save the file and
it starts the pipe. This comes of quite often and is
really annoying.
I guess it has something to do when the transformation
file is open somewhere else.

"count" not allowed as XML element name

Anonymous — Wed, 12 Apr 2006 08:50:35 -0000

Because of a bug in the SLL grammar, "count" (which
is a SLL keyword) is currently not allowed as a XML
element name.
The editor throws the problem "unexpected token:
count".

SLL syntax highlighting

Anonymous — Wed, 12 Apr 2006 08:47:41 -0000

The SLL editor starts highlighting SLL code as XML-
content after a '<' character.
This is a wrong behaviour in case a '<' as condition,
e.g. in:

for (var $i as xs:integer =0; $i<100; $i=$i+1) {
...
}

Currently, everything after the '<' ("<100; $i=$i+1) {
...
} " is highlighted as XML content up to the
next '>' character.

Wildcards in XPath/XQuery expressions

Anonymous — Wed, 29 Mar 2006 09:38:35 -0000

The SLL plain-text editor throws the problem
"expecting semicolon, found '}'" when using the star-
wildcard in XPath/XQuery expressions, e.g. in the
expression:

insert <new/> into $a/test/*;

This is because the SLL grammar interpretes the '/*'
as the start of the multi-line comment.

TL and CVS

Anonymous — Mon, 27 Mar 2006 10:59:06 -0000

Preconditions:
If you have TL files and you use them in pipelines,
the corresponding xTL files are located in the xLang
folder.
The TL files are checked into a CVS and the xLang
folder is added to CVS ignore list.

Bug:
If you perform a CVS update (and new versions of the
TL files are checked out) and re-execute a pipeline
that uses these files, the corresponding xTL files
are not re-generated. Instead, the old xTL files are
used for the transformation.

Solution (by hand):
After performing a CVS update, delete the xLang
folder in you fxl-project.

Feature request:
Before executing a pipeline it should be checked
whether the xTL (xLang) files are up to date with
their corresponding source (lang) files.

Error starting plugins + Solution

Ulrich Dinger — Mon, 13 Feb 2006 17:26:29 -0000

If the FXL plugins are started, a message box

"An error has occured. See log for more details."
ocurrs. The error log shows the following exception:

java.lang.NullPointerException
at
de.siemens.fxl.ui.editors.pipeline.library.view.MyView
LabelProvider.getText(MyViewLabelProvider.java:31)
at
org.eclipse.jface.viewers.StructuredViewer.buildLabel
(StructuredViewer.java:1877)
...

This is a general bug when eclipse is located in a
directory containing white spaces, e.g. c:/program
files/eclipse.
Please copy your eclipse to a folder without white
spaces.

your fxl team

Iterator over variables does not work on Java 1.5 + Solution

Ulrich Dinger — Mon, 13 Feb 2006 11:57:39 -0000

If you use Java 1.5 as VM for your eclipse, iterators
over variables will not work for TL/XSLT:

e.g.

var books = value-of("/books);
for (x:"$books") {
...
}

This will not work!

Error: Couldn't load document

christian.reichel — Thu, 11 Aug 2005 16:37:34 -0000

This is a general FXL bug when eclipse is started with a
JRE. In this case, Ant isn't able to find a Java compile
task (javac) which is needed for the FXL language
compilation. To solve this problem, please start you
eclipse platform with the "-vm" option followed by a valid
JSDK directory.