[jira] Commented: (ODE-773) I wish ODE would clean up processes by default

["David McLure (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ODE-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841364#action_12841364 ] 

David McLure commented on ODE-773:
----------------------------------

Hi Tammo,

Sorry for the rant - but aside from that distraction, I really did intend to add a wish list item here - that being to have BPEL processes clean themselves up by default.  The whole reason that I am attempting to build and debug ODE is to try and figure out why processes currently do not cleanup as they should - so while this rant was a bit of a distraction from main point of the Jira, I believe that the Jira still does have merit.

I will admit however, that the Jira might actually belong in a category other than "Deployment", but none of the other categories really seemed to hit the spot either.

In any case, I have since joined the dev mailinglist where I will continue ranting.  :-)

David McLure

p.s.  Part of the reason for my ranting is also because the buildr build process is currently not working.  I have posted details on my findings as a comment to ODE-755.

> I wish ODE would clean up processes by default
> ----------------------------------------------
>
>                 Key: ODE-773
>                 URL: https://issues.apache.org/jira/browse/ODE-773
>             Project: ODE
>          Issue Type: Wish
>          Components: Deployment
>    Affects Versions: 2.0-beta2
>         Environment: Running ODE as a war in Tomcat (tcserver), on Windows XP, Eclipse 3.5 (STS 2.3.0), Java 1.5.0_15-b04, jruby 1.4.0 (ruby 1.8.7 patchlevel 174)
>            Reporter: David McLure
>
> I am trying to figure out how best to clean-up old BPEL processes on the ODE server (ODE v2.0 Beta2).
> Not having had much luck using either the instance data cleanup (http://ode.apache.org/user-guide.html#UserGuide-InstanceDataCleanup), or the hydration (http://ode.apache.org/user-guide.html#UserGuide-ControllingODEMemoryFootprint) features, I set about trying to debug ODE to see how to enable some of these features.
> Warning: ramble alert!  After a crash course in Ruby (and settling on JRuby since Ruby sucks on Windows) I eventually managed to "successfully" build all 25 ODE projects using jruby and import them into Eclipse for debugging.  I am now realizing however that the jsp files appear to be missing from the axis2-war project.  Assuming I can locate these missing jsp files, then properly configuring the axis2-war in order to be able to deploy and run in the eclipse debugger also seems to be fairly involved.  I am assuming that I may also be missing some axis2 config artifacts as well, since I currently need to manually create lib, conf, and repository folders in order to enable Axis2 project facets for the axis2-war project to satisfy the Axis2 runtime location requirements.  There are also some build Java Build Path issues in the axis2-war project "Cannot nest output folder 'ode-axis2-war/target/test/classes' inside 'ode-axis2-war/target/test'"  - to summarize, it turns out that debugging ODE is proving to be a little more involved than I first thought!  I may also need to enter Jiras around some of these problems - not sure at this point?
> I am wondering - for those developing ODE, what sort of IDE are you using?  I picked the latest version of STS (SpringSource Tool Suite 3.2.0) thinking it might have the best starting point in terms of base Eclipse plugins and so on.
> Anyway, now I have managed to become completely distracted from my original mission (i.e. to get process cleanup working).  I guess this entire adventure has left me wishing for a simple way to have BPEL processes clean up after themselves by default.
> Thanks for developing this product (and for listening to this rant!  :-)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.