True, with the approach, DAS can use Metadata API and treat Derby specially
(as
Derby Embedded Driver API returns FALSE, set it to TRUE)
1) If provided in Config - it will be used, no Metadata API check
2) If not provided in Config - Metadata API check - In this for Derby ALWAYS
SET TO TRUE, and
I analysed component model object in tuscany.
Here my question is: all the component model object has implemented interface
[org.apache.tuscany.sca.assembly.Visitable]. But in fact the [accept] method
are never invoked. More of it, there is a [Visitor] interface, but nobody
implements it.
My p
Ole
On 7/24/07, Ole Ersoy <[EMAIL PROTECTED]> wrote:
Hey Luciano,
Luciano Resende wrote:
> Hi Ole
>
> After you mentioned you are almost done with a initial version of
> LDAP DAS that provides CRUD operations [1] I went to your sandbox [2]
> to take a quick look at the current implementation
Thank you for your attention ant!
You encouraged me reading osoa's specification again, then I found your point.
OK, now let me speak about my question to some further:
I found in WebService_Binding 2.3, wsdl should be generated for an binding.ws,
and
there follows a generation rule in the spec,
Great tip Adriano. I modeled the configuration file using ecore, so I just
made it a multiplicity many EAttribute with type EString. I'll make a note in
my todo list make it a TreeSet instead.
Thanks,
- Ole
Adriano Crestani wrote:
This list of xsd namespaces, instead of using List, wouldn
Hey Luciano,
Luciano Resende wrote:
Hi Ole
After you mentioned you are almost done with a initial version of
LDAP DAS that provides CRUD operations [1] I went to your sandbox [2]
to take a quick look at the current implementation and have couple
questions :
- Where is the latest implementa
Hi,
Please see my comments inline.
Thanks,
Raymond
- Original Message -
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, July 24, 2007 6:46 PM
Subject: Re: Resolving WSDL/XSD import/include for SCA contributions
Two questions inline.
Raymond Feng wrote:
Hi,
Two questions inline.
Raymond Feng wrote:
Hi,
I'm working on the artifact processing of WSDL/XSD from SCA
contributions, especially for the import/include directives. I would
like to share what I have so far to get your feedback.
Let's assume we have the following artifacts ([1][2]).
* he
Trying to build Native/C++ SDO on Linux RHEL5 gives me this error:
if /bin/sh ../../../../../libtool --tag=CXX --mode=compile g++
-DHAVE_CONFIG_H -I. -I. -I../../../../..
-I../../../../../runtime/core/src -I//home/delfinoj/include/libxml2
-g -O0 -MT HelperProvider.lo -MD -MP -MF ".deps/Help
Hi Ole
After you mentioned you are almost done with a initial version of
LDAP DAS that provides CRUD operations [1] I went to your sandbox [2]
to take a quick look at the current implementation and have couple
questions :
- Where is the latest implementation of LDAP DAS available ? Is the
co
Hi,
We currently use XmlSchema to load XSDs. To resolve the import/include
directives using our schemes, we provide an implementation of
org.apache.ws.commons.schema.resolver.URIResolver and set it to
org.apache.ws.commons.schema.XmlSchemaCollection. It works well if the
schemaLocation attrib
EAttribute.isID() will only be true if the type is xsd:ID.
Frank.
"Pinaki Poddar" <[EMAIL PROTECTED]> wrote on 07/24/2007 05:31:09 PM:
> Hi Frank,
>> Database IDs (e.g., primary and foreign keys) are more related to
> xsd:key/xsd:keyref, then xsd:ID, but fortunately SDO 3 is planning to
> ad
Hi Frank,
> Database IDs (e.g., primary and foreign keys) are more related to
xsd:key/xsd:keyref, then xsd:ID, but fortunately SDO 3 is planning to
address all of them :-)
Thanks for telling me this.
Now is ((property.getType().isDataType()) &&
((EAttribute)property).isID())) == true for a
I've applied the patch. I'm having a few problems on Windows with my
environment I'm getting errors like:
compile.cpp.osoa:
[cc] 2 total files to be compiled.
[cc] CompositeContext.cpp
[cc]
D:\tuscanysvn\cpp\sca\runtime\extensions\cpp\src\osoa\sca\CompositeContext.cpp(44)
: war
[
https://issues.apache.org/jira/browse/TUSCANY-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Yoder updated TUSCANY-1478:
---
Attachment: TUSCANY-1478.txt
This patch resolves the issue and adds a unit test.
> For sch
For schemas with elementFormDefault=true, serialized instance documents are
invalid
---
Key: TUSCANY-1478
URL: https://issues.apache.org/jira/browse/TUSCANY-1478
Project:
Hi,
I would like to mention that the "location" attribute is required for for
by the WSDL 1.1 spec. But "schemaLocation" is optional for
and .
BTw, can also be used to import an XSD in addtion to WSDL. I
don't think it's a good practice but the WSDL 1.1 spec has an example for
that.
Th
Hi,
I think it's a great opportunity for both Synapse and Tuscany. From Tuscany
side, the following features may be helpful.
1) We have the SCA assembly model defined as pure interfaces in Tuscany and
factories can be plugged in to provide different implementations.
2) We already have a mod
Hi,
I'm working on the artifact processing of WSDL/XSD from SCA contributions,
especially for the import/include directives. I would like to share what I
have so far to get your feedback.
Let's assume we have the following artifacts ([1][2]).
* helloworld-service.wsdl (definition) imports he
On 7/24/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
I recently read Dan's blog entry on the SCA assembly model:
http://netzooid.com/blog/2007/07/22/sca-assembly-vs-spring-cxf/
That and some other discussions I've had made me think about maybe
offering the SCA assembly model to configure Synap
Hi Pinaki,
Identity support is also in the SDO 3 charter: Support for a concept of
identity in SDO, and its relationship to other technologies.
Database IDs (e.g., primary and foreign keys) are more related to
xsd:key/xsd:keyref, then xsd:ID, but fortunately SDO 3 is planning to
address all of
This list of xsd namespaces, instead of using List, wouldn't be
better to user TreeSet? Once you need to look up for namespaces on
the list frequently, unless if there are another reason to use List that I'm
not aware about : )
Regards,
Adriano Crestani
On 7/24/07, Ole Ersoy <[EMAIL PROTECTED]>
To get the distributed domain support up to a level that is suitable for
including in the next release I think we need to make the node configuration
and management more dynamic.
Scenarios
--
The current scenario being used to test distributed support is the
calculator-distributed sam
Hi Luciano,
If I call DomainCompositeHelper.startComponent() on each of the components
from the first contribution after deploying the second, (that is after Step
6 from below), it results in an Exception which I ignore and continue. But
towards the end I have services from both contributions ru
All set, build ran sucessful.
On 7/24/07, Ignacio Silva-Lepe <[EMAIL PROTECTED]> wrote:
Thanks Luciano, let me know if there are any other issues.
On 7/24/07, Luciano Resende <[EMAIL PROTECTED]> wrote:
>
> There was an issue with the sca-api group id, I have fixed under
> revision #559106 and I
Thanks Luciano, let me know if there are any other issues.
On 7/24/07, Luciano Resende <[EMAIL PROTECTED]> wrote:
There was an issue with the sca-api group id, I have fixed under
revision #559106 and I have started a new build in continuum.
On 7/24/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]
I updated the jira1438 with update 4, which includes the following:
https://issues.apache.org/jira/browse/TUSCANY-1438
New build.xml files for the following
- runtime/extensions/python
- runtime/extensions/rest
- runtime/extensions/ruby
Moved -DSCA_EXPORT from Tuscany-BaseCompiler in syst
Hi Luciano,
I have created TUSCANY-1477 for the issue.
Here is another situation I am running into.
Step 0: Create an EmbeddedSCADomain.
Step 1: Add contribution from contribution1.jar (which provides say
"Service1") to EmbeddedSCADomain from Step 0.
Step 2: Call EmbeddedSCADomain.DomainComposit
[
https://issues.apache.org/jira/browse/TUSCANY-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brady Johnson updated TUSCANY-1438:
---
Attachment: tuscany_patch_update4_jira1438
Attaching update4 which includes the following n
There was an issue with the sca-api group id, I have fixed under
revision #559106 and I have started a new build in continuum.
On 7/24/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
This change breaks the continuum nightly build (even though a local
build is successful). Could you please
This change breaks the continuum nightly build (even though a local
build is successful). Could you please investigate and help fix it? Thanks.
[EMAIL PROTECTED] wrote:
Author: isilval
Date: Mon Jul 23 09:50:14 2007
New Revision: 558796
URL: http://svn.apache.org/viewvc?view=rev&rev=558796
Log
Hi Amita,
Since DAS has JDK 1.4 as a requirement and the JDBC 3.0 APIs are built into JDK
1.4, isn't it sufficient to interpret a JDBC 2.0 driver throwing a exception
from supportsGetGeneratedKeys() as a false. Also, since the DAS is currently a
pre-1.0 release, I don't think our solution need
Luciano Resende wrote:
Are we trying to make it much more complex ?
:-) I'm a big believer in as simple as possible, but no simpler.
Are users going to get
confused to think they have a local copy of the XML config file, but
the LDAP DAS is really using the one stored on the server ?
You
Hi Frank,
Thanks.
> SDO (SDO 3) is planning to provide an api for accessing extended XSD
metadata
That is good news. However, identity mechanics should appear more
distinctly on API surface e.g.
boolean Proprty.isIdentifier();
List Type.getIdentifiers();
I will qualify absence of any
Hi Pinaki,
They can't be distinguished in the current version of SDO metadata, you
need to look at the original XSD. The next version of SDO (SDO 3) is
planning to provide an api for accessing extended XSD metadata. In
Tuscany, you can currently determine this by downcasting to the EMF
impleme
I recently read Dan's blog entry on the SCA assembly model:
http://netzooid.com/blog/2007/07/22/sca-assembly-vs-spring-cxf/
That and some other discussions I've had made me think about maybe
offering the SCA assembly model to configure Synapse. So it seems to
me that you can draw a direct correla
That was the only drawback that I could see too. Each depot ought to be
basically stand-alone.
As for a top-level build.xml for all 3 projects, that would be very
simple and would not require any of the ant infrastructure used by the
individual projects. It would be very similar to the root build
[
https://issues.apache.org/jira/browse/TUSCANY-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amita Vadhavkar updated TUSCANY-1353:
-
Attachment: 1353.patch
Please see details posted on
http://www.mail-archive.com/tuscan
Hi,
Below are some details about the solution for JIRA-1353.
Please review the patch.
http://issues.apache.org/jira/browse/DERBY-242 - indicates that for 10.1.1.0,
DatabaseMetadata.supportsGetGeneratedKeys() returns false. Also, checked
that for the current Maven Repo's Derby version (10.1.2.1)
Simon Laws wrote:
Ah, thanks Mike. I didn't latch onto the implication of the word intent.
The choice we are talking about here seems more like a concrete decision
than an intent. Does this match well with the, erm, intention of intents?
Simon
It is one use of intents - and, in my opinion, it
On 7/24/07, Mike Edwards <[EMAIL PROTECTED]> wrote:
Simon Laws wrote:
> On 7/24/07, Mike Edwards <[EMAIL PROTECTED]> wrote:
>>
>> Simon Laws wrote:
>> > Has anyone in Tuscany made a binding that ships SOAP messages over
JMS
>> > instead of HTTP? Looking at the current code base and at the old
>>
On 7/24/07, ant elder <[EMAIL PROTECTED]> wrote:
- change builds to use the maven release plugin to avoid most of the manual
steps when creating a release
- use maven to as much as possible automate the adding of dependency
information to the LICENSE and NOTICE files
- update the RAT tool to v
On 7/24/07, ant elder <[EMAIL PROTECTED]> wrote:
I agree we could do things to improve our releases. Most ASF releases end up
having several RCs, its a natural part of the process, I'm not sure it
indicates any failing somewhere.
IMHO when you use the RC method, having multiple RCs does not ind
CompositeActivatorImpl.deactivate() is empty
Key: TUSCANY-1477
URL: https://issues.apache.org/jira/browse/TUSCANY-1477
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-0.91
Simon Laws wrote:
On 7/24/07, Mike Edwards <[EMAIL PROTECTED]> wrote:
Simon Laws wrote:
> Has anyone in Tuscany made a binding that ships SOAP messages over JMS
> instead of HTTP? Looking at the current code base and at the old
code in
> the
> sandbox I don't see anything.
>
> Simon
>
Simon,
ant elder wrote:
Couldn't this just use the existing Axis2 facilities, the soap/jms uri
format and be done with the scdl binding uri attribute, eg:
org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616&java.naming.security.principal=system&java.n
The sca jms binding spec also supports defining all that with the uri
attribute doesn't it. The ws soap/jms uri format has been an evolving
technique used for quite a while, and there is an attempt to standardized
it, see :
http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200701.mbox/[EMAIL
P
On 7/24/07, Mike Edwards <[EMAIL PROTECTED]> wrote:
Simon Laws wrote:
> Has anyone in Tuscany made a binding that ships SOAP messages over JMS
> instead of HTTP? Looking at the current code base and at the old code in
> the
> sandbox I don't see anything.
>
> Simon
>
Simon,
Shouldn't this be a
On 7/24/07, ant elder <[EMAIL PROTECTED]> wrote:
On 7/24/07, Mike Edwards <[EMAIL PROTECTED]> wrote:
>
> Simon Laws wrote:
> > Has anyone in Tuscany made a binding that ships SOAP messages over JMS
> > instead of HTTP? Looking at the current code base and at the old code
in
> > the
> > sandbox I
On 7/24/07, Mike Edwards <[EMAIL PROTECTED]> wrote:
Simon Laws wrote:
> Has anyone in Tuscany made a binding that ships SOAP messages over JMS
> instead of HTTP? Looking at the current code base and at the old code in
> the
> sandbox I don't see anything.
>
> Simon
>
Simon,
Shouldn't this be a
snip..
There's already lots of doc about doing releases in the ASF - on the ASF
main dev pages and within the Incubator site etc.
The problem with there being lots of docs is that there are, ahem, lots of
docs. Where is the definitive set of guides that provide the detail required
to release
Simon Laws wrote:
Has anyone in Tuscany made a binding that ships SOAP messages over JMS
instead of HTTP? Looking at the current code base and at the old code in
the
sandbox I don't see anything.
Simon
Simon,
Shouldn't this be a "simple" extension of the Web services binding?
The interest
hi,all
I checked out all the code and found the composite building method has been
changed to the method named incrementalBuild,not used the method named
build.The purpose is to build every composite separately,instead of the old
implementation merged all included composites first.
This will m
[
https://issues.apache.org/jira/browse/TUSCANY-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514922
]
wangful commented on TUSCANY-1355:
--
Hi,
binary distribution at
http://people.apache.org/~lresende/tuscany/das-b
I agree we could do things to improve our releases. Most ASF releases end up
having several RCs, its a natural part of the process, I'm not sure it
indicates any failing somewhere. We've been restructuring our builds and
distributions recently, with changes like that going on there will be
wrinkle
On 7/23/07, Luciano Resende <[EMAIL PROTECTED]> wrote:
Any more inputs here ?
Maybe we could stage this in two phases, for now just make all project
consistent and pointing to 2-incubating as
suggested on this thread. And then continue discussions on pros/cons
of having multiple poms, one for e
Luciano Resende wrote:
Should we start thinking on a formal release guide, merging together
couple documents we already have as of today, and also creating a
checklist as it looks like couple release candidates are having the
same issues ?
+1 - yes, most definitely.
Yours, Mike.
57 matches
Mail list logo
