Ah that's great. We use docker container for our builds.

On Aug 13, 2017 21:10, "Samuel Rose" <samuel.r...@gmail.com> wrote:

> FWIW I agree with the statement at
> https://stackoverflow.com/questions/45096685/getting-
> http-error-500-while-running-bpel-project-in-eclipse-with-
> apache-ode/45116731#45116731
>
> "I personally don't usually go with eclipse based deployments for ODE.
> It's always better to do it the manual way."
>
> So what I do for local development is still writing code in an IDE
> like eclipse, but then I script it's build/deploy to a virtualbox
> machine via tools like Fabric and/or ansible
>
> I use ansible to build ODE, install all packages in the OS, database,
> etc, and I use fabric to deploy the developed services to
> tomcat/webapps/ode/WEB-INF/processes once service is deployed, then I
> have another script to run tests
>
> I have personally found https://github.com/zatosource/zato-apitest to
> be great for automated testing of SOAP services. Plus, in my case I
> was typically integrating ODE with https://zato.io/
>
> On Sun, Aug 13, 2017 at 8:43 AM, Sathwik B P <sathwik...@gmail.com> wrote:
> > To step over the code by adding breakpoints, follow the usual way of
> > running tomcat with jpda and use remote attach in eclipse.
> > regards,
> > sathwik
> >
> > On Aug 13, 2017 17:32, "Sathwik B P" <sathwik...@gmail.com> wrote:
> >
> >> To get deep insight into the execution of ODE, enable DEBUG/TRACE level
> on
> >> org.apache.ode category in the log file.
> >>
> >> 1 - https://github.com/apache/ode/blob/ode-1.3.x/bpel-runtime/
> >> src/main/java/org/apache/ode/bpel/runtime/SWITCH.java
> >> 2 - Build involves auto generation of java source and hence direct
> project
> >> compilation in eclipse cannot be done. Running test cases during the
> build
> >> is the ideal way that most of us follow.
> >>
> >> If you are want to deploy ODE war within eclipse, you can follow this
> >> thread.
> >> https://stackoverflow.com/questions/45096685/getting-
> >> http-error-500-while-running-bpel-project-in-eclipse-with-
> >> apache-ode/45116731#45116731
> >>
> >> regards,
> >> sathwik
> >>
> >> On Sun, Aug 13, 2017 at 5:39 AM, Samuel Rose <samuel.r...@gmail.com>
> >> wrote:
> >>
> >>> On Sat, Aug 12, 2017 at 6:38 PM Muhammad Adeel Zahid <
> >>> 16030...@lums.edu.pk>
> >>> wrote:
> >>>
> >>> > Hi,
> >>> >
> >>> > I have been able to sucessfully compile apache ode 1.3.5 from the
> >>> sources
> >>> > using the wonderful support provided by @Satwik. Now my next task is
> to
> >>> > make some changes in the source code and then recompile the it. I am
> >>> able
> >>> > to create eclipse projects from the source code using "buildr
> eclipse"
> >>> > command and open the projects using eclipse. I have two questions
> >>> regarding
> >>> > the changes I want to make in the source code
> >>> >
> >>> >
> >>> > 1- The main change I want to make is to print the IF activities in
> the
> >>> > logs. By default, all service invocations are logged in the log files
> >>> but
> >>> > there are no logs for the IF activities. Mainly, I want to emit, the
> >>> name
> >>> > of the IF activity, the conditional expression and its result (true
> or
> >>> > false). What project, files would I need to change?
> >>> >
> >>> >
> >>> > 2- Is it possible to compile and deploy ODE from within the eclipse?
> >>> > Currently, I have to make changes in the sources from within eclipse
> >>> then
> >>> > compile it from buildr and then deploy the compiled project back in
> >>> > eclipse. This way I have to do a lot of work for testing a simple
> print
> >>> > statement. Is there an easy way of testing changes? What pattern ODE
> >>> team
> >>> > follows for development?
> >>> >
> >>> >
> >>> > Regards
> >>> >
> >>> > Adeel
> >>> >
> >>>
> >>
> >>
>

Reply via email to