Folks,
I'd just like to say that if you need Confluence help, that I have some
expertise in this area since I manage the www.osoa.org site, which is
also based on Confluence.
Yours, Mike.
ant elder wrote:
On 6/7/07, Luciano Resende <[EMAIL PROTECTED]> wrote:
Do you have Confluence Admi
+1 from me
Yours, Mike.
ant elder wrote:
On 6/7/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
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
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 somethi
Muhwas,
I dont understand what you are saying here.
Surely, the actual service has a specific interface - it isn't simply
"anything", so you can only cast to the actual business interface it
actually implements.
Or did you envisage your client code introspecting the returned service
proxy a
Jean-Sebastien,
OK, with the latest commit to the sandbox, there is a working version of
the Spring implementation. It has the fixes you need, plus a set of
other changes which have got the basic version working.
I'll hold off on further updates until it's in trunk.
The next step is to get
>> I
> >> thought.
> >>
> >> - Venkat
> >>
> >> On 5/18/07, haleh mahbod <[EMAIL PROTECTED]> wrote:
> >> >
> >> > posted a new logo. You'll find Logo1, Logo2, Logo 3
> >> >
> >> > http://cwiki.
Haleh,
As others have said, the right hand side is superb - keep it.
The cypress image is a good idea, but the particular one that you have
doesn't look effective when it is Icon sized - it's too detailed and
fussy. Better to have a simpler image with fewer, bolder trees. I'll
have a hunt t
Hi,
Replies to some of your questions:
Mike Edwards
[EMAIL PROTECTED] wrote:
I've been using Tuscany M2 for a little while and I had a couple issues:
- implementation.spring seems to be broken. Is there a target release for this
fix?
I am working on the Spring implementation type -
Folks,
I ran into a problem building and running the Itests for SCA.
I was unable to get the jaxws-maven-plugin resolved and the whole thing
failed - this was despite there being a copy of the plugin in my local
repository - it just turned out to be unacceptably old for some reason
best known
ant elder wrote:
On 5/4/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
Nicholas Williams wrote:
> My understanding is that Tuscany does not currently validate SCDL
against the schemas. Assuming that this is correct, when do you think
such
functionality will be introduced?
>
> Thanks
>
Jean-Sebastien Delfino wrote:
Jean-Sebastien Delfino wrote:
Raymond Feng wrote:
ComponentReference.getReference() should give you the reference on
the component type.
Thanks,
Raymond
ComponentReference.getReference() will give you the reference from the
ComponentType. I think that Ant i
Jean-Sebastien,
+1 for sca/demos/bigbank
I'd like to show it at IMPACT 2007 in Orlando week after next - I may
ask for some help next week as I prepare ;-)
Thanks for preparing it - it helped to give the JavaOne BOF some much
needed reality !
Yours, Mike.
Raymond Feng wrote:
Hi,
It's
Venkat,
Responses inline
Yours, Mike.
Venkata Krishnan wrote:
Hi,
I am trying to bring the SPI model and the Loaders in sync with the current
level of the specs as available on OSOA site. I am currently looking at
'references' - as and how they are defined in ComponentType,
ComponentDef
Jean-Sebastien Delfino wrote:
Jean-Sebastien Delfino wrote:
Yang ZHONG wrote:
WSDL has schemas and portTypes.
WSDL2Java uses SDO CodeGen to compute classes names for schemas and
generates classes for portTypes.
SDO code seem not actually generated.
Is that desired?
If not, I can look into h
Folks,
With my spec hat on - the NAMES of the specs ain't going to change.
However, some of the FILES belonging to the spec are VERY likely to
change before publication. I know FOR SURE that sca-core.xsd is going
to change from the currently published version, since the Assembly WG
agreed th
Luciano,
Removing a page is dreadfully simple - be cautious about its use. Go
into Edit mode on the page you want to delete. On the top right of the
editing pane, you will find a trash can icon with a link labelled
"Remove Page". Click on either the trash can or the text and that will
dele
mples will still be using
the
old pom.xml in your local maven repo.
I agree its not easy, which is why I've always argued a pre-built distro
complete with everything in a single download zip makes for a much easier
first time experience.
...ant
On 3/2/07, Mike Edwards <[EMAIL PROTECTED]>
On 2/27/07, Mike Edwards <[EMAIL PROTECTED]> wrote:
Raymond,
Thanks for your reply.
I had seen your previous note and I tried applying the lines:
tuscany.online
false
into the web.xml file within the deployed Tomcat webapp.
Unfortunately, it ma
y
thought at all.
Yours, Mike.
Jeremy Boynes wrote:
Mike
You mention Java API files - are those available as well? If so, do you
intend to also distribute them through the Maven repo system?
Thanks
--
Jeremy
On Feb 28, 2007, at 3:13 AM, Mike Edwards wrote:
Folks,
1) I am arranging to p
Folks,
I can confirm that the current 1.0 spec schemas are available on
http://www.osoa.org/xmlns/sca/1.0/.xsd
Yours, Mike.
Jeremy Boynes wrote:
The sca-api module contains old versions of the schemas from 0.9 days.
I think we should remove these from the jar as they are orthogonal
fro
Folks,
1) I am arranging to publish all of the SCA spec schemas on the
www.osoa.org site - we've completed a site upgrade that now allows us to
publish random files outside the Wiki.
So, expect to see the 1.0 SCA XSDs on
http://www.osoa.org/xmlns/.
by the end of today.
Please note that
Folks,
I only saw this discussion recently, since I was heads-down with the SCA
1.0 specs for the past month.
The www.osoa.org site is wholly based on using the Confluence Wiki and
our experience with it is good. You can pass your own judgement on how
good the www.osoa.org site looks ;-)
Raymond,
Thanks for your reply.
I had seen your previous note and I tried applying the lines:
tuscany.online
false
into the web.xml file within the deployed Tomcat webapp.
Unfortunately, it makes no difference. The axis2 jar is still not
found with exactly
Folks,
I'd appreciate any help with the problem I'm having running the BigBank
sample with the M2 release.
First, I'm using:
- Tomcat 5.5.20
- Maven 2.0.4
- Sun JDK 5.0
as advised in the sample readme.
I build the sample using mvn
I deploy the sample to Tomcat using mvn tomcat:deploy
The
Jim,
I don't follow you. What would you expect the service name to look like?
I especially dont want to see us making the simple case of a single
unambiguous interface look more complex. Can you draw up a sample or
two of what you mean?
Yours, Mike.
Jim Marino wrote:
Not if we use Java
Raymond,
First point I need to make is that just because two components are in
the same composite does not mean that they are automatically running in
the same VM or even the same operating system process. Composites can
span components running on different nodes (node = machine and/or o/s
p
information.
Forwarding your email to tuscany-user mailing list as well.
-- Forwarded message --
From: *Mike Edwards* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>
Date: Oct 24, 2006 5:52 AM
Subject: Closer Involvement with the OSOA Specifications for Tuscany
Developers
that any detailed feedback that you give on the specifications is
donated in a way that meets those terms.
Individuals may join the OSOA Supporters group as well as companies.
Yours, Mike Edwards
Chair of SCA Assembly Specification Working Group
Folks,
I'm not sure that adding more comments inline is going to help clarity,
so I'll try to make my points standalone here:
1) My view is that binding.sca was intended to imply "the binding that
the SCA runtime system will use if you specify no other specific binding"
- implying that a de
Sebastien,
This sounds like a good approach to me.
Yours, Mike.
Jean-Sebastien Delfino wrote:
Hi,
I think it's about time that we implement the SCA
"default" binding, about 10 months after the publication of the initial
SCA spec v0.9 :)
As far as I can remember all discussions on the su
're looking for feedback
from the Tuscany team - and from anyone in the wider
community too.
Yours, Mike Edwards.
SCA Assembly Spec working group chair.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Jeremy,
Glad to see that the policy page covers code like the stuff associated
with the SCA & SDO specs:
-
Treatment of Third-Party Works
0. The term "third-party work" refers to a work not submitted
directly to the ASF by the copyright owner or owner's agent.
1.
2. Do not mod
Folks,
The SCA specification is developed by a group of collaborators including
IBM, BEA, Oracle, SAP, Sybase, IONA and Interface21 (soon to be expanded).
The collaborators work under a legal agreement which guides how
contributions are made to the specification and also defines how
material i
Paul,
I'll try to spell out the way that the SCA Specification
collaboration works and the IP rules that apply. I'll
do this in a post following from Mike Rowley's note on
"Project IP"
Yours, Mike.
Paul Fremantle wrote:
Jim
I understand the IP and Royalty requirements of the published
+1 from me.
Mike.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
+1 - go for it!!
Yours, Mike.
Jean-Sebastien Delfino wrote:
Hi!
I created source and binary distributions of the latest Tuscany
Milestone 1 release candidate level (SVN revision r407596) and placed
them in my home directory:
http://people.apache.org/~jsdelfino/test-incubating-M1/tuscany-inc
Hi Andrew,
Welcome aboard!
You will not need to feel "out on a limb" by being in the UK - there are
quite a few of us Brits working on Tuscany and SCA - especially the C++
implementation. We're mostly based in Hursley, near Winchester.
Yours, Mike.
Andrew Borley wrote:
Hi Everyone,
Afte
Simon,
This sounds good to me.
The more public stuff the better.
Yours, Mike.
Simon Laws wrote:
Pete has recently followed the java team's lead and initiated a "to
do"/"wish list" up on the Tuscany wiki for the C++ implementation effort.
The PHP/SDO PECL project needs to do the same thing b
+1 [x] java/samples/bigbank
Jean-Sebastien Delfino wrote:
I'm not sure that we really have decided on a good name for our top
level "samples" directory, currently java/samples/.
This directory hosts "samples". They are of a different nature than the
"technology samples" under sca/samples, das
I think that the principle of building a test case that demonstrates the
problem is a good practice. If there is a problem, them it is almost
always the case that the current test suite does not find the problem.
To ensure a fix, then *someone* has to build the test, which needs to be
added to
+1 from me, Jim
James F Marino wrote:
I've noticed several issues have been logged against the Java
container where entire Maven projects or samples are used to
demonstrate a problem. Sometimes this may be unavoidable, but I would
like to propose that we get into the habit of submitting failing
+1
Start with a user list now - good way to separate out issues that people
have when trying to use Tuscany rather then in developing pieces of it.
Yours, Mike.
Sounds like a good idea to me too. If I was going to look at Tuscany to
help me understand what SCA, SDO and DAS are, and play with,
I really would like to make a distinction here between source form
documents and final form documents.
I agree that anything placed on the website as a final form document
should be in a generally acceptable "open" form. HTML, Maven Xdoc,
PDF, for example. Word documents are NOT acceptable a
+1
Jeremy Boynes wrote:
This directory contains the seed code from BEA and IBM. Things have
moved on quite a bit since then so I would like to suggest we remove
this code from the tree - old versions can still be found in the SVN
history if needed. This tree has been modified so no longer repres
Ant,
At the moment, neither the SDO nor the SCA specification lists are
publicly viewable.
For SCA, we are investigating setting up a public website - one function
of this website would be to allow for publicly viewable lists.
Yours, Mike.
ant elder wrote:
On 3/9/06, Mike Edwards <[EM
Folks,
I notice a number of JIRA issues raised against the SDO C++
implementation that have the smell of being specification issues rather
than implementation issues.
If the issues really do imply changing or extending the specification of
SDO for C++, then I believe that the issues should r
Folks,
The process for making changes to the Tuscany web site is now easier,
thanks to some work by Rick Rineholt.
You can prepare the changes to the source on your own workstation, build
the site and submit the target output to the live site on apache with a
couple of Maven 2.0 commands, as
Sebastien,
I can see the advantage of this from a development perspective, so I'm
OK with it.
However, when we eventually deliver binary builds, I'd hope that all the
binary tools would end up in one place since end-users may not easily
see the distinctions between the different tools.
You
Jason Henley wrote:
I would very much like to get involved in this project. I have gone through the entire archive and
website, but I am still having some trouble getting my environment set up. I can pull the code down
and run maven from the command line, but I am assuming most of you guys ar
Folks,
I've updated the Tuscany website material.
The major changes are:
- the source material and the target material generated by Maven are now
in a site subproject
- switched to using Maven 2.0 for the site build process
- updated the "How to Build Site" page to reflect the new organisat
This sounds good to me.
Yours, Mike.
Jeremy Boynes wrote:
On 1/31/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
Yes, we shouldn't allow anonymous users to raise issues, we got the same
recommendation from Paul who ran into problems with this in the Synapse
project, but logged on user
Kevin,
It works for me now - there must have been some temporary problem.
Yours, Mike.
Kevin Williams wrote:
I am unable to reach our SVN repository
(https://svn.apache.org/repos/asf/incubator/tuscany/java). I also
notice that our web site (http://incubator.apache.org/tuscany/) is not
res
I suppose this would mean that any authenticated contributor could raise
, assign, modify and close issues. I suppose this isn't really a
problem - as long as the person doing the changes is known and recorded.
It is probably better to allow this than to burden the committers with
the chore o
Folks,
The Tuscany web site has been updated today. All pages and links should
be present now.
I'd appreciate comments on the content, especially on any links that you
think we should have to the more detailed project documentation such as
Javadoc and readme files.
Yours, Mike.
Folks,
Regarding the issue of who should be given privileges on JIRA, it seems
to me that all Tuscany committers should be given the privileges to
assign, modify and close issues.
Regarding the status of developers who are contributing but who are not
committers, I think that if they cannot
Hi,
I've got a JIRA ID (edwardsmj) but this is just at regular jira-user
priviledge level. How can I get my ID to have the priviledges to enable
me to update / assign issues, please?
Yours, Mike.
Folks,
The main page of the Tuscany web site is now live at:
http://incubator.apache.org/tuscany/
I am working to get all the subsidiary pages up and live
on the site.
Mike Edwards.
Jack,
+1 to this suggestion too.
I think Maven2 is far enough along now - and much of the
documentation and help relating to Maven is heavily focussed
on Maven2, so making the switch is necessary in the near future.
Yours, Mike.
[EMAIL PROTECTED] wrote:
If no one else is working on this, and
Kevin,
Take a look in the /trunk/docs directory on SVN.
Soon, we will have much of this stuff linked from the Tuscany
web pages - I'm working on that.
Yours, Mike.
lee zhenghui wrote:
Hi,
I have been looking for SCA framework for a long time. I am excited that
there is a open source fram
James Strachan wrote:
...snip
We should bring it up with the spec group.
Just out of interest; is the spec group a private separate mail list?
It might be worth using a tuscany mail list for public discussions of
the spec. I guess we could just reuse the dev list and use a [spe
James,
Here is my view of the questions you have with regard to the SCA spec:
James Strachan wrote:
BTW I really like the SCA specification, though coming from a POJO /
Spring background the distinction between @Reference and @Property
seems a little surprising at first - I just wanted to de
301 - 361 of 361 matches
Mail list logo
