Fwd: Graduation
Forwarding for those not on tuscany-dev... Congratulations everyone and a very big thank you to our mentors and all the incubator folks for their help and guidance during the incubation, wouldn't have made it without you. ...ant -- Forwarded message -- From: Matthieu Riou [EMAIL PROTECTED] Date: Wed, May 21, 2008 at 10:14 PM Subject: Graduation To: tuscany-dev [EMAIL PROTECTED] Special order 7B, Establish the Apache Tuscany Project, was approved by Unanimous Vote of the directors present. Congratulations guys! Matthieu
SCA Tools Project newsgroup
Hi, An Eclipse newsgroup named SCA Tools was created to discuss about the Eclipse SCA Tools project: news://news.eclipse.org/eclipse.stp.sca-tools You need a password to access the newsgroup server [0]. SCA Tools is proposed as a sub-project under the top level project Eclipse SOA Tools Platform (STP) [1]. To know more, see the SCA Tools Project Proposal page: - http://www.eclipse.org/proposals/sca-tools/ the Eclipse SCA web page: - http://www.eclipse.org/stp/sca/index.php the Eclipse SCA wiki: - http://wiki.eclipse.org/STP/SCA_Component Thanks for your support. Best regards, Stéphane Drapeau Obeo [0]: http://www.eclipse.org/newsgroups/register.php [1]: http://www.eclipse.org/stp/
Re: Web Service References
Mike:
I don't know if you are talking about this sample:
https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/samples/helloworld-bpel-ws/
If it's the case, the helloworld.composite does not have a reference, it
simply exposes a BPEL implementation as a service.
I think I understand a bit better the rationale for not modeling external
references as components and why components need to have an
implementation. I am fine with it since a component must belong to a domain.
I have tried to do some cross-domain work by modeling a service (external to
the domain) invoked by a BPEL implementation and I get some errors. I don't
know if anyone could help me.
Here is my composite file (I replaced the GreetingsService component by a
reference to an external web service (implemented in a different domain)):
?xml version=1.0 encoding=ISO-8859-15?
composite xmlns=http://www.osoa.org/xmlns/sca/1.0; xmlns:sca=
http://www.osoa.org/xmlns/sca/1.0; xmlns:hns=http://helloworld;
xmlns:instance=http://www.w3.org/2004/08/wsdl-instance; xmlns:tuscany=
http://tuscany.apache.org/xmlns/sca/1.0; name=helloworld targetNamespace=
http://bpel;
component name=HelloWorldService
tuscany:implementation.bpel process=hns:HelloWorld/
reference name=greetingsPartnerLink /
/component
reference name=GreetingsService
promote=HelloWorldService/greetingsPartnerLink
tuscany:interface.wsdl interface=
http://laptop2:8085/GreetingsService#wsdl.portType(Greetings)/
binding.ws wsdlElement=
http://laptop2:8085/GreetingsService#wsdl.service(GreetingsService)
instance:wsdlLocation=http://laptop2:8085/GreetingsService.wsdl/
/reference
/composite
I do get a series of errors coming from the domain trying to implement this
composite:
[java] May 22, 2008 7:44:59 AM
org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor
read
[java] WARNING: Element {
http://tuscany.apache.org/xmlns/sca/1.0}implementation.bpel cannot be
processed. ([row,col {unknown-source}]: [4,5])
[java] May 22, 2008 7:44:59 AM
org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor
read
[java] WARNING: Element {
http://tuscany.apache.org/xmlns/sca/1.0}interface.wsdl cannot be processed.
([row,col {unknown-source}]: [8,5])
[java] May 22, 2008 7:44:59 AM
org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1 problem
[java] WARNING: No implementation for component: HelloWorldService
[java] May 22, 2008 7:44:59 AM
org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1 problem
[java] WARNING: Reference not found for component reference:
HelloWorldService/greetingsPartnerLink
[java] May 22, 2008 7:44:59 AM
org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1 problem
[java] WARNING: No implementation for component: HelloWorldService
[java] May 22, 2008 7:44:59 AM
org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1 problem
[java] WARNING: Reference not found for component reference:
HelloWorldService/greetingsPartnerLink
[java] No service is declared on component HelloWorldService
BTW, of course the greetings service is up and running and I can query its
WSDL (v1.1)
In the composite I did try both wsdl.interface and wsdl.portType and got the
same result (same interface.wsdl cannot be processed)
thanks,
JJ-
On Sat, May 17, 2008 at 7:29 AM, Jean-Jacques Dubray [EMAIL PROTECTED]
wrote:
Luciano, Mike:
thanks for the detailed answer. Yes, I am aware there are different types.
I am not so concerned having to declare an implementation within the same
domain. As a matter of fact, it looks to me that it is not even within an
entire domain, but within a composite since there is an implementation type
which is implementation.composite, so the scope to which an implementation
declaration is exposed is fairly limited (which is good).
I am more concerned of cross domain interactions and in particular how,
say, a .Net based web service gets assembled. In that case you won't be
able to find a valid implementation to expose as a composite. In cross
domain interactions you are also left to use Web Services technologies
(which I'm fine with, it'd be a shame to find no real use for WS-* after all
this energy spent :-).
Do you have a sample for that use case?
thanks,
JJ-
On Sat, May 17, 2008 at 5:34 AM, Mike Edwards
[EMAIL PROTECTED] wrote:
Jean-Jacques Dubray wrote:
Luciano:
thanks, actually in the test/bpel/helloworld-reference composite
definition
you also have a component defined with a binding.ws and there to, there
is
an implementation.java element. Is it required?
!-- Simple ws-reference --
!--
component name=HelloWorldService
implementation.java class=helloworld.HelloWorldServiceImpl/
reference name=greetingsService
binding.ws uri=http://localhost:8085/GreetingsService/
/reference
/component
--
Would you consider ws
Re: Web Service References
Good point, I removed the tuscany namespace that had been added by the
Composite Editor and the errors are gone
I do get however:
[java] Starting setup
[java] [INFO] - GeronimoLog.info(79) | Using embedded Geronimo
transaction manager
[java] java.lang.NullPointerException
The same behavior is true whether I use:
interface.wsdl interface=
http://192.168.2.2:8085/GreetingsService#wsdl.interface(Greetings)/
or interface.wsdl interface=
http://192.168.2.2:8085/GreetingsService#wsdl.portType(Greetings)/
JJ-
On Thu, May 22, 2008 at 8:49 AM, Luciano Resende [EMAIL PROTECTED]
wrote:
The errors you are getting usually means that the necessary
dependencies that register processors to parse those elements are not
available (e.g implementation.bpel and interface.wsdl).
On Thu, May 22, 2008 at 8:11 AM, Jean-Jacques Dubray [EMAIL PROTECTED]
wrote:
Mike:
I don't know if you are talking about this sample:
https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/samples/helloworld-bpel-ws/
If it's the case, the helloworld.composite does not have a reference, it
simply exposes a BPEL implementation as a service.
I think I understand a bit better the rationale for not modeling external
references as components and why components need to have an
implementation. I am fine with it since a component must belong to a
domain.
I have tried to do some cross-domain work by modeling a service (external
to
the domain) invoked by a BPEL implementation and I get some errors. I
don't
know if anyone could help me.
Here is my composite file (I replaced the GreetingsService component by a
reference to an external web service (implemented in a different
domain)):
?xml version=1.0 encoding=ISO-8859-15?
composite xmlns=http://www.osoa.org/xmlns/sca/1.0; xmlns:sca=
http://www.osoa.org/xmlns/sca/1.0; xmlns:hns=http://helloworld;
xmlns:instance=http://www.w3.org/2004/08/wsdl-instance; xmlns:tuscany=
http://tuscany.apache.org/xmlns/sca/1.0; name=helloworld
targetNamespace=
http://bpel;
component name=HelloWorldService
tuscany:implementation.bpel process=hns:HelloWorld/
reference name=greetingsPartnerLink /
/component
reference name=GreetingsService
promote=HelloWorldService/greetingsPartnerLink
tuscany:interface.wsdl interface=
http://laptop2:8085/GreetingsService#wsdl.portType(Greetings)http://laptop2:8085/GreetingsService#wsdl.portType%28Greetings%29
/
binding.ws wsdlElement=
http://laptop2:8085/GreetingsService#wsdl.service(GreetingsService)http://laptop2:8085/GreetingsService#wsdl.service%28GreetingsService%29
instance:wsdlLocation=http://laptop2:8085/GreetingsService.wsdl/
/reference
/composite
I do get a series of errors coming from the domain trying to implement
this
composite:
[java] May 22, 2008 7:44:59 AM
org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor
read
[java] WARNING: Element {
http://tuscany.apache.org/xmlns/sca/1.0}implementation.bpelhttp://tuscany.apache.org/xmlns/sca/1.0%7Dimplementation.bpelcannot
be
processed. ([row,col {unknown-source}]: [4,5])
[java] May 22, 2008 7:44:59 AM
org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor
read
[java] WARNING: Element {
http://tuscany.apache.org/xmlns/sca/1.0}interface.wsdlhttp://tuscany.apache.org/xmlns/sca/1.0%7Dinterface.wsdlcannot
be processed.
([row,col {unknown-source}]: [8,5])
[java] May 22, 2008 7:44:59 AM
org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
problem
[java] WARNING: No implementation for component: HelloWorldService
[java] May 22, 2008 7:44:59 AM
org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
problem
[java] WARNING: Reference not found for component reference:
HelloWorldService/greetingsPartnerLink
[java] May 22, 2008 7:44:59 AM
org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
problem
[java] WARNING: No implementation for component: HelloWorldService
[java] May 22, 2008 7:44:59 AM
org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
problem
[java] WARNING: Reference not found for component reference:
HelloWorldService/greetingsPartnerLink
[java] No service is declared on component HelloWorldService
BTW, of course the greetings service is up and running and I can query
its
WSDL (v1.1)
In the composite I did try both wsdl.interface and wsdl.portType and got
the
same result (same interface.wsdl cannot be processed)
thanks,
JJ-
On Sat, May 17, 2008 at 7:29 AM, Jean-Jacques Dubray [EMAIL PROTECTED]
wrote:
Luciano, Mike:
thanks for the detailed answer. Yes, I am aware there are different
types.
I am not so concerned having to declare an implementation within the
same
domain. As a matter of fact, it looks to me that it is not even within
an
Re: Web Service References
Would you mind creating a JIRA and posting at least your composite,
wsdl and deploy.xml files so i can take a look.
On Thu, May 22, 2008 at 9:00 AM, Jean-Jacques Dubray [EMAIL PROTECTED] wrote:
Good point, I removed the tuscany namespace that had been added by the
Composite Editor and the errors are gone
I do get however:
[java] Starting setup
[java] [INFO] - GeronimoLog.info(79) | Using embedded Geronimo
transaction manager
[java] java.lang.NullPointerException
The same behavior is true whether I use:
interface.wsdl interface=
http://192.168.2.2:8085/GreetingsService#wsdl.interface(Greetings)/
or interface.wsdl interface=
http://192.168.2.2:8085/GreetingsService#wsdl.portType(Greetings)/
JJ-
On Thu, May 22, 2008 at 8:49 AM, Luciano Resende [EMAIL PROTECTED]
wrote:
The errors you are getting usually means that the necessary
dependencies that register processors to parse those elements are not
available (e.g implementation.bpel and interface.wsdl).
On Thu, May 22, 2008 at 8:11 AM, Jean-Jacques Dubray [EMAIL PROTECTED]
wrote:
Mike:
I don't know if you are talking about this sample:
https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/samples/helloworld-bpel-ws/
If it's the case, the helloworld.composite does not have a reference, it
simply exposes a BPEL implementation as a service.
I think I understand a bit better the rationale for not modeling external
references as components and why components need to have an
implementation. I am fine with it since a component must belong to a
domain.
I have tried to do some cross-domain work by modeling a service (external
to
the domain) invoked by a BPEL implementation and I get some errors. I
don't
know if anyone could help me.
Here is my composite file (I replaced the GreetingsService component by a
reference to an external web service (implemented in a different
domain)):
?xml version=1.0 encoding=ISO-8859-15?
composite xmlns=http://www.osoa.org/xmlns/sca/1.0; xmlns:sca=
http://www.osoa.org/xmlns/sca/1.0; xmlns:hns=http://helloworld;
xmlns:instance=http://www.w3.org/2004/08/wsdl-instance; xmlns:tuscany=
http://tuscany.apache.org/xmlns/sca/1.0; name=helloworld
targetNamespace=
http://bpel;
component name=HelloWorldService
tuscany:implementation.bpel process=hns:HelloWorld/
reference name=greetingsPartnerLink /
/component
reference name=GreetingsService
promote=HelloWorldService/greetingsPartnerLink
tuscany:interface.wsdl interface=
http://laptop2:8085/GreetingsService#wsdl.portType(Greetings)http://laptop2:8085/GreetingsService#wsdl.portType%28Greetings%29
/
binding.ws wsdlElement=
http://laptop2:8085/GreetingsService#wsdl.service(GreetingsService)http://laptop2:8085/GreetingsService#wsdl.service%28GreetingsService%29
instance:wsdlLocation=http://laptop2:8085/GreetingsService.wsdl/
/reference
/composite
I do get a series of errors coming from the domain trying to implement
this
composite:
[java] May 22, 2008 7:44:59 AM
org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor
read
[java] WARNING: Element {
http://tuscany.apache.org/xmlns/sca/1.0}implementation.bpelhttp://tuscany.apache.org/xmlns/sca/1.0%7Dimplementation.bpelcannot
be
processed. ([row,col {unknown-source}]: [4,5])
[java] May 22, 2008 7:44:59 AM
org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor
read
[java] WARNING: Element {
http://tuscany.apache.org/xmlns/sca/1.0}interface.wsdlhttp://tuscany.apache.org/xmlns/sca/1.0%7Dinterface.wsdlcannot
be processed.
([row,col {unknown-source}]: [8,5])
[java] May 22, 2008 7:44:59 AM
org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
problem
[java] WARNING: No implementation for component: HelloWorldService
[java] May 22, 2008 7:44:59 AM
org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
problem
[java] WARNING: Reference not found for component reference:
HelloWorldService/greetingsPartnerLink
[java] May 22, 2008 7:44:59 AM
org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
problem
[java] WARNING: No implementation for component: HelloWorldService
[java] May 22, 2008 7:44:59 AM
org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
problem
[java] WARNING: Reference not found for component reference:
HelloWorldService/greetingsPartnerLink
[java] No service is declared on component HelloWorldService
BTW, of course the greetings service is up and running and I can query
its
WSDL (v1.1)
In the composite I did try both wsdl.interface and wsdl.portType and got
the
same result (same interface.wsdl cannot be processed)
thanks,
JJ-
On Sat, May 17, 2008 at 7:29 AM, Jean-Jacques Dubray [EMAIL PROTECTED]
wrote:
Luciano, Mike:
thanks for the detailed
Re: Graduation
excellent news ! The first step in making Tuscany and enterprise grade open source project. It's so much easier to sell something that doesn't have the word incubation in front of it... jeff On 5/22/08, ant elder [EMAIL PROTECTED] wrote: Forwarding for those not on tuscany-dev... Congratulations everyone and a very big thank you to our mentors and all the incubator folks for their help and guidance during the incubation, wouldn't have made it without you. ...ant -- Forwarded message -- From: Matthieu Riou [EMAIL PROTECTED] Date: Wed, May 21, 2008 at 10:14 PM Subject: Graduation To: tuscany-dev [EMAIL PROTECTED] Special order 7B, Establish the Apache Tuscany Project, was approved by Unanimous Vote of the directors present. Congratulations guys! Matthieu -- Jeff Anderson http://agileconsulting.blogspot.com/
ClassNotFoundException On WebSphere
This may have been discussed before, but just in case I want to bring to everyone's attention. If you are trying to run some of the Tuscany sample and demo web applications on WebSphere, you may see the following exception: Caused by: java.lang.ClassNotFoundException: org.apache.tuscany.sca.host.webapp.WebSCADomain at java.lang.Class.forNameImpl(Native Method) at java.lang.Class.forName(Class.java:169) The solution to this problem is that you must set application properties to use the application class loader before the parent container class loader. Then Tuscany class dependencies packaged in your web app will be successfully loaded and resolved. A step by step explanation and walk through is given my Jean-Sebastien at http://jsdelfino.blogspot.com/2007/10/how-to-use-apache-tuscany-with.html. -- Thanks, Dan Becker
