On 5/30/06, Geoffrey Winn [EMAIL PROTECTED] wrote:
Simon,
On 26/05/06, Simon Laws [EMAIL PROTECTED] wrote:
A long time ago I posted about doing some interoperability testing. I've
got
back to this now and I've put some ideas about how we do this on the
wiki,
here
Coming up with a new management API sounds like it will take some time, I'd
like to be able to get at the list of components today, and then change the
code later when The Spec Group or whoever come up with an official API.
Seems like there's three things that could be done:
1) Use the hack
The build-dist.bat is the correct way, please go ahead and raise a JIRA.
Thanks,
...ant
On 5/27/06, Luciano Resende [EMAIL PROTECTED] wrote:
Hi
The following page have instructions on how to run the sample apps
http://incubator.apache.org/tuscany/projectjava.html
It currently says :
[ http://issues.apache.org/jira/browse/TUSCANY-419?page=all ]
ant elder reassigned TUSCANY-419:
-
Assign To: ant elder
Template XML for JavaScript components
--
Key: TUSCANY-419
URL:
Thanks Ant.
I have got the POM done. I am just making sure I have got all the
runtime dependencies. I will write up some simple instructions to run
this using one of the spaces implementations (I have tested it with the
JINI starter kit) and try to submit it by COP today.
I may start looking at
[ http://issues.apache.org/jira/browse/TUSCANY-419?page=all ]
ant elder reassigned TUSCANY-419:
-
Assign To: (was: ant elder)
Template XML for JavaScript components
--
Key: TUSCANY-419
URL:
[ http://issues.apache.org/jira/browse/TUSCANY-435?page=all ]
ant elder reassigned TUSCANY-435:
-
Assign To: ant elder
Spaces binding for SCA
--
Key: TUSCANY-435
URL:
Dear Release Managers,
[Sorry for the cross post!]
Please don't make a release unless there are 3 binding votes from pmc
members. We need it for legal purposes.
There is one more quirk about what we actually vote on. HTTPD pmc
votes on a svn tag and then the release managers cut binaries
The SCA Assembly Model specification (0.9) gives database stored procedure
as an example of a binding type. I've had a bit of a scout around the
Tuscany site and in Google and there is discussion of interacting with
stored procedures via SDO, i.e. using a relational DAS. Before I have a go
does
I'd prefer we come up with a management API as that is the only
solution that will work properly. More comments inline
On May 31, 2006, at 1:25 AM, ant elder wrote:
Coming up with a new management API sounds like it will take some
time, I'd
like to be able to get at the list of components
Hi,
Can we update the page
http://incubator.apache.org/tuscany/userguidejava.html with information for
the Your First Tuscany Application and FAQ. These sections have been
empty for a while now. To start with we could point to the pdf on
Simplified Big Bank application on the 'documenation'
How about having a management API for Tuscany?
The use case i have right now for this is so a J2SE client to can find out
what are the valid service names it can use in the locateService method on
the org.osoa.sca.ModuleContext interface. This is to make the JavaScript
interactive client able to
So much talk and so few management API proposals...ok, lets give this a try
and see if we can get some quick discussion iterations and there's no
suggestions to ask the spec group what they think until there's a working
way to get at the names of the services in a module. I'll start this on
instructions on how to run the sample apps should point to run build-dist.bat
--
Key: TUSCANY-438
URL: http://issues.apache.org/jira/browse/TUSCANY-438
Project: Tuscany
Type: Bug
[ http://issues.apache.org/jira/browse/TUSCANY-438?page=all ]
Luciano Resende updated TUSCANY-438:
Attachment: patch-TUSCANY-438-projectjava.xml
Patch for projectjava.xml
instructions on how to run the sample apps should point to run
I think these are good suggestions. Having an FAQ that is updated
frequently based on real user questions on common newbie issues
would be a great help in enabling new users to overcome initial
obstacles to using Tuscany.
The BigBank pdf document does a good job of describing the code
and other
I have seen in a couple of offlist email discussions about prospective
committers but I am concerned that not all committers may be on them.
IIRC Ant had suggested we create a private or PPMC list for all
committers and I think that would be a good idea.
Dims, Sam, Geir, could someone with
Hi Ant,
Obviously the easiest way to do this is adding whatever methods we need into
classes where those methods reside naturally. But I do not see those methods
can be qualified as management APIs. If your intention is to have APIs that
potentially can be exposed to management/instrumentation
18 matches
Mail list logo