[Aplaws-devel] Work around to problem of ccm load not finding pdl file in application build on aplaws+

[<Paw...@ne...>]

In build an application using the Aplaws+ Beta distribution from Ferbuary 
2004 the PDL file for a new content type are not place correctly by the 
provided Ant deploy task and you get the following error message when 
trying to load the application: 
>  2004-02-19 14:19:48,227 [ main] INFO  packaging.Loader - Running 
initializer com.net2s.edemocracy.cms.contenttypes.CouncillorInitializer
> Exception in thread "main" java.lang.IllegalStateException: 
edemocracy.pdl.mf: 6: no such resource 
'com/net2s/edemocracy/cms/contenttypes/Councillor.pdl'
>         at 
com.arsdigita.persistence.pdl.ManifestSource.parse(ManifestSource.java:94)
>         at 
com.arsdigita.runtime.PDLInitializer.init(PDLInitializer.java:69)
>         at 
com.arsdigita.runtime.CompoundInitializer.init(CompoundInitializer.java:97)
>         at 
com.arsdigita.runtime.CompoundInitializer.init(CompoundInitializer.java:97)
>         at com.arsdigita.runtime.Startup.run(Startup.java:215)
>         at com.arsdigita.packaging.Loader.loadData(Loader.java:109)
>         at com.arsdigita.packaging.Load.run(Load.java:341)
>         at com.arsdigita.packaging.MasterTool.main(MasterTool.java:90)

A work arround is manully to copy the file to the directory of the class 
files (Contenttype, Initiliazer and Loader) for that content type. This 
will then enable loading the content type. You then subsequently have to 
remember copying the file again when changes have been mae to the PDL file
.

Paw Hammerlund Andersen
Principal Consultant, www.net2s.com