Looking at the include path it appears you have not set the required
environment variables: TUSCANY_SDOCPP, TUSCANY_SCACPP.
Cheers,
On 27/06/06, Rick <[EMAIL PROTECTED]> wrote:
I down loaded the binary distro unpacked it downloaded Axis2C too and
unpacked but didn't do anything else with it.
W
Thanks. Hopefully we will be able post something today,
On 27/06/06, Luciano Resende <[EMAIL PROTECTED]> wrote:
Hey Pete
When the C++ win release is available I can give it a try and provide
feedback.
- Luciano
*"Pete Robbins" <[EMAIL PROTECTED]>*
06/24/2006 07:22 AM Please resp
That's a good idea. I'll go with tuscany_sca_cpp-$version-$type where $type
is bin or src.
On 27/06/06, Rick <[EMAIL PROTECTED]> wrote:
Was wondering if the download package names should have something that
distinguishes between cpp and java?
tuscany-cpp-sca-0.1.incubating-M1.tar.gz <
http://p
Hi,
databinding module in sandbox is not included as part of build at the moment.
Are we going to still have this module in the new core? In Monday's IRC chat,
Jeremy mentioned that we need to fix the version in the sdo databinding pom, is
anyone working on this right now?
Also SDOXMLHelper.ja
Forgot to say that the instructions for building the samples are in the
samples/INSTALL file.
On 28/06/06, Pete Robbins <[EMAIL PROTECTED]> wrote:
Looking at the include path it appears you have not set the required
environment variables: TUSCANY_SDOCPP, TUSCANY_SCACPP.
Cheers,
--
Pete
Raymond,
You can get the type of T if you have a parameterized field of a generic
type. Some thing like this,
import java.lang.reflect.Field;
import java.lang.reflect.ParameterizedType;
public class Test {
private Test myField;
/**
* @param args
*/
public static void
Thanks found it after I sent the message. Sorry for the confusion.
Pete Robbins wrote:
Forgot to say that the instructions for building the samples are in the
samples/INSTALL file.
On 28/06/06, Pete Robbins <[EMAIL PROTECTED]> wrote:
Looking at the include path it appears you have not set th
Thanks Jeremy -- "works on my machine".
Raymond, I've submitted a bunch of Spring changes, including your
patch to upgrade to Spring 2.0-rc1.
On 6/27/06, Jeremy Boynes <[EMAIL PROTECTED]> wrote:
On 6/26/06, Jeremy Boynes <[EMAIL PROTECTED]> wrote:
>
> I've disabled the checkstyle stuff for now
If I read the following doc:
http://www.apache.org/tuscany/interop";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.apache.org/tuscany/interop interop01.xsd
">
SimpleTypeWithName
With the following schema
http://www.w3.org/2001/XMLSchema";
The C++/SDO implementation generates an xsi:type attribute on the root
element of documents written out via the XMLHelper. Is it possible to turn
this feature off?
Regards
Simon
I'd like to start working on providing support for callbacks, assuming the
sandbox is a good place to do this. Currently, I am focusing on local,
stateless callbacks to begin with. Later, and assuming that conversational
support is in place (which I am also keen on contributing to) I can work on
Hi Simon,
I think it should work. Your example is a little strange in that the
xsi:type is the same as the actual element type. Usually the xsi:type is
used to identify a subtype, so maybe the implementation has a bug that
only turns up in this case.
Is there someone with more XML expertise t
OK, thanks Frank, I tried that and the effect is the same regarless of
whether the xsi:type reference to an extension or not. xsi:type does work
with both extensions and base classes if it's used on an element that is not
the root element. I have opened a jira (505) and added this information.
Re
xsi:type on root element fo XML doc causes problems
---
Key: TUSCANY-505
URL: http://issues.apache.org/jira/browse/TUSCANY-505
Project: Tuscany
Type: Bug
Components: Java SDO Implementation
Versions: Java-M1
I have uploaded the slides from our presentation at ApacheConEU to:
http://svn.apache.org/repos/asf/incubator/tuscany/site/src/site/resources/Tuscany%20ApacheConEU%202006.ppt
Sorry about the PPT format but that's all I have on this machine. If
someone can covert to a more open format I would appr
On 6/28/06, Meeraj Kunnumpurath <[EMAIL PROTECTED]> wrote:
Raymond,
You can get the type of T if you have a parameterized field of a generic
type. Some thing like this,
I think you can also get the parameterized type information from Class
itself. Jim was doing some introspection like this
On 6/28/06, Liu, Jervis <[EMAIL PROTECTED]> wrote:
Hi,
databinding module in sandbox is not included as part of build at the moment.
Are we going to still have this module in the new core?
I think so, yes.
In Monday's IRC chat, Jeremy mentioned that we need to fix the version in the
sdo da
Hi,
Do you think if my prototype can be used as a seed to flush out a good data
mediation story? If so, does it make sense that somebody commits it into the
sandbox to get more people involved? I'll update the wiki page as I add more
things.
Thanks,
Raymond
- Original Message -
Fro
Given
Collection strings = ...;
Collection integers = ...;
According to Java language spec, this is true:
strings.getClass() == integers.getClass()
After all, Java doesn't generate .class files for EACH
parametization/instantiation like C++.
It seems impossible to get the parameter type from
I don't think you can get the instance type information from within the
class as it is erased by the compiler.
-Original Message-
From: Yang ZHONG [mailto:[EMAIL PROTECTED]
Sent: 28 June 2006 18:22
To: tuscany-dev@ws.apache.org
Subject: Re: Question on java generics
Given
Collection s
[ http://issues.apache.org/jira/browse/TUSCANY-477?page=all ]
Yang ZHONG updated TUSCANY-477:
---
Attachment: patch&tests.zip
Attaching patch & 2 test cases.
> SDO runtime should report unresolved types in a meaningful way if
> xsd:import/include cannot be
[
http://issues.apache.org/jira/browse/TUSCANY-477?page=comments#action_12418326
]
Yang ZHONG commented on TUSCANY-477:
The proposed fix is to throw IllegalArgumentException for type unable to be
resolved, such as the test case 1. That behavior comform
[
http://issues.apache.org/jira/browse/TUSCANY-505?page=comments#action_12418335
]
Yang ZHONG commented on TUSCANY-505:
First of all, there're spaces within NameSpace in both XSD and XML, it makes
references broken, especially
http://www.w3.org/200
[ http://issues.apache.org/jira/browse/TUSCANY-503?page=all ]
Yang ZHONG updated TUSCANY-503:
---
Attachment: patch&test.zip
Attaching contribution and test case.
> XSD substitution support in SDO2
>
>
> Key: TUSCANY
[
http://issues.apache.org/jira/browse/TUSCANY-503?page=comments#action_12418353
]
Yang ZHONG commented on TUSCANY-503:
Test code (& the new API usage example):
public final class SubstitutionValues extends junit.framework.TestCase
{
public void test
Hi Raymond,
I think this would be really good to get it into the sandbox. Can
you point me to the latest patch and we'll get it in ASAP?
Jim
On Jun 28, 2006, at 9:36 AM, Raymond Feng wrote:
Hi,
Do you think if my prototype can be used as a seed to flush out a
good data mediation story?
Hi Raymond,
I think the question to be answered is how this data mediation is supposed to
be used. For example, shall I use this data mediation as a java util just same
as how I use SDOXMLHelper.java before? In this way, the data mediation might
look like a replacement or enhancement to SDOXMLH
Hi,
I'm looking into the direction to make the data mediation pluggable into a
system service which holds a registry for all the mediators. Then the usage
pattern will become the following:
1) Get the data mediation system service (can be done by injection on
"autowire").
2) Transform the da
I was thinking it would be a system service since it appears to be
applicable to a wide variety of things in the runtime. Having it as a
system service also allows it to be managed and autowired to other
extension points (e.g. services, bindings, components that may want
to use it).
If it
29 matches
Mail list logo
