On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Pete Robbins wrote:
Our current method of packaging and loading an extension is fairly
simple:
we load all schema
On 30/11/06, Simon Laws [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Pete Robbins wrote:
Our current method of packaging and
On 11/29/06, Jeremy Boynes [EMAIL PROTECTED] wrote:
On Nov 29, 2006, at 4:00 AM, ant elder wrote:
Looks like that answers all the questions and sounds convincing to
me. We
discussed doing this the other day and agreed it needed doing and
based on
that Simon went ahead and did the work for
On 30/11/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Simon Laws [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Simon Laws [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Pete Robbins [EMAIL PROTECTED] wrote:
On
On 30/11/06, Simon Laws [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Simon Laws [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Pete
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Simon Laws [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Simon Laws [EMAIL PROTECTED] wrote:
On 11/30/06, Pete
snip
I would package the cpp language extension as
cpp/
bin/
lib/
include/
xsd/
extension/
The bin, lib, include are exactly what you would expect from a package that
you might want to build against. The extension/ folder would hold the
library that implements the
On 30/11/06, Andrew Borley [EMAIL PROTECTED] wrote:
snip
I would package the cpp language extension as
cpp/
bin/
lib/
include/
xsd/
extension/
The bin, lib, include are exactly what you would expect from a package
that
you might want to build against. The
On 30/11/06, Andrew Borley [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Simon Laws [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06,
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Andrew Borley [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Simon Laws [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Pete
On 30/11/06, Simon Laws [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Andrew Borley [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Simon Laws [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Simon Laws [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Andrew Borley [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Simon Laws
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Simon Laws [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Andrew Borley [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Simon Laws
It's a good time to take stock of where we are and where we want to go with
SDO for Java. Clearly there's work to be done with heading towards an
implementation of the SDO Java 2.1 spec [1,2,3], but what else might we
do; where do you want to take things?
[1] the new 2.1 spec
Folks,
Can't you just use maven's exclusion mechanism:
http://maven.apache.org/ref/2.0.4/maven-model/maven.html#class_exclusion
to exclude the specific version of axiom and add a specific dependency
on the new one?
thanks,
dims
On 11/29/06, Davanum Srinivas [EMAIL PROTECTED] wrote:
Aha! so
I've tried out the suggested fixes and I have run into a big problem.
By proxying the inbound wire of the composite reference, there is no
databinding interceptor in the invocation chain. This causes
Axis2TargetInvoker to choke.
Exception java.lang.IllegalArgumentException Exception message:
OK, I can set any attribute ; )
You got an exception? I'm getting no exception here, the new item is just
not being updated in the database.
Adriano Crestani
On 11/30/06, Kevin Williams [EMAIL PROTECTED] wrote:
Hello Adriano,
No. It should not be working this way and thanks for finding
It is strange that you do not see an exception since the generated
INSERT statement is not valid.
Everything should work fine if you use the work-around and set any
attribute to some value.
Thanks.
--
Kevin
Adriano Crestani wrote:
OK, I can set any attribute ; )
You got an exception? I'm
Hmm, not sure what's going on. I don't get the failure. It
almost sounds like the container is not getting the remove
call from the target invoker, which could happen if the
target invoker did not see a sequence end in the message,
which in turn could happen if the end interceptor were not
there
[ http://issues.apache.org/jira/browse/TUSCANY-885?page=all ]
Kelvin Goodson resolved TUSCANY-885.
Resolution: Fixed
fixed in 478825
Property DataObject.getProperty(String propertyName) should return null if
the property cannot be found
[ http://issues.apache.org/jira/browse/TUSCANY-932?page=all ]
Kelvin Goodson resolved TUSCANY-932.
Resolution: Fixed
fixed in 478825
Invoking DataObject.isSet(String path) with invalid path would result in NPE
On 29/11/06, Pete Robbins [EMAIL PROTECTED] wrote:
This was introduced when opentype support was added. Is it needed? Don't
know. What do you expect to be returned when you try to get the type of
entry??
I've considered your question, and I can't see a valid alternative. I don't
intend to
NPE generated during a property set of a static SDO
---
Key: TUSCANY-958
URL: http://issues.apache.org/jira/browse/TUSCANY-958
Project: Tuscany
Issue Type: Bug
Components: Java SDO
This I think highlights a problem with the spec around using
CurrentCompositeContext from unmamanged code in general...a locate
service only returns half of an invocation chain since the source
is not a component and is unmamanged code. Can you describe you
client code, is it a JSP or is
On 30/11/06, Caroline Maynard [EMAIL PROTECTED] wrote:
On 29/11/06, Pete Robbins [EMAIL PROTECTED] wrote:
This was introduced when opentype support was added. Is it needed? Don't
know. What do you expect to be returned when you try to get the type of
entry??
I've considered your
[
http://issues.apache.org/jira/browse/TUSCANY-578?page=comments#action_12454700
]
Kelvin Goodson commented on TUSCANY-578:
Transferring in TUSCANY-951
here's the report
==
Calling set() with an invalid property
I've been playing with the BigBank sample and have added a fault to the
AccountService's withdraw operation. After changing the
AccountService.wsdl (attached), the Tuscany WSDL2Java no longer works.
(Exception from the build is below.)
When I took a quick look at the code, it seemed that the
On 11/30/06, Jim Marino [EMAIL PROTECTED] wrote:
This I think highlights a problem with the spec around using
CurrentCompositeContext from unmamanged code in general...a locate
service only returns half of an invocation chain since the source
is not a component and is unmamanged code. Can you
O.K that's why I asked about what the source side looked like. A
degenerate outbound wire seems right. One thing on this is can we
cache the degenerate wire so the wire only need to be constructed
once while the runtime is in operation?
We have the problem I outlined, e.g. if the target is
[
http://issues.apache.org/jira/browse/TUSCANY-931?page=comments#action_12454705
]
Kelvin Goodson commented on TUSCANY-931:
Without having reviewed this issue in detail, it's worth capturing the
observation that this property has a .
I've been using a JSP to test this. At this point I'm not sure how much
restricting the client to an SCA component helps because the locateService
is still dynamic. Anyway the spec says locateService is available to
non-SCA clients.
On 11/30/06, Jim Marino [EMAIL PROTECTED] wrote:
This I
Hi all,
I've just tracked down a bug that's turned up in Axis2C 0.95 - most
of our web service calls are fine, but the samples that call out to
the external www.webservicex.net services (CppBigBank, RubyBigBank,
PythonWeatherForecast) fail due to a missing HTTP SOAPAction header.
I've raised
Simon Laws wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Simon Laws [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Andrew Borley [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On
On 21/11/06, Geoffrey Winn [EMAIL PROTECTED] wrote:
As far as SDO itself is concerned, I think we would be OK if the user of
SDO
could guarantee that whenever an SDO artifact (data factory, data object,
type, XSDHelper ...) is created then that artifact will be used
_exclusively_ by the thread
- Original Message -
From: Jeremy Boynes [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Thursday, November 30, 2006 9:10 AM
Subject: Re: Creating proxies (fix for TUSCANY-862)
On 11/30/06, Jim Marino [EMAIL PROTECTED] wrote:
This I think highlights a problem with the spec
On Nov 30, 2006, at 9:21 AM, Greg Dritschler wrote:
I've been using a JSP to test this. At this point I'm not sure how
much
restricting the client to an SCA component helps because the
locateService
is still dynamic. Anyway the spec says locateService is available to
non-SCA clients.
[ http://issues.apache.org/jira/browse/TUSCANY-956?page=all ]
Kelvin Goodson resolved TUSCANY-956.
Fix Version/s: Java-Mx
Resolution: Fixed
Patch committed at level 481007
SDOFactory instance lookup is using the wrong namespace URI
On 30/11/06, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Simon Laws wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Simon Laws [EMAIL PROTECTED] wrote:
On 11/30/06, Pete Robbins [EMAIL PROTECTED] wrote:
On 30/11/06, Andrew Borley [EMAIL PROTECTED] wrote:
On 11/30/06, Dan Murphy [EMAIL PROTECTED] wrote:
I would like to propose starting a community test suite for service data
objects (SDO CTS) implementations written in Java. Based on feedback from
an
earlier post this seems to be the first logical step in getting
interoperable SDO
Hi Folks,
When I deploy a Tuscany sample to Tomcat, I see what looks like Maven
trying to update its repository.
Is there a way to disable this behavior? (Something akin to maven's '-o'
command-line option maybe...)
Thanks,
-Matt
Also not seeing this issue. The junit test works for me in eclipse too. svn
rev 480786 Sun jdk java full version 1.5.0_10-b03
Raymond Feng wrote:
Hi,
I'm seeing the following test case failure in trunk code.
Raymond
---
T E S T S
It's a bit wierd. Now it works for me as well.
Thanks,
Raymond
- Original Message -
From: Rick [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Thursday, November 30, 2006 10:10 AM
Subject: Re: Test case fails: LoanAppConversationTestCase
Also not seeing this issue. The junit
There is a context parameter tuscany.online which defaults to true -
if you set this to false in webapp.xml then it should disable this
behaviour.
--
Jeremy
On 11/30/06, Matthew Duftler [EMAIL PROTECTED] wrote:
Hi Folks,
When I deploy a Tuscany sample to Tomcat, I see what looks like Maven
Please use thread-safe libraries
Key: TUSCANY-959
URL: http://issues.apache.org/jira/browse/TUSCANY-959
Project: Tuscany
Issue Type: Improvement
Components: C++ SDO
Affects Versions:
This is now http://issues.apache.org/jira/browse/TUSCANY-959
Spurious xsi:type=OpenDataObject attribute generated
--
Key: TUSCANY-960
URL: http://issues.apache.org/jira/browse/TUSCANY-960
Project: Tuscany
Issue Type: Improvement
On 30/11/06, Pete Robbins [EMAIL PROTECTED] wrote:
Ah a test!! Would it be that classs is serialized as both an attribute and
an element??
Indeed. Not only class, but xml:base and xml:lang, too.
I've opened http://issues.apache.org/jira/browse/TUSCANY-960 for the
xsi:type=OpenDataObject
I would like to propose starting a community test suite for service data
objects (SDO CTS) implementations written in Java. Based on feedback from an
earlier post this seems to be the first logical step in getting
interoperable SDO implementations in all languages. I can see this leading
to an
Kelvin,
My feeling is that runtime code should never throw a
NullPointerException. In this particular case where it is very easy
for users to input an invalid string value because of typos, case
sensitivity, or just not remembering the correct property name, it is
pretty ugly. If there is no
Jim,
See below please.
-Dave
- Original Message -
From: Jim Marino [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Thursday, November 30, 2006 12:44 PM
Subject: Re: Creating proxies (fix for TUSCANY-862)
On Nov 30, 2006, at 9:21 AM, Greg Dritschler wrote:
I've been using
Hi,
This is an appealing proposal. I will give a try.
Thanks,
Raymond
- Original Message -
From: Davanum Srinivas [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Thursday, November 30, 2006 5:48 AM
Subject: Re: Much ado about nothing (Re: WSCOMMONS-131 and options for
Tuscany
DAS: Using deprected SDO method causes Type lookup failure
--
Key: TUSCANY-961
URL: http://issues.apache.org/jira/browse/TUSCANY-961
Project: Tuscany
Issue Type: Bug
[ http://issues.apache.org/jira/browse/TUSCANY-961?page=all ]
Brent Daniel reassigned TUSCANY-961:
Assignee: Brent Daniel
DAS: Using deprected SDO method causes Type lookup failure
--
On Nov 30, 2006, at 1:06 PM, scabooz wrote:
Jim,
See below please.
-Dave
- Original Message - From: Jim Marino
[EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Thursday, November 30, 2006 12:44 PM
Subject: Re: Creating proxies (fix for TUSCANY-862)
On Nov 30, 2006, at
[
http://issues.apache.org/jira/browse/TUSCANY-578?page=comments#action_12454761
]
Yang ZHONG commented on TUSCANY-578:
Having discussed with Frank, will fix this along within 935
Exceptions thrown by SDO runtime not the same as defined
[
http://issues.apache.org/jira/browse/TUSCANY-951?page=comments#action_12454763
]
Yang ZHONG commented on TUSCANY-951:
Having discussed with Frank, will fix this along within 935
NullPointerException when setting an invalid property
I feel that M2 should have been (is) in lock down and fixes should only be to
issues that clearly break functionality. However, we the community SHOULD have
stuck to that position. Given we gave the go ahead to this and two people have
claimed to have tested it and it addresses the issue
[ http://issues.apache.org/jira/browse/TUSCANY-97?page=all ]
Yang ZHONG updated TUSCANY-97:
--
Attachment: EnforceReadOnly.97
The attachment is requested for public review.
Thanks.
Read only properties
Key:
Caroline Maynard wrote:
On 21/11/06, Geoffrey Winn [EMAIL PROTECTED] wrote:
As far as SDO itself is concerned, I think we would be OK if the user of
SDO
could guarantee that whenever an SDO artifact (data factory, data
object,
type, XSDHelper ...) is created then that artifact will be used
60 matches
Mail list logo