Re: [Jonto-users] R: [JeromeDL-devel] R: R: Jeromedl customization: localization of taxonomies, wordnet vocabulary, and indexing properties

[Giuseppe B. <giu...@al...>]

Maeusz,
I have stil a bit progress, but not a complete one. After a lot of test, =
I have the following test results:

1) JontoTest:=20
   1.1 the label of the new dCont taxonomy is displayed together with =
the other native jonto taxonomies;
   1.2 an AJAX call error is displayed on each taxonomy label: Servlet =
TaxonomyBrowser is not available.

2) JeromeDL resource uploading:
    2.1) all the taxonomies ( the new dCont included) are listed and =
completely loaded in the  Domains section;
    2.2) the domain filtering on a specific term results in the display =
of an equal number of matches on all the taxonomies; however only the =
taxonomies really including             the given term highlight the =
occurring submatches.

3) Sesame-jonto repository:
    3.1) the triples of the new dCont taxonomies are completely =
generated.

So  an AIAX call error seems to still prevent the successfull completion =
of my test.

Can you suggest some workaround?

Giuseppe=20


   =20

----- Original Message -----=20
  From: Mateusz Kaczmarek=20
  To: Giuseppe Bux=20
  Cc: Devel JeromeDL ; jon...@li...=20
  Sent: Friday, January 11, 2008 4:07 PM
  Subject: Re: R: [JeromeDL-devel] R: R: Jeromedl customization: =
localization of taxonomies, wordnet vocabulary, and indexing properties


  Giuseppe,
  the only mistake you have in your build.xml is that in
  <target name=3D"cleanModules" description=3D"Clean required jerome =
modules">
  you have
          <ant antfile=3D"${jontoAcmPath}/build.xml" target=3D"build">
              <property name=3D"basedir" value=3D"${jontoAcmPath}/"/>
              <property name=3D"lib.dir" =
value=3D"${jontoBasePath}/lib"/>
          </ant>
                  <ant antfile=3D"${jontoDcontPath}/build.xml" =
target=3D"build">
              <property name=3D"basedir" value=3D"${jontoDcontPath}/"/>
              <property name=3D"lib.dir" =
value=3D"${jontoBasePath}/lib"/>
          </ant>
  though you should have:
          <ant antfile=3D"${jontoAcmPath}/build.xml" target=3D"clean">
              <property name=3D"basedir" value=3D"${jontoAcmPath}/"/>
              <property name=3D"lib.dir" =
value=3D"${jontoBasePath}/lib"/>
          </ant>
                  <ant antfile=3D"${jontoDcontPath}/build.xml" =
target=3D"clean">
              <property name=3D"basedir" value=3D"${jontoDcontPath}/"/>
              <property name=3D"lib.dir" =
value=3D"${jontoBasePath}/lib"/>
          </ant>

  As far as your Tomcat log is concerned, I don't recall to have such an =
exception, but I suppose it is not connected to JOnto.

  I would recommend you to check if after building the JOnto modules =
they are really copied to Tomcat/lib.
  Once more clean all projects, refresh them (F5 in Eclipse) and build =
all modules using build.xml from JOnto_base.
  You can also try to clean the cache of your web browser.

  Regards,
  Mateusz


    Mateusz,
    a bit progress we acheeved!=20
    By applying your below suggestions  finally the jontotest.jsp is =
running. However, as in my initial trial of jeromedl customization, the =
jontotest loads only the native jonto taxonomies (i.e: acm, udc, ddc, =
dmoz, loc). My dcont taxonomy is not loaded. I ran the ant on the =
dcont/build.xml, in order to build the related jonto project, and I =
verified again the dcont references included in jonto_base/build.xml, as =
well in jonto_base/src/context.properties files: it seems to me  to be =
all ok!=20
    Please verify my build.xml file here attached .
    Another doubt, coming to me, concerns the =
jonto_base/src/sesame.conf: should be it updated?

    Last output of my trial is the tomcat log of my jontotest process: =
it highlights an exception. Please verify it in the attached file.

    Sorry to disturb you with my configuration problems, but their =
solution is basic for my jeromedl customization process.
    Giuseppe=20




  __________ NOD32 2782 (20080110) Information __________

  This message was checked by NOD32 antivirus system.
  http://www.eset.com