Re: Happy Birthday Tuscany
Cool anniversary! Nice to know about it :) On Thu, Dec 8, 2011 at 6:16 AM, Nirmal Fernando wrote: > Happy Birthday Tuscany!! :) > > > On Thu, Dec 8, 2011 at 5:06 AM, Raymond Feng wrote: > >> Wow, six years! >> >> Raymond Feng >> Sent from my iPhone >> >> On Dec 7, 2011, at 2:30 PM, ant elder wrote: >> >> > Its six years today since Tuscany started as an incubator project at >> > the ASF [1]. >> > >> > ...ant >> > >> > [1] http://apache.markmail.org/message/sc4h3eyfo46tlbfp >> > > > > -- > Best Regards, > Nirmal > > C.S.Nirmal J. Fernando > Department of Computer Science & Engineering, > Faculty of Engineering, > University of Moratuwa, > Sri Lanka. > > Blog: http://nirmalfdo.blogspot.com/ > >
Re: Happy Birthday Tuscany
Happy Birthday Tuscany!! :) On Thu, Dec 8, 2011 at 5:06 AM, Raymond Feng wrote: > Wow, six years! > > Raymond Feng > Sent from my iPhone > > On Dec 7, 2011, at 2:30 PM, ant elder wrote: > > > Its six years today since Tuscany started as an incubator project at > > the ASF [1]. > > > > ...ant > > > > [1] http://apache.markmail.org/message/sc4h3eyfo46tlbfp > -- Best Regards, Nirmal C.S.Nirmal J. Fernando Department of Computer Science & Engineering, Faculty of Engineering, University of Moratuwa, Sri Lanka. Blog: http://nirmalfdo.blogspot.com/
Re: Happy Birthday Tuscany
Wow, six years! Raymond Feng Sent from my iPhone On Dec 7, 2011, at 2:30 PM, ant elder wrote: > Its six years today since Tuscany started as an incubator project at > the ASF [1]. > > ...ant > > [1] http://apache.markmail.org/message/sc4h3eyfo46tlbfp
Fwd: Dynamic service references (summary)
This is good and i will have a go in 2.x to see if a similar approach
works there. But i can't help thinking its a slightly convoluted
approach and as we have more flexibility in 2.x to add more APIs I
wonder if we should just add a more direct API method to set the URIs
with extra methods on Node, or also perhaps something like being able
to do: ((TuscanyServiceReference)serviceReference).setURI(uri)?
...ant
-- Forwarded message --
From: Simon Nash
Date: Wed, Dec 7, 2011 at 1:04 PM
Subject: Re: Dynamic service references (summary)
To: u...@tuscany.apache.org
Millies, Sebastian wrote:
>
> Thank you very much for all your help, Simon.
>
You're very welcome. I'm glad this is working for you now.
> I summarize here the result of this discussion for everyone's benefit:
>
> For dynamic web service endpoints, get a wsdl for the web service and define
> a service reference with interface.wsdl using wsdl.binding and a dummy
> URI in the binding.ws element.
>
One small point--it doesn't need to be interface.wsdl. It should also work
if you use interface.java.
Simon
>
> interface="urn:functions#wsdl.interface(ZWS_BAPI_COSTCENTER_GETLIST)" />
>
> wsdlElement="urn:functions#wsdl.binding(ZWS_BAPI_COSTCENTER_GETLISTBinding)"
> uri="dynamicURI" />
>
>
> At run time get the service reference, serialize it to XML, replace the
> dummy URI with the real endpoint URI, deserialize the reference and call the
> service method. The serialization coding goes like this:
>
> public String serializeServiceReferenceXML( ServiceReference sr )
> throws IOException
> {
> ServiceReferenceImpl sri = (ServiceReferenceImpl) sr;
> return sri.toXMLString();
> }
>
> public ServiceReference deserializeServiceReferenceXML( String
> serializedSR )
> throws Exception
> {
> StringReader reader = new StringReader( serializedSR );
> XMLStreamReader xmlReader =
> XMLInputFactory.newInstance().createXMLStreamReader( reader );
> ServiceReferenceImpl sri = new ServiceReferenceImpl( xmlReader );
> return sri;
> }
>
> The deserialized reference will work also when using policy sets (I have
> tested
> that with basic authentication).
>
> For background on the changes that have been made to the 1.x trunk to make
> this possible, refer to TUSCANY-3984.
>
> -- Sebastian
>
> IDS Scheer Consulting GmbH
> Geschäftsführer/Managing Directors: Kamyar Niroumand, Ivo Totev
> Sitz/Registered office: Altenkesseler Straße 17, 66115 Saarbrücken, Germany -
> Registergericht/Commercial register: Saarbrücken HRB 19681
> http://www.softwareag.com
>
Happy Birthday Tuscany
Its six years today since Tuscany started as an incubator project at the ASF [1]. ...ant [1] http://apache.markmail.org/message/sc4h3eyfo46tlbfp
[jira] [Created] (TUSCANY-3993) otest pom.xml needs to point to apache snapshots repo
otest pom.xml needs to point to apache snapshots repo - Key: TUSCANY-3993 URL: https://issues.apache.org/jira/browse/TUSCANY-3993 Project: Tuscany Issue Type: Bug Components: Java SCA Verification Tests Affects Versions: Java-SCA-2.0-M4 Reporter: Tom Seelbach Priority: Minor Need to change the incubating-repo to snapshots repo Index: pom.xml === --- pom.xml (revision 1211541) +++ pom.xml (working copy) @@ -30,8 +30,13 @@ -apache.incubator -http://people.apache.org/repo/m2-incubating-repository + apache.snapshots + Apache Snapshot Repository + + http://repository.apache.org/snapshots + +false + -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TUSCANY-3965) In a Service Implementation annotated with @Service, it's unannonated properties should not be introspected
[
https://issues.apache.org/jira/browse/TUSCANY-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws closed TUSCANY-3965.
---
Resolution: Fixed
I've uploaded the updates OASIS JCI tests so I'm closing this issue now.
> In a Service Implementation annotated with @Service, it's unannonated
> properties should not be introspected
> ---
>
> Key: TUSCANY-3965
> URL: https://issues.apache.org/jira/browse/TUSCANY-3965
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Assembly Model
>Affects Versions: Java-SCA-2.0-Beta1
> Environment: All
>Reporter: Hasan Muhammad
>Priority: Critical
> Fix For: Java-SCA-2.x
>
>
> I was trying to deploy a composite which has component implementing a java
> implementation annotated with @Service which has the following field
> @Service(TestOasis.class)
> public class TestOasisImpl implements TestOasis {
> @DefaultHelperContext
> protected HelperContext helperContext;
> This is not a property as it clearly does not have a @Property annotation and
> hence the composite definition does not define this property. However, the
> validation is logging this as an error as follows
> [Composite: {http://docs.oasis-open.org/ns/opencsa/sca/200912}, Component:
> SDOSimpleServiceJavaSerOasis] - No type specified on component property:
> Component = SDOSimpleServiceJavaSerOasis Property = helperContext
> This is coming from org.apache.tuscany.sca.builder.impl.ComponentBuilderImpl
> and the message ID is NoTypeForComponentProperty
> This validation is too strict and we should ignore properties defined in
> Service class which are not annotated with @Property. The CI spec section 8.1
> appears to confirm to this deduction.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
