Uploaded image for project: 'Commons JCI'
  1. Commons JCI
  2. JCI-6

[jci] FileResourceStore does not store class files correctly

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      Operating System: other
      Platform: Other

    • Bugzilla Id:
      36237

      Description

      The FileResourceStore stores class files in BASE_DIR/my.package.MyClass while
      the rest of the Java world would expect it in BASE_DIR/my/package/MyClass.class.
      To communicate with the rest of the Java world - in my case with XSP inside
      Cocoon - it would be necessary to change the FileResourceStore accordingly.

      When writing this I wonder what happens with non-to-be-compiled-resources. Their
      name will be also converted to class file names, and - as long as the rest of
      the Java world is not involved - they can be stored and read again - even if
      their name will be garbled.

        Activity

        Hide
        joerg.heinicke@gmx.de Jörg Heinicke added a comment -

        Created an attachment (id=16088)
        Patch to FileResourceStore.

        Show
        joerg.heinicke@gmx.de Jörg Heinicke added a comment - Created an attachment (id=16088) Patch to FileResourceStore.
        Hide
        tcurdt Torsten Curdt added a comment -

        you are right this should be changed and the "+ .class" should
        go away. basically it should be moved up the call chain.
        this can be done proberly when the matching support (see TODO) is being tackled

        Show
        tcurdt Torsten Curdt added a comment - you are right this should be changed and the "+ .class" should go away. basically it should be moved up the call chain. this can be done proberly when the matching support (see TODO) is being tackled
        Hide
        joerg.heinicke@gmx.de Jörg Heinicke added a comment -

        And you already have fixed the issue I came across when changing my output dir
        to another dir than the input dir: The files were no longer stored due to
        missing parent dirs.

        Thanks

        Show
        joerg.heinicke@gmx.de Jörg Heinicke added a comment - And you already have fixed the issue I came across when changing my output dir to another dir than the input dir: The files were no longer stored due to missing parent dirs. Thanks

          People

          • Assignee:
            Unassigned
            Reporter:
            joerg.heinicke@gmx.de Jörg Heinicke
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development