Hi,
I'm trying to understand the project setting for the code you use to test the
JMX integration. Do you have your own maven module or do you reuse an existing
sample module?
Are you trying to run
samples/running-tuscany/jse/src/main/java/launcher/LaunchCalculatorContribution
to see if the JMX is activated?
If so, that pom has the following dependency:
<dependency>
<groupId>org.apache.tuscany.sca</groupId>
<artifactId>tuscany-base-runtime</artifactId>
<version>2.0-SNAPSHOT</version>
</dependency>
If you have the jmx modules added to the base-runtime pom, they should be
picked up. You can run "mvn dependency:tree" under samples/running-tuscany/jse
to confirm.
Back to the build issue, can you do the following:
1) Send us the error message
2) Use "mvn clean install -fae -Dmaven.test.skip=true" for the purpose of
compilation and archive.
Thanks,
Raymond
________________________________________________________________
Raymond Feng
rf...@apache.org
Apache Tuscany PMC member and committer: tuscany.apache.org
Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com
Personal Web Site: www.enjoyjava.com
________________________________________________________________
On Aug 3, 2011, at 7:03 AM, Amindri Udugala wrote:
> Hi Raymond,
>
> I quite didn't understand what u asked for. Can you please explain what you
> exactly meant.
> I'm running the LaunchCalculatorContribution class in the sample module to
> bootstrap tuscany.
>
>
>
> On 2 August 2011 23:16, Raymond Feng <enjoyj...@gmail.com> wrote:
> Can you point out which sample from svn are you trying to pick up your
> modules?
>
> Thanks,
> Raymond
> ________________________________________________________________
> Raymond Feng
> rf...@apache.org
> Apache Tuscany PMC member and committer: tuscany.apache.org
> Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com
> Personal Web Site: www.enjoyjava.com
> ________________________________________________________________
>
> On Aug 2, 2011, at 9:12 AM, Amindri Udugala wrote:
>
>> Hi,
>>
>> I tried that out but still could not resolve the memory issue, changed the
>> surefire plugin in trunk/pom.xml as follows
>> <configuration>
>> <argLine>-ea -Xmx1024m -Xms756m -XX:MaxPermSize=512m</argLine>
>> </configuration>
>>
>> I added dependencies to features/all/pom.xml and
>> modules/base-runtime/pom.xml and still the modules are not included to the
>> class path. Is it because I was not able to build the project?
>>
>> On 25 July 2011 19:24, Amindri Udugala <amindriudug...@gmail.com> wrote:
>> Thanx Raymond I'll try that out.
>>
>>
>> On 26 July 2011 11:24, Raymond Feng <enjoyj...@gmail.com> wrote:
>> Hi, Amindri.
>>
>> Can you try to add your modules to features/all/pom.xml and
>> modules/base-runtime/pom.xml? It seems that the sample uses base-runtime as
>> the dependency to create the class path.
>>
>> For the memory issue, can you try to change memory setting for the surefire
>> plugin? It is configured in the pom.xml under the <plugin> element whose
>> artifactid is maven-surefire-plugin.
>>
>> Sent from my iPad
>>
>> On Jul 24, 2011, at 8:11 PM, Amindri Udugala <amindriudug...@gmail.com>
>> wrote:
>>
>>> Hi,
>>> Herewith I have listed down the artifacts that I have exposed to JMX
>>> connection and the attributes of the artifacts I have exposed. Also I have
>>> exposed some of the operations of these artifacts as well to the JMX
>>> connection. Please comment if I have missed anything out. Have attached
>>> the latest patch with all the latest changes.
>>>
>>> With this I think I have done with most of my work, but the problem which
>>> I'm facing is that I still couldn't get the jmx-activator module activated
>>> when Tuscany is bootstrapped. I'm using LaunchCalculatorContribution in the
>>> sample module to bootstrap tuscany. I found out that jmx-activator module
>>> is not included in the classpath when I'm running the
>>> LaunchCalculatorContribution.
>>>
>>> I guess the reason for this is, that I was never able to build the whole
>>> trunk at once, due to lack of perm space. I executed MAVEN_OPTS="-Xmx1024m
>>> -Xms512m -XX:MaxPermSize=384m" before building the trunk, but still the
>>> problem remains.
>>>
>>> If I can get a solution for this problem, I'll be able to verify the
>>> correctness of the code...
>>> Component
>>> Attributes
>>> getComponents - Lists all runtime Components with following
>>> attributes - Name, URI, AutoWire, Implementation
>>>
>>> Operations
>>> getComponent(String name) - Lists all the attributes of the
>>> specified component- Name, URI, AutoWire, Implementation, ExtensionType,
>>>
>>> AttributeExtensions, Services, References, Properties, RequiredIntents,
>>> PolicySets, Extensions
>>> setComponentURI(String currURI, String newURI)
>>> setComponentName(String uri, String newName)
>>> setComponentAutoWire(String uri, boolean autoWire)
>>> setComponentUnresolved(String uri, boolean unresolved)
>>>
>>> ComponentService
>>> Attributes
>>> getComponentServices - Lists all runtime ComponentServices with
>>> following attributes - Name, CallBackReference, Service
>>>
>>> Operations
>>> getComponentService(String name) - Lists all attributes of the
>>> specified ComponentService - Name, CallBackReference, Service,
>>>
>>> InterfaceContract, Bindings, AttributeExtensions, Endpoints,
>>> RequiredIntents, PolicySets ,
>>> Extensions
>>> setComponentServiceUnresolved(String name, boolean unresolved)
>>> setComponentServiceForCallback(String name, boolean forCallBack)
>>> setComponentServiceName(String currName, String newName)
>>>
>>> Composite
>>> Attributes
>>> getComposites() - Lists all runtime Composites with following
>>> attributes - Name, URI, ExtensionType, ContributionURI, SpecVersion, Local
>>>
>>> Operations
>>> getComposite(String uri) - Lists all attributes of the specified
>>> ComponentService - Name, URI, ExtensionType, ContributionURI, SpecVersion ,
>>> Local, IsAutoWire,
>>> Unresolved, Components, Includes, FusedIncludes, RequiredIntents, Services,
>>> references , Operations,
>>> Wires, Properties, PolicySets, Extensions, AttributeExtensions
>>> setCompositeContributionURI(String uri, String contributionURI)
>>> setCompositeURI(String currURI, String newURI)
>>> setCompositeSpecVersion(String uri, String specVersion)
>>> setCompositeLocal(String uri, boolean local)
>>> setCompositeAutoWire(String uri, boolean autoWire)
>>> setCompositeUnresolved(String uri, boolean unresolved)
>>>
>>> Endpoint
>>> Attributes
>>> getEndpointView() - Lists all runtime Endpoints with following
>>> attributes - URI, DeployedURI, ExtensionType, Service, Component, Binding ,
>>>
>>> ComponentServiceInterfaceContract,
>>>
>>> Operations
>>> getEndpoint(String uri) - Lists attributes of the specified
>>> Endpoint - URI, DeployedURI, ExtensionType, Service, Component, Binding ,
>>>
>>> ComponentServiceInterfaceContract, AsyncInvocation, Remote, Unresolved,
>>> PolicySets, EndpointReferences,
>>> RequiredIntents
>>> setEndpointUnresolved(String epURI, boolean unresolved);
>>> setEndpointRemote(String epURI, boolean remote);
>>> setEndpointURI(String epURI);
>>> setEndpointDeployedURI(String epURI, String depURI)
>>>
>>> EndpointReference
>>> Attributes
>>> getEndpointReferences() - Lists all runtime EndpointReferences
>>> with following attributes - URI,Status, CallbackEndpoint, TargetEndpoint ,
>>> Binding, Component,
>>> AsyncInvocation
>>>
>>> Operations
>>> getEndpointReference(String epRefUri) - Lists attributes of the
>>> specified EndpointReference - URI,Status, CallbackEndpoint, TargetEndpoint
>>> ,
>>> Binding, Component, AsyncInvocation, ComponentReferenceInterfaceContract,
>>> ExtensionType,
>>> Reference, RequiredIntents, PolicySets
>>> setEndpointReferenceURI(String epRefUri, String uri)
>>> setEndpointReferenceUnresolved(String epRefUri, boolean
>>> unresolved)
>>> setStatus(String epRefUri, String status)
>>>
>>> ProviderFactoryExtensionPoint
>>> Attributes
>>> getProviderFactoryExtensionPoint() -Shows the runtime
>>> ProviderFactoryExtensionPoint with following attribute -
>>> PolicyProviderFactories
>>>
>>> Operations
>>> removePolicyProviderFactory(String pf)
>>>
>>> DefaultWireProcessorExtensionPoint
>>> Attributes
>>> getDefaultWireProcessorExtensionPoint() - Shows the runtime
>>> DefaultawireProcessorExtensionPoint with following attribute -
>>> WireProcessors
>>>
>>> Operations
>>> removeWireProcessor(String runtimeWP)
>>> startWireProcessorExtensionPoint()
>>> stopWireProcessorExtensionPoint()
>>>
>>> RuntimeWireProcessor
>>> Attributes
>>> getRuntimeWireProcessors() - Shows the runtime
>>> DefaultawireProcessorExtensionPoint with following attribute - Name of
>>> runtime wire
>>> processor
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Thanks
>>>
>>> Amindri Udugala
>>> University of Colombo School of Computing,
>>> Sri Lanka.
>>>
>>
>>
>>
>> --
>> Thanks
>>
>> Amindri Udugala
>> University of Colombo School of Computing,
>> Sri Lanka.
>>
>>
>>
>>
>> --
>> Thanks
>>
>> Amindri Udugala
>> University of Colombo School of Computing,
>> Sri Lanka.
>>
>
>
>
>
> --
> Thanks
>
> Amindri Udugala
> University of Colombo School of Computing,
> Sri Lanka.
>
