BIRT Exchange Forum: BIRT Flex Output Emitter - BIRT Exchange Forum

Jump to content


 

No Latest Open Poll.

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

BIRT Flex Output Emitter Rate Topic: -----

#1 User is offline   mpovolny Icon

  • Junior Member
  • Pip
  • Group: Members
  • Posts: 2
  • Joined: 11-September 08


Posted 04 February 2010 - 02:46 AM

Hallo,

I have tried the BIRT Flex Output Emitter downloaded from the marketplace under Linux with the OSS BIRT and have found 2 problems:

1) the tool has hard-coded windows slashes:
WARNING: Cannot run program "/home/martin/birt/flash/flex/\bin\mxmlc.exe": java.io.IOException: error=2, No such file or directory

2) the output is not well formed and does not translate or validate:
$ xmllint mxml_20100131152148.mxml
mxml_20100131152148.mxml:105: parser error : Opening and ending tag mismatch: Grid line 33 and GridItem


Is there a newer (fixed) version or source code somewhere available to play with? Or do you have better experience with the emitter under similar circumstances?

Thanks and regards,

Martin Povolny
0

#2 User is offline   Sandeep Icon

  • Junior Member
  • Pip
  • Group: Members
  • Posts: 5
  • Joined: 14-May 08


Posted 10 February 2010 - 05:45 PM

Hi Martin,

Thanks for reviewing the Flex Output Emitter.

We had restricted the testing environment to Windows only. I will see if i can make it to run in a Linux environment. Meanwhile, were you able to run the sample reports in a Windows environment?

On the second issue of report not getting translated, were you trying one of the sample reports or your own report?

I will try to answer your queries as much as possible.

Thanks
Sandeep
0

#3 User is offline   mpovolny Icon

  • Junior Member
  • Pip
  • Group: Members
  • Posts: 2
  • Joined: 11-September 08


Posted 25 February 2010 - 01:11 PM

Hallo, and thanks for you reply.

I did not test the plugin on windows, I tested only Linux and given the error (wrong type of slashes) I do not expect the problem to occur on windows.

Fix should be fairly simple: use File.pathSeparator instead of hard coded windows shash "\".

The second problem occured when testing my own report.

Regards,

Martin Povolny
0

#4 User is offline   Sandeep Icon

  • Junior Member
  • Pip
  • Group: Members
  • Posts: 5
  • Joined: 14-May 08


Posted 08 March 2010 - 06:27 PM

Martin,

I will test out the change in the linux environment. In the meanwhile, could you send me the report design you are trying to run? If you could send me an associated report document as well that would be great.

Thanks
Sandeep
0

#5 User is offline   BArmstrong Icon

  • Newbie
  • Pip
  • Group: Members
  • Posts: 3
  • Joined: 21-January 11


Posted 31 January 2011 - 11:50 AM

I just tried the emitter under with Actuate 11 on Windows and I can't get it to work. The documentation all references Actuate 10. Is there a version for Actuate 11, or some documentation on what I would need to change to get it working on 11?
0

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users