Re: assembly-conformance-messages.properties?

2011-10-31 Thread Simon Laws
On Thu, Oct 27, 2011 at 9:01 AM, Simon Laws  wrote:
> Can I remove the file assembly-conformance-messages.properties [1]? I
> don't think we use it any more. I'll remove it in a few days if no one
> shouts.
>
> Simon
>
> [1] 
> http://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/modules/assembly/src/main/resources/org/apache/tuscany/sca/assembly/builder/assembly-conformance-messages.properties
>
> --
> Apache Tuscany committer: tuscany.apache.org
> Co-author of a book about Tuscany and SCA: tuscanyinaction.com
>

Done at revision: 1195395

Simon

-- 
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com


[jira] [Closed] (TUSCANY-3924) Inherited fields in service impl classes are treated as Properties

2011-10-31 Thread Simon Laws (Closed) (JIRA)

 [ 
https://issues.apache.org/jira/browse/TUSCANY-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Laws closed TUSCANY-3924.
---

Resolution: Fixed

Fixed

> Inherited fields in service impl classes are treated as Properties
> --
>
> Key: TUSCANY-3924
> URL: https://issues.apache.org/jira/browse/TUSCANY-3924
> Project: Tuscany
>  Issue Type: Bug
>  Components: Java SCA Assembly Model
>Affects Versions: Java-SCA-2.x
>Reporter: Vijai Kalathur
> Fix For: Java-SCA-2.x
>
>
> In the scenario where the Service impl class extends a class which has no SCA 
> annotations in it, protected fields in the base class are interpreted like 
> Properties.
> Ideally, only the fields in the impl class should be introspected for 
> References/Properties.  The fields in the base class should not be 
> interpreted as References/Properties if there are no SCA annotations. 

--
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-3966) Duplicate message ID in contribution-validation-messages.properties

2011-10-31 Thread Simon Laws (Closed) (JIRA)

 [ 
https://issues.apache.org/jira/browse/TUSCANY-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Laws closed TUSCANY-3966.
---

Resolution: Fixed

Fixed

> Duplicate message ID in contribution-validation-messages.properties
> ---
>
> Key: TUSCANY-3966
> URL: https://issues.apache.org/jira/browse/TUSCANY-3966
> Project: Tuscany
>  Issue Type: Bug
>  Components: Java SCA Problem Determination
>Affects Versions: Java-SCA-2.0-Beta1
>Reporter: Hasan Muhammad
>Priority: Trivial
>
> There is a duplicate message ID in 
> contribution-validation-messages.properties under 
> contribution\src\main\resources
> The ID is AttributeCannotBeProcessed

--
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] [Created] (TUSCANY-3967) Binding jms modules should be more easily extendable

2011-10-31 Thread Jennifer A Thompson (Created) (JIRA)
Binding jms modules should be more easily extendable


 Key: TUSCANY-3967
 URL: https://issues.apache.org/jira/browse/TUSCANY-3967
 Project: Tuscany
  Issue Type: Improvement
  Components: SCA Java Runtime
Affects Versions: Java-SCA-2.x
Reporter: Jennifer A Thompson
 Fix For: Java-SCA-2.x


There are limitations to how binding.jms can be extended. For example, in 
JMSResourceFactoryImpl.java (contained in the binding-jms-runtime module),  
there is a hard dependency on 
"org.apache.activemq.jndi.ActiveMQInitialContextFactory". This shouldn't be 
required for extensions which wish to pick up the runtime module but implement 
their own Resource Factory implementation which doesn't use ActiveMQ. (This 
also creates a dependency on ActiveMQ in the pom).

--
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