Skip to Content
avatar image
Former Member

java.lang.NoClassDefFoundError when using Public Parts

Hi there,

following situation:

i have a local EJB Module DC where i made Classes for Business Delegate available as public parts.

I'm using this Public part in a local WD-DC.

Now when i Build the WD DC and have a look inside the generated EAR file, there is a WDA file inside.

looking into this WDA file, i find a PORTAL-INF\lib directory, where the JAR with the classes from the J2EE DC is located.

everything looks quite good.

but i get a warning when i am deploying the WD DC:

1.: development component 'xxxxxxwd'/'pose.com'/'LOCAL'/'20040621162031'

dependency:

name: 'yyyy'

vendor: 'pose.com'

ok, so i tried the other way on the WD-Application:

"Deploy new Archive an RUN"

it starts, but i cannot find the classes that should be in the JAR.

Trying it that way, there is no JAR in the EAR! Where does this come from?

I get "java.lang.NoClassDefFoundError" in my Browser.

what is a safe way to make use of other PP's in a Web Dynpro Application?

Thanks for your help

Norbert

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Jun 21, 2004 at 02:36 PM

    Hi Norbert,

    there must be a Sharing Reference from the WD enterprise application to the enterprise application used (in this case residing in the EJB container) to find the classes at runtime. The referencing (as Used DC) of the PP of this application does not add/remove this reference automatically. There's no need to include the jars of the J2EE module DC inside the WD enterprise app. To make this work, you have to deploy the EAR including the J2EE module first, followed by the WD app, since the "standard" properties of the PP usage includes a "must be active at deploy" property. From this the warning you receive is raised.

    Hope that helps.

    Regards

    Stefan

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Norbert,

      i'm not sure whether DTR usage will change this behaviour (from my point of view it seems to be difficult to resolve all implicit and explicit reference dependencies on libraries, services, enterprise apps at design time automatically). Sometime ago i posted a proposal in the WD forum to let the developer add an arbitrary reference via the context menu, selecting a used DC entry, to avoid manual, error-prone typing. Let's wait and see 😉

      Best regards

      Stefan