IBM Support

PK57070: LOOSECONFIG.XMI NOT PROPERLY CREATED WHEN USING EJB PROJECTS AS WEB LIBRARY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • NoClassDefFoundError at runtime when using Web Libraries instead
    of MANIFEST.MF due to looseconfig.xmi file not being created
    properly. It seems that when you use EJB projects as web
    library projects, the logic fails to resolve the correct
    directory for where the output folder of the EJB project
    is and therefore the classes are never found by the
    runtime.
    

Local fix

  • Unknown
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the v5.1 WebSphere Test         *
    *                 Environment running applications that        *
    *                 consist of Enterprise Java Bean (EJB)        *
    *                 modules as Web Library projects.             *
    ****************************************************************
    * PROBLEM DESCRIPTION: The looseconfig.xmi file does not       *
    *                      contain the correct path to the         *
    *                      output folder of the EJB modules        *
    *                      configured as Web library projects.     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The output directory for the EJB modules configured as web
    library projects in the looseconfig.xmi file was the output
    folder of the corresponding web project.  Therefore, the
    WebSphere Application Server runtime was unable to locate the
    classes from the EJB module as these class files do not reside
    in the dynamic web projects output folder.
    

Problem conclusion

  • The correct EJB project output directory will not be added to
    the looseconfig.xmi file when the EJB module has been
    configured as a Web library project.  The fix for this APAR is
    currently scheduled for inclusion into the Rational
    Application Developer v7.0.0.6 fixpack.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK57070

  • Reported component name

    WEBAPP SERVER A

  • Reported component ID

    5724J0820

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-11-26

  • Closed date

    2007-12-06

  • Last modified date

    2007-12-06

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBAPP SERVER A

  • Fixed component ID

    5724J0820

Applicable component levels

  • R610 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
19 October 2021