On Fri, Feb 20, 2009 at 7:27 PM, Matthieu Riou matthieu.r...@gmail.comwrote:
On Fri, Feb 20, 2009 at 3:48 PM, Assaf Arkin ar...@intalio.com wrote:
On Fri, Feb 20, 2009 at 2:24 PM, Matthieu Riou
matthieu.r...@gmail.comwrote:
On Fri, Feb 20, 2009 at 2:08 PM, Assaf Arkin ar...@intalio.com
, Feb 19, 2009 at 10:31 PM, Ciaran ciar...@gmail.com wrote:
On Thu, Feb 19, 2009 at 4:54 PM, Assaf Arkin ar...@intalio.com
wrote:
On Thu, Feb 19, 2009 at 8:43 AM, Alex Boisvert boisv...@intalio.com
wrote:
The confusion comes from the fact that we pseudo-released 1.3
On Feb 20, 2009, at 1:09 PM, Matthieu Riou matthieu.r...@gmail.com
wrote:
On Fri, Feb 20, 2009 at 10:05 AM, Assaf Arkin ar...@intalio.com
wrote:
On Thu, Feb 19, 2009 at 10:44 AM, Matthieu Riou matthieu.r...@gmail.com
wrote:
On Thu, Feb 19, 2009 at 10:20 AM, Milinda Pathirage
On Fri, Feb 20, 2009 at 2:24 PM, Matthieu Riou matthieu.r...@gmail.comwrote:
On Fri, Feb 20, 2009 at 2:08 PM, Assaf Arkin ar...@intalio.com wrote:
In my scenario there's an RC, a separate entity from the final release.
And it may have passed through the release process and voted
On Mon, Oct 13, 2008 at 7:56 PM, Matthieu Riou [EMAIL PROTECTED] wrote:
Hey guys,
Jukka Zitting has created a read-only (yeah, I know) semi official (or semi
unofficial, depending on your inclinations) mirror of our repo:
http://jukka.zitting.name/git/
git://jukka.zitting.name/ode.git
It
On Thu, Oct 9, 2008 at 1:39 PM, Alexis Midon [EMAIL PROTECTED] wrote:
Hi all,
I really feel more and more constrained by JUnit these days. The only fancy
things we get are setUp and tearDown. thrilling...
In the other corner of the ring is TestNG. TestNG comes with many nice
things like
On Tue, Sep 30, 2008 at 4:18 PM, Karthick Sankarachary
[EMAIL PROTECTED] wrote:
d) Is there a reason why we can't propagate the transaction context in
one-way invokes?
Because we're treating two-way as synchronous and one-way as
asynchronous (different from request with empty
On Mon, Sep 29, 2008 at 2:33 PM, Karthick Sankarachary
[EMAIL PROTECTED] wrote:
Just a few quick observations on the atomic
scopeshttp://ode.apache.org/atomic-scopes-extension-for-bpel.html
spec:
a) The state of a scope consists of not just its variables but also its
correlation sets. So,
On Mon, Sep 29, 2008 at 3:46 PM, Karthick Sankarachary
[EMAIL PROTECTED] wrote:
b) The spec doesn't say how atomic scopes should be retried in the case
of
faults.
By repeating the activity.
Does that mean that we have to redefine the ext:retryFor and
ext:retryDelay options for the
[
https://issues.apache.org/jira/browse/ODE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12633995#action_12633995
]
Assaf Arkin commented on ODE-377:
-
+1
Better attribute value would be one | all; any means
On Tue, Sep 2, 2008 at 12:41 PM, Tammo van Lessen [EMAIL PROTECTED] wrote:
Hi guys,
we've been struggling lately with buildr and particularly in conjunction
with Ode's build.
I'm not sure whether this belongs more to [EMAIL PROTECTED] or [EMAIL
PROTECTED], but as
the communities are quite
[
https://issues.apache.org/jira/browse/ODE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12622694#action_12622694
]
Assaf Arkin commented on ODE-364:
-
While there are many ways to register subscriptions, we
[
https://issues.apache.org/jira/browse/ODE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12622719#action_12622719
]
Assaf Arkin commented on ODE-364:
-
Having said that, there might be a use-case where
[
https://issues.apache.org/jira/browse/ODE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12622812#action_12622812
]
Assaf Arkin commented on ODE-364:
-
Thumb up for enableSharing. I like that name.
Publishing
[
https://issues.apache.org/jira/browse/ODE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12615710#action_12615710
]
Assaf Arkin commented on ODE-344:
-
Mixed content is the root of all unexplained bugs
, instead of detecting and
failing because foo is not a simple type.
Assaf
On Tue, Jul 22, 2008 at 11:21 AM, Assaf Arkin (JIRA) [EMAIL PROTECTED]
wrote:
[
https://issues.apache.org/jira/browse/ODE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId
On Mon, Jul 14, 2008 at 1:54 AM, Tammo van Lessen [EMAIL PROTECTED]
wrote:
Assaf Arkin wrote:
On Sun, Jul 13, 2008 at 3:52 AM, Tammo van Lessen [EMAIL PROTECTED]
wrote:
+1 for both approaches. I think in the medium-term we need an
authorization model for management purposes, so we could
On Sun, Jul 13, 2008 at 12:04 AM, Thilina Gunarathne [EMAIL PROTECTED]
wrote:
IIRC we can already retrieve the wsdl using ?wsdl.. Not sure whether we
can
retrieve the bpel doc using ?bpel... But ?bpel would be a cool nice to have
feature.
There is indeed a ?wsdl convention that allows you
into a limited set of URLs.
Management tools should access the WSDL/BPEL from their API, which is access
controlled. Other tools should access the public metadata, which is stripped
down to that which is publicly viewable.
Assaf
Cheers,
Tammo
On Sun, Jul 13, 2008 at 09:54, Assaf Arkin [EMAIL
+1
On Jun 27, 2008, at 3:18 PM, Matthieu Riou [EMAIL PROTECTED]
wrote:
Hi,
I've finally cut the 1.2 final release of ODE. The source and binary
distributions are here:
http://people.apache.org/~mriou/ode-1.2/org/apache/ode/apache-ode-war/1.2/apache-ode-war-1.2.zip
For anyone who wants to try out Git, here's a couple of good
resources. The first is a cheat sheet, I keep that one handy:
http://ktown.kde.org/~zrusin/git/git-cheat-sheet-medium.png
The second is a presentation (PDF document) given out by Scott Chacon
at RailsConf 2008. No Rails knowledge
Or we can include the task in ODE's rakelib.
Assaf
On Jun 10, 2008, at 2:07 PM, Matthieu Riou [EMAIL PROTECTED]
wrote:
Hi guys,
I've update our Rakefile to use Buildr 1.3.1.1 and it seems to work
now.
However there are a few gotchas. The first is that there's a bug in
the
XmlBeans
On Wed, May 21, 2008 at 9:52 PM, Paul Fremantle [EMAIL PROTECTED] wrote:
Folks
Take a look at relax-ws:
http://code.google.com/p/relax-ws/
I'm seeing heavy usage of sane defaults and common sense conventions.
Want!
Assaf
Paul
On Thu, May 22, 2008 at 2:55 AM, Sanjiva Weerawarana
precisely what he was trying to avoid with the last sentence of his post!
Thanks!
Assaf
Cheers,
Zubin.
On 5/19/08, Sanjiva Weerawarana [EMAIL PROTECTED] wrote:
Assaf Arkin wrote:
Besides the management console, we have three other ongoing projects in
Ode.
One adds HTTP binding
On Mon, May 19, 2008 at 10:14 AM, Sanjiva Weerawarana [EMAIL PROTECTED]
wrote:
Assaf Arkin wrote:
Besides the management console, we have three other ongoing projects in
Ode.
One adds HTTP binding and REST support to the engine, so you can use Ode
to
interact with and develop services
On Wed, May 14, 2008 at 2:43 AM, Tammo van Lessen [EMAIL PROTECTED]
wrote:
Assaf Arkin wrote:
Forget about that, PUT and DELETE seems to be supported by
XMLHttpRequests...
PUT, DELETE not supported on Safari, and on some browsers may not do the
right thing (you don't want to get a cached
in reading JSON?
Most people would prefer a nicely styled HTML page, so now that JSON has to
be converted into HTML on the client-side. Or you could just send HTML
directly from the server (for the buzzword inclined, it's called AJAH).
Assaf
Matthieu
On Tue, May 13, 2008 at 11:33 AM, Assaf Arkin
On Tue, May 13, 2008 at 2:41 PM, Tammo van Lessen [EMAIL PROTECTED]
wrote:
On Tue, May 13, 2008 at 11:19 PM, Tammo van Lessen [EMAIL PROTECTED]
wrote:
On
the detail level there may be some pitfalls as browsers don't support PUT
and DELETE, so there is some JS needed to emulate these verbs
On Tue, May 13, 2008 at 2:19 PM, Tammo van Lessen [EMAIL PROTECTED]
wrote:
Assaf Arkin wrote:
And for the XML allergic (count me in) I Abdera has a JSON
representation as well.
Then for the view, I'm sure there are some JS Atom readers that would
also
help a lot (I know JFeed for JQuery
On Tue, May 13, 2008 at 2:53 PM, Tammo van Lessen [EMAIL PROTECTED]
wrote:
Assaf Arkin wrote:
On Tue, May 13, 2008 at 2:41 PM, Tammo van Lessen [EMAIL PROTECTED]
wrote:
On Tue, May 13, 2008 at 11:19 PM, Tammo van Lessen [EMAIL PROTECTED]
wrote:
On
the detail level there may be some
On Mon, Apr 7, 2008 at 10:43 AM, Alexis Midon [EMAIL PROTECTED] wrote:
Regarding #2 and #3: The special exception I mentioned was supposed to be
a
solution for #2. My idea was to add a checked exception that indicates
that
Ode shall rollback the transaction and should throw a BPEL fault
That's strange, your package manager should allow you to override rake with
gem install rake, which I recommend since we're already moving to Rake 0.8.
Try this:
sudo gem update --system
sudo gem install buildr
Assaf
On 2/4/08, Sebastian Breier [EMAIL PROTECTED]
wrote:
I get command not
+1
Assaf
On 1/11/08, Matthieu Riou [EMAIL PROTECTED] wrote:
Hi guys,
Following up on our discussion about a final release and the release
process, this is a call to vote on the release of ODE 1.1.1. No major bugs
have been discovered in RC1 and only very few changes have been made since
On 1/9/08, Matthieu Riou [EMAIL PROTECTED] wrote:
There have been a few discussions on the legal-discuss mailing list about
the release process and building Release Candidates that are just rebuilt
to
make a final version when everybody is okay is more and more frowned upon
for diverse
On 12/19/07, Matthieu Riou [EMAIL PROTECTED] wrote:
Here c, v, ca and va are actually aliases to the original path. I'd also
propose (optional) that a non-existent path used in *with* gets created if
it doesn't exist when a *with* relies on it. So in my previous example if
On 12/19/07, Matthieu Riou [EMAIL PROTECTED] wrote:
On Dec 19, 2007 11:45 AM, Assaf Arkin [EMAIL PROTECTED] wrote:
On 12/19/07, Matthieu Riou [EMAIL PROTECTED] wrote:
Here c, v, ca and va are actually aliases to the original path. I'd
also
propose (optional) that a non-existent path
Basically a partnerLinkType is an abstraction that names two related
portTypes, so you can then define two partnerLinks the represent each view (
i.e. roles reversed), and given two process definition somehow deduct (and
often be right) that they're related because they share a common
On 11/22/07, Tammo van Lessen [EMAIL PROTECTED] wrote:
On 21/11/2007, Assaf Arkin [EMAIL PROTECTED] wrote:
On 11/21/07, Tammo van Lessen [EMAIL PROTECTED] wrote:
o Links: Great idea. Shouldn't the join method support more than one
link? I'd just drop the link parameter and would allow
On 11/21/07, Tammo van Lessen [EMAIL PROTECTED] wrote:
Hi all,
So any opinion on both proposals? What are the parts that you like better?
Tammo, did you have a look at AAM?
I finally got the time to look at your simbpel proposal. Sorry for the
delay...
Great work! And interestingly
On 11/20/07, Matthieu Riou [EMAIL PROTECTED] wrote:
Hi guys,
Our 1.1 release has proven to be useful to a lot of (hopfeully) happy users
but since then we've fixed quite a few bugs and have done some nice
improvements. So what about cutting a new release in the short to middle
term? Has
On 9/17/07, Matthieu Riou [EMAIL PROTECTED] wrote:
Hi,
We've taken on the bad habit of fixing stuff without necessarily creating
a
Jira task for it. On one side it removes some bureaucracy but on the other
it makes it almost impossible to assemble accurate release notes when we
make
On 9/11/07, Alex Boisvert [EMAIL PROTECTED] wrote:
On 9/10/07, Noel J. Bergman [EMAIL PROTECTED] wrote:
Assaf Arkin wrote:
Alex Boisvert wrote:
I would also suggest using the standardized NIST RBAC terminology
(user,
role, permission) because it's most widely used and more
On 9/9/07, Alex Boisvert [EMAIL PROTECTED] wrote:
On 9/9/07, Assaf Arkin [EMAIL PROTECTED] wrote:
I think it should be principal or role on receive, principal on invoke.
Asserting that a user belongs to a role on receive is something that
authorization system should deal with, no need
On 9/10/07, Alex Boisvert [EMAIL PROTECTED] wrote:
On 9/10/07, Assaf Arkin [EMAIL PROTECTED] wrote:
On 9/10/07, Alex Boisvert [EMAIL PROTECTED] wrote:
That's not the point. You may still want to have only JohnDoe or any
HR
personnel invoke a specific operation, irrespective
In a scope you can define a principal:
principal name=NCName
The scope semantics are similar to variables, partner links and
correlations.
To invoke/receive activity we add a principal attribute that can reference a
principal. On recieve, assigning from inbound message to the principal, and
on
On 9/10/07, Alex Boisvert [EMAIL PROTECTED] wrote:
On 9/10/07, Assaf Arkin [EMAIL PROTECTED] wrote:
To invoke/receive activity we add a principal attribute that can
reference
a
principal. On recieve, assigning from inbound message to the principal,
and
on invoke assigning from
On 9/9/07, Tammo van Lessen [EMAIL PROTECTED] wrote:
2007/9/7, Assaf Arkin [EMAIL PROTECTED]:
Well, it is a header that's only applicable to some protocol, so it's no
longer utilizing the WSDL protocol abstraction, it fixes the abstract
message usage to the actual protocol bindings
On 9/9/07, Tammo van Lessen [EMAIL PROTECTED] wrote:
partnerLink roles are strictly invoker or invokee. whether you're admin
or
johndoe, you are still going to interact through a limited set of
operations
available on the interface (portType), and the partnerLink role tells
you
which
that a user belongs to a role on invoke is pointless, the receiver
should never trust your assertion and should make up their own determination
upon receiving the message.
Assaf
alex
On 9/9/07, Tammo van Lessen [EMAIL PROTECTED] wrote:
2007/9/10, Assaf Arkin [EMAIL PROTECTED]:
On 9/9/07
On 9/7/07, Dan Kearns [EMAIL PROTECTED] wrote:
2007/9/6, Alex Boisvert [EMAIL PROTECTED]:
I've just added experimental support for HTTP authentication in the
1.1branch
On 9/6/07, Tammo van Lessen [EMAIL PROTECTED] wrote:
Yes, I agree. Introducing an extra message part for credentials
On 9/5/07, Paul Brown [EMAIL PROTECTED] wrote:
Let me try to put a finer point on what Maciej's saying. Part of the
infrastructure that the engine maintains is the set of correlation
keys, and there is some magic to do pre-computation of keys for
processes. This facility puts a lot of
51 matches
Mail list logo