Jean-Sebastien Delfino wrote:
[snip]
Florian Rosenberg wrote:
Jean-Sebastien Delfino wrote:
Mike Edwards wrote:
Florian,
I'd point out that the recommended way of doing things is to add
things in your own namespace.
Adding stuff to the OSOA XSDs is not encouraged.
If using your own
Ashwin J [EMAIL PROTECTED] wrote on 09/26/2007 09:46:09 AM:
Hi Simon,
Thanks for your reply.
I am facing the same problem in 0.99 release also.
the javacError in your stacktrace probably indicates an error in your
environment setup, Tomcat can compile the JSPs to servlet (internally). to
be
Jean-Sebastien Delfino [EMAIL PROTECTED] wrote on 09/25/2007 12:24:55
PM:
Florian Rosenberg wrote:
hi raymond,
On Sun, September 23, 2007 2:31 pm, Raymond Feng wrote:
Hi, Florian.
Can you elaborate a bit on why you need the component name during the
read/resolve phase for your
that you can't introspect the splice implementations
for the relevant information, of course...
i'm working on that right now. should be finished soon.
Thanks again for your insights.
-Florian
Florian Rosenberg wrote:
folks,
I'm writing a component impl type and in my artifact processor I
of the component type. The spec says the name of
the componentType file and the composite file should match (if I remember
correctly)/
Thanks,
-Florian
- Original Message -
From: Florian Rosenberg [EMAIL PROTECTED]
To: tuscany-user@ws.apache.org
Sent: Saturday, September 22, 2007 9:23 PM
folks,
I'm writing a component impl type and in my artifact processor I would need
the name attribute from a component defined in the composite file to be
able to use a constistant resolving mechanism for my componentType files
that describe the component.
Example:
component name=FooComponent
11:17:52
PM:
Florian Rosenberg wrote:
hi,
we have created a component implementation for a small RESTful
composition
language which does not support references to other components, now we
want
to add support for that. The component implementation is similar to
BPEL,
but without all
hi,
we have created a component implementation for a small RESTful composition
language which does not support references to other components, now we want
to add support for that. The component implementation is similar to BPEL,
but without all the WSDL and partnerlink stuff. Just support for
hi skip,
Skip Schuler [EMAIL PROTECTED] wrote on 08/27/2007 02:13:57 PM:
I'm trying to leverage the atom and rss bindings to expose some feeds
using
java sca build 0.91. More specifically I'm trying to deploy a war on my
Tomcat instance. I have a class that implements
hi,
I'm implementing a component type for running RESTful workflows (or
compositions - whatever you wanna call it) within SCA. The implementation
worked fine but since I updated to the latest SVN head today it get the
following error message when running it. After some time of debugging I
/22/07, Florian Rosenberg [EMAIL PROTECTED] wrote:
hi,
I'm implementing a component type for running RESTful workflows (or
compositions - whatever you wanna call it) within SCA. The
implementation
worked fine but since I updated to the latest SVN head today it get the
following error
open a jira issue for that?.
-Florian
On 8/22/07, Florian Rosenberg [EMAIL PROTECTED] wrote:
hi,
I'm implementing a component type for running RESTful workflows (or
compositions - whatever you wanna call it) within SCA. The
implementation
worked fine but since I
as the CRUD component. I was working
yesterday before the SVN update.
Thanks,,
-Florian
- Original Message -
From: Florian Rosenberg [EMAIL PROTECTED]
To: tuscany-user@ws.apache.org
Sent: Wednesday, August 22, 2007 11:08 AM
Subject: Re: component type impl
Luciano Resende [EMAIL
in the
org.apache.tuscany.sca.contribution.processor.StAXArtifactProcessor:
com.ibm.sca.implementation.splice.SpliceArtifactProcessor;type=http://www.osoa.org/xmlns/sca/1.0#implementation.splice,model=com.ibm.sca.implementation.splice.SpliceImplementation
but actually the type= is now qname=. It works again.
-Florian
- Forwarded by Florian Rosenberg
hi SCA folks,
I'm pretty new to SCA and I want to develop a new component type
implementation, similar to BPEL (sorry for any terminology mismatch). The
stuff I'm currently having here is basically a composition engine for
RESTful services which I currently running on Tomcat (as a servlet with
15 matches
Mail list logo
