> FYI there are several issues that are currently affecting us, in order of > least important first > i) The shipped eclipse .classpath files refer to invalid project names ( > can get a patch for this easily enough ) > ii) The default .war file thats created doesn't have an empty 'processes' > folder in the WEB-INF folder so when it first de-compresses it > refuses to start and we have to shut it down and manually create the folder > ( again can patch this for you) > iii) When it does start up it complains about a missing table in the DB > (ODE_SCHEMA_VERSION iirc) > iv) The WSDL exposed by the deployment services appears not to be > validating in any tool ( can get a patch for this, we raised this previously > as https://issues.apache.org/jira/browse/ODE-399 , but it still seems > wrong on our side, perhaps we're not understanding this!) > v) Rapid Deployments + Un-deployments appear to cause issues where folders > remain on the disk (deepDelete fails, similar to ' > https://issues.apache.org/jira/browse/ODE-482' but this seems to be > affecting the .cbp file and the .wsdl . I *think* can see where the .cbp is > left open, around the processconf object getCBPInputStream, but I"m not sure > As a follow up to this posting in case anyone is following, we've fixed and provided patches for issues ii, iv and v (ODE-522, ODE-517 and ODE-521 respectively). Issue i was a local issue with an old eclipse install (my bad), and we're not too worried by issue iii as it only seems to be a warning (although it seems strange to continuously warn on every statup?)
Hope this helps, cheery-bye:) - Cj
