It's a bug. The property should be validated early and deployment should be rejected if it's invalid. Right now, it looks like things fail after deployment (due to the invalid property).
alex On Thu, Apr 23, 2009 at 5:10 AM, Denis Weerasiri <ddweeras...@gmail.com>wrote: > Hi, > > I tried to deploy a process with a following deploy.xml. Here I'm tring to > test deploy a process with an incomplete <property> element. Here the > <property> has no name attribute > > <?xml version="1.0" encoding="UTF-8"?> > <deploy xmlns="http://www.apache.org/ode/schemas/dd/2007/03"; > xmlns:helloWorld="http://helloWorld";> > <process name="helloWorld:HelloWorldNew"> > <active>true</active> > <process-events generate="all"/> > <provide partnerLink="client"> > <service name="helloWorld:HelloWorldProcessService" > port="HelloWorldProcessPort"/> > </provide> > <cleanup on="always" /> > *<property>abcd1234</property> * > </process> > </deploy> > > While deploying the process it gives the following stack. > > ERROR - GeronimoLog.error(108) | Error persisting deployment record for { > http://helloWorld}HelloWorldNew-1; process will not be available after > restart! > java.lang.NullPointerException > at > > org.apache.ode.store.jpa.ProcessConfDaoImpl.setProperty(ProcessConfDaoImpl.java:134) > at > org.apache.ode.store.ProcessStoreImpl$2.call(ProcessStoreImpl.java:281) > at > org.apache.ode.store.ProcessStoreImpl$2.call(ProcessStoreImpl.java:255) > at > > org.apache.ode.store.ProcessStoreImpl$Callable.call(ProcessStoreImpl.java:719) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at > > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) > at > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) > at java.lang.Thread.run(Thread.java:619) > DEBUG - GeronimoLog.debug(66) | Process store event: > {ProcessStoreEvent#DEPLOYED:{http://helloWorld}HelloWorldNew-1} > DEBUG - GeronimoLog.debug(66) | Ignoring store event: > {ProcessStoreEvent#DEPLOYED:{http://helloWorld}HelloWorldNew-1}......... > > But after restarting the ODE, the same process is still there. Is this a > bug.? > Or as the deploy.xml is erroneous, why the deploy.xml is not discarded at > the deployment time? > > Best Regards, > Denis Weerasiri. >
