See http://hudson.zones.apache.org/hudson/job/ODE-trunk/32/changes
See http://hudson.zones.apache.org/hudson/job/ODE-trunk-jdk6/20/changes
On Thu, Oct 16, 2008 at 1:34 PM, Tammo van Lessen <[EMAIL PROTECTED]>wrote:
> Hi guys,
>
> please join me to welcome Hudson. It took him a while to build his voice
> but this time I could understand him quote clearly.
>
Yeah, he finally knocked the door, I let him in :)
>
> We will all learn to
Hi guys,
please join me to welcome Hudson. It took him a while to build his voice
but this time I could understand him quote clearly.
We will all learn to hate him ;)
Cheers,
Tammo
Apache Hudson Server wrote:
> See http://hudson.zones.apache.org/hudson/job/ODE-trunk-jdk6/19/changes
>
>
See http://hudson.zones.apache.org/hudson/job/ODE-trunk-jdk6/19/changes
Agreed.
If we can find a way to pass in whatever authenticated principal was used in
the call chain, then it should be tied to the deployer's name. This was
the intent from the beginning.
(I think the IP address is a weak form of authentication/audit information
but I guess it's better than not
Thanks for you help.
Milinda.
On Thu, Oct 16, 2008 at 8:36 PM, Matthieu Riou <[EMAIL PROTECTED]>wrote:
> On Thu, Oct 16, 2008 at 5:07 AM, Tammo van Lessen <[EMAIL PROTECTED]
> >wrote:
>
> > Hi Milinda,
> >
> > at the time when ODE was still PXE, there was support for debugging with
> > breakpoin
On Thu, Oct 16, 2008 at 5:07 AM, Tammo van Lessen <[EMAIL PROTECTED]>wrote:
> Hi Milinda,
>
> at the time when ODE was still PXE, there was support for debugging with
> breakpoints. It was integrated with Sun's netbeans and worked quite
> well. I'm not sure which parts of this survived the incubat
Hi Alexis,
thanks for changing the test port. I just changed the CI configuration
to run the HTTP tests, too. Unfortunately there are several errors and
the execution of the tests seem to stuck.
I don't really understand what's going wrong there :( Do you?
Here is the transcript:
http://hudson.z
[
https://issues.apache.org/jira/browse/ODE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640164#action_12640164
]
Tammo van Lessen commented on ODE-389:
--
Ah, I got it, thanks for the clarification.
> Su
[
https://issues.apache.org/jira/browse/ODE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Spurk updated ODE-389:
Attachment: CoreWS.wsdl
the auto-generated file which can be found after deployment of the testcase at
[
https://issues.apache.org/jira/browse/ODE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640150#action_12640150
]
Christian Spurk commented on ODE-389:
-
@Tammo, thanks for looking into this!
Maybe I was
[
https://issues.apache.org/jira/browse/ODE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640149#action_12640149
]
Tammo van Lessen commented on ODE-389:
--
I can't find any issue with the testcase.
The onl
Hi Milinda,
at the time when ODE was still PXE, there was support for debugging with
breakpoints. It was integrated with Sun's netbeans and worked quite
well. I'm not sure which parts of this survived the incubation but at
least some relics are still there:
engine/src/main/java/org/apache/ode/bpe
I'm not ODE developer, but as far as I know, ODE hasn't got such
functionality.
One workaround I know, is to implement own event listener to log events
and use deprecated EventContext class to obtain variables. But this
class is deprecated, because it simply doesn't work especially for in
memory p
Hi,
Do ODE has debugging API for BPEL processes which we can use to set break
point remotely and get the present status of the running instances we are
interested. I saw that there are some support in BPEL compiler which will
include line numbers like information in compiled BPEL and from the Insta
[
https://issues.apache.org/jira/browse/ODE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Spurk updated ODE-389:
Attachment: testcase.zip
testcase for this issue
> Successfully Deployed BPEL Artifact Has an Invalid
Successfully Deployed BPEL Artifact Has an Invalid WSDL with an Undefined
Namespace Prefix ("null")
---
Key: ODE-389
URL: https://issues.apache.org/jira/browse/ODE-389
18 matches
Mail list logo
