Connectors in Component Diagram

[Devashish Bansal]

I am using IBM Rational Software Architect tool for my assignment, although its a great tool I am unable to use connectors and ports in component diagram (seems extremely difficult), instead i am using simple arrows with <<use>> between every component, giving interface name as text on arrows, my question is does it make my component diagram non-UML compliant or will it cost me good amount of marks?

One supporting relief is that Cade's component diagram also have arrows with <<uses>> but as usual all Cade's diagrams are debatable.
Please give your views on this.

As a side question, I am using simple java class to talk to JMS queue (synchronous messaging is required) and this class is directly used by SLSBs, do i need to show this class in Integration tier or Business tier?

[Arnold Reuser]

Communication based on service activators, implemented as message listeners, should indeed be specified as part of the integration tier.
Otherwise your component will be part of the business tier.

[Vijaykumar Dixit]

I am using free open source BOUML which provides very user friendly interface to create components. If you have all the classes created in the project, it gives nice tabs of Provided interfaces, Required Interfaces and Realizations. These then come handy to create ports and connectors and joining them with other components.

You can give it a try, but you will have to create those classes.

[Devashish Bansal]

Arnold Reuser wrote:Communication based on service activators, implemented as message listeners, should indeed be specified as part of the integration tier.
Otherwise your component will be part of the business tier.

So that clarifies my side question....thanks.

Since i developed all my diagrams in this tool, it wouldn't look good if i use another tool for component diagram so i think that cannot be a solution....thanks anyway.
Can anybody help me out clarifying if my use of arrows with <<uses>> is OK or can be a "single point of failure" for my component diagram.