Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.5
    • Fix Version/s: 1.0.6
    • Component/s: Core
    • Labels:
      None
    • Number of attachments :
      7

      Description

      CARGO-828 will probably fix this.

      Once done, also remember to update http://cargo.codehaus.org/JSR88

      1. JSR88GenericExtraConfigurationTest.java
        4 kB
        Lev Olkhovich
      2. JSR88GenericTest.java
        5 kB
        Lev Olkhovich
      3. JSR88GenericTest.java
        4 kB
        Lev Olkhovich
      4. jsr88-patch-0.txt
        55 kB
        Lev Olkhovich
      5. JSR88TypedTest.java
        4 kB
        Lev Olkhovich
      6. JSR88TypedTest.java
        3 kB
        Lev Olkhovich
      7. JSR88TypedTest.java
        3 kB
        Lev Olkhovich

        Issue Links

          Activity

          Hide
          Lev Olkhovich added a comment -

          Here are three sample files for current JSR-88 implementation.

          This example assumes Geronimo libraries to be available in d:\dev\cargo\geronimo-1.0-169186, Geronimo server to be available at the default URI with default login and password.

          For samples to work, the following five JARs from the Geronimo distribution have to be in the CARGO's classpath (Playing around with classloaders doesn't help as, for example, RMI protocol handlers are not visible to java.net unless they're in the classpath; hope this only affects Geronimo):

          mx4j-remote-3.0.1.jar
          mx4j-3.0.1.jar
          cglib-nodep-2.1.jar
          commons-logging-1.0.4.jar
          geronimo-kernel-1.0-169186.jar

          Show
          Lev Olkhovich added a comment - Here are three sample files for current JSR-88 implementation. This example assumes Geronimo libraries to be available in d:\dev\cargo\geronimo-1.0-169186, Geronimo server to be available at the default URI with default login and password. For samples to work, the following five JARs from the Geronimo distribution have to be in the CARGO's classpath (Playing around with classloaders doesn't help as, for example, RMI protocol handlers are not visible to java.net unless they're in the classpath; hope this only affects Geronimo): — mx4j-remote-3.0.1.jar mx4j-3.0.1.jar cglib-nodep-2.1.jar commons-logging-1.0.4.jar geronimo-kernel-1.0-169186.jar —
          Hide
          Vincent Massol added a comment -

          Moving to version 0.8 as it's not ready to be released in Cargo 0.7

          Show
          Vincent Massol added a comment - Moving to version 0.8 as it's not ready to be released in Cargo 0.7
          Hide
          Brice Copy added a comment -

          JSR-88 appears a nice solution to deploy to OC4J 10g - anyone with an update on this issue's status ?

          Show
          Brice Copy added a comment - JSR-88 appears a nice solution to deploy to OC4J 10g - anyone with an update on this issue's status ?
          Hide
          Vincent Massol added a comment -

          Brice,

          Unfortunately nobody is currently working on it... It's waiting for someone to jump in....

          Thanks
          -Vincent

          Show
          Vincent Massol added a comment - Brice, Unfortunately nobody is currently working on it... It's waiting for someone to jump in.... Thanks -Vincent
          Hide
          Markku Saarela added a comment -

          I have implemented little framefork on jsr88 based on this patch. No each container has responsibility of deployment-jar and classpath. CARGO-147 my implication of WAS 6.0 deployr support is done by this (and actually ongoing WAS6.1 support also).

          BTW your eclipse coding convention file is not working on Eclipse 3.2 plus versions(can you provide sufficient one).

          regards,

          -markku

          Show
          Markku Saarela added a comment - I have implemented little framefork on jsr88 based on this patch. No each container has responsibility of deployment-jar and classpath. CARGO-147 my implication of WAS 6.0 deployr support is done by this (and actually ongoing WAS6.1 support also). BTW your eclipse coding convention file is not working on Eclipse 3.2 plus versions(can you provide sufficient one). regards, -markku
          Hide
          Markku Saarela added a comment -

          I success that this issues should be closed, because it is pruned from Java EE 6 specification, due to lack of support from app server vendors. (The same this is going to JSR-77).

          Show
          Markku Saarela added a comment - I success that this issues should be closed, because it is pruned from Java EE 6 specification, due to lack of support from app server vendors. (The same this is going to JSR-77).
          Hide
          Adrian Cole added a comment -

          I agree. This should be closed and the JSR88PropertySet that was accidentally committed removed.

          Show
          Adrian Cole added a comment - I agree. This should be closed and the JSR88PropertySet that was accidentally committed removed.
          Hide
          Savas Ali Tokmen added a comment -

          Done revision 2160, first use case being GlassFish 3.x.

          Show
          Savas Ali Tokmen added a comment - Done revision 2160, first use case being GlassFish 3.x.

            People

            • Assignee:
              Savas Ali Tokmen
              Reporter:
              Vincent Massol
            • Votes:
              16 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: