On 4/24/07, Kevin Williams [EMAIL PROTECTED] wrote:
Hi Sebastien,
The test runs fines from /http-tomcat.
--Kevin
On 4/24/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
[snip]
Kevin Williams wrote:
Now, I am getting the Connection refused error:
INFO: Stopping Coyote HTTP/1.1 on
On 4/25/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Simon Laws wrote:
On 4/24/07, Kevin Williams [EMAIL PROTECTED] wrote:
Hi Sebastien,
The test runs fines from /http-tomcat.
--Kevin
On 4/24/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
[snip]
Kevin Williams wrote
On 4/25/07, Simon Laws [EMAIL PROTECTED] wrote:
On 4/25/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Simon Laws wrote:
On 4/24/07, Kevin Williams [EMAIL PROTECTED] wrote:
Hi Sebastien,
The test runs fines from /http-tomcat.
--Kevin
On 4/24/07, Jean-Sebastien Delfino
On 4/24/07, Simon Laws [EMAIL PROTECTED] wrote:
Following Sebastiens post about the databinding test locking up (he went
ahead and removed it from the itest pom to get the build to work) I tried
the test and, once I had changed the poms to depend on http-jetty as they
used to, I got the same
On 4/25/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
ant elder wrote:
On 4/25/07, Simon Laws [EMAIL PROTECTED] wrote:
On 4/25/07, Simon Laws [EMAIL PROTECTED] wrote:
On 4/25/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Simon Laws wrote:
On 4/24/07, Kevin
I talking to a user of the PHP SDO implementatio about a problem they have
where SDO fails to parse an XML file with the error:
SDO_DAS_XML_ParserException - unknown element errors...
Looking at the code what seems to be going on is that annonymous types are
being overwritten when the
On 4/24/07, Simon Laws [EMAIL PROTECTED] wrote:
Following on from the release content thread [1] I'd like to kick off a
discussion on how we resurrect support for a distributed runtime. We had
this feature before the core modularization and I think it would be good to
bring it back again
Have just checked out the build I had to fix up
samples/helloworld-ws/pom.xml to change the artifactId from
sample-helloworld-ws to tuscany-sample-helloworld-ws as
helloworld-wsclient depends on tuscany-sample-helloworld-ws.
This made me look at the others and there are a variety of forms of
.
Cheers,
On 27/04/07, Simon Laws [EMAIL PROTECTED] wrote:
I talking to a user of the PHP SDO implementatio about a problem they
have
where SDO fails to parse an XML file with the error:
SDO_DAS_XML_ParserException - unknown element errors...
Looking at the code what seems to be going
On 5/1/07, Pete Robbins [EMAIL PROTECTED] wrote:
Simon, I'll take a look at this. It may be fairly simple to mirror what
the
Tuscany Java implementation does.
On 01/05/07, Simon Laws [EMAIL PROTECTED] wrote:
On 4/30/07, Frank Budinsky [EMAIL PROTECTED] wrote:
This is an open issue
On 5/1/07, Pete Robbins [EMAIL PROTECTED] wrote:
I've checked in a fix to append 1, 2 etc to anonymous type names that
clash. In your example you will get types Overlapping and Overlapping1.
Cheers,
On 01/05/07, Simon Laws [EMAIL PROTECTED] wrote:
On 5/1/07, Pete Robbins [EMAIL PROTECTED
On 4/30/07, ant elder [EMAIL PROTECTED] wrote:
Excellent thanks, thats type type feedback I was looking for! Comments in
line...
On 4/30/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
snip/
I have a few questions and suggestions.
- tuscany-sca.jar contains .svn directories, I guess
On 5/2/07, ant elder [EMAIL PROTECTED] wrote:
On 5/2/07, Simon Laws [EMAIL PROTECTED] wrote:
On 4/30/07, ant elder [EMAIL PROTECTED] wrote:
Excellent thanks, thats type type feedback I was looking for! Comments
in
line...
On 4/30/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote
On 5/2/07, Simon Nash [EMAIL PROTECTED] wrote:
I saw the following discussion in Monday's IRC chat log. (I couldn't
attend the chat because I was on a plane.)
[12:37] ant_ oh, so with the samples again, I guess we need Ant build
scripts
[12:37] ant_ lresende, it does right now and i think
On 5/2/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
[snip]
Simon Laws wrote:
- tuscany-rmi? Should this be a binding
Yes, would be better as tuscany-binding-rmi.
We already have a tuscany-binding-rmi module: the implementation of the
RMI binding.
The tuscany-rmi module defines
On 5/2/07, ant elder [EMAIL PROTECTED] wrote:
I'm trying to change tuscany-itest-databindings-sdo pom.xml to use
1.0-incubating-SNAPSHOT for the tuscany-sdo-plugin version as its been
changed to that from 1.0-incubator-SNAPSHOT but it keeps getting changed
back, i guess this is done by the way
On 5/2/07, ant elder [EMAIL PROTECTED] wrote:
On 5/2/07, Simon Laws [EMAIL PROTECTED] wrote:
On 5/2/07, Simon Nash [EMAIL PROTECTED] wrote:
I saw the following discussion in Monday's IRC chat log. (I couldn't
attend the chat because I was on a plane.)
[12:37] ant_ oh, so
in thread main
[java] Java Result: 1
Simon
ant elder wrote:
On 5/2/07, Simon Laws [EMAIL PROTECTED] wrote:
On 5/2/07, Simon Nash [EMAIL PROTECTED] wrote:
I saw the following discussion in Monday's IRC chat log. (I couldn't
attend the chat because I was on a plane.)
[12:37
On 5/2/07, Simon Nash [EMAIL PROTECTED] wrote:
I thought Ant's suggestion was just 0.90 and not beta anything. I can
live with this. I don't think we are ready yet to call it beta 1.0
or beta1 1.0.
Simon
haleh mahbod wrote:
why does it matter if we call it beta1 or beta .90? It is a
On 5/3/07, ant elder [EMAIL PROTECTED] wrote:
On 5/3/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Simon Nash wrote:
Here is the complete list of dependencies loaded by the code in
tuscany-sca-all-1.0-incubating-SNAPSHOT.jar when starting the
Tuscany core runtime.
(XML
Hi, some comments in line
There has been many commits and good progress the last few days, so I
spent a little bit of time checking the status of the trunk.
Here's a summary of what I found:
- The code cleanup is almost complete, I think there's a little bit work
left to refactor one last
Hi
I'm working steadily through the samples...
- Converting readmes to simple text READMEs and updating where appropriate
- Adding build.xml (or mulitple as required) to provide an ant build for the
binary distribution
- Adding a diagram of the sample composite (not necessary for the
I've seen much discussion on the list re. a webapp solution. There is now a
calculator-web sample but it seems to be the same as the calculator sample.
Is this a work in progress?
Regards
Simon
PROTECTED] wrote:
Ok, i'll do at least one to help review how its done, i'll start at the
bottom with the supplychain sample.
...ant
On 5/8/07, Simon Laws [EMAIL PROTECTED] wrote:
Hi
I'm working steadily through the samples...
- Converting readmes to simple text READMEs and updating
I tried running the calculator-web sample this morning and got an NPE in
calc.jsp. I'm guessing but it looks like it can't find the domain instance,
i.e.
application.getAttribute(org.apache.tuscany.sca.SCADomain);
Returns null.
To set up all I did was run mvn to build the war then I dropped
So what is it using doamin uri for. Looking at the sca-contribution.xml in
the assembly spec there doesn't seem to be any information that I would
equate with the uri of a domain. Then again I don't know what Tuscany is
using the domainUri for yet!
Simon
On 5/9/07, ant elder [EMAIL PROTECTED] wrote:
On 5/9/07, Simon Laws [EMAIL PROTECTED] wrote:
So what is it using doamin uri for. Looking at the sca-contribution.xmlin
the assembly spec there doesn't seem to be any information that I would
equate with the uri of a domain. Then again I don't
+1 to including java -cp instructions. The samples/README (to which the
reader is referred) contains this already. Do you want it included in
individual READMEs too?
I'm not sure I really like distributing sample jars. But it is fairly easy
to make the jars and give people the option of how they
What's the process for controlled commits. Patches?
The release process takes a resonable amount of time when you include the
time to vote on it and the possibiliy that faults will be found and we have
to fix and vote again. So when do we think we will be in the position to
roll a release
Ok, The scripts already take account of the missing JUnit so let's not
change that just yet.
Happy to go add the Java -cp run line to the READMEs and the jar command to
the build.xml. I have a NPE in the WS tests when run from the command line I
have to fix first.
B.t.w the binary distro
Hi Jacek
I should add that we are working on the samples/readmes etc for the current
release right now now so if you do give it a try and let us know what you
think that would be great.
If you can't face svn we are going to start trying out candidates for the
release candidate (!) later today
opinion on this.
Simon
ant elder wrote:
On 5/10/07, Simon Laws [EMAIL PROTECTED] wrote:
snip/
B.t.w the binary distro includes bigbank, das-service and
loan-application
none of which are in the build currently. We should either fix them or
remove them.
Thanks, I've excluded those
I've checked in changes to allows the provided jar to be run (and built).
Outstanding is the issue of including classes from
src/test in the sample jar or alternatively moving the application classes
to src/main. This effect of this currently is that
binding.echo
databinding.echo
snip
I don't think the client that is used should be different
depending on whether ant or mvn was used to run the sample.
In both cases I think calculatorClient should be used.
So we would need to engineer the poms in the build to run the new client
classes rather than the junit classes. I
Simon
I get the same effect here. It's because the shaded bundle jar can't be
copied over the original jar. The shader plugin that is used here is alpha
and has zero docs so I really can't tell what it's doing or why it's going
worng without diving into the code. I took a quick look but I
Hi, so it looks like you were building Data Access Service (das) here. I
just tried and it works for me (sorry that's not much help to you). I have
to admit though that we don't build this currently as part of the sca build
as das doesn't get used in any of the sca tests just at the moment.
If
Done http://issues.apache.org/jira/browse/TUSCANY-1265. I'll take a look at
it a little later.
Simon
Hi, I was thinking about this problem the other way round
At the moment the binary distribution builds with the following structure
(taking binding-echo and simple-bigbank as two examples)
docs/
lib/
modules/
samples/
binding-echo
src/
main/
extension sample code
test/
at this from different
angles. So probably need others opinions to see which way to go.
Some more comments in line taking this into account.
On 5/11/07, Simon Nash [EMAIL PROTECTED] wrote:
Thanks for the detailed review and comments. My responses are inline.
Simon
Simon Laws wrote:
Hi, I
I'm probably stating the obvious and I'm guess this is the motivation behind
Ant's question but I don't see the DAS itself in the bindary distro. Is the
proposition to ship the DAS jar(s) as part of the SCA distiribution? I'm not
expressing an opinion here just working out what the question is;-)
I'm having problems with the latest check in. On a fresh update and mvn from
the top level I get
---
[INFO] Building Apache Tuscany Interface Model
[INFO]task-segment: [install]
[INFO]
-
---
[INFO] artifact
I, ahem, invented the missing
org.apache.tuscany.sca.interfacedef.ConversationSequence class
public class ConversationSequence {
public static ConversationSequence CONVERSATION_NONE = null;
public static ConversationSequence CONVERSATION_START= new
ConversationSequence();
public
yep - looks good for me too. Thanks all.
So let me try and summarize...
All samples will be:
samples/
src/
main/
sample code
client code (non-junit)
test/
junit tests
ant compile- compile the sample
ant (run) - run the sample
ant test - run the Junit tests
mvn -
On 5/13/07, Simon Nash [EMAIL PROTECTED] wrote:
Simon Laws wrote:
So let me try and summarize...
All samples will be:
samples/
src/
main/
sample code
client code (non-junit)
test/
junit tests
Does this mean that client code would become part
snip
My suggestion was much simpler, i.e., that we could keep the client
code out of the sample extension jar and include a .class file for the
client code for these 3 samples in the binary distro. This is similar
to what real users will do when developing extensions.
Making this happen is
ok - well we can do that and it's pretty much zero change as that is where
we are at the moment, i.e. you have to build the sample before you run it. I
don't think providing ant scripts is a problem as we could make the run
target depend on the compile target for the three extension samples.
On 5/15/07, ant elder [EMAIL PROTECTED] wrote:
This looks really good. I've fixed the distributions now to not include
the
the das-service, and tomcat work directories, and the few .pmd type files
missing licenses so RAT should look pretty clean now.
...ant
On 5/15/07, Venkata Krishnan
I already tried that to no avail :-(
Simon
I have some questions about how we are using cwiki
From the original request for creation of our space [1] I see that rfeng is
the group admin for tuscany-committers. Are you able to add other committers
as admins? Would be good to have more than one (you may already have done
this of
Good thinking re. getting mails sent out. I'll look into it to see if we can
do it if you like.
Simon
For those interested in SCA and SDO in PHP, version 1.2.1 of the SCA_SDO
package for PHP has been released. This package uses the Tuscany C++ SDO
code. FYI here's the release announce.
Ok sounds good to me. Assuming everyone is happy for this to go in now we
can tidy this up pretty quickly I think. If SimonN creates three new
projects to hold the client/application code for the extension samples I'm
happy to take a look at the patches and commit. I can also go and fix up the
Thanks for the comments raymond, some more in line
On 5/15/07, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
Please see my comments inline.
Thanks,
Raymond
- Original Message -
From: Simon Laws [EMAIL PROTECTED]
To: tuscany-dev tuscany-dev@ws.apache.org
Sent: Tuesday, May 15, 2007 3
Following on from Jean-Sebastien's SPI point. There are still open issues,
e.g. [1] related to SPIs that we choose to put where. I'm only now getting
to grips with what has been done in the reorganization effort (apologies for
not keeping up) and am spotting some things that, on the face of it,
Sorry Ant. I wasn't clear myself. The bit that is cryptic (to me) is how the
extension actually works not how to use it necessarily. Looking at the the
reverseAJAX bit is where I go a little lost. I think I get it now though.
So, having read your explanation, I see why you went for binding.ajax.
Ok, I took a look at the patch and committed it. I made a few minor changes:
package name changed to crud
include copy of composite file from implementation-crud
move diagrams from implementation-crud
But looks good.
Last update relating to this was at revision 538481.
The binding-echo and
On 5/16/07, Simon Nash [EMAIL PROTECTED] wrote:
Simon,
Thanks for committing this. See comments inline below.
Simon
Simon Laws wrote:
Ok, I took a look at the patch and committed it. I made a few minor
changes:
package name changed to crud
I deliberately changed the package name
On 5/16/07, Simon Laws [EMAIL PROTECTED] wrote:
On 5/16/07, Simon Nash [EMAIL PROTECTED] wrote:
Simon,
Thanks for committing this. See comments inline below.
Simon
Simon Laws wrote:
Ok, I took a look at the patch and committed it. I made a few minor
changes:
package name
Looking at the databinding-echo sample I realize now that it is not showing
how to define a new databinding but using the sample echo binding to show
how the existing databindings work. However the source code from
binding-echo is duplicated here which is not great. I propose that instead
of
No go ahead - I'm testing the other samples at the moment.
Simon
I've started getting an NPE in some of the samples when I run in the binary
disitrbution from ant. It works fine running from maven. Has some extra
dependency crept in that I'm not taking account of in the build.xml files.
Here's an example
ples\helloworld-ws-serviceant run
Buildfile: build.xml
It's because the SDO classes are not in the SCA all jar now.
Simon
On 5/16/07, Simon Laws [EMAIL PROTECTED] wrote:
It's because the SDO classes are not in the SCA all jar now.
Simon
for all read manifest.
Ant pointed out on irc that the distro build sometimes does strange things
and includes an sdo jar with the wrong name in the distribution lib dir
Having to think about release notes kicked off a thought. I've been back to
the wiki and reorganized the Wish List [1] and Next Release [2] pages a
little to help us do this next time round.
I've translated the notes we made on the precursor to these pages [3]. I
would like to add a feature list
Nice list. Just to be clear. When you say, for example,
org.apache.tuscany.sca.assembly
Do you mean just the interfaces in this package or do you include interfaces
from any of the subpackages? For example,
org.apache.tuscany.sca.assembly.builder
Simon
I haven't found a solution to this yet. I involves debugging through the
shader plugin and I have got round to that yet. I have a very ugly and
manual work round that allows me to get on. Here is what I do:
1/ Edit sca/disitribution/pom.xml to remove bundle reactor reference so that
I can do the
Currently the sample overview section of the samples/README contains some
very high level words about what samples we have but nothing to guide the
user in. Ant suggested on the IRC that we add and ordered list. How about
the following order
calculator - A calculator build
Hi Mike
I've just refereshed the Wish list up on the web site (
http://cwiki.apache.org/TUSCANY/sca-java-wish-list.html). Do you want to put
a note there about the spring stuff you are looking at?
Simon
OK, done at revision 538871.
On the subject of samples. I'm just adding the mission README and build for
the jsonrpc sample. Does this work for you now?
Simon
You are a star Venkat, I'll give it a spin. Then I want to fiddle with the
build files a little. I'm going to move the current build.xml to
build-dojo.xml and introduce a new build.xml to allow the sample to be built
using ant. I'll fix up the pom to take account of this change
Simon
snip
If yes, I'll go ahead and add it to the website ( I'll need help for
doing this correctly please ).
If you want to put a logo up on the site in place of the confluence logo
(the man type thing with a C wrapped round him) then there is an option
under space admin to set the space
Ant
Have just been tidying some of the core-spi comments. Done a complete
rebuild and looks OK in the branch. Are you happy for me to check them into
the release branch?
Simon
I've added a CHANGES file [1] to the 0.90 branch to include a feature list
for this release. I've moved the SPI details from RELEASE_NOTES to this file
and I've included the file in the distribution build. I included a section
noting that we address all parts of the Java API and Annotations spec
The distribution build in the release 0.90 branch works fine for me all the
way through, Very strange!
Simon
Hi
I'm all for sorting out the sample naming to bring more consistency but I
would stop short of recombining the application and extension samples. Simon
is right that there we faced technical dilemmas [1] but I'm sure everything
could be made to work however we wanted to lay these samples out.
This time round, as so much had changed, we didn't include JIRA numbers in
the release docs. It seems like a good thing to do in the future though. If
everyone agrees that this is a good thing we need to be fairly organized
about how we use JIRA otherwise we suffer a lot of pain come release time
I've given the src and binary distros a spin on linux. My configuration is
Fedora Core5
IBM JDK 1.5.0
Maven 2.0.6
Binary:
I concur with Luciano that the READMEs for
calculator-rmi-reference
calculator-rmi-service
implementation-crud
now don't match the way that the samples are currently
OK, I agree. I note that SDO already does this. Any more thoughts about
things we can do to improve the way we can all work in this area? What else
do SDO, DAS do that SCA needs to do? Maybe we can come up with a checklist
for the build and release up on the developer guide section of the web
OK, so I can't get the compile to work on my linux box with a simple change
to the version/location of the maven-jaxb-plugin that the build uses. I'm
going to upgrade my JDK and see if that has a positive effect but of course
that has no bearing on the SCA release. As this problem is restricted
Hi
Just started looking at this in the context of bringing the aggregator
sample to the Java runtime. I like the idea of having a dynamic interface as
an option as it reduces the amount of configuration. The term dynamic term
confused me to start with - I initially thought this was about
+1 XXX-Next
I don't mind who assigns JIRA to the release number. It can't be done though
until we know that the release number will be (was quite late in the last
cycle). Hopefully we will do more frequent releases from now so there will
be few JIRAs in the XXX-Next box and more with the actual
Ant
Wow, thats what I call a list. I can add a couple of things to the list that
I want to work on for the next release.
Runtime
Distributed domains (simple version of anyhow)
Demos
Port feed aggregator over from Native SCA - has implications for scriting
so I can help out there a bit.
So
I didn't. I looked at both versions of maven-jaxb-plugin at
https://maven-repository.dev.java.net/repository/com.sun.tools.xjc.maven2/poms/and
both have the odd characters in. There seem to be other
implementations
of the maven-jaxb-plugin around and I tried the ones I could find but got
NPEs in
+1 for
- Have three builds, that would build each project separately
Simon
Hi Venkat, sounds great. Can I just ask, when you say...
snip
- Get the navigation bar of our wiki site
http://cwiki.apache.org/confluence/display/TUSCANY/Home to look like a
classic navigation bar with menu items
Do you mean the one on the left hand side or the tabs at the top or
something
Hi Jacek
It's because we haven't pushed any snapshots out to the Apache Incubator
repository yet. Primarily this is because the code has been changing a lot
in the run up to the current 0.90 release vote and we have concentrated on
getting all the modules to build together rather than pushing
I fixed the sample problems when we mentioned them before (that's 5 and 6
from Sebatien's list). I can look at other things first thing as it sounds
like we are going to respin. Too tired now to get it right.
I still don't think we wait for a fix for my build problem. It's the first
time it's
I just ran a build this morning and it looks like some kind sole has
deployed some snapshots so it may work now. I only say may as I haven't
tried from a completely clean repo yet.
Regards
Simon
Ok, good, thanks. FYI. On the Confluence installation over at osoa.org there
is a Left Navigation Theme in place that organizes this left had menu for
us. You still edit the menu as a wiki page but just a little bit more
organized. I note that this is also available in the Tuscany space (see
OK, below is an errata based on the points that people have highlighted as
important in this thread. Anything else need to be added? Anyone have any
better words for installing samples from the binary distro in Eclipse or any
words at all for IDEA. Now we have most people's comments in, this is
Cool. Look forward to reading the article.
Simon
On 4/30/07, Simon Laws [EMAIL PROTECTED] wrote:
On 4/24/07, Simon Laws [EMAIL PROTECTED] wrote:
Following on from the release content thread [1] I'd like to kick off a
discussion on how we resurrect support for a distributed runtime. We had
this feature before the core modularization
From a clean install of RC2 and an empty local repo...
I tried a selection of the samples in the binary distro using ant scripts.
All OK
I built the source distiribution. It took a lng time (3 hours!) to get
through it all told. In my case this seemed to be primarily that the repo
hosting
Hi Tony,
I'm assuming you are using the sample CalculatorClient style code try to
access the service, i.e. the part that uses the scaDomain to get a local
reference to a component service.
CalculatorService calculatorService =
scaDomain.getService(CalculatorService.class,
Re. the point about how to link extension descriptions into the site. We
have a page called Extension Guide (distinct from the Extension Developers
Guide) that is on the left hand menu and lists all the extensions and should
be linked into the description pages like the one Ant has just made.
I should have included a link to the extension guide page - here it is
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+Extension+Guide
Simon
Thanks for the help Hernan,
This is really good stuff.
Simon
Starting to look a lot better.
Venkat +1 for info in release right on the front page. Instead of, or as
well as, the Release Notes can you include the information from the Changes
doc which tells people what is in the release?
Also I note that the link to the Extension Guide has gone missing.
I don't think there is a right answer here as it mainly comes down to
personal preference. How we each like to see information presented. If I
were travelling in my car I'd prefer to read a line on a map, many people I
know would much prefer to read a list of written instructions (turn right
301 - 400 of 1885 matches
Mail list logo
