[jira] Created: (ODE-398) SoapHeaderTest fails when Rampart is engaged

SoapHeaderTest fails when Rampart is engaged Key: ODE-398 URL: https://issues.apache.org/jira/browse/ODE-398 Project: ODE Issue Type: Bug Components: Axis2 Integration Report

[jira] Updated: (ODE-397) log4j configuration loaded from rampart-core.jar

[ https://issues.apache.org/jira/browse/ODE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexis Midon updated ODE-397: - Description: rampart-core is shipped with its log4j.properties file. When executing buildr, this file is pi

[jira] Created: (ODE-397) log4j configuration loaded from rampart-core.jar

log4j configuration loaded from rampart-core.jar Key: ODE-397 URL: https://issues.apache.org/jira/browse/ODE-397 Project: ODE Issue Type: Bug Components: Axis2 Integration

[jira] Closed: (ODE-393) do not load Rampart in the axis2.xml

[ https://issues.apache.org/jira/browse/ODE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexis Midon closed ODE-393. Resolution: Fixed > do not load Rampart in the axis2.xml > > >

[jira] Commented: (ODE-393) do not load Rampart in the axis2.xml

[ https://issues.apache.org/jira/browse/ODE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641208#action_12641208 ] Alexis Midon commented on ODE-393: -- fixed in r706455 Using the name/targetNamespace attribut

[jira] Updated: (ODE-393) do not load Rampart in the axis2.xml

[ https://issues.apache.org/jira/browse/ODE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexis Midon updated ODE-393: - Comment: was deleted > do not load Rampart in the axis2.xml > > >

[jira] Created: (ODE-396) Atomic Scopes And Processes

Atomic Scopes And Processes --- Key: ODE-396 URL: https://issues.apache.org/jira/browse/ODE-396 Project: ODE Issue Type: New Feature Components: Axis2 Integration, BPEL Compilation/Parsing, BPEL Runtime, JB

Re: Students work - extending ode

Thank you guys for response! My first step is to write course work with title "Extension possibilities of BPMS system Apache Ode". This will be mainly research in Ode architecture. Later once this finished and I will see that I can manage to add some extension, I will continue this work fo

RE: Library usage in ODE

Hi Matthieu, thank you for your fast response. I looked into the older IP cases. The jaxen lib was rejected because of pedigree issues. In this case they where not able to document that all comitters are getting through a process stating that they make their contributions below BSD before ge

RE: Memory consumption of In-memory processes

> That would be perfect. I can comment on it if I see any problem and we > can increment on that. There it is: https://issues.apache.org/jira/browse/ODE-395 Thanks, Juergen

[jira] Updated: (ODE-395) MessageExchangeDAOs of in-memory processes are kept in memory despite release()

[ https://issues.apache.org/jira/browse/ODE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jürgen Schumacher updated ODE-395: -- Attachment: inmemory-mexdao-release.patch Extends BpelDAOConnection with a releaseMessageExchange(

[jira] Created: (ODE-395) MessageExchangeDAOs of in-memory processes are kept in memory despite release()

MessageExchangeDAOs of in-memory processes are kept in memory despite release() --- Key: ODE-395 URL: https://issues.apache.org/jira/browse/ODE-395 Project: ODE Issu

Re: Library usage in ODE

Hi Georg, I'm surprised that Jaxen didn't meet your IP requirements, it's MIT licensed which is fairly liberal. We could even relicense it under ASL 2.0 if we wanted to. It's hard to remove the dependency toward both Jaxen and Saxon: the former is provided to support XPath 1.0 and the latter XPat

Library usage in ODE

Hi, currently we try to use the ODE BPEL engine within our SMILA project to process annotation pipelines. Due to our IP process at Eclipse we must declare some libraries as external references, because they did not meet IP requirements set by the foundation. These libraries are: * jax

Re: Students work - extending ode

I would also consider working on improving our WS-BPEL 2.0 support, there are a few interesting things that we don't do yet: http://ode.apache.org/ws-bpel-20-specification-compliance.html Things like inlined variable initialization, fromPart and toPart in invoke and receive or being able to send/

Re: Memory consumption of In-memory processes

On Mon, Oct 20, 2008 at 6:44 AM, <[EMAIL PROTECTED]> wrote: > Hello, > > We have experienced a high memory consumption by ODE in scenarios where > in-memory processes are invoked with a relatively high frequency. This is > caused by the org.apache.ode.bpel.memdao.BpelDAOConnectionImpl which keeps

Memory consumption of In-memory processes

Hello, We have experienced a high memory consumption by ODE in scenarios where in-memory processes are invoked with a relatively high frequency. This is caused by the org.apache.ode.bpel.memdao.BpelDAOConnectionImpl which keeps the created instances of MessageExchangeDAOImpl in memory until the

Re: Students work - extending ode

Madars, thanks for your interest in Ode and especially for your interest in extending it. Regarding the WS-* specifications, ODE is mainly reusing the functionality provided by axis2. Therefore most of the standards below come with Ode out-of-the-box, however there might be some interesting tasks