Adding package to translator

[Ashok Hariharan]

Hi Luca,

I am adding a package to the current version of the translator in svn ...

I dont call the translator directly from the editor anymore -- instead
i use reflection calls / and load it via a custom classloader -- to do
this i add a standard interface of functions to any library integrated
to the editor ...

it will be under org.bungeni.plugins.translator.*

Ashok

--
++++ Ashok Hariharan ++++

[Luca Cervone]

Ok Ashok, thank you. 

In the meanwhile I'm working to fix the problem of the messages. 

But, did you see the new kind of messages that I output when an error is raised?

What do you think about them?

Ciao

Luca

Luca Cervone

Web and XML solutions designer

e-mail:     cervo...@gmail.com

  luca.c...@unibo.it

lcer...@cs.unibo.it

mobile phone:    0039 348 26 27 545

home   phone:  0039 051 199 82 854

skype:   cervoneluca

[Ashok Hariharan]

On Thu, Jun 4, 2009 at 10:27 AM, Luca Cervone <cervo...@gmail.com> wrote:
> But, did you see the new kind of messages that I output when an error is
> raised?
> What do you think about them?

Much better i must say ... [1]

I am adding the new integration in today -- and then testing with a
more elaborate document to see how it holds up.

[1] - example error messages returned by the translator --

There was a problem during the validation of the document
In the section with type: subdivision, Having ID: motion1, Starting
with the words: Adoption of 35TH CPA (Africa Region) ReportMr Acheka
Included in the section with type: noticesOfMotion, Having ID: allmotions1
The problem is: The additional info 'name' is mandatory for the
element 'subdivision'
There was a problem during the validation of the document
In the section with type: subdivision, Having ID: motion2, Starting
with the words: Adoption of Report of First and Second Sessions of Pan
African ParliamentMr. NoK
Included in the section with type: noticesOfMotion, Having ID: allmotions1
The problem is: The additional info 'name' is mandatory for the
element 'subdivision'

[Luca Cervone]

Great. 

Another think that we have to talk about is how to show the problems relatives to the section that the user cannot see. 

For example, what we should display if something in the metadata section is not complete? 

I know that the metadata section is a part of the document that the translator creates (so if there is an error in almost all cases the problem is due to a translator issue ... "an implementation problem" .. so it should never happen). But in same case the problem can occurs due to an user mistake. For example if the user do not insert the publication date in the metadata of the document. 

Let me know. 

Ciao

Luca

[Ashok Hariharan]

On Thu, Jun 4, 2009 at 10:47 AM, Luca Cervone <cervo...@gmail.com> wrote:
> Great.
> Another think that we have to talk about is how to show the problems
> relatives to the section that the user cannot see.
> For example, what we should display if something in the metadata section is
> not complete?

There are 2 related problems here :

a -- missing metadata

- e.g. publication date -- or incomplete URI -- for these you can
just display an error message saying 'publication date' is not set.
there is nothing to point to within the original document.

b -- missing reference

-e.g. member of parliament reference is missing e.g. if there is a
speech section type without any member of parliament (from / by)
information set - it should generate an error and point to the section
that is the culprit.

Ashok

[Ashok Hariharan]

On Thu, Jun 4, 2009 at 10:27 AM, Luca Cervone<cervo...@gmail.com> wrote:

> In the meanwhile I'm working to fix the problem of the messages.

Hi Luca,

if you are fixing the problem of the messages, please checkout the
project afresh, as I have made some updates.

Ashok