WDK extends to modifies migration

Andre Machado

Hi friends,

I have 2 WDK applications with these layers hierarchy:
wdk ... wp - custom - project1
wdk ... wp - custom - project2

I have one component (about_component) with these configurations:
- about_component from custom extends about component from wp and replaces jsps and nlsbundle tags
- about_component from project1 extends about component from custom and replaces only nlsbundle tag
- about_component from project2 extends about component from custom and replaces only nlsbundle tag

I want to migrate my WDK component to use modifies syntax.

First, I did this step:
- change the about component from custom to modifies about component from wp
- replace a jsp and nlsbundle tags

Now I want to apply the "modifies" syntax at project1 and project2 layers, how can I do that?

I did some tests and the only way that worked was to use "extends" in custom layer and "modifies" in project1 and project2 layers.

Is it the best practice in this case?

Thanks,

Andre

lastnitescurry

Modfies to change the NLS Bundle does not work unless, you put a copy of that NLS file into the modified layer. This is a limiation of the modifies.

Personally I would have aimed for the following wdk app layers

wdk->..->wp->mysharedfunctionality->project1->custom

wdk->..->wp->mysharedfunctionality->project2->custom

That way I can have "boiler plate/reusable/same old stuff" code in one layer and configs (business logic) projects in a seperate layer. Leaving custom as final layer on stack, means not having to modify web.xml and means that intergrating 3rd party stuff (e.g. brava) is eaiser