Re: A question about SCA descriptor file structure and meaning.

[Jean-Sebastien Delfino]

legolas wood wrote:

Hi
Thank you for reading my post
Can you please explain following snippet for me?



   interface="http://www.stockquote.org/StockQuoteService#wsdl.interface(StockQuote)"/> 



   wsdlElement="http://www.stockquote.org/StockQuoteService#wsdl.service(StockQuoteService)" 


   wsdli:wsdlLocation="http://www.stockquote.org/StockQuoteService
   http://www.stockquote.org/StockQuoteService.wsdl"; />




Imagine that i have a java class named Calculate, it has one method 
which takes two numbers and return an integer as result. something like :






@WebService()

public class Calculate {

   /**

* Web service operation

*/

   @WebMethod

   public int addThem(@WebParam(name = "a")

   int a, @WebParam(name = "b")

   int b) {

   // TODO write your implementation code here:

   return a+b;

   }

  
}




URL to wsdl of this web service is like: 
http://localhost:8080/sample/CalculateService?wsdl


Now how the above code snippet which is an SCA code snippet should 
change to use my web service and its addThem method?



Thanks




Hi,

If I understand correctly you're trying to use an SCA reference with an 
SCA Web Service binding to talk to a CalculateService Web service, for 
which you already have a WSDL?


If this is your scenario then it's pretty simple.

You simply need to change the SCA reference to name the WSDL  
and  (or ) representing the CalculateService in the WSDL 
returned at http://localhost:8080/sample/CalculateService?wsdl.


It's probably best to have a local copy of the CalculateService WSDL 
instead of relying on http://localhost:8080/sample/CalculateService?wsdl 
to be online all the time, so I'd recommend to save it to 
CalculateService.wsdl, store that WSDL locally with your other SCA 
artifacts, then change your SCA  like this:




 

   
  interface="http://calculate-namespace#wsdl.interface(Calculate)"/>
  wsdlElement="http://calculate-namespace#wsdl.service(CalculateService)"/>

   

   ... other configuration of your component

 



A few comments:

- An SCA reference usually lives inside a component (representing the 
code that's going to talk to the reference), inside an SCA composite. I 
just added them here to put the  in context.


- I have to guess what's in your WSDL, so in my example 
http://calculate-namespace would be the namespace of your WSDL definition


- Calculate would be the name of your WSDL 

- CalculateService would be the name of your WSDL 

- I recommend to avoid using wsdlLocation in general as I doubt that 
your application will always run on localhost:8080 :) and when you 
install it somewhere else you probably don't want to go back to your SCA 
reference and change that location. What we usually do instead is we 
place a local copy of the WSDL file in the client application, and the 
Tuscany runtime will automatically find it for you.


Hope this helps.

--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

SDO integration with external projects

[Ron Gavlin]

One way to expand the visibility and adoption of SDO within the broader 
community is to improve its integration story with external projects. A few 
projects in particular seem obvious, namely the Spring Framework, Apache CXF, 
and Apache Axis2. Some of this work might simply be documentation. In other 
cases, integration/glue code might be needed. Is this type of work outside the 
scope of Tuscany SDO? If not, would Tuscany SDO consider hosting this type of 
integration code until such a time as the external projects decided to host it 
themselves? Any thoughts?

- Ron



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [DAS] Status of DAS Release

[Amita Vadhavkar]

Things tested to be working -
all UT as part of mvn build
all samples in different browsers.

Apart from das\distribution\binary\pom.xml - change and documentation
changes in JIRA 1335, I have a doubt in logging mechanism in web samples.

In DBConfig utility , the code uses Logger.getLogger(className) - to get
logger from log4j.

Whereas in all RDB DAS code, it is
LoggerFactory.INSTANCE.getLogger(className) - to get logger from RDB DAS
util.
In this, the level is OFF - hardcoded in the code.

So, when the log4j.properties file is used in tomcat to switch on logging,
the logging works for DBConfig (as it is using direct log4j), but logging
does not switch on for RDB DAS classes, as it is hardcoded OFF in the RDB
DAS jar.

Is this the desired behavior? Will there be any need to switch on logging in
web samples for RDB DAS code and how to do it without touching
tuscany-das-rdb-1.0-incubating.jar?

Regards,
Amita

On 6/11/07, Amita Vadhavkar <[EMAIL PROTECTED]> wrote:


Hi All,

When tried mvn -Pdistribution on das:-
das\distribution\binary\pom.xml - does not list ajax web sample under
dependency and thus does not package same

As now, non-committer does not have access to edit wiki, I have created
JIRA-TUSCANY-1335 for all the pending updates for DAS I was doing. Please
see how these can be completed using attached zipped files.

Architecture Guide -
http://cwiki.apache.org/confluence/display/TUSCANY/RDB+DAS+architecture+guide
images to upload - ClassDiag.jpg, rdbDAS.gif

User Guide -
http://cwiki.apache.org/confluence/display/TUSCANY/RDB+DAS+-+User+Guide
Under Samples(See Capabilities in use)
Put links for:-
Web Sample -
https://svn.apache.org/repos/asf/incubator/tuscany/java/das/samples/companyweb/readme.htm
J2SE Sample -
https://svn.apache.org/repos/asf/incubator/tuscany/java/das/samples/customer/readme.htm
Advanced Web Sample - 
https://svn.apache.org/repos/asf/incubator/tuscany/java/das/samples/sample-ajax-das/readme.htm


Development Guide - DAS_Java_Development_Guide.txt - need to add to wiki

need to checkin under 
https://svn.apache.org/repos/asf/incubator/tuscany/java/das/distribution/src/main/release/RELEASE
NOTES
RELEASE_NOTES.txt

About to complete CHANGES.txt , will add by eod to JIRA 1335..

Regards,
Amita

On 6/10/07, Adriano Crestani <[EMAIL PROTECTED]> wrote:
>
> I went through all das samples and they seem to be working fine on
> Windows
> XP Home Edition SP 2 environment. I also corrected some links on readmes
> that were pointing to old tuscany website.
>
> I ran the rat on java/das directory and added Apache Licence header to
> files
> that were missing it.
>
> Regards,
> Adriano Crestani
>
> On 6/8/07, Luciano Resende <[EMAIL PROTECTED]> wrote:
> >
> > First of all, let me thank you all for helping on this release.
> > Recently there has been a lot of progress, and things are looking good
> > from the list of issues we had listed in the wiki [1]. The remaining
> > documentation tasks could probably go in parallel with the release
> > candidates. So, we should start thinking about creating a branch for
> > the next release sometime soon, probably over the weekend or Monday
> > and then start publishing release candidates from that.
> >
> > Also, I think we should look into the following items before we create
> > the first RC :
> >
> >- run rat and make the results available
> >- review the contents of license, readme, release_notes, changes,
> etc
> >- review javadoc
> >- make sure samples readme are updated and correct and the samples
> > are working ok on different environments
> >
> > I'd also like to suggest two other things :
> >- Name the release beta1, to be aligned with the beta1 release of
> SDO.
> >- Any blocking issue to be tracked as blocking JIRA and directly
> > assigned to beta1 release.
> >
> > Does this sound ok to everyone?  Any Thoughts ?
> >
> >
> > [1]
> >
> 
http://cwiki.apache.org/confluence/display/TUSCANY/RDB+DAS+-+Java+DAS+Beta1+Release
> >
> >
> > --
> > Luciano Resende
> > Apache Tuscany Committer
> > http://people.apache.org/~lresende
> > http://lresende.blogspot.com/
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>