Re: Use EmbeddedScaDomain to deploy multiple contributions

2009-03-31 Thread Luciano Resende
On Tue, Mar 31, 2009 at 1:18 PM, Raymond Feng  wrote:
> Hi,
>
> The wire element has some errors:
>
>              Target="/StoreServiceComponent /StoreService"/>
>
> should be:
>
>             target="StoreServiceComponent /StoreService"/>
>

Good catch Raymond... but also no space on the target, right ?

 should be:

  



> Thanks,
> Raymond
>
> From: Dong Liu
> Sent: Tuesday, March 31, 2009 12:43 PM
> To: user@tuscany.apache.org
> Subject: Use EmbeddedScaDomain to deploy multiple contributions
>
>
> I tried to use Tuscany EmbeddedScaDomain to deploy multiple contributions
> which can share some common resources. Here are my contributions:
>
> Contribution A (http://inner) contains InnerComposite, looks like:
>
> http://www.osoa.org/xmlns/sca/1.0";
> targetNamespace="http://inner";
>  name="InnerComposite">
>  
>       
>       
>                       
>      
>  
> 
>
> Contribution B(http://outer) contains OuterComposite, looks like:
>
> http://www.osoa.org/xmlns/sca/1.0";
>   targetNamespace="http://hello";  xmlns:inner="http://inner";
>   name="OuterComposite">
>
>  
>  
>       
>       
>    
>              Target="/StoreServiceComponent /StoreService"/>
> 
>
> Both composites are declared as deployable. Contribution A is exported to
> namespace http://inner and contribution B imports it.
>
> The “Store” service is implemented using “COMPOSITE” Scope annotation, which
> is intend to provide a shareable store instance for other contributions such
> like B.
>
> However, I got a warning message when deploying B after contribution A is
> deployed successfully. The warning message is “Wire target not found :
> HelloComponent/Store”. It looks like the wire in one composite can’t link to
> components belongs to other composites.
>
> I can make contribution B deployed only by adding the “include” declaration.
> But I am not sure this will meet my requirement because now the "Store"
> service belongs to two composites.  The instance shouldn’t be shared among
> multiple composites since its scope is “COMPOSITE”.
>
> If there are other solutions for this problem?
>
>
> Thanks
>
> Dong
>



-- 
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/


Re: Use EmbeddedScaDomain to deploy multiple contributions

2009-03-31 Thread Raymond Feng

Hi,

The wire element has some errors:

 

should be:

 

Thanks,
Raymond

From: Dong Liu
Sent: Tuesday, March 31, 2009 12:43 PM
To: user@tuscany.apache.org
Subject: Use EmbeddedScaDomain to deploy multiple contributions


I tried to use Tuscany EmbeddedScaDomain to deploy multiple contributions 
which can share some common resources. Here are my contributions:


Contribution A (http://inner) contains InnerComposite, looks like:

http://www.osoa.org/xmlns/sca/1.0"; 
targetNamespace="http://inner";

  name="InnerComposite">
 
   
   
   

  
  


Contribution B(http://outer) contains OuterComposite, looks like:

http://www.osoa.org/xmlns/sca/1.0";
   targetNamespace="http://hello";  xmlns:inner="http://inner";
   name="OuterComposite">

  
  
   
   

 


Both composites are declared as deployable. Contribution A is exported to 
namespace http://inner and contribution B imports it.


The “Store” service is implemented using “COMPOSITE” Scope annotation, which 
is intend to provide a shareable store instance for other contributions such 
like B.


However, I got a warning message when deploying B after contribution A is 
deployed successfully. The warning message is “Wire target not found : 
HelloComponent/Store”. It looks like the wire in one composite can’t link to 
components belongs to other composites.


I can make contribution B deployed only by adding the “include” declaration. 
But I am not sure this will meet my requirement because now the "Store" 
service belongs to two composites.  The instance shouldn’t be shared among 
multiple composites since its scope is “COMPOSITE”.


If there are other solutions for this problem?


Thanks

Dong 



Re: Use EmbeddedScaDomain to deploy multiple contributions

2009-03-31 Thread Luciano Resende
On Tue, Mar 31, 2009 at 12:43 PM, Dong Liu  wrote:
> I tried to use Tuscany EmbeddedScaDomain to deploy multiple contributions
> which can share some common resources. Here are my contributions:
>..
>
> Both composites are declared as deployable. Contribution A is exported to
> namespace http://inner and contribution B imports it.
>
> The “Store” service is implemented using “COMPOSITE” Scope annotation, which
> is intend to provide a shareable store instance for other contributions such
> like B.
>
> However, I got a warning message when deploying B after contribution A is
> deployed successfully. The warning message is “Wire target not found :
> HelloComponent/Store”. It looks like the wire in one composite can’t link to
> components belongs to other composites.
>
> I can make contribution B deployed only by adding the “include” declaration.
> But I am not sure this will meet my requirement because now the "Store"
> service belongs to two composites.  The instance shouldn’t be shared among
> multiple composites since its scope is “COMPOSITE”.
>
> If there are other solutions for this problem?
>
>

Have you looked into itest/contribution-import-export or
tutorial/store/assets ? It has couple examples related to what you are
doing.

One thing I didn't see in your e-mail is how you are using
sca-contribution.xml, that is the file that would tell the Tuscany
runtime to use a different contribution when resolving dependencies
(based on import/export from sca-contribution.xml)

>
>
>
> Thanks
>
>
>
> Dong
>



-- 
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/


Use EmbeddedScaDomain to deploy multiple contributions

2009-03-31 Thread Dong Liu
I tried to use Tuscany EmbeddedScaDomain to deploy multiple contributions which 
can share some common resources. Here are my contributions:
 
Contribution A (http://inner) contains InnerComposite, looks like:
 
http://www.osoa.org/xmlns/sca/1.0"; 
targetNamespace="http://inner";
   name="InnerComposite">
  
     
    
    
   
    

 
Contribution B(http://outer) contains OuterComposite, looks like:
 
http://www.osoa.org/xmlns/sca/1.0";
    targetNamespace="http://hello"  xmlns:inner="http://inner";
    name="OuterComposite">
  
    
   
    
    
 
  
 
 
Both composites are declared as deployable. Contribution A is exported to 
namespace http://inner and contribution B imports it.
 
The “Store” service is implemented using “COMPOSITE” Scope annotation, which is 
intend to provide a shareable store instance for other contributions such like 
B.
 
However, I got a warning message when deploying B after contribution A is 
deployed successfully. The warning message is “Wire target not found : 
HelloComponent/Store”. It looks like the wire in one composite can’t link to 
components belongs to other composites. 
 
I can make contribution B deployed only by adding the “include” declaration. 
But I am not sure this will meet my requirement because now the "Store" service 
belongs to two composites.  The instance shouldn’t be shared among multiple 
composites since its scope is “COMPOSITE”. 
 
If there are other solutions for this problem? 
 
 
Thanks
 
Dong


  

Integration with ServiceMix4?

2009-03-31 Thread Zhang,Dafang
Hi, I posted a message on the ServiceMix mailing list, asking the possibility 
to integrate Tuscany with ServiceMix [1].  Looks like not much work done on 
their end, but one of the ServiceMix leaders is willing to help out with a 
proof of concept.  It would be great to have some sample code in either or both 
of Tuscany and ServiceMix projects.

I searched the Tuscany list here and found a great post by Raymond Feng [2]. 

I also found Charuka Jayarathna's academic work in this direction [3].  
Jean-Sebastien Delfino provided some guidelines in implementing it[4], and it's 
a different approach from the one presented in JavaOne 2008 [5].  I hope 
Charuka can come back and provide feedback.  Hopefully, the final 
implementation would be OSGi based.

Is there any other practical work done in this area?  Any insight/examples 
would be greatly appreciated.  

[1] http://www.mail-archive.com/us...@servicemix.apache.org/msg08712.html 

[2] http://www.mail-archive.com/user@tuscany.apache.org/msg01107.html

[3] http://www.mail-archive.com/d...@tuscany.apache.org/msg00296.html 

[4] http://www.mail-archive.com/d...@tuscany.apache.org/msg00323.html 

[5] 
http://developers.sun.com/learning/javaoneonline/j1sessn.jsp?sessn=TS-5870&yr=2008&track=soa
 

--
CONFIDENTIALITY NOTICE This message and any included attachments are from 
Cerner Corporation and are intended only for the addressee. The information 
contained in this message is confidential and may constitute inside or 
non-public information under international, federal, or state securities laws. 
Unauthorized forwarding, printing, copying, distribution, or use of such 
information is strictly prohibited and may be unlawful. If you are not the 
addressee, please promptly delete this message and notify the sender of the 
delivery error by e-mail or you may call Cerner's corporate offices in Kansas 
City, Missouri, U.S.A at (+1) (816)221-1024.


Re: SchemaValidation

2009-03-31 Thread Raymond Feng
Sorry for the confusion. What I said is that Tuscany only supports schema 
validations for system code. We don't validate the XML messages from the 
application against the schema.


FYI: We are discussing a binding.ws implementation based on JAX-WS APIs for 
GSoC 2009 [1]. Your requirement can be potentially supported by that.


Thanks,
Raymond
--
From: "Ali, Haneef" 
Sent: Monday, March 30, 2009 6:25 PM
To: 
Subject: RE: SchemaValidation


Hi,

Just to clarify, If  I need to create a webservice using contract first 
approach, then only way to validate the contract is to extract the types 
section from the  wsdl and put it in a separate xsd file that can be 
plugged into tuscany extension.


This seems totally awkward.


Thanks,
Haneef


From: Raymond Feng [enjoyj...@gmail.com]
Sent: Monday, March 30, 2009 5:03 PM
To: user@tuscany.apache.org
Subject: Re: SchemaValidation

Hi,

We don't support the @SchemaValidation. In Tuscany, we do validate the
composite files and other XML files loaded by Tuscany against the SCA
schemas. The schemas can be plugged into as an extension to Tuscany using
META-INF/services/org.apache.tuscany.sca.contribution.processor.ValidationSchema.
The content of the file lists the schema locations. You can find an 
example

at [1].

Thanks,
Raymond

[1]
https://svn.apache.org/repos/asf/tuscany/java/sca/modules/assembly-xsd/src/main/resources/META-INF/services/org.apache.tuscany.sca.contribution.processor.ValidationSchema

--
From: "Ali, Haneef" 
Sent: Monday, March 30, 2009 4:46 PM
To: 
Subject: SchemaValidation


Hi,

I have created stubs from the wsdl. But the stub created using jaxws
doesn't do schema validation by default.  So I added schemavalidation
annotation to the service. Still it doesn't do schemavalidation. Does
Tuscany do schemavalidation?

e.g

@javax.jws.WebService(..)
@SchemaValidation(handler=ErrorHandler.class)

public class MyServiceImpl implements MyService {
--
}


Is @SchemaValidation supported in Tuscany?=