[jira] Created: (TUSCANY-2379) CompositeProcessor.java is calling promotedService.getService() instead of promotedService.getName() when writing out a composite file.
CompositeProcessor.java is calling promotedService.getService() instead of
promotedService.getName() when writing out a composite file.
---
Key: TUSCANY-2379
URL: https://issues.apache.org/jira/browse/TUSCANY-2379
Project: Tuscany
Issue Type: Bug
Components: Java SCA Assembly Model
Affects Versions: Java-SCA-1.2
Reporter: Richard Mah
CompositeProcessor.java is calling promotedService.getService() instead of
promotedService.getName() when writing out the promoted service to file.
Here is the snippet of code starting from line 546 (Revision 665831):
String promote;
if (promotedService != null) {
if (promotedService.getName() != null) {
promote = promotedComponent.getName() + '/' +
promotedService.getService();-Here is the
promotedService.getService() call
} else {
promote = promotedComponent.getName();
}
promotedService.getService() looks like it should be promotedService.getName()
instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: Registering ModuleActivators without specifying a META-INF/services/org.apache.tuscany.sca.core.ModuleActivator file
Hi, I'm using a pre-1.2 code base. I'll grab the 1.2 base and give it a try. This refactoring sounds like it's exactly what I'm looking for. Thanks Jean-Sebastion. Richard On Wed, Apr 23, 2008 at 4:20 AM, Jean-Sebastien Delfino < [EMAIL PROTECTED]> wrote: > Richard Mah wrote: > > > Hi, > > > > Yes. I'm interested in only a subset of Tuscany and not the entire > > runtime. Thanks for the answer. > > > > The ModuleActivators I'm trying to use are > > WSDLInterfaceRuntimeModuleActivator, > > JavaInterfaceRuntimeModuleActivator, and JavaRuntimeModuleActivator. > > This leads to another question. For the JavaRuntimeModuleActivator, it > > seems to require bootstraping code which adds a > > ContextFactoryExtensionPoint/DefaultContextFactoryExtensionPoint to the > > registry. However ContextFactoryExtensionPoint and > > DefaultContextFactoryExtensionPoint are non SPI. What do I need in my > > bootstraping code in order for me to use JavaRuntimeModuleActivator > > without > > SPI violations? > > > > Thanks. > > > > Richard Mah > > > > > I can't find WSDLInterfaceRuntimeModuleActivator in the 1.2 code base. > What level of Tuscany are you using? > > JavaRuntimeModuleActivator belongs to the runtime layer (in module > implementation-java-runtime) so that's probably not what you want if you > want to use the Tuscany models without bringing the whole runtime. > > In SVN revision r650720 of trunk I've moved some of the Java model > initialization out of JavaRuntimeModuleActivator into a new > JavaImplementationModuleActivator in module implementation-java. > > This will allow you to get an initialized model environment (and in > particular a JavaImplementationFactory configured with all the right Java 5 > annotation processors that introspect Java component implementation classes > and populate the Java models) without having to drag module > implementation-java-runtime and its runtime dependencies. > > So the short answer to your question is: You shouldn't need > JavaRuntimeModuleActivator anymore :) > > I've also committted new sample programs [1] that show how to bootstrap a > subset of Tuscany to work with the various models without runtime > dependencies. > > [1] > http://svn.apache.org/repos/asf/incubator/tuscany/java/sca/samples/domain-management/ > > Hope this helps. > -- > Jean-Sebastien >
Re: Registering ModuleActivators without specifying a META-INF/services/org.apache.tuscany.sca.core.ModuleActivator file
Hi, Yes. I'm interested in only a subset of Tuscany and not the entire runtime. Thanks for the answer. The ModuleActivators I'm trying to use are WSDLInterfaceRuntimeModuleActivator, JavaInterfaceRuntimeModuleActivator, and JavaRuntimeModuleActivator. This leads to another question. For the JavaRuntimeModuleActivator, it seems to require bootstraping code which adds a ContextFactoryExtensionPoint/DefaultContextFactoryExtensionPoint to the registry. However ContextFactoryExtensionPoint and DefaultContextFactoryExtensionPoint are non SPI. What do I need in my bootstraping code in order for me to use JavaRuntimeModuleActivator without SPI violations? Thanks. Richard Mah
Registering ModuleActivators without specifying a META-INF/services/org.apache.tuscany.sca.core.ModuleActivator file
Hi, Can someone point me to some examples or info on how I can register ModuleActivators without specifying a META-INF/services/org.apache.tuscany.sca.core.ModuleActivator file. Jean-Sebastien mentioned there's something out there where I can simply call a method specifying the ModuleActivator to register. Thanks. Richard Service Component Architecture (SCA) Tools Internal Mail: D3/QCT/8200 /MKM Phone: (905) 413 - 4115Internet: [EMAIL PROTECTED] Notes: Richard Mah/Toronto/[EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1840) Bootstrapping a subset of Tuscany runtime to support object modeling in tools
[ https://issues.apache.org/jira/browse/TUSCANY-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583868#action_12583868 ] Richard Mah commented on TUSCANY-1840: -- We only wish to bootstrap parts of Tuscany required to use the model objects. For example, in our current bootstraping code, creating and registering STAX processors, document processors, the various extension points, etc... Our current use of the Tuscany model involves the loading, use, and persistence of Tuscany model objects. For example: -Load contributions from a sca-contribution.xml or sca-contribution-generated.xml into a Tuscany model Contribution object. -Load composites from a .composite file into a Tuscany assembly model Composite object. -Edit the Contribution and Composite objects. -Write the Contribution object back to the sca-contribution.xml or sca-contribution-generated.xml file. -Write the Composite object back to the .composite file. -Load up WSDL and Java resources into the corresponding Tuscany model objects. In the future, we'll be adding loading/writing .componentType and .definitions along with policy sets and intents to our list of Tuscany usage. Additionally, we require the ability to specify the various ModuleActivators (for example, WSDLInterfaceRuntimeModuleActivator, etc...) other than the current way of specifying them on the classpath. For example, some api to set the list of ModuleActivators. > Bootstrapping a subset of Tuscany runtime to support object modeling in tools > - > > Key: TUSCANY-1840 > URL: https://issues.apache.org/jira/browse/TUSCANY-1840 > Project: Tuscany > Issue Type: New Feature > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.0 > Environment: Windows or Linux >Reporter: Sean Zhou > Fix For: Java-SCA-Next > > > When adopting Tuscany object models in a tooling environment, a subset of > Tuscany runtime requires bootstrap such as creating extension points and > factories. Currently there are no standard API methods or classes for Tuscany > bootstrapping for modeling. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
