DAS is no longer needing the config.xsd to read xml configuration files
since revision 544749.
Adriano Crestani
On 5/30/07, Adriano Crestani [EMAIL PROTECTED] wrote:
Since revision 542742, DAS C++ is only working with SDO on trunk, and not
with SDO C++ M3.
Adriano Crestani
On 5/29/07,
[
https://issues.apache.org/jira/browse/TUSCANY-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kelvin Goodson updated TUSCANY-1325:
Patch Info: [Patch Available]
Property value with xsd:QName type is not deserialized
I would be disappointed to lose the ability to contribute directly to
the Web site pages. When the move to a wiki-based approach was first
discussed, one of the benefits was that it would not be necessary to
limit updates to committers as was the case with the previous web site.
Would it be
+1 for reverting implementation-crud back to the official SPIs and
adding another sample for the simplified extension layer.
Simon
Jean-Sebastien Delfino wrote:
Ant,
This commit introduced breaking changes to the helloworld-ws-reference
and helloworld-ws-service samples, using some kind
The rules, as documented [1], don't restrict editorship of a wiki used as a
project website to just committers but ask that only those who have a signed
CLA on file be allowed to edit the pages destined for the project website.
It doesn't say we can't restrict it to just committers of course.
I
Everybody knows what to expect from a wiki (due to wikis very nature) and what
to expect from an official website.
AFAIK, if a content is not developed and/or entirely controlled by the
committers then it can not be called official. There have been endless
discussions on this topic on infra@
Thanks for the pointers/info. I assume the intention is to add in the
ability to specify the binding specific base system uri on a binding by
binding bases (as well as implementing all the other rules of course). I
don't see this configuration in the code now.
sca domain
sca runtime
+1, it would be unfortunate to have the home paged covered in unsavory links
by some spammer just as 0.90 has been announced.
...ant
On 6/6/07, Simon Laws [EMAIL PROTECTED] wrote:
Ok Hernan, thanks for your advice on this, I guess we can go with just
having committers access on the space
ant elder wrote:
I'm not sure i agree about the sample, wont it be even more confusing
having
it use the old way? Maybe if there was something the sample was doing
that
required the complex SPI but while there isn't wont it just seem odd
to do
it an unnecessarily complicated way.
Do we even
I think it was Ted Husted who created your space first, you could start there.
Either way, you need to send the request to infra@ and open a JIRA with the
request so those folks can keep track
Cheers!
Hernan
Simon Laws wrote:
Ok Hernan, thanks for your advice on this, I guess we can go with
On 6/6/07, Simon Laws [EMAIL PROTECTED] wrote:
Thanks for the pointers/info. I assume the intention is to add in the
ability to specify the binding specific base system uri on a binding by
binding bases (as well as implementing all the other rules of course). I
don't see this configuration in
[snip]
Simon Laws wrote:
Ok, I've taken the next step here and have a distributed runtime example
running in my sandbox. A sample calculator application [1] showing the
disitributed runtime in action and a module containing the changes I
had to
make to the runtime to get this to work [2]. The
Generate static SDO APIs from wsdl files with type definition from
wsdl:import and wsdl:include
---
Key: TUSCANY-1327
URL:
OK, I need to take a closer look. Assuming we don't hard code the info we
can potentially determine the IP info (although that might not even be the
case when there are multiple NICs) but we need to get the port selection
from somewhere. Is there currently a natural place where this config info
[
https://issues.apache.org/jira/browse/TUSCANY-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kelvin Goodson resolved TUSCANY-1325.
-
Resolution: Fixed
Fixed at revision 544858
Property value with xsd:QName type is not
[
https://issues.apache.org/jira/browse/TUSCANY-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501951
]
Frank Budinsky commented on TUSCANY-1327:
-
If I remember correctly, types defined in wsdl files cannot be
When we do this, we should also be asking for 'administrator' access for a
couple of us atleast so that we could give Hernan a break on somethings such
as a manual autoexport. Thanks.
- Venkat
On 6/6/07, Simon Laws [EMAIL PROTECTED] wrote:
Ok Hernan, thanks for your advice on this, I guess
With this new approach, how can a non-committer make a change?
Will there be a mirror of the web site in the separate space
with committer+CLA access where I can do this? Or will I need
to create diff patches and attach them to a JIRA?
Simon
ant elder wrote:
+1, it would be unfortunate to
Hi,
I like the topology.xml approach. For the topology composite, I suggest that
we use a syntax something like the following:
composite
component name=runtimeA
implementation.runtime host=hostname or ip-address
mappings
binding name=binding.ws
scheme name=http
Simon,
I think that the idea is to split the material between official
Website pages and general Wiki pages. The official website pages would
be restricted to editing by committers. The rest of the Wiki can be
open to editing by all.
The simplest way for a non-committer to create
diff for patches wont work as the confluence native content (the source) is not
on svn. That is unless those patches are for any other static content that is
not served directly by confluence but still is being referenced by it,
something like the css or some images like logos, templates, etc.
Hi, Ant.
I agree with you that we should generalize the service binding URI. I think
I have a proposal here.
When the CompositeBuidler builds the composite, we should calculate the
service binding URI based on various pieces of the information as defined by
the spec and save the effective
OK so,
I'll raise a JIRA against infrastructure asking for a new space to act as
our wiki:
Name: Apache Tuscany Wiki
Key: TUSCANYWIKI
Is everyone happy with this name?
Venkat, when you say administrator privileges I assume you mean confluence
admin privileges? Wouldn't this be a separate
So, the idea is to have the current wiki as the official Tuscany
website, and the new one, would be used as general purpose wiki ?
On 6/6/07, Simon Laws [EMAIL PROTECTED] wrote:
OK so,
I'll raise a JIRA against infrastructure asking for a new space to act as
our wiki:
Name: Apache Tuscany
Yes. Make sense?
Simon
Yes - confluence admin. Ok for now shall I go ahead and raise requests for
Admin previleges for me and Luciano ?
- Venkat
On 6/6/07, Simon Laws [EMAIL PROTECTED] wrote:
OK so,
I'll raise a JIRA against infrastructure asking for a new space to act as
our wiki:
Name: Apache Tuscany Wiki
I would suggest you guys use lower case for the space names, at least for the
one with the highest hierarchy. Remember the URL is case sensitive and it is
based on the space ID.
Ideally http://cwiki.apache.org/tuscany should take you to a page consolidating pointers
to all the other Tuscany
Should we have a discussion around our wiki strategy and make sure we
do the right thing?
We could use the Geronimo wiki strategy [1] as an example and start point.
I think we should consider the following things:
- Naming Convention
- Access Control List for the wiki spaces
- Scope for
[
https://issues.apache.org/jira/browse/TUSCANY-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502022
]
Scott Kurz commented on TUSCANY-1327:
-
What authority (if any) does the Basic Profile 1.1 have here?
BP 1.1
I'm actually bumping up against one of the problems that ant has
described - the creation of $self$ reference URIs.
I don't believe a binding implementation should have to expect to deal
with odd URI's that were generated by the runtime and I'm curious how
bindings are supposed to know what
Matthew Sykes wrote:
I'm actually bumping up against one of the problems that ant has
described - the creation of $self$ reference URIs.
I don't believe a binding implementation should have to expect to deal
with odd URI's that were generated by the runtime and I'm curious how
bindings are
Hi,
Let's look at a use case:
Assuming we have a deployable composite as follows.
composite ...
component name=MyComponent
service name=MyService
binding.ws .../
/service
/component
/composite
When this composite is deployed to the SCA domain, then MyService
[snip]
Raymond Feng wrote:
Hi, Ant.
I agree with you that we should generalize the service binding URI. I
think I have a proposal here.
When the CompositeBuidler builds the composite, we should calculate
the service binding URI based on various pieces of the information as
defined by the
You pretty much summarized the advantages of having multiple spaces
From Admin point of view, there are all benefits from having multiple spaces, you have
more control on everything, it is more granular and the maintenance is
lighter-weight.
From the user perspective it is transparent,
[
https://issues.apache.org/jira/browse/TUSCANY-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502077
]
Fuhwei Lwo commented on TUSCANY-1327:
-
wsdl:include was introduced in WSDL 1.2 so for now, let's not worry
[
https://issues.apache.org/jira/browse/TUSCANY-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fuhwei Lwo updated TUSCANY-1327:
Attachment: Types.xsd
Messages.wsdl
Bindings.wsdl
Generate
Hi,
Please see my comments inline below.
Thanks,
Raymond
- Original Message -
From: Jean-Sebastien Delfino [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Wednesday, June 06, 2007 1:09 PM
Subject: Re: Servlet path change?
[snip]
Raymond Feng wrote:
Hi, Ant.
I agree with
[snip]
That's where the SCA domain configuration of base URIs for
hierarchical URI scheme comes to play. The SCA spec says: An SCA
domain should define a base URI for each hierarchical URI scheme on
which it intends to provide services.
Let's assume we have two bindings: binding.x and
can not locate service from a component whose implementation is composite
-
Key: TUSCANY-1328
URL: https://issues.apache.org/jira/browse/TUSCANY-1328
Project: Tuscany
Hi,
I think the base URI for a scheme cannot be global to a SCA domain. As you
said, that would be useless. The spec needs some clarifications here.
We might have two options here:
1) The SCA domain defines the base URI pattern such as http://$host:8080/.
And $host will be replaced by the
I also think the assembly spec is a little deficient in this area. I don't
think it's description of the Base Domain URI at line 2357 chimes well with
the notion that an SCA Domain may be represented across a number of runtime
nodes at line 2765.
While we might assume from how it stands that
Contribution metada initializer is using classloader wrongly
Key: TUSCANY-1329
URL: https://issues.apache.org/jira/browse/TUSCANY-1329
Project: Tuscany
Issue Type: Bug
Ant,
I was trying to add the link to this document from the website and was not
sure where you intended to sit? It seems like user doc is the right place
for it?
On 6/4/07, Venkata Krishnan [EMAIL PROTECTED] wrote:
Hi Ant,
I was trying to avoid the uri scheme and thought this to be a sure way
Raymond, if you think CompositeBuilder is the right place to do this then I
have to bow to your better judgement.
The binding base URLs should be stored in a topology model (as in the SCA
Binding and Distribution thread). So if you are going to make this change it
would be good to instigate
Sebastien,
I should say that I'm working on a default binding that replaces the
Tuscany implementation. The URI isn't changed but new references are
created with target URIs that are unknown to the binding implementation
on the service side.
CompositeBuilderImpl.createSelfReferences
Hi,
I agree with you that the base URIs are from the topology model. What I
meant before is that the CompositeBuilder will be aware of the topology
model and use it to compute the effective URI for the service bindings. Are
we on the same page?
Thanks,
Raymond
- Original Message -
Raymond Feng wrote:
Hi,
I agree with you that the base URIs are from the topology model. What
I meant before is that the CompositeBuilder will be aware of the
topology model and use it to compute the effective URI for the service
bindings. Are we on the same page?
Thanks,
Raymond
-
Good points. +1 to have separate modules handle the physical topology
aspect.
Thanks,
Raymond
- Original Message -
From: Jean-Sebastien Delfino [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Wednesday, June 06, 2007 3:46 PM
Subject: Re: Servlet path change?
Raymond Feng
Fuhwei, you're right.. the BP's just saying not to use WSDL import to import
schemas directly. Sorry for the confusion.
Scott
On 6/6/07, Fuhwei Lwo (JIRA) tuscany-dev@ws.apache.org wrote:
[
Calculator webapp composite file and sca contribution metadata file are missing
targetNamespace attribute
-
Key: TUSCANY-1330
URL:
[snip]
haleh mahbod wrote:
How about we change the name of the document to 'Tuscany cwiki Website
Structure'
And remove the paragraphs marked with the pink comments?
http://cwiki.apache.org/confluence/pages/viewpage.action?pageId=56590
This document is purely sharing the wiki stucture and
Jean-Sebastien Delfino wrote:
[snip]
haleh mahbod wrote:
How about we change the name of the document to 'Tuscany cwiki Website
Structure'
And remove the paragraphs marked with the pink comments?
http://cwiki.apache.org/confluence/pages/viewpage.action?pageId=56590
This document is purely
[snip]
haleh mahbod wrote:
http://cwiki.apache.org/confluence/pages/viewpage.action?pageId=56590
This document is purely sharing the wiki stucture and explains how to
move
cwiki to the website.
According to this doc a change to the Wiki representing the Tuscany Web
site is:
1.
Comments inline
On 6/6/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
[snip]
haleh mahbod wrote:
http://cwiki.apache.org/confluence/pages/viewpage.action?pageId=56590
This document is purely sharing the wiki stucture and explains how to
move
cwiki to the website.
According to this
Luciano Resende wrote:
Wouldn't that fail if you start from a clean repo ? It expects the
other modules to be built or available as deployed snapshots no ?
On 6/5/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
[snip]
Luciano Resende wrote:
I'm looking for a distribution that I could use
[
https://issues.apache.org/jira/browse/TUSCANY-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino reassigned TUSCANY-1316:
---
Assignee: Jean-Sebastien Delfino
WriteAllTestCase:
[
https://issues.apache.org/jira/browse/TUSCANY-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino resolved TUSCANY-1318.
-
Resolution: Invalid
This works as designed.
SCA composites are
Luciano Resende wrote:
Comments inline
On 6/6/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
[snip]
haleh mahbod wrote:
http://cwiki.apache.org/confluence/pages/viewpage.action?pageId=56590
This document is purely sharing the wiki stucture and explains how to
move
cwiki to the
Do you have Confluence Admin rights ? We are trying to get couple of
people with Admin rights in order to be able to resolve this infra
issues. Otherwise we are dependent on the existent confluence admins,
and Herman is one of the guys that are helping us.
On 6/6/07, Jean-Sebastien Delfino
59 matches
Mail list logo
