[jira] Resolved: (TUSCANY-2923) Stest code submit by kujunguo 2009_03_06
[ https://issues.apache.org/jira/browse/TUSCANY-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2923. - Resolution: Fixed Fix Version/s: Java-SCA-Next Completed in branch 1.x at revision: 756113 Stest code submit by kujunguo 2009_03_06 Key: TUSCANY-2923 URL: https://issues.apache.org/jira/browse/TUSCANY-2923 Project: Tuscany Issue Type: Test Components: Java SCA Assembly Model Affects Versions: Java-SCA-1.3.1 Reporter: Ku Jun Guo Fix For: Java-SCA-Next Attachments: kujunguo_2008_03_19_stest.diff My stest code for SCA 1.x, it contains: stest\sampleTest\src\main\resources\jndi.properties stest\sampleTest\src\main\resources\TestComposite23.composite stest\sampleTest\src\main\resources\Test_ASM_0024.composite stest\sampleTest\src\main\resources\Test_ASM_0039.composite stest\sampleTest\src\main\resources\Test_ASM_0040.composite stest\sampleTest\src\main\resources\Test_ASM_0041.composite stest\sampleTest\src\main\resources\Test_ASM_0042.composite stest\sampleTest\src\main\resources\Test_ASM_0043.composite stest\sampleTest\src\test\java\client\ASM_0024_TestCase.java stest\sampleTest\src\test\java\client\ASM_0039_TestCase.java stest\sampleTest\src\test\java\client\ASM_0040_TestCase.java stest\sampleTest\src\test\java\client\ASM_0041_TestCase.java stest\sampleTest\src\test\java\client\ASM_0042_TestCase.java stest\sampleTest\src\test\java\client\ASM_0043_TestCase.java I'll attach a detailed document later. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2926) Stest code invalid ignore tag in test case ASM_0024
[ https://issues.apache.org/jira/browse/TUSCANY-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2926. - Resolution: Fixed Fix Version/s: Java-SCA-Next Stest code invalid ignore tag in test case ASM_0024 --- Key: TUSCANY-2926 URL: https://issues.apache.org/jira/browse/TUSCANY-2926 Project: Tuscany Issue Type: Bug Reporter: Dan Becker Assignee: Dan Becker Priority: Trivial Fix For: Java-SCA-Next This item is illegally place in test case ASM_0024. @Ignore(TUSCANY-2925) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2926) Stest code invalid ignore tag in test case ASM_0024
[ https://issues.apache.org/jira/browse/TUSCANY-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reassigned TUSCANY-2926: --- Assignee: Dan Becker Stest code invalid ignore tag in test case ASM_0024 --- Key: TUSCANY-2926 URL: https://issues.apache.org/jira/browse/TUSCANY-2926 Project: Tuscany Issue Type: Bug Reporter: Dan Becker Assignee: Dan Becker Priority: Trivial Fix For: Java-SCA-Next This item is illegally place in test case ASM_0024. @Ignore(TUSCANY-2925) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2883) [1.x] NPE occurs when doing negative test about conformace item 60008
[
https://issues.apache.org/jira/browse/TUSCANY-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12682767#action_12682767
]
Dan Becker commented on TUSCANY-2883:
-
Problem looks valid and I've recreated on 1.x 755259. It seems like wiring
needs an extra level processing to connect the promoted AComponent/b reference
to the c service.
[1.x] NPE occurs when doing negative test about conformace item 60008
-
Key: TUSCANY-2883
URL: https://issues.apache.org/jira/browse/TUSCANY-2883
Project: Tuscany
Issue Type: Task
Components: Java SCA Assembly Model
Affects Versions: Java-SCA-1.4
Reporter: Shu Chao Wan
Attachments: composite.patch
In ASM60008, it says that The interfaces of the component references
promoted by a composite reference MUST be the same, or if the composite
reference itself declares an interface then all the component reference
interfaces must be compatible with the composite reference interface.
Compatible means that the component reference interface is the same or is a
strict subset of the composite reference interface.
In order to verify this statement in negative way, I wrote a composite file
whose promoted component interface is incompatible with the composite
reference's interface, one is CService, and the other is BService, and then a
ServiceRuntimeException is expected as the result. But actually I got a
NullPointerException.
TestCase
@Test
public void ASM60008_n() throws Exception {
initDomain(differentreferenceinterface_outer.composite);
AService service = ServiceFinder.getService(AService.class,
DifferentInterfaceComponent/AService);
System.out.println(service.getState());
cleanupDomain();
}
differentreferenceinterface_outer.composite
composite ..
component name=DifferentInterfaceComponent
implementation.composite
name=assembly-tests:Assembly-different-reference-interface-inner-Composite/
reference name=c target=CComponent/
/component
component name=CComponent
implementation.java
class=org.apache.tuscany.sca.vtest.assembly.composite.impl.CServiceImpl/
/component
/composite
differentreferenceinterface_inner.composite
composite ..
service name=AService promote=AComponent/
component name=AComponent
implementation.java
class=org.apache.tuscany.sca.vtest.assembly.composite.impl.AServiceImpl /
reference name=b
interface.java
interface=org.apache.tuscany.sca.vtest.assembly.composite.BService /
/reference
/component
reference name=c promote=AComponent/b
interface.java
interface=org.apache.tuscany.sca.vtest.assembly.composite.CService /
/reference
/composite
NullPointerException
java.lang.NullPointerException
at
org.apache.tuscany.sca.vtest.assembly.composite.impl.AServiceImpl.getState(AServiceImpl.java:39)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:162)
at
org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:310)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:163)
at $Proxy9.getState(Unknown Source)
at
org.apache.tuscany.sca.vtest.assembly.composite.CompositeTestCase.ASM60008_n(CompositeTestCase.java:330)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at
[jira] Resolved: (TUSCANY-2822) Focus samples names on the Tuscany feature being tested.
[ https://issues.apache.org/jira/browse/TUSCANY-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2822. - Resolution: Duplicate Since this is superceded by TUSCANY-2917, I will let the later, more comprehensive Jira take care of the fix. Focus samples names on the Tuscany feature being tested. Key: TUSCANY-2822 URL: https://issues.apache.org/jira/browse/TUSCANY-2822 Project: Tuscany Issue Type: Improvement Components: Java SCA Samples Affects Versions: Java-SCA-2.0 Environment: All Reporter: Simon Laws Priority: Minor In 1.x our samples were names calculator-??? helloworld-??? Which puts the focus on the application scenario rather that the Tuscany feature being demonstrated by the sample. Change sample names and directory names to the form binding-rmi-reference-calculator binding-rmi-service-calculator binding-ws-calculator host-webapp-calculator implementation-java-calculator launcher-osgi-calculator launcher-jse-calculator maven-osgi-junit-calculator To focus on the main thing being shown by the sample. This has the effect of focusing the samples on specific extensions (of course each sample will use more features but these features are not the focus of the sample). It also has the effect of grouping samples in the sample directory according to what feature they are testing so it is easier to find a sample of interest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2797) Update the homepage URL to refer to the new org.oasisopen URL
[ https://issues.apache.org/jira/browse/TUSCANY-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2797. - Resolution: Fixed Fix Version/s: (was: Java-SCA-2.0) Java-SCA-Next Fixed or updated pages at: http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Articles+About+Tuscany http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Getting+started+with+Tuscany+SCA+development Please open a Jira with any other pages that need updating with better Open OASIS spec linkgs. Update the homepage URL to refer to the new org.oasisopen URL --- Key: TUSCANY-2797 URL: https://issues.apache.org/jira/browse/TUSCANY-2797 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-2.0-M1 Reporter: Mark Combellack Assignee: Mark Combellack Fix For: Java-SCA-Next Currently various files refer to thehomepage for SCA as: http://www.osoa.org/display/Main/Service+Component+Architecture+Specifications This should be updated to refer to the equivalent OASIS Open SCA-J page -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (TUSCANY-2822) Focus samples names on the Tuscany feature being tested.
[ https://issues.apache.org/jira/browse/TUSCANY-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reopened TUSCANY-2822: - As Simon commented on the mailing list, the subject of TUSCANY-2917 is less encompassing than I infered. I am reopening this because I agree. Focus samples names on the Tuscany feature being tested. Key: TUSCANY-2822 URL: https://issues.apache.org/jira/browse/TUSCANY-2822 Project: Tuscany Issue Type: Improvement Components: Java SCA Samples Affects Versions: Java-SCA-2.0 Environment: All Reporter: Simon Laws Priority: Minor In 1.x our samples were names calculator-??? helloworld-??? Which puts the focus on the application scenario rather that the Tuscany feature being demonstrated by the sample. Change sample names and directory names to the form binding-rmi-reference-calculator binding-rmi-service-calculator binding-ws-calculator host-webapp-calculator implementation-java-calculator launcher-osgi-calculator launcher-jse-calculator maven-osgi-junit-calculator To focus on the main thing being shown by the sample. This has the effect of focusing the samples on specific extensions (of course each sample will use more features but these features are not the focus of the sample). It also has the effect of grouping samples in the sample directory according to what feature they are testing so it is easier to find a sample of interest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2686) Vtest code for Java SCA assembly componentType ASM40002
[ https://issues.apache.org/jira/browse/TUSCANY-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2686. - Resolution: Won't Fix Yiwen states that TUSCANY-2686 is superceded by TUSCANY-2765. Vtest code for Java SCA assembly componentType ASM40002 --- Key: TUSCANY-2686 URL: https://issues.apache.org/jira/browse/TUSCANY-2686 Project: Tuscany Issue Type: Test Components: Java SCA Assembly Model Affects Versions: Java-SCA-1.3 Reporter: Yiwen Huang Assignee: Simon Laws Priority: Minor Attachments: ASM40002.patch, ASM40002_b.patch, ASM40002_c.patch Hello, I'd like to submit my first vtest patch, for conformance test ASM40002. As this is my first attempt at writing vtest, please let me know if there is any problem with the patch or the test method. As I mentioned in my post (http://www.mail-archive.com/dev@tuscany.apache.org/msg03443.html), the test does not fail for me, which it should. Let me know what we should do about it too, thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2884) [1.x] This jira is used to submit test case
[ https://issues.apache.org/jira/browse/TUSCANY-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2884. - Resolution: Won't Fix [1.x] This jira is used to submit test case Key: TUSCANY-2884 URL: https://issues.apache.org/jira/browse/TUSCANY-2884 Project: Tuscany Issue Type: Test Components: Java SCA Assembly Model Affects Versions: Java-SCA-1.4 Reporter: Shu Chao Wan Assignee: Dan Becker Attachments: composite.patch It's used to submit test case for conformance items 60001-60008, and 60015-60016. Thanks -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (TUSCANY-2884) [1.x] This jira is used to submit test case
[ https://issues.apache.org/jira/browse/TUSCANY-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680904#action_12680904 ] Dan Becker edited comment on TUSCANY-2884 at 3/11/09 12:30 PM: --- Whoops. These vtests are in fact unrelated to the Tuscany-2907 stests. Let me reopen was (Author: beckerdo): Whoops. These vtests are in fact unrelated to the Tuscany-2904 stests. Let me reopen [1.x] This jira is used to submit test case Key: TUSCANY-2884 URL: https://issues.apache.org/jira/browse/TUSCANY-2884 Project: Tuscany Issue Type: Test Components: Java SCA Assembly Model Affects Versions: Java-SCA-1.4 Reporter: Shu Chao Wan Assignee: Dan Becker Attachments: composite.patch It's used to submit test case for conformance items 60001-60008, and 60015-60016. Thanks -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2907) Stest code submit by kujunguo 2009_03_06
[ https://issues.apache.org/jira/browse/TUSCANY-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reassigned TUSCANY-2907: --- Assignee: Dan Becker Stest code submit by kujunguo 2009_03_06 Key: TUSCANY-2907 URL: https://issues.apache.org/jira/browse/TUSCANY-2907 Project: Tuscany Issue Type: Test Components: Java SCA Assembly Model Affects Versions: Java-SCA-1.3.1 Reporter: Ku Jun Guo Assignee: Dan Becker Priority: Minor Attachments: Kujunguo_SCA_Assembly_TestCases.doc, stest_20090306_kujunguo.diff Simon, Here is my TestCases from ASM_0025 to ASM_0031, you can apply it to stest directory. Any problem pls let me know. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2898) SCA 1.x failed to get the property value for the complex type
[
https://issues.apache.org/jira/browse/TUSCANY-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Becker reassigned TUSCANY-2898:
---
Assignee: Dan Becker
SCA 1.x failed to get the property value for the complex type
-
Key: TUSCANY-2898
URL: https://issues.apache.org/jira/browse/TUSCANY-2898
Project: Tuscany
Issue Type: Bug
Components: Java SCA Assembly Model
Affects Versions: Java-SCA-1.3.1
Reporter: Ku Jun Guo
Assignee: Dan Becker
When I ran the stest case for SCA 1.x, I found it failed
!-- Tests that where a component/ property/ has its value set by means
of a child value/ element, that the type of the value/ element
matches
the type declared for the property/ element --
composite xmlns=http://www.osoa.org/xmlns/sca/1.0;
targetNamespace=http://oasis/tests;
xmlns:tns=http://oasis/tests;
xmlns:test=http://oasis/tests;
name=TEST_ASM_0025
component name=TestClient
implementation.composite name=tns:TestClient_0002/
service name=TestInvocation
interface.java interface=test.TestInvocation/
binding.ws/
/service
reference name=reference1 target=TestComponent1/Service1 /
property name=testNameASM_0025/property
/component
component name=TestComponent1
implementation.composite name=tns:TestComposite12/
service name=Service1
interface.java interface=test.Service1/
/service
property name=serviceNameservice1/property
!-- Property with complex type with a value declared using a
value/ subelement --
property name=complexType type=test:ComplexType1
ComplexType1Value type=test:ComplexType1
test:firstDatacomplex1/test:firstData
test:secondDatacomplex2/test:secondData
/ComplexType1Value
!--
value
firstDatacomplex1/firstData
secondDatacomplex2/secondData
/value
--
/property
/component
/composite
TestComposite12.composite::
composite xmlns=http://www.osoa.org/xmlns/sca/1.0;
targetNamespace=http://oasis/tests;
xmlns:test=http://oasis/tests;
name=TestComposite12
service name=Service1 promote=TestComponent1/Service1
interface.java interface=test.Service1/interface.java
/service
property name=serviceName type=string/
property name=complexType type=test:ComplexType1/
component name=TestComponent1
implementation.java class=test.service1Impl5/
service name=Service1
interface.java interface=test.Service1/
/service
property name=serviceName source=$serviceName/
property name=serviceData1 source=$complexType/firstData/
property name=serviceData2 source=$complexType/secondData/
/component
/composite
service1Impl5.java :
@Service(Service1.class)
public class service1Impl5 implements Service1 {
@Property
public String serviceName = service1;
@Property
public String serviceData1;
@Property
public String serviceData2;
public String operation1(String input) {
return serviceName + operation1 invoked + serviceData1 +
serviceData2;
}
}
Test_Types.xsd:
schema xmlns=http://www.w3.org/2001/XMLSchema;
targetNamespace=http://oasis/tests;
xmlns:test=http://oasis/tests;
xmlns:sca=http://www.osoa.org/xmlns/sca/1.0;
elementFormDefault=qualified
!-- A complex type --
complexType name=ComplexType1
element name=firstData type=string /
element name=secondData type=string /
/complexType
!-- A global element with a complex type --
element name=globalElement1 type=test:ComplexType1/
/schema
Anything wrong with my artifacts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2907) Stest code submit by kujunguo 2009_03_06
[ https://issues.apache.org/jira/browse/TUSCANY-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680504#action_12680504 ] Dan Becker commented on TUSCANY-2907: - Hello Ku Jun Guo, I am seeing test failures in the following test case on branch 1.x, revision 752101: Failed tests: testDummy(client.BaseJAXWSTestCase) testDummy(client.ASM_0028_TestCase) testDummy(client.ASM_0023_TestCase) Are these expected until other Jiras are fixed? Do these match your testing or do we differ? Stest code submit by kujunguo 2009_03_06 Key: TUSCANY-2907 URL: https://issues.apache.org/jira/browse/TUSCANY-2907 Project: Tuscany Issue Type: Test Components: Java SCA Assembly Model Affects Versions: Java-SCA-1.3.1 Reporter: Ku Jun Guo Assignee: Dan Becker Priority: Minor Attachments: Kujunguo_SCA_Assembly_TestCases.doc, stest_20090306_kujunguo.diff Simon, Here is my TestCases from ASM_0025 to ASM_0031, you can apply it to stest directory. Any problem pls let me know. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2901) It should throw a runtime exception when component property name is not matched
[
https://issues.apache.org/jira/browse/TUSCANY-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680510#action_12680510
]
Dan Becker commented on TUSCANY-2901:
-
I can see no requirement in the OSOA or OASIS assembly specification that
requires a failure or exception if a property does not exist in an
implementation. In my view, a warning is appropriate since the value is not
being used, and the builder is letting you know about this. Since the user is
being notified, I think the current behavior is adequate and acceptable.
It should throw a runtime exception when component property name is not
matched
---
Key: TUSCANY-2901
URL: https://issues.apache.org/jira/browse/TUSCANY-2901
Project: Tuscany
Issue Type: Bug
Components: Java SCA Assembly Model
Affects Versions: Java-SCA-1.3.1
Reporter: Ku Jun Guo
If the property name in composite file is not matched with the
implementation, it should throw a ServiceRuntimeException, but in my test, it
just
gave some warning messages.
Mar 4, 2009 9:54:57 AM
org.apache.tuscany.sca.assembly.builder.impl.ComponentConfigurationBuilderImpl
WARNING: Property not found for component property: Component =
TestComponent1 Property = randomName
Mar 4, 2009 9:54:57 AM
org.apache.tuscany.sca.assembly.builder.impl.CompositeBindingURIBuilderImpl
WARNING: Property not found for component property: Component =
TestComponent1 Property = randomName
My composite file:
component name=TestComponent1
implementation.composite name=tns:TestComposite1/
service name=Service1
interface.java interface=test.Service1/
/service
!--
property name=serviceNameservice1/property
--
!-- Property with @name attribute that does not match the @name
attribute of any of the property/ elements in the
componentType/ of the implementation/ --
property name=randomNamerandomValue/property
/component
Service Impl class :
@Service(Service1.class)
public class service1Impl implements Service1 {
@Property
public String serviceName = service1;
public String operation1(String input) {
return serviceName + operation1 invoked;
}
}
Anyone has comments on this? Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2905) Default operation selection does not implement third rule which is supposed to look for an operation name in the root element of the XML payload
[ https://issues.apache.org/jira/browse/TUSCANY-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reassigned TUSCANY-2905: --- Assignee: Dan Becker Default operation selection does not implement third rule which is supposed to look for an operation name in the root element of the XML payload Key: TUSCANY-2905 URL: https://issues.apache.org/jira/browse/TUSCANY-2905 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Reporter: Kaushik Mukherjee Assignee: Dan Becker Attachments: TUSCANY-2905.patch Default operation selection does not implement third rule which is supposed to look for an operation name in the root element of the XML payload The Oasis spec adds a rule to default operation selection as follows: 290 • Otherwise, if the message is a JMS text or bytes message containing XML, then the selected 291 operation name is taken from the local name of the root element of the XML payload. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2905) Default operation selection does not implement third rule which is supposed to look for an operation name in the root element of the XML payload
[ https://issues.apache.org/jira/browse/TUSCANY-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2905. - Resolution: Fixed Hello Kaushik, Thanks for contributing the patch. I've applied it to the 1.x branch and run unit, stests, and itests, and it passes. I have a few suggestions for future patches that will help make it easier to integrate and test: 1) Let us know whether the branch is for trunk or one of the branches. 2) Generate the diff from the module or higher level. 3) Provide a unit test in the patch that tests the positive and negative aspects of the patch. These steps make it easier to find which directory to apply the patch, and the unit tests make it easy to see the fix in action. Default operation selection does not implement third rule which is supposed to look for an operation name in the root element of the XML payload Key: TUSCANY-2905 URL: https://issues.apache.org/jira/browse/TUSCANY-2905 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Reporter: Kaushik Mukherjee Assignee: Dan Becker Attachments: TUSCANY-2905.patch Default operation selection does not implement third rule which is supposed to look for an operation name in the root element of the XML payload The Oasis spec adds a rule to default operation selection as follows: 290 • Otherwise, if the message is a JMS text or bytes message containing XML, then the selected 291 operation name is taken from the local name of the root element of the XML payload. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2897) requestConnection and responseConnection in JMSBinding model should be QNames not Strings
[ https://issues.apache.org/jira/browse/TUSCANY-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reassigned TUSCANY-2897: --- Assignee: Dan Becker requestConnection and responseConnection in JMSBinding model should be QNames not Strings - Key: TUSCANY-2897 URL: https://issues.apache.org/jira/browse/TUSCANY-2897 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Reporter: Greg Dritschler Assignee: Dan Becker Priority: Minor Attachments: tuscany-2897.patch In the JMSBinding model the requestConnection and responseConnection attributes are treated as Strings. According to the schema they are supposed to be QNames (where the namespace is used to locate the definition document and the local part is the binding name). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2897) requestConnection and responseConnection in JMSBinding model should be QNames not Strings
[ https://issues.apache.org/jira/browse/TUSCANY-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2897. - Resolution: Fixed Fix Version/s: Java-SCA-Next Resolved in branch 1.x at revision: 750052 . Thanks for the fix. requestConnection and responseConnection in JMSBinding model should be QNames not Strings - Key: TUSCANY-2897 URL: https://issues.apache.org/jira/browse/TUSCANY-2897 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Reporter: Greg Dritschler Assignee: Dan Becker Priority: Minor Fix For: Java-SCA-Next Attachments: tuscany-2897.patch In the JMSBinding model the requestConnection and responseConnection attributes are treated as Strings. According to the schema they are supposed to be QNames (where the namespace is used to locate the definition document and the local part is the binding name). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2884) [1.x] This jira is used to submit test case
[ https://issues.apache.org/jira/browse/TUSCANY-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reassigned TUSCANY-2884: --- Assignee: Dan Becker [1.x] This jira is used to submit test case Key: TUSCANY-2884 URL: https://issues.apache.org/jira/browse/TUSCANY-2884 Project: Tuscany Issue Type: Test Components: Java SCA Assembly Model Affects Versions: Java-SCA-1.4 Reporter: Shu Chao Wan Assignee: Dan Becker Attachments: composite.patch It's used to submit test case for conformance items 60001-60008, and 60015-60016. Thanks -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2884) [1.x] This jira is used to submit test case
[ https://issues.apache.org/jira/browse/TUSCANY-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12678915#action_12678915 ] Dan Becker commented on TUSCANY-2884: - Hello Shu Chao Wan, Can you investigate this patch? I attempt to use the patch on my \branches\sca-java-1.x\vtest\assembly\composite\ repos and svn complains. For example CService.java in your patch was made from revision 743607. However, when I look at the public repos, CService.java is at the 721498 level. And the branch 1.4 version of CService is at the 722428 revision. So please let us know how you made this patch or let me know if I've misapplied your patch. Thanks. [1.x] This jira is used to submit test case Key: TUSCANY-2884 URL: https://issues.apache.org/jira/browse/TUSCANY-2884 Project: Tuscany Issue Type: Test Components: Java SCA Assembly Model Affects Versions: Java-SCA-1.4 Reporter: Shu Chao Wan Assignee: Dan Becker Attachments: composite.patch It's used to submit test case for conformance items 60001-60008, and 60015-60016. Thanks -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2871) ClassCastException using atom-abdera binding
[
https://issues.apache.org/jira/browse/TUSCANY-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Becker reassigned TUSCANY-2871:
---
Assignee: Dan Becker
ClassCastException using atom-abdera binding
Key: TUSCANY-2871
URL: https://issues.apache.org/jira/browse/TUSCANY-2871
Project: Tuscany
Issue Type: Bug
Components: Java SCA ATOM Binding Extension
Affects Versions: Java-SCA-1.4
Reporter: Brent Daniel
Assignee: Dan Becker
If you use the atom-abdera binding with a reference that points to an RSS
feed rather than an atom feed, you get a ClassCastException rather than a
reasonable error. This occurs in the Tuscany feed-aggregator sample, but the
exception is being swallowed in the java implementation.
From FeedAggregator.composite in the feed-aggregator sample (the uri points
to an RSS 2.0 feed):
reference name=atomFeed1
tuscany:binding.atom
uri=http://www.oreillynet.com/pub/feed/35/
/reference
The following code in AtomBindingInvoker (346-348) results in the
ClassCastException:
DocumentFeed doc = abderaParser.parse(new
InputStreamReader(getMethod.getResponseBodyAsStream()));
parsing = true;
Feed feed = doc.getRoot();
doc.getRoot() returns an instance of
org.apache.abdera.parser.stax.FOMExtensibleElement rather than Feed.
AggregatorImpl in the feed-aggregator sample is swallowing the exception here
(85-89):
if (atomFeed1 != null) {
try {
entries.addAll(atomFeed1.getFeed().getEntries());
} catch (Exception e) {}
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2879) [1.x] ITest failure in TEST-interfacewsdl.xml.InvalidWSDLInterfaceAttrTestCase
[ https://issues.apache.org/jira/browse/TUSCANY-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker closed TUSCANY-2879. --- I'm getting a clean build as well. [1.x] ITest failure in TEST-interfacewsdl.xml.InvalidWSDLInterfaceAttrTestCase -- Key: TUSCANY-2879 URL: https://issues.apache.org/jira/browse/TUSCANY-2879 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-Next Environment: branch 1.x revision 747826 Reporter: Dan Becker Fix For: Java-SCA-Next testcase time=0.094 name=testCalculator failure message=null expected:amp;lt;[InvalidWSDLInterfaceAttr]amp;gt; but was:amp;lt;[AttributeCannotBeProcessed]amp;gt; type=junit.framework.ComparisonFailurejunit.framework.ComparisonFailure: null expected:amp;lt;[InvalidWSDLInterfaceAttr]amp;gt; but was:amp;lt;[AttributeCannotBeProcessed]amp;gt; at junit.framework.Assert.assertEquals(Assert.java:81) at junit.framework.Assert.assertEquals(Assert.java:87) at interfacewsdl.xml.InvalidWSDLInterfaceAttrTestCase.testCalculator(InvalidWSDLInterfaceAttrTestCase.java:58) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:79) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879) /failure -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (TUSCANY-2856) 'property' validation conflicts with osoa spec
[ https://issues.apache.org/jira/browse/TUSCANY-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reopened TUSCANY-2856: - I see when running itest-jms PolicyHeadersTestCase the following error: Feb 25, 2009 8:26:37 AM org.apache.tuscany.sca.contribution.processor.ValidatingXMLStreamReader SEVERE: XMLSchema validation error occured in: null ,line = 25, column = 19, Message = cvc-type.3.1.1: Element 'property' is a simple type, so it cannot have attributes, excepting those whose namespace name is identical to 'http://www.w3.org/2001/XMLSchema-instance' and whose [local name] is one of 'type', 'nil', 'schemaLocation' or 'noNamespaceSchemaLocation'. However, the attribute, 'name' was found. This appears to be the same error as reported by Christopher. I will look into this. 'property' validation conflicts with osoa spec -- Key: TUSCANY-2856 URL: https://issues.apache.org/jira/browse/TUSCANY-2856 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-1.4 Environment: Java JMS Binding extention Reporter: Christopher N. Ortiz Assignee: Dan Becker The validation of 'property' element like this property name=propName type=stringmyvalue/property produced this error: Element 'property' is a simple type, so it cannot have attributes, excepting those whose namespace name is identical to 'http://www.w3.org/2001/XMLSchema-instance' and whose [local name] is one of 'type', 'nil', 'schemaLocation' or 'noNamespaceSchemaLocation'. However, the attribute, 'name' was found. XMLSchema validation error occured in: null ,line = -1, column = -1, Message = cvc-type.3.1.1: But the OSOA SCA JMS spec defines property in header element like this: property name=NMTOKEN type=NMTOKEN* -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2879) [1.x] ITest failure in TEST-interfacewsdl.xml.InvalidWSDLInterfaceAttrTestCase
[1.x] ITest failure in TEST-interfacewsdl.xml.InvalidWSDLInterfaceAttrTestCase -- Key: TUSCANY-2879 URL: https://issues.apache.org/jira/browse/TUSCANY-2879 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-Next Environment: branch 1.x revision 747826 Reporter: Dan Becker testcase time=0.094 name=testCalculator failure message=null expected:amp;lt;[InvalidWSDLInterfaceAttr]amp;gt; but was:amp;lt;[AttributeCannotBeProcessed]amp;gt; type=junit.framework.ComparisonFailurejunit.framework.ComparisonFailure: null expected:amp;lt;[InvalidWSDLInterfaceAttr]amp;gt; but was:amp;lt;[AttributeCannotBeProcessed]amp;gt; at junit.framework.Assert.assertEquals(Assert.java:81) at junit.framework.Assert.assertEquals(Assert.java:87) at interfacewsdl.xml.InvalidWSDLInterfaceAttrTestCase.testCalculator(InvalidWSDLInterfaceAttrTestCase.java:58) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:79) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879) /failure -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2880) [1.x] ITest failure in TEST-binding.jms.UnexpectedElementTestCase
[1.x] ITest failure in TEST-binding.jms.UnexpectedElementTestCase - Key: TUSCANY-2880 URL: https://issues.apache.org/jira/browse/TUSCANY-2880 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-Next Environment: Branch 1.x revision 747826 Reporter: Dan Becker Priority: Minor failure message=null expected:amp;lt;[UnexpectedElement]amp;gt; but was:amp;lt;[SchemaError]amp;gt; type=junit.framework.ComparisonFailurejunit.framework.ComparisonFailure: null expected:amp;lt;[UnexpectedElement]amp;gt; but was:amp;lt;[SchemaError]amp;gt; at junit.framework.Assert.assertEquals(Assert.java:81) at junit.framework.Assert.assertEquals(Assert.java:87) at binding.jms.UnexpectedElementTestCase.testCalculator(UnexpectedElementTestCase.java:58) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:79) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879) /failure -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2857) Correct handling of JMSDeliveryMode and JMSPriority
[ https://issues.apache.org/jira/browse/TUSCANY-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2857. - Resolution: Fixed Fix Version/s: Java-SCA-Next Completed in branch 1.x: At revision: 747867 Correct handling of JMSDeliveryMode and JMSPriority --- Key: TUSCANY-2857 URL: https://issues.apache.org/jira/browse/TUSCANY-2857 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Reporter: Greg Dritschler Assignee: Dan Becker Priority: Minor Fix For: Java-SCA-Next I've noticed that JMSHeaderReferencePolicyInterceptor and TransportServiceInterceptor set the JMSDeliveryMode and JMSPriority headers in the request and response JMS messages respectively before the messages are sent. I am under the impression that the JMS API requires these header values to be set via the MessageProducer interface. The values in the Message are ignored. See Table 31-1 here: http://docs.sun.com/app/docs/doc/819-3669/bnceh?l=jaa=view This issue was discussed on dev list on January 20, 2009 and it was agreed this is a bug. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2856) 'property' validation conflicts with osoa spec
[ https://issues.apache.org/jira/browse/TUSCANY-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2856. - Resolution: Fixed Fix Version/s: Java-SCA-Next Fixed in branch 1.x at revision: 747933 . Thanks Christopher. 'property' validation conflicts with osoa spec -- Key: TUSCANY-2856 URL: https://issues.apache.org/jira/browse/TUSCANY-2856 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-1.4 Environment: Java JMS Binding extention Reporter: Christopher N. Ortiz Assignee: Dan Becker Fix For: Java-SCA-Next The validation of 'property' element like this property name=propName type=stringmyvalue/property produced this error: Element 'property' is a simple type, so it cannot have attributes, excepting those whose namespace name is identical to 'http://www.w3.org/2001/XMLSchema-instance' and whose [local name] is one of 'type', 'nil', 'schemaLocation' or 'noNamespaceSchemaLocation'. However, the attribute, 'name' was found. XMLSchema validation error occured in: null ,line = -1, column = -1, Message = cvc-type.3.1.1: But the OSOA SCA JMS spec defines property in header element like this: property name=NMTOKEN type=NMTOKEN* -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2849) Unable to define operation-level intents on binding.jms
[ https://issues.apache.org/jira/browse/TUSCANY-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2849. - Resolution: Fixed Fix Version/s: Java-SCA-Next Completed in branch 1.x at revision: 745909 Unable to define operation-level intents on binding.jms --- Key: TUSCANY-2849 URL: https://issues.apache.org/jira/browse/TUSCANY-2849 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Reporter: Greg Dritschler Assignee: Dan Becker Priority: Minor Fix For: Java-SCA-Next binding.jms does not appear to support operation-level policy intents. I believe the following needs to be done to add the support. (1) org.apache.tuscany.sca.binding.jms.impl.JMSBinding needs to implement the org.apache.tuscany.sca.assembly.OperationsConfigurator interface. (2) org.apache.tuscany.sca.binding.jms.impl.JMSBindingProcessor needs to implement calls to org.apache.tuscany.sca.assembly.xml.ConfiguredOperationProcessor to read and write the operation elements. The web service binding has an example of how to do this (although it seems to be missing the write logic). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2856) 'property' validation conflicts with osoa spec
[ https://issues.apache.org/jira/browse/TUSCANY-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12675112#action_12675112 ] Dan Becker commented on TUSCANY-2856: - Christopher, On which element of the JMS binding did you specify this property? I tried the following property and found no validation error: binding.jms uri=jms:testQueue headers property name=propName type=stringmyvalue/property /headers /binding.jms I will test other locations for properties in binding.jms to see if Tuscany has different validations. I will report back here if I find a specific location that has a problem. If you have a sample that demonstrates the validation issue, please comment here. 'property' validation conflicts with osoa spec -- Key: TUSCANY-2856 URL: https://issues.apache.org/jira/browse/TUSCANY-2856 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-1.4 Environment: Java JMS Binding extention Reporter: Christopher N. Ortiz Assignee: Dan Becker The validation of 'property' element like this property name=propName type=stringmyvalue/property produced this error: Element 'property' is a simple type, so it cannot have attributes, excepting those whose namespace name is identical to 'http://www.w3.org/2001/XMLSchema-instance' and whose [local name] is one of 'type', 'nil', 'schemaLocation' or 'noNamespaceSchemaLocation'. However, the attribute, 'name' was found. XMLSchema validation error occured in: null ,line = -1, column = -1, Message = cvc-type.3.1.1: But the OSOA SCA JMS spec defines property in header element like this: property name=NMTOKEN type=NMTOKEN* -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2856) 'property' validation conflicts with osoa spec
[ https://issues.apache.org/jira/browse/TUSCANY-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2856. - Resolution: Cannot Reproduce Was able to read and validate the following composite XML using JMSBindingProcessorTestCase code: public static final String HEADERS2 = ?xml version=\1.0\ encoding=\ASCII\? + composite xmlns=\http://www.osoa.org/xmlns/sca/1.0\; targetNamespace=\http://binding-jms\; name=\binding-jms\ + component name=\HelloWorldComponent\ +implementation.java class=\services.HelloWorld\/ + service name=\HelloWorldService\ + binding.jms uri=\jms:testQueue\ + headers JMSType=\myType\ JMSCorrelationID=\myCorrelId\ JMSDeliveryMode=\PERSISTENT\ JMSTimeToLive=\54321\ JMSPriority=\5\ + property name=\First prop\ type=\string\that prop/property + property name=\Second prop\ type=\long\1234567/property + /headers + /binding.jms + /service + /component + /composite; Tuscany had no problem validating and returning the properties. Since this property read code is shared throughout the Tuscany jms.binding, I think the issue is caused outside of Tuscany. 'property' validation conflicts with osoa spec -- Key: TUSCANY-2856 URL: https://issues.apache.org/jira/browse/TUSCANY-2856 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-1.4 Environment: Java JMS Binding extention Reporter: Christopher N. Ortiz Assignee: Dan Becker The validation of 'property' element like this property name=propName type=stringmyvalue/property produced this error: Element 'property' is a simple type, so it cannot have attributes, excepting those whose namespace name is identical to 'http://www.w3.org/2001/XMLSchema-instance' and whose [local name] is one of 'type', 'nil', 'schemaLocation' or 'noNamespaceSchemaLocation'. However, the attribute, 'name' was found. XMLSchema validation error occured in: null ,line = -1, column = -1, Message = cvc-type.3.1.1: But the OSOA SCA JMS spec defines property in header element like this: property name=NMTOKEN type=NMTOKEN* -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2856) 'property' validation conflicts with osoa spec
[ https://issues.apache.org/jira/browse/TUSCANY-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reassigned TUSCANY-2856: --- Assignee: Dan Becker 'property' validation conflicts with osoa spec -- Key: TUSCANY-2856 URL: https://issues.apache.org/jira/browse/TUSCANY-2856 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-1.4 Environment: Java JMS Binding extention Reporter: Christopher N. Ortiz Assignee: Dan Becker The validation of 'property' element like this property name=propName type=stringmyvalue/property produced this error: Element 'property' is a simple type, so it cannot have attributes, excepting those whose namespace name is identical to 'http://www.w3.org/2001/XMLSchema-instance' and whose [local name] is one of 'type', 'nil', 'schemaLocation' or 'noNamespaceSchemaLocation'. However, the attribute, 'name' was found. XMLSchema validation error occured in: null ,line = -1, column = -1, Message = cvc-type.3.1.1: But the OSOA SCA JMS spec defines property in header element like this: property name=NMTOKEN type=NMTOKEN* -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2849) Unable to define operation-level intents on binding.jms
[ https://issues.apache.org/jira/browse/TUSCANY-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reassigned TUSCANY-2849: --- Assignee: Dan Becker Unable to define operation-level intents on binding.jms --- Key: TUSCANY-2849 URL: https://issues.apache.org/jira/browse/TUSCANY-2849 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Reporter: Greg Dritschler Assignee: Dan Becker Priority: Minor binding.jms does not appear to support operation-level policy intents. I believe the following needs to be done to add the support. (1) org.apache.tuscany.sca.binding.jms.impl.JMSBinding needs to implement the org.apache.tuscany.sca.assembly.OperationsConfigurator interface. (2) org.apache.tuscany.sca.binding.jms.impl.JMSBindingProcessor needs to implement calls to org.apache.tuscany.sca.assembly.xml.ConfiguredOperationProcessor to read and write the operation elements. The web service binding has an example of how to do this (although it seems to be missing the write logic). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2855) Holder sample not appearing in 1.x repos
Holder sample not appearing in 1.x repos Key: TUSCANY-2855 URL: https://issues.apache.org/jira/browse/TUSCANY-2855 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-Next Environment: All Reporter: Dan Becker Assignee: Dan Becker Priority: Minor Fix For: Java-SCA-Next Had a bit of trouble comitting holder sample wia Tuscany-2768. Will add holder sample via this Jira. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2855) Holder sample not appearing in 1.x repos
[ https://issues.apache.org/jira/browse/TUSCANY-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2855. - Resolution: Fixed Commited in 1.x branch Completed: At revision: 745215 Holder sample not appearing in 1.x repos Key: TUSCANY-2855 URL: https://issues.apache.org/jira/browse/TUSCANY-2855 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-Next Environment: All Reporter: Dan Becker Assignee: Dan Becker Priority: Minor Fix For: Java-SCA-Next Had a bit of trouble comitting holder sample wia Tuscany-2768. Will add holder sample via this Jira. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2825) JMSBindingProcessor missing 'write' method implementation
[ https://issues.apache.org/jira/browse/TUSCANY-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2825. - Resolution: Fixed Fix Version/s: Java-SCA-Next Fixed in branch 1.x at revision: 743796 JMSBindingProcessor missing 'write' method implementation - Key: TUSCANY-2825 URL: https://issues.apache.org/jira/browse/TUSCANY-2825 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-1.4 Environment: JAva SCA JMS extension Reporter: Christopher N. Ortiz Assignee: Dan Becker Fix For: Java-SCA-Next The 'write' method in JMSBindingProcessor is just a stub and needs to be implemented. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2825) JMSBindingProcessor missing 'write' method implementation
[ https://issues.apache.org/jira/browse/TUSCANY-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker updated TUSCANY-2825: Due Date: 12/Feb/09 JMSBindingProcessor missing 'write' method implementation - Key: TUSCANY-2825 URL: https://issues.apache.org/jira/browse/TUSCANY-2825 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-1.4 Environment: JAva SCA JMS extension Reporter: Christopher N. Ortiz Assignee: Dan Becker The 'write' method in JMSBindingProcessor is just a stub and needs to be implemented. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2825) JMSBindingProcessor missing 'write' method implementation
[ https://issues.apache.org/jira/browse/TUSCANY-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reassigned TUSCANY-2825: --- Assignee: Dan Becker JMSBindingProcessor missing 'write' method implementation - Key: TUSCANY-2825 URL: https://issues.apache.org/jira/browse/TUSCANY-2825 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-1.4 Environment: JAva SCA JMS extension Reporter: Christopher N. Ortiz Assignee: Dan Becker The 'write' method in JMSBindingProcessor is just a stub and needs to be implemented. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2835) JMS Binding does not save operation names unless there are properties.
[ https://issues.apache.org/jira/browse/TUSCANY-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reassigned TUSCANY-2835: --- Assignee: Dan Becker JMS Binding does not save operation names unless there are properties. -- Key: TUSCANY-2835 URL: https://issues.apache.org/jira/browse/TUSCANY-2835 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-1.4 Environment: All Reporter: Dan Becker Assignee: Dan Becker Priority: Minor Fix For: Java-SCA-Next Christopher Ortiz: I believe there is still a problem with the way the OperationProperties element is being processed in the JMSBinding. The new method getOperationNames() will return the keySet from the operationProperties map. However, operationProperties is the map of 'property' found in the 'header' subelement of OperationProperties. If no header element with a property is present in OperationProperties, the operationProperties name (opName) is never set in this map. When the 'operations properties' element is parsed in JMSBindingProcessor in parseOperationProperties, the operation Name attribute (opName) is retrieved from the reader. But it is not saved anywhere. The nativeOperation attribute is read next. If it is present, it is set to a map with the opName as a key. But since the NativeOperation attribute is optional, it may not be present, and the opName is not preserved. Dan Becker: I see what you're saying. It sounds like we need to add operation names, even if there are no properties for the operation name. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2835) JMS Binding does not save operation names unless there are properties.
JMS Binding does not save operation names unless there are properties. -- Key: TUSCANY-2835 URL: https://issues.apache.org/jira/browse/TUSCANY-2835 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-1.4 Environment: All Reporter: Dan Becker Priority: Minor Fix For: Java-SCA-Next Christopher Ortiz: I believe there is still a problem with the way the OperationProperties element is being processed in the JMSBinding. The new method getOperationNames() will return the keySet from the operationProperties map. However, operationProperties is the map of 'property' found in the 'header' subelement of OperationProperties. If no header element with a property is present in OperationProperties, the operationProperties name (opName) is never set in this map. When the 'operations properties' element is parsed in JMSBindingProcessor in parseOperationProperties, the operation Name attribute (opName) is retrieved from the reader. But it is not saved anywhere. The nativeOperation attribute is read next. If it is present, it is set to a map with the opName as a key. But since the NativeOperation attribute is optional, it may not be present, and the opName is not preserved. Dan Becker: I see what you're saying. It sounds like we need to add operation names, even if there are no properties for the operation name. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2835) JMS Binding does not save operation names unless there are properties.
[ https://issues.apache.org/jira/browse/TUSCANY-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2835. - Resolution: Fixed Fixed in branch 1.x at revision: 743094 JMS Binding does not save operation names unless there are properties. -- Key: TUSCANY-2835 URL: https://issues.apache.org/jira/browse/TUSCANY-2835 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-1.4 Environment: All Reporter: Dan Becker Assignee: Dan Becker Priority: Minor Fix For: Java-SCA-Next Christopher Ortiz: I believe there is still a problem with the way the OperationProperties element is being processed in the JMSBinding. The new method getOperationNames() will return the keySet from the operationProperties map. However, operationProperties is the map of 'property' found in the 'header' subelement of OperationProperties. If no header element with a property is present in OperationProperties, the operationProperties name (opName) is never set in this map. When the 'operations properties' element is parsed in JMSBindingProcessor in parseOperationProperties, the operation Name attribute (opName) is retrieved from the reader. But it is not saved anywhere. The nativeOperation attribute is read next. If it is present, it is set to a map with the opName as a key. But since the NativeOperation attribute is optional, it may not be present, and the opName is not preserved. Dan Becker: I see what you're saying. It sounds like we need to add operation names, even if there are no properties for the operation name. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2825) JMSBindingProcessor missing 'write' method implementation
[ https://issues.apache.org/jira/browse/TUSCANY-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672416#action_12672416 ] Dan Becker commented on TUSCANY-2825: - In progress. I'm using the following process to test the JMSBinding write method: 1. Create a new JMSBindingProcessorWriteTestCase 2. For each composite in JMSBindingProcessorTestCase (about 16 examples). 2a. Read the composite from XML String to a JMSBinding model. 2b. Write the JMSBinding model to a XML String. 2c. Read the XML String of 2b to a second JMSBinding model. 2d. Compare the JMSBinding model of 2a to 2c. They should be equal. JMSBindingProcessor missing 'write' method implementation - Key: TUSCANY-2825 URL: https://issues.apache.org/jira/browse/TUSCANY-2825 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-1.4 Environment: JAva SCA JMS extension Reporter: Christopher N. Ortiz Assignee: Dan Becker The 'write' method in JMSBindingProcessor is just a stub and needs to be implemented. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2826) Sample READMEs have mistakes
Sample READMEs have mistakes Key: TUSCANY-2826 URL: https://issues.apache.org/jira/browse/TUSCANY-2826 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-2.0 Environment: All Reporter: Dan Becker Priority: Minor 1) README in samples directory mentions lib directory rather than modules directory, and it does not match the README info in lower sample subdirs. 2) implementation-java-calculator does not run with instructions given in its README (on Windows XP, IBM JDK 1.6.0) From this launch: java -jar ..\..\features\tuscany-sca-equinox-manifest.jar -composite Calculator.composite -config ..\..\features\configuration\ -ttl 0 target\implementation-java-calculator.jar I get: SEVERE: SCA Node could not be created Throwable occurred: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ... org.apache.tuscany.sca.node.equinox.launcher.NodeMain.main(NodeMain.java:59) Caused by: org.oasisopen.sca.ServiceRuntimeException: org.apache.tuscany.sca.contribution.processor.ContributionReadException: java.io.FileNotFoundException: E:\t\tuscany-sca-2.0-M1\samples\implementation-java-calculator\target\implementati on-java-calculator.jar (The system cannot find the file specified.) ... The file is named sample-implementation-java-calculator.jar and not implementation-java-calculator.jar -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2826) Sample READMEs have mistakes
[ https://issues.apache.org/jira/browse/TUSCANY-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2826. - Resolution: Fixed Fix Version/s: Java-SCA-Next Resolved in trunk at revision: 742589 Sample READMEs have mistakes Key: TUSCANY-2826 URL: https://issues.apache.org/jira/browse/TUSCANY-2826 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-2.0 Environment: All Reporter: Dan Becker Assignee: Dan Becker Priority: Minor Fix For: Java-SCA-Next 1) README in samples directory mentions lib directory rather than modules directory, and it does not match the README info in lower sample subdirs. 2) implementation-java-calculator does not run with instructions given in its README (on Windows XP, IBM JDK 1.6.0) From this launch: java -jar ..\..\features\tuscany-sca-equinox-manifest.jar -composite Calculator.composite -config ..\..\features\configuration\ -ttl 0 target\implementation-java-calculator.jar I get: SEVERE: SCA Node could not be created Throwable occurred: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ... org.apache.tuscany.sca.node.equinox.launcher.NodeMain.main(NodeMain.java:59) Caused by: org.oasisopen.sca.ServiceRuntimeException: org.apache.tuscany.sca.contribution.processor.ContributionReadException: java.io.FileNotFoundException: E:\t\tuscany-sca-2.0-M1\samples\implementation-java-calculator\target\implementati on-java-calculator.jar (The system cannot find the file specified.) ... The file is named sample-implementation-java-calculator.jar and not implementation-java-calculator.jar -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (TUSCANY-2806) Modules in the build depend on modules later on in the build
[ https://issues.apache.org/jira/browse/TUSCANY-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reopened TUSCANY-2806: - Raymond, your fix helped and got me further on into a clean build, but I see the following clean repos build error [jar] Building jar: E:\t\java\sca\distribution\all\target\apache-tuscany-s ca-all-2.0-SNAPSHOT-dir\tuscany-sca-2.0-SNAPSHOT\samples\calculator-rmi-referenc e\target\sample-calculator-rmi-reference.jar run: [java] Feb 6, 2009 9:28:05 AM org.apache.tuscany.sca.node.impl.NodeImpl in it [java] INFO: Creating node: CalculatorRMIReference.composite [java] Feb 6, 2009 9:28:05 AM org.apache.tuscany.sca.node.impl.NodeImpl con figureNode [java] INFO: Loading contribution: file:/E:/t/java/sca/distribution/all/tar get/apache-tuscany-sca-all-2.0-SNAPSHOT-dir/tuscany-sca-2.0-SNAPSHOT/samples/cal culator-rmi-reference/target/sample-calculator-rmi-reference.jar [java] Feb 6, 2009 9:28:06 AM org.apache.tuscany.sca.node.impl.NodeImpl sta rt [java] INFO: Starting node: CalculatorRMIReference.composite [java] Exception in thread main java.lang.reflect.InvocationTargetExcepti on [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces sorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet hodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:597) [java] at org.apache.tuscany.sca.launcher.LauncherMain.invokeMainMethod (LauncherMain.java:110) [java] at org.apache.tuscany.sca.launcher.LauncherMain.main(LauncherMai n.java:55) [java] Caused by: org.apache.tuscany.sca.host.rmi.RMIHostRuntimeException: Connection refused to host: localhost; nested exception is: [java] java.net.ConnectException: Connection refused: connect [java] at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java: 601) [java] at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel. java:198) [java] at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.jav a:184) [java] at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322) [java] at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source) [java] at org.apache.tuscany.sca.host.rmi.DefaultRMIHost.findService(De faultRMIHost.java:106) [java] at org.apache.tuscany.sca.host.rmi.ExtensibleRMIHost.findService (ExtensibleRMIHost.java:56) [java] at org.apache.tuscany.sca.binding.rmi.provider.RMIBindingInvoker .invokeTarget(RMIBindingInvoker.java:80) [java] at org.apache.tuscany.sca.binding.rmi.provider.RMIBindingInvoker .invoke(RMIBindingInvoker.java:54) [java] at org.apache.tuscany.sca.core.invocation.impl.JDKInvocationHand ler.invoke(JDKInvocationHandler.java:289) [java] at org.apache.tuscany.sca.core.invocation.impl.JDKInvocationHand ler.invoke(JDKInvocationHandler.java:156) [java] at $Proxy6.add(Unknown Source) [java] at calculator.CalculatorServiceImpl.add(CalculatorServiceImpl.ja va:54) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces sorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet hodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:597) [java] at org.apache.tuscany.sca.implementation.java.invocation.JavaImp lementationInvoker.invoke(JavaImplementationInvoker.java:132) [java] at org.apache.tuscany.sca.core.databinding.wire.PassByValueInter ceptor.invoke(PassByValueInterceptor.java:112) [java] at org.apache.tuscany.sca.binding.sca.provider.SCABindingInvoker .invoke(SCABindingInvoker.java:61) [java] at org.apache.tuscany.sca.core.databinding.wire.PassByValueInter ceptor.invoke(PassByValueInterceptor.java:112) [java] at org.apache.tuscany.sca.core.invocation.impl.JDKInvocationHand ler.invoke(JDKInvocationHandler.java:289) [java] at org.apache.tuscany.sca.core.invocation.impl.JDKInvocationHand ler.invoke(JDKInvocationHandler.java:156) [java] at $Proxy5.add(Unknown Source) [java] at calculator.CalculatorClient.main(CalculatorClient.java:40) [java] ... 6 more [java] Feb 6, 2009 9:28:26 AM org.apache.tuscany.sca.node.launcher.NodeLaun cher main [java] INFO: SCA Node is now started. [java] Feb 6, 2009 9:28:26 AM org.apache.tuscany.sca.node.launcher.NodeLaun cher main [java] INFO: Waiting for 4000 milliseconds ... [java] Feb 6, 2009 9:28:30 AM org.apache.tuscany.sca.node.impl.NodeImpl sto p [java] INFO: Stopping node: null [java] Feb 6, 2009 9:28:30 AM org.apache.tuscany.sca.node.launcher.NodeLaun cher stopNode
[jira] Assigned: (TUSCANY-2804) Component-Type Calculator iTest fails with NPE
[ https://issues.apache.org/jira/browse/TUSCANY-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reassigned TUSCANY-2804: --- Assignee: (was: Dan Becker) Unassigning as I do not have a machine to reproduce the problem on Red Hat. Component-Type Calculator iTest fails with NPE -- Key: TUSCANY-2804 URL: https://issues.apache.org/jira/browse/TUSCANY-2804 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Affects Versions: Java-SCA-2.0-M1 Reporter: Luciano Resende Fix For: Java-SCA-2.0-M1 java.lang.NullPointerException at calculator.CalculatorServiceImpl.add(CalculatorServiceImpl.java:48) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:132) at org.apache.tuscany.sca.binding.sca.provider.SCABindingInvoker.invoke(SCABindingInvoker.java:61) at org.apache.tuscany.sca.core.invocation.impl.JDKInvocationHandler.invoke(JDKInvocationHandler.java:289) at org.apache.tuscany.sca.core.invocation.impl.JDKInvocationHandler.invoke(JDKInvocationHandler.java:156) at $Proxy6.add(Unknown Source) at calculator.CalculatorTestCase.testCalculator(CalculatorTestCase.java:55) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41) at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.ParentRunner.run(ParentRunner.java:220) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2821) No method available on JMSBinding to retreive set of operationPropertiesNames
[ https://issues.apache.org/jira/browse/TUSCANY-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2821. - Resolution: Fixed Fixed in 1.x branch at revision: 741694 . Added JMS binding APIs: public SetString getOperationNames(); public Object getOperationProperty(String opName, String propName ); and appropriate test cases. No method available on JMSBinding to retreive set of operationPropertiesNames - Key: TUSCANY-2821 URL: https://issues.apache.org/jira/browse/TUSCANY-2821 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-1.4 Environment: Java SCA JMSBinding Reporter: Christopher N. Ortiz Assignee: Dan Becker Priority: Critical The operationProperties element can appear multiple times in a JMS Binding. All of the get methods for sub elements of the operationProperties require the opName as an argument to determine which operationProperties element to access. But there is no method available to get the key set of operationProperties Names. Without the name set to key off of, it is impossible to determine which operationProperties element to reference. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2806) Modules in the build depend on modules later on in the build
[ https://issues.apache.org/jira/browse/TUSCANY-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2806. - Resolution: Fixed Like ointment on the infected area, revisions 741409 and 741626 cleared up my build problems. Thanks Raymond and Ant. Modules in the build depend on modules later on in the build - Key: TUSCANY-2806 URL: https://issues.apache.org/jira/browse/TUSCANY-2806 Project: Tuscany Issue Type: Bug Reporter: ant elder Priority: Blocker Fix For: Java-SCA-2.0-M1 Modules in the build depend on modules later on in the build which means when building them they either fail if its the first time you are building or if the later on module has been changed then the change isn't used until a subsequent build. I think this is one of the reasons we're having so many build problems - you make a change run a build and its fine so check it in, but the changed wasn't used and its not till the next build it gets picked up and you can see if the change was ok or not. I think we need to move some thing out of the sca build into separate build and releasable artifacts and other things restructure the build so it runs in a better order. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2766) Warning message conflicts with conformance item ASM60008
[
https://issues.apache.org/jira/browse/TUSCANY-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Becker reassigned TUSCANY-2766:
---
Assignee: Dan Becker
Warning message conflicts with conformance item ASM60008
-
Key: TUSCANY-2766
URL: https://issues.apache.org/jira/browse/TUSCANY-2766
Project: Tuscany
Issue Type: Bug
Components: Java SCA Assembly Model
Affects Versions: Java-SCA-1.3
Reporter: Shu Chao Wan
Assignee: Dan Becker
Attachments: ASM60008.patch
I'm testing conformance item ASM60008, and found something strange.
In ASM60008, it says that The interfaces of the component references
promoted by a composite reference MUST be the same, or if the composite
reference itself declares an interface then all the component reference
interfaces must be compatible with the composite reference interface.
Compatible means that the component reference interface is the same or is a
strict subset of the composite reference interface.
In order to verify this statement, I wrote a composite file like that
composite...
service name=AService promote=AComponent/
component name=AComponent
implementation.java
class=org.apache.tuscany.sca.vtest.assembly.composite.impl.AServiceImpl /
reference name=b/
reference name=c
interface.java
interface=org.apache.tuscany.sca.vtest.assembly.composite.CService /
/reference
/component
reference name=c promote=AComponent/c
interface.java
interface=org.apache.tuscany.sca.vtest.assembly.composite.CSuperService /
/reference
reference name=b promote=AComponent/b/
service
/composite
Here, the interface CSuperService is super set of interface CService, that is
to say, interface CSuperServicecontains more methods than interface CService
does.
But when I load this composite file, I got warning message:
Jan 12, 2009 11:27:27 AM
org.apache.tuscany.sca.assembly.builder.impl.CompositePromotionBuilderImpl
WARNING: Interface of composite reference AComponent/c must be compatible
with the interface declared by promoted component reference.
Jan 12, 2009 11:27:27 AM
org.apache.tuscany.sca.assembly.builder.impl.ComponentReferenceWireBuilderImpl
WARNING: Incompatible interfaces on component reference and target: Composite
= {http://assembly-tests}Assembly-sub-reference-interface-outer-Composite
Reference = c Service = CComponent
It seems that this warning message conflicts with this conformance item,
which causes that service can not be invoked correctly in the following test.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2755) Tuscany 1.3.2 and STP-SCA tooling Integration
[ https://issues.apache.org/jira/browse/TUSCANY-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12670827#action_12670827 ] Dan Becker commented on TUSCANY-2755: - https://bugs.eclipse.org/bugs/show_bug.cgi?id=261222 Status|RESOLVED Resolution|FIXED --- Comment #10 from Stéphane Drapeau stephane.drap...@obeo.fr 2009-02-05 11:48:24 -0400 --- Fixed. Commit #2883. Tuscany 1.4 is now supported. Dan, if you have an opportunity to test the tools, I'm interested in your feedback. Thanks for your contribution. I will give this one a test in the near future. If anyone else wants to test the Eclipse STP tools, feel free to do a 1.4 composite, and report back here or on the dev list. Tuscany 1.3.2 and STP-SCA tooling Integration - Key: TUSCANY-2755 URL: https://issues.apache.org/jira/browse/TUSCANY-2755 Project: Tuscany Issue Type: Improvement Components: Java SCA Tools Reporter: Dhaval Chauhan Assignee: Dan Becker Attachments: Tuscany-Eclipse_STP_SCA integration.doc Attached word document explains the current status of integration of eclipse STP-SCA tool with Tuscany's latest release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2701) NPE when verifying conformance item ASM60006 in OASIS sepc
[ https://issues.apache.org/jira/browse/TUSCANY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reassigned TUSCANY-2701: --- Assignee: Dan Becker NPE when verifying conformance item ASM60006 in OASIS sepc -- Key: TUSCANY-2701 URL: https://issues.apache.org/jira/browse/TUSCANY-2701 Project: Tuscany Issue Type: Test Components: Java SCA Assembly Model Affects Versions: Java-SCA-1.3 Reporter: Shu Chao Wan Assignee: Dan Becker Priority: Minor Conformance item 60006 says that, The name of a composite reference/ element MUST be unique across all the composite references in the composite. According to the above description, I wrote a composite file inner.composite with two same composite reference/ element NonUniqueReference within the composite. --- inner.composite --- composite ... service name=AService promote=AComponent/ component name=AComponent reference name=b / reference name=c / /component reference name=NonUniqueReference promote=AComponent/b / reference name=NonUniqueReference promote=AComponent/c / /composite And a outer composite file to use inner composite as the implementation of component. --- outer.composite --- composite component name=TestNonUniqueReferenceComponent implementation.composite name=assembly-tests:Assembly-non-unique-reference-inner--Composite/ reference name=NonUniqueReference target=BComponent/ reference name=NonUniqueReference target=CComponent/ /component component name=BComponent implementation.java class=org.apache.tuscany.sca.vtest.assembly.composite.impl.BServiceImpl/ property name=somePropertysome b component value/property /component component name=CComponent implementation.java class=org.apache.tuscany.sca.vtest.assembly.composite.impl.CServiceImpl/ /component /composite When I invoke two different methods from the component service AService, I got NullPointerException from one method invocation. -- TestCase -- initDomain(nonuniquereference_outer.composite); AService service = ServiceFinder.getService(AService.class, TestNonUniqueReferenceComponent/AService); service.getBProperty(); service.getState(); cleanupDomain(); Here is the detailed info about exception --- Exception Trace --- java.lang.NullPointerException at org.apache.tuscany.sca.vtest.assembly.composite.impl.AServiceImpl.getBProperty(AServiceImpl.java:43) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:132) at org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:287) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154) at $Proxy9.getBProperty(Unknown Source) at org.apache.tuscany.sca.vtest.assembly.composite.CompositeTestCase.ASM60006(CompositeTestCase.java:209) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46) at
[jira] Assigned: (TUSCANY-2821) No method available on JMSBinding to retreive set of operationPropertiesNames
[ https://issues.apache.org/jira/browse/TUSCANY-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reassigned TUSCANY-2821: --- Assignee: Dan Becker No method available on JMSBinding to retreive set of operationPropertiesNames - Key: TUSCANY-2821 URL: https://issues.apache.org/jira/browse/TUSCANY-2821 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-1.4 Environment: Java SCA JMSBinding Reporter: Christopher N. Ortiz Assignee: Dan Becker Priority: Critical The operationProperties element can appear multiple times in a JMS Binding. All of the get methods for sub elements of the operationProperties require the opName as an argument to determine which operationProperties element to access. But there is no method available to get the key set of operationProperties Names. Without the name set to key off of, it is impossible to determine which operationProperties element to reference. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2806) Modules in the build depend on modules later on in the build
[ https://issues.apache.org/jira/browse/TUSCANY-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12670907#action_12670907 ] Dan Becker commented on TUSCANY-2806: - I see this issue as well. I updated to trunk revision 741267 and I see --- T E S T S --- Running calculator.CalculatorTestCase Feb 5, 2009 2:49:59 PM org.apache.tuscany.sca.node.equinox.launcher.NodeLauncher Util collectClasspathEntries INFO: Runtime classpath: 1 JAR from E:\t\java\sca\modules\node-launcher-equinox\ target Feb 5, 2009 2:49:59 PM org.apache.tuscany.sca.node.equinox.launcher.NodeLauncher Util collectClasspathEntries INFO: Runtime classpath: 6 JARs from E:\t\java\sca\modules\node-launcher-equinox Feb 5, 2009 2:49:59 PM org.apache.tuscany.sca.node.equinox.launcher.NodeLauncher Util collectClassLoaderClasspathEntries INFO: Runtime classpath: 1 JAR from application classpath. Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.813 sec FA ILURE! calculator.CalculatorTestCase Time elapsed: 0 sec ERROR! java.lang.IllegalStateException: java.lang.NullPointerException at org.apache.tuscany.sca.node.equinox.launcher.EquinoxHost.start(Equino xHost.java:329) at org.apache.tuscany.sca.node.equinox.launcher.NodeLauncher.init(Node Launcher.java:62) at org.apache.tuscany.sca.node.equinox.launcher.NodeLauncher.newInstance (NodeLauncher.java:71) at calculator.CalculatorTestCase.setUpBeforeClass(CalculatorTestCase.jav a:44) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(Framework Method.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCal lable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMe thod.java:41) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores. java:27) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.ja va:31) at org.junit.runners.ParentRunner.run(ParentRunner.java:220) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet. java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTes tSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(Ab stractDirectoryTestSuite.java:127) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(Su refireBooter.java:338) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.j ava:997) Caused by: java.lang.NullPointerException at org.apache.tuscany.sca.node.equinox.launcher.EquinoxHost.start(Equino xHost.java:289) ... 23 more This is on Windows with Sun JDK 1.6.0_11. I'll report in a moment how the subsequent build runs. Modules in the build depend on modules later on in the build - Key: TUSCANY-2806 URL: https://issues.apache.org/jira/browse/TUSCANY-2806 Project: Tuscany Issue Type: Bug Reporter: ant elder Priority: Blocker Fix For: Java-SCA-2.0-M1 Modules in the build depend on modules later on in the build which means when building them they either fail if its the first time you are building or if the later on module has been changed then the change isn't used until a subsequent build. I think this is one of the reasons we're having so many build problems - you make a change run a build and its fine so check it in, but the changed wasn't used and its not till the next build it gets picked up and you can see if the change was ok or not. I think we need to move some thing out of the sca build into separate build and releasable artifacts and other things restructure the build so it runs in a better order. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2804) Component-Type Calculator iTest fails with NPE
[ https://issues.apache.org/jira/browse/TUSCANY-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12670532#action_12670532 ] Dan Becker commented on TUSCANY-2804: - Hey Luciano. I definitely have component-type running (it is not commented out). I tried clean/build/test with IBM Java 1.5 and Sun and IBM Java 1.6. All seemed to work for me. Strange. So it could be Red-Hat issue. Could you try with a different JVM? Component-Type Calculator iTest fails with NPE -- Key: TUSCANY-2804 URL: https://issues.apache.org/jira/browse/TUSCANY-2804 Project: Tuscany Issue Type: Bug Components: Java SCA Integration Tests Affects Versions: Java-SCA-2.0-M1 Reporter: Luciano Resende Assignee: Dan Becker Fix For: Java-SCA-2.0-M1 java.lang.NullPointerException at calculator.CalculatorServiceImpl.add(CalculatorServiceImpl.java:48) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:132) at org.apache.tuscany.sca.binding.sca.provider.SCABindingInvoker.invoke(SCABindingInvoker.java:61) at org.apache.tuscany.sca.core.invocation.impl.JDKInvocationHandler.invoke(JDKInvocationHandler.java:289) at org.apache.tuscany.sca.core.invocation.impl.JDKInvocationHandler.invoke(JDKInvocationHandler.java:156) at $Proxy6.add(Unknown Source) at calculator.CalculatorTestCase.testCalculator(CalculatorTestCase.java:55) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41) at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.ParentRunner.run(ParentRunner.java:220) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2807) Automate JavaDocs production
Automate JavaDocs production Key: TUSCANY-2807 URL: https://issues.apache.org/jira/browse/TUSCANY-2807 Project: Tuscany Issue Type: Improvement Components: Java SCA Documentation Environment: Java Reporter: Dan Becker Priority: Minor Fix For: Java-SCA-2.0 Provide Maven profile, Ant scripts, or other automation to produce JavaDocs for a Tuscany release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2807) Automate JavaDocs production
[ https://issues.apache.org/jira/browse/TUSCANY-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reassigned TUSCANY-2807: --- Assignee: Dan Becker Automate JavaDocs production Key: TUSCANY-2807 URL: https://issues.apache.org/jira/browse/TUSCANY-2807 Project: Tuscany Issue Type: Improvement Components: Java SCA Documentation Environment: Java Reporter: Dan Becker Assignee: Dan Becker Priority: Minor Fix For: Java-SCA-2.0 Provide Maven profile, Ant scripts, or other automation to produce JavaDocs for a Tuscany release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2743) [Documentation] Improve user documentation for SCA Java
[ https://issues.apache.org/jira/browse/TUSCANY-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12669960#action_12669960 ] Dan Becker commented on TUSCANY-2743: - Note that Tuscany Jira http://issues.apache.org/jira/browse/TUSCANY-2485 provided docs for Tuscany 1.4. This is one component of improving user documentation. They are available in SVN at http://svn.apache.org/repos/asf/tuscany/site/site-publish/doc/javadoc/java-sca-1.4/ [Documentation] Improve user documentation for SCA Java --- Key: TUSCANY-2743 URL: https://issues.apache.org/jira/browse/TUSCANY-2743 Project: Tuscany Issue Type: Improvement Components: Website Reporter: haleh mahbod Assignee: haleh mahbod Priority: Critical Fix For: Java-SCA-Next Need to majorly enhance user documentation. Trying to get more information from users as to what is exactly missing. Meanwhile I am going through the website and ensuring the basic concepts are clear and have sufficient examples. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2755) Tuscany 1.3.2 and STP-SCA tooling Integration
[ https://issues.apache.org/jira/browse/TUSCANY-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reassigned TUSCANY-2755: --- Assignee: Dan Becker Tuscany 1.3.2 and STP-SCA tooling Integration - Key: TUSCANY-2755 URL: https://issues.apache.org/jira/browse/TUSCANY-2755 Project: Tuscany Issue Type: Improvement Components: Java SCA Tools Reporter: Dhaval Chauhan Assignee: Dan Becker Attachments: Tuscany-Eclipse_STP_SCA integration.doc Attached word document explains the current status of integration of eclipse STP-SCA tool with Tuscany's latest release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2803) Module Apache Tuscany SCA Node Implementation Model: stop searching after the first matching component.
[
https://issues.apache.org/jira/browse/TUSCANY-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Becker resolved TUSCANY-2803.
-
Resolution: Fixed
Fix Version/s: Java-SCA-Next
Resolved in branch 1.x at revision: 740031. Thanks for bringing up the issue.
Module Apache Tuscany SCA Node Implementation Model: stop searching after
the first matching component.
-
Key: TUSCANY-2803
URL: https://issues.apache.org/jira/browse/TUSCANY-2803
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-1.4
Reporter: Radu Fantaziu
Assignee: Dan Becker
Priority: Minor
Fix For: Java-SCA-Next
The following code extracted from
org.apache.tuscany.sca.node.impl.NodeImpl.getServiceReference()
for (Component compositeComponent : composite.getComponents()) {
if (compositeComponent.getName().equals(componentName)) {
component = compositeComponent;
}
}
should be:
..
for (Component compositeComponent : composite.getComponents()) {
if (compositeComponent.getName().equals(componentName)) {
component = compositeComponent;
break;
}
}
.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2485) java API documentation outdated
[ https://issues.apache.org/jira/browse/TUSCANY-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12669249#action_12669249 ] Dan Becker commented on TUSCANY-2485: - Note that generating the docs for Tuscany 1.4, the javadoc tool exists with a ClassCastException, preventing generating the full Javadocs: java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl incompatible wi th com.sun.javadoc.AnnotationTypeDoc at com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDes cImpl.java:58) at com.sun.tools.doclets.internal.toolkit.util.Util.isDeprecated(Util.ja va:823) at com.sun.tools.doclets.formats.html.AbstractIndexWriter.printComment(A bstractIndexWriter.java:191) at com.sun.tools.doclets.formats.html.AbstractIndexWriter.printDescripti on(AbstractIndexWriter.java:176) at com.sun.tools.doclets.formats.html.AbstractIndexWriter.generateConten ts(AbstractIndexWriter.java:101) at com.sun.tools.doclets.formats.html.SingleIndexWriter.generateIndexFil e(SingleIndexWriter.java:89) at com.sun.tools.doclets.formats.html.SingleIndexWriter.generate(SingleI ndexWriter.java:64) at com.sun.tools.doclets.formats.html.HtmlDoclet.generateOtherFiles(Html Doclet.java:115) at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration (AbstractDoclet.java:134) at com.sun.tools.doclets.internal.toolkit.AbstractDoclet.start(AbstractD oclet.java:76) at com.sun.tools.doclets.formats.html.HtmlDoclet.start(HtmlDoclet.java:5 4) at com.sun.tools.doclets.standard.Standard.start(Standard.java:35) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:45) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:577) at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:227) at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:103) at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:352) at com.sun.tools.javadoc.Start.begin(Start.java:140) at com.sun.tools.javadoc.Main.execute(Main.java:52) at com.sun.tools.javadoc.Main.main(Main.java:42) I ran into this exception with IBM JDK 1.5, IBM JDK 1.6, Sun JDK 1.5 and Sun JDK 1.6.0_11. I found this unsolved bug describing the unresolved issue: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6442982 java API documentation outdated --- Key: TUSCANY-2485 URL: https://issues.apache.org/jira/browse/TUSCANY-2485 Project: Tuscany Issue Type: Bug Components: Java SCA Documentation, Website Affects Versions: Java-SCA-1.2 Reporter: Malte Marquarding Assignee: Dan Becker Fix For: Java-SCA-Next The java API documentation is outdated - it reflects java-sca-0.9, see http://tuscany.apache.org/doc/javadoc/ Please update this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2776) The JMSBindingProcessor does not perform validation of binding properties
[
https://issues.apache.org/jira/browse/TUSCANY-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Becker resolved TUSCANY-2776.
-
Resolution: Fixed
Fix Version/s: Java-SCA-Next
Commited to the 1.x branch at revision: 739312
The JMSBindingProcessor does not perform validation of binding properties
-
Key: TUSCANY-2776
URL: https://issues.apache.org/jira/browse/TUSCANY-2776
Project: Tuscany
Issue Type: Bug
Components: Java SCA JMS Binding Extension
Affects Versions: Java-SCA-1.4
Environment: All
Reporter: Simon Laws
Assignee: Dan Becker
Fix For: Java-SCA-Next
The JMS binding spec defines some cross field validations. The validate()
method in the JMSBindingProcessor is as follows.
/**
* The validation rules for the JMS model are relatively complicated to
they all live together here
*/
public void validate() throws JMSBindingException {
/*
* first fix up anything now the model has been read
*/
/*
* Now some cross field validation
*/
// connection factory doesn't contradict destination type
// connection factory and activation Specification are mutually
exclusive
// TODO check Specification for all validations
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2485) java API documentation outdated
[ https://issues.apache.org/jira/browse/TUSCANY-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12668069#action_12668069 ] Dan Becker commented on TUSCANY-2485: - For now we have generated a temporary JavaDoc for Tuscany 1.4 at http://people.apache.org/~beckerdo/tuscany/javadoc-sca-1.4/. After some comments on the docs, we will generate a final version and place in SVN. Thanks for bringing this up. java API documentation outdated --- Key: TUSCANY-2485 URL: https://issues.apache.org/jira/browse/TUSCANY-2485 Project: Tuscany Issue Type: Bug Components: Java SCA Documentation, Website Affects Versions: Java-SCA-1.2 Reporter: Malte Marquarding Assignee: Dan Becker Fix For: Java-SCA-Next The java API documentation is outdated - it reflects java-sca-0.9, see http://tuscany.apache.org/doc/javadoc/ Please update this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2754) NPE received when wsdlElement is incorrectly specified
[ https://issues.apache.org/jira/browse/TUSCANY-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2754. - Resolution: Invalid Invalid port is flagged by Tuscany. Caller program ignores flag and continues use of model to build WSDL. NPE received when wsdlElement is incorrectly specified --- Key: TUSCANY-2754 URL: https://issues.apache.org/jira/browse/TUSCANY-2754 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-1.3 Environment: Tuscany 1.3.1 Reporter: Lou Amodeo Assignee: Dan Becker When one inadvertently specifies an incorrect wsdlElement service name as part of the wsdl.port a NPE is thrown rather than a validation exception. It also appears that in general there is no validation occurring for the wsdlElment namespace, service, port, or binding names. Instead NPE exceptions occur in different locations making it difficult to diagnose the problem. I think the wsdlElement's attributes need to be validated with the appropriate error messages emitted to identify the corrections required. This particular error can reproduced by specifying a service in wsdl.port that does not refer to a service in the contributed wsdl. java.lang.NullPointerException at org.apache.tuscany.sca.binding.ws.wsdlgen.WSDLServiceGenerator.configureWSDLDefinition(WSDLServiceGenerator.java:247) at org.apache.tuscany.sca.binding.ws.wsdlgen.BindingWSDLGenerator.createWSDLDocument(BindingWSDLGenerator.java:277) at org.apache.tuscany.sca.binding.ws.wsdlgen.BindingWSDLGenerator.generateWSDL(BindingWSDLGenerator.java:172) at org.apache.tuscany.sca.binding.ws.xml.BindingBuilderImpl.build(BindingBuilderImpl.java:55) at org.apache.tuscany.sca.assembly.builder.impl.ComponentServiceBindingBuilderImpl.buildServiceBindings(ComponentServiceBindingBuilderImpl.java:66) at org.apache.tuscany.sca.assembly.builder.impl.ComponentServiceBindingBuilderImpl.build(ComponentServiceBindingBuilderImpl.java:48) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2485) java API documentation outdated
[ https://issues.apache.org/jira/browse/TUSCANY-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reassigned TUSCANY-2485: --- Assignee: Dan Becker java API documentation outdated --- Key: TUSCANY-2485 URL: https://issues.apache.org/jira/browse/TUSCANY-2485 Project: Tuscany Issue Type: Bug Components: Java SCA Documentation, Website Affects Versions: Java-SCA-1.2 Reporter: Malte Marquarding Assignee: Dan Becker Fix For: Java-SCA-Next The java API documentation is outdated - it reflects java-sca-0.9, see http://tuscany.apache.org/doc/javadoc/ Please update this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2579) Tuscany Schemas use sequences which makes the composite elements to have order, while that is not the case with Spec
[
https://issues.apache.org/jira/browse/TUSCANY-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Becker resolved TUSCANY-2579.
-
Resolution: Won't Fix
OSOA closed this issue with no action and will not update the spec here. Since
Tuscany must follow the OSOA spec for this issue, we cannot add choice and must
follow java.implementation in the same order as OSOA specs.
Tuscany Schemas use sequences which makes the composite elements to have
order, while that is not the case with Spec
Key: TUSCANY-2579
URL: https://issues.apache.org/jira/browse/TUSCANY-2579
Project: Tuscany
Issue Type: Bug
Components: Java SCA Problem Determination
Environment: All
Reporter: Hasan Muhammad
Fix For: Java-SCA-Next
The schema for component is as such:
element name=componentType type=sca:ComponentType/
complexType name=ComponentType
sequence
choice minOccurs=0 maxOccurs=1
element ref=sca:implementation/
any namespace=##other processContents=lax/
/choice
choice minOccurs=0 maxOccurs=unbounded
element name=service type=sca:ComponentService /
element name=reference type=sca:ComponentReference/
element name=property type=sca:Property/
/choice
!--
any namespace=##other processContents=lax minOccurs=0
maxOccurs=unbounded/
--
/sequence
attribute name=constrainingType type=QName use=optional/
anyAttribute namespace=##any processContents=lax/
/complexType
This forces the user to have the element implementation.java before the
other elements such as service, reference etc, which should not be the case.
The following error is generated
alidatingXML E XMLSchema validation error occured in: null ,line = -1,
column = -1, Message = cvc-complex-type.2.4.a: Invalid content was found
starting with element 'implementation.java'. One of
'{http://www.osoa.org/xmlns/sca/1.0:service,
http://www.osoa.org/xmlns/sca/1.0:reference,
http://www.osoa.org/xmlns/sca/1.0:property}' is expected.
So the schema needs to be changed. This problem may exist at other places in
this schema and other schemas as well
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2583) only first method's parameter is send in JMS Message
[
https://issues.apache.org/jira/browse/TUSCANY-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Becker resolved TUSCANY-2583.
-
Resolution: Fixed
As stated by Ant, the issue has been fixed and now all message parameters are
sent in the message body. (Spec compliance is another issue which should be
addressed in another Jira.)
only first method's parameter is send in JMS Message
Key: TUSCANY-2583
URL: https://issues.apache.org/jira/browse/TUSCANY-2583
Project: Tuscany
Issue Type: Bug
Components: Java SCA JMS Binding Extension
Affects Versions: Java-SCA-1.3
Reporter: Gaetan RUAULT
Assignee: ant elder
Fix For: Java-SCA-Next
Original Estimate: 4h
Remaining Estimate: 4h
The JMS provider generate only the first parameter of the service call
example :
for a jms interface service like this :
package personne.stub;
import org.osoa.sca.annotations.Remotable;
@Remotable
public interface TestJMSService {
int add(Integer x, Integer y);
int subtract(Integer x, Integer y);
}
with call like this : testJMSService.add(1,6)
the XMLTextMessageProcessor class generate this body for the JMS Message :
arg0 xmlns:ns2=http://stub.personne/;1/arg0
but il would generated :
arg0 xmlns:ns2=http://stub.personne/;1/arg0
arg1 xmlns:ns2=http://stub.personne/;6/arg1
this problem appear in the method createJMSMessage of
org.apache.tuscany.sca.binding.jms.provider.XMLTextMessageProcessor class.
only the first element of the array is set for body text.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2776) The JMSBindingProcessor does not perform validation of binding properties
[
https://issues.apache.org/jira/browse/TUSCANY-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Becker reassigned TUSCANY-2776:
---
Assignee: Dan Becker
The JMSBindingProcessor does not perform validation of binding properties
-
Key: TUSCANY-2776
URL: https://issues.apache.org/jira/browse/TUSCANY-2776
Project: Tuscany
Issue Type: Bug
Components: Java SCA JMS Binding Extension
Affects Versions: Java-SCA-1.4
Environment: All
Reporter: Simon Laws
Assignee: Dan Becker
The JMS binding spec defines some cross field validations. The validate()
method in the JMSBindingProcessor is as follows.
/**
* The validation rules for the JMS model are relatively complicated to
they all live together here
*/
public void validate() throws JMSBindingException {
/*
* first fix up anything now the model has been read
*/
/*
* Now some cross field validation
*/
// connection factory doesn't contradict destination type
// connection factory and activation Specification are mutually
exclusive
// TODO check Specification for all validations
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2794) JMS callback property variable ends with space - not a valid Javaidentifier
[ https://issues.apache.org/jira/browse/TUSCANY-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reassigned TUSCANY-2794: --- Assignee: Dan Becker JMS callback property variable ends with space - not a valid Javaidentifier --- Key: TUSCANY-2794 URL: https://issues.apache.org/jira/browse/TUSCANY-2794 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-1.4 Reporter: Tom Seelbach Assignee: Dan Becker We are seeing this exception when trying to run some JMS callback scenarios: org.osoa.sca.ServiceRuntimeException: org.apache.tuscany.sca.binding.jms.impl.JMSBindingException: javax.jms.MessageFormatException: CWSIA0112E:The property name scaCallbackQueue is not a valid Javaidentifier. at com.ibm.ws.soa.sca.binding.sca.SCAServiceBindingProvider.invokeServiceOperation(SCAServiceBindingProvider.java:540) at ... In looking at JMSBindingConstants I see that this property is defined oddly with a trailing space: String CALLBACK_ID_PROPERTY = CallbackID; String CALLBACK_Q_PROPERTY = scaCallbackQueue ; String CONVERSATION_ID_PROPERTY = scaConversationId; Removing the space fixes the problem for us. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2794) JMS callback property variable ends with space - not a valid Javaidentifier
[ https://issues.apache.org/jira/browse/TUSCANY-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2794. - Resolution: Fixed Resolved in Tuscany 1.x at revision: 737840 JMS callback property variable ends with space - not a valid Javaidentifier --- Key: TUSCANY-2794 URL: https://issues.apache.org/jira/browse/TUSCANY-2794 Project: Tuscany Issue Type: Bug Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-1.4 Reporter: Tom Seelbach Assignee: Dan Becker We are seeing this exception when trying to run some JMS callback scenarios: org.osoa.sca.ServiceRuntimeException: org.apache.tuscany.sca.binding.jms.impl.JMSBindingException: javax.jms.MessageFormatException: CWSIA0112E:The property name scaCallbackQueue is not a valid Javaidentifier. at com.ibm.ws.soa.sca.binding.sca.SCAServiceBindingProvider.invokeServiceOperation(SCAServiceBindingProvider.java:540) at ... In looking at JMSBindingConstants I see that this property is defined oddly with a trailing space: String CALLBACK_ID_PROPERTY = CallbackID; String CALLBACK_Q_PROPERTY = scaCallbackQueue ; String CONVERSATION_ID_PROPERTY = scaConversationId; Removing the space fixes the problem for us. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2557) Test support for JAX-WS holders with the referenced WSDL
[ https://issues.apache.org/jira/browse/TUSCANY-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2557. - Resolution: Duplicate Fixed in branch 1.x via the code commit of Tuscany 2332 of and the sample of Tuscany 2768. Test support for JAX-WS holders with the referenced WSDL - Key: TUSCANY-2557 URL: https://issues.apache.org/jira/browse/TUSCANY-2557 Project: Tuscany Issue Type: Sub-task Components: Java SCA Data Binding Runtime Reporter: Jean-Sebastien Delfino Assignee: Dan Becker Fix For: Java-SCA-Next Create a test case with the WSDL given in [1] as JAX-WS wsimport will generate a Holder for it. [1] http://marc.info/?l=tuscany-userm=121895603228804 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2567) Support for streaming postMedia and putMedia in Atom binding
[ https://issues.apache.org/jira/browse/TUSCANY-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker closed TUSCANY-2567. --- Support for streaming postMedia and putMedia in Atom binding - Key: TUSCANY-2567 URL: https://issues.apache.org/jira/browse/TUSCANY-2567 Project: Tuscany Issue Type: New Feature Environment: All Reporter: Dan Becker Assignee: Dan Becker Fix For: Java-SCA-Next - support for postMedia and putMedia, including the ability to stream that content in the target application component One of the requested enhancements to the Atom binding -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2601) HTTP binding eTag and lastModified test cases
[ https://issues.apache.org/jira/browse/TUSCANY-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker closed TUSCANY-2601. --- HTTP binding eTag and lastModified test cases - Key: TUSCANY-2601 URL: https://issues.apache.org/jira/browse/TUSCANY-2601 Project: Tuscany Issue Type: Bug Components: Java SCA Misc Binding Extensions Affects Versions: Java-SCA-1.3.2, Java-SCA-1.4 Environment: All Reporter: Dan Becker Assignee: Dan Becker The test cases to test condional HTTP methods was inadvertantly left out of the patch for TUSCANY-2516. This JIRA provides the test cases and test implementation which was left out of the original patch and sat on my local repository. These test cases are essential to see the ETag and LastModified caching in action. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2597) Generation of AtomPub workspace/service document
[ https://issues.apache.org/jira/browse/TUSCANY-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker closed TUSCANY-2597. --- Generation of AtomPub workspace/service document Key: TUSCANY-2597 URL: https://issues.apache.org/jira/browse/TUSCANY-2597 Project: Tuscany Issue Type: New Feature Components: Java SCA ATOM Binding Extension Affects Versions: Java-SCA-1.3.2, Java-SCA-1.4 Environment: All Reporter: Dan Becker Assignee: Dan Becker Fix For: Java-SCA-1.4 Breaking out a sub feature from the parent JIRA TUSCANY-2393 so we can commit in stages. - complete generation of an AtomPub workspace/service document, for a service, component or a group of related components (potentially in a composite), somebody should study this to find the correct granularity level -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2754) NPE received when wsdlElement is incorrectly specified
[
https://issues.apache.org/jira/browse/TUSCANY-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12666722#action_12666722
]
Dan Becker commented on TUSCANY-2754:
-
It looks like this is a case of a particular incorrect use of Tuscany. Tuscany
is reporting the WSDL error, however the calling program (WebSphere) is
ignoring the error, and using the incorrect model to attempt to build and
generate WSDL anyway. See the 2nd, 4th, 7th, and 8th line in this log:
[1/23/09 8:52:34:328 EST] 001e servlet I
com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: [isclite]
[/ibm/console] [/com.ibm.ws.console.blamanagement/pagingLayoutWithoutForm.jsp]:
Initialization successful.
[1/23/09 8:52:40:031 EST] 0022 WebServiceBin W
org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor The
#wsdl.service({http://components.ws.bindings.sca.test}BackEndComponentServiceBad)
does not match with the WSDL Definitions
[1/23/09 8:52:40:218 EST] 0022 CompositeBind W Multiple bindings with the
same name for a service: Service = BackEndComponentService Binding name =
BackEndComponentService
[1/23/09 8:52:40:343 EST] 0022 WSDLServiceGe E PortType
{http://components.ws.bindings.sca.test/}BackEndComponentService in
BackEndComp/BackEndComponentService was not found
[1/23/09 8:52:40:343 EST] 0022 FfdcProvider I
com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted
on
C:\WASSCAGA\AppServer\profiles\SOAAppSrv01\logs\ffdc\server1_597b597b_09.01.23_08.52.40.3437845428562332705775.txt
com.ibm.ws.soa.sca.contribution.monitor.impl.WASLoggingMonitorImpl.problem 115
[1/23/09 8:52:40:390 EST] 0022 FfdcProvider I
com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted
on
C:\WASSCAGA\AppServer\profiles\SOAAppSrv01\logs\ffdc\server1_597b597b_09.01.23_08.52.40.390364647672699910925.txt
org.apache.tuscany.sca.binding.ws.wsdlgen.BindingWSDLGenerator 190
[1/23/09 8:52:40:390 EST] 0022 BindingWSDLGe W Exception while generating
WSDL for BackEndComp/BackEndComponentService
[1/23/09 8:52:40:390 EST] 0022 BindingWSDLGe E Exception thrown was:
java.lang.NullPointerException
NPE received when wsdlElement is incorrectly specified
---
Key: TUSCANY-2754
URL: https://issues.apache.org/jira/browse/TUSCANY-2754
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-1.3
Environment: Tuscany 1.3.1
Reporter: Lou Amodeo
Assignee: Dan Becker
When one inadvertently specifies an incorrect wsdlElement service name as
part of the wsdl.port a NPE is thrown rather than a validation exception. It
also appears that in general there is no validation occurring for the
wsdlElment namespace, service, port, or binding names. Instead NPE
exceptions occur in different locations making it difficult to diagnose the
problem. I think the wsdlElement's attributes need to be validated with the
appropriate error messages emitted to identify the corrections required.
This particular error can reproduced by specifying a service in wsdl.port
that does not refer to a service in the contributed wsdl.
java.lang.NullPointerException
at
org.apache.tuscany.sca.binding.ws.wsdlgen.WSDLServiceGenerator.configureWSDLDefinition(WSDLServiceGenerator.java:247)
at
org.apache.tuscany.sca.binding.ws.wsdlgen.BindingWSDLGenerator.createWSDLDocument(BindingWSDLGenerator.java:277)
at
org.apache.tuscany.sca.binding.ws.wsdlgen.BindingWSDLGenerator.generateWSDL(BindingWSDLGenerator.java:172)
at
org.apache.tuscany.sca.binding.ws.xml.BindingBuilderImpl.build(BindingBuilderImpl.java:55)
at
org.apache.tuscany.sca.assembly.builder.impl.ComponentServiceBindingBuilderImpl.buildServiceBindings(ComponentServiceBindingBuilderImpl.java:66)
at
org.apache.tuscany.sca.assembly.builder.impl.ComponentServiceBindingBuilderImpl.build(ComponentServiceBindingBuilderImpl.java:48)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2782) Create schema for tuscany-binding-hessian
Create schema for tuscany-binding-hessian - Key: TUSCANY-2782 URL: https://issues.apache.org/jira/browse/TUSCANY-2782 Project: Tuscany Issue Type: Improvement Affects Versions: Java-SCA-Next Environment: All Reporter: Dan Becker Priority: Minor Tuscany should create the schema/XSF for tuscany-binding-hessian to aid in the validation of hessian syntax in SCA composite files. This schema will also aid Eclipse STP tools team in adding meta-model support for Tuscany in the graphics tools. The most likely place to park the schema would be in http://svn.apache.org/repos/asf/tuscany/branches/sca-java-1.x/modules/assembly-xsd/src/main/resources/. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2781) Create schema for tuscany-binding-corba
Create schema for tuscany-binding-corba --- Key: TUSCANY-2781 URL: https://issues.apache.org/jira/browse/TUSCANY-2781 Project: Tuscany Issue Type: Improvement Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: All Reporter: Dan Becker Priority: Minor Tuscany should create the schema/XSF for tuscany-binding-corba to aid in the validation of CORBA syntax in SCA composite files. This schema will also aid Eclipse STP tools team in adding meta-model support for Tuscany in the graphics tools. The most likely place to park the schema would be in http://svn.apache.org/repos/asf/tuscany/branches/sca-java-1.x/modules/assembly-xsd/src/main/resources/. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2783) Create schema for tuscany-binding-gdata
Create schema for tuscany-binding-gdata --- Key: TUSCANY-2783 URL: https://issues.apache.org/jira/browse/TUSCANY-2783 Project: Tuscany Issue Type: Improvement Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: All Reporter: Dan Becker Priority: Minor Tuscany should create the schema/XSF for tuscany-binding-gdata to aid in the validation of gdata syntax in SCA composite files. This schema will also aid Eclipse STP tools team in adding meta-model support for Tuscany in the graphics tools. The most likely place to park the schema would be in http://svn.apache.org/repos/asf/tuscany/branches/sca-java-1.x/modules/assembly-xsd/src/main/resources/. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2784) Create schema for tuscany-implementation-jee
Create schema for tuscany-implementation-jee Key: TUSCANY-2784 URL: https://issues.apache.org/jira/browse/TUSCANY-2784 Project: Tuscany Issue Type: Improvement Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Reporter: Dan Becker Priority: Minor Tuscany should create the schema/XSF for tuscany-implementation-jee to aid in the validation of JEE syntax in SCA composite files. This schema will also aid Eclipse STP tools team in adding meta-model support for Tuscany in the graphics tools. The most likely place to park the schema would be in http://svn.apache.org/repos/asf/tuscany/branches/sca-java-1.x/modules/assembly-xsd/src/main/resources/. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2785) Create schema for tuscany-binding-ajax
Create schema for tuscany-binding-ajax -- Key: TUSCANY-2785 URL: https://issues.apache.org/jira/browse/TUSCANY-2785 Project: Tuscany Issue Type: Improvement Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Reporter: Dan Becker Priority: Minor Tuscany should create the schema/XSF for tuscany-binding-ajaxto aid in the validation of Ajax syntax in SCA composite files. This schema will also aid Eclipse STP tools team in adding meta-model support for Tuscany in the graphics tools. The most likely place to park the schema would be in http://svn.apache.org/repos/asf/tuscany/branches/sca-java-1.x/modules/assembly-xsd/src/main/resources/. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2777) JavaScript errors in http://localhost:9990/ui/cloud/cloud-gadget.html precent contribution list from showing
[ https://issues.apache.org/jira/browse/TUSCANY-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2777. - Resolution: Invalid Customer reports Firefox plugin was cause of the issue. The Firefox Firebug plugin and Firefox JavaScript console also corroborate this finding. JavaScript errors in http://localhost:9990/ui/cloud/cloud-gadget.html precent contribution list from showing Key: TUSCANY-2777 URL: https://issues.apache.org/jira/browse/TUSCANY-2777 Project: Tuscany Issue Type: Bug Components: Java SCA Tutorial Affects Versions: Java-SCA-1.4 Environment: Linux, Firefox 3.0.5 or konqueror, Sun JDK 1.6, Tuscany 1.4 Reporter: Dan Becker Customer (wouterh on IRC chat #tuscany on 2009/01/20) reports client side JavaScript errors that prevent the tutorial domain cloud from showing contributions. To recreate: cd tutorials\store\domain java -jar ../../../modules/tuscany-node-launcher-1.4.jar domain Visit http://localhost:9990/ui/cloud/ with browser. Customer sees no contribution list. (I was able to see contribution list on windows/firefox 3.0.5) When customer runs Firebug plugin and visits http://localhost:9990/ui/cloud/cloud-gadget.html, the plugin reports the following errors: [08:28] wouterh 2 errors for http://localhost:9990/ui/cloud/cloud-gadget.html [08:28] wouterh the same 2 I pasted earlier [08:29] wouterh redeclaration of const Generator [08:29] wouterh http://localhost:9990/ui/cloud-gadget/cloud-gadget.js [08:29] wouterh Line 474 [08:29] wouterh and [08:29] wouterh Reference is not defined [08:29] wouterh http://localhost:9990/ui/cloud/cloud-gadget.html [08:29] wouterh Line 66 Full transcript is available on irc chat #tuscany from 2009-01-20. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2768) Create sample to demonstrate web services Holder support
[ https://issues.apache.org/jira/browse/TUSCANY-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2768. - Resolution: Fixed Fix Version/s: Java-SCA-Next Completed: At revision: 736344 Create sample to demonstrate web services Holder support Key: TUSCANY-2768 URL: https://issues.apache.org/jira/browse/TUSCANY-2768 Project: Tuscany Issue Type: Improvement Components: Java SCA Samples Affects Versions: Java-SCA-Next Environment: All Reporter: Dan Becker Assignee: Dan Becker Priority: Minor Fix For: Java-SCA-Next Attachments: sample-holder-ws-service.20090112.zip TUSCANY-2332 introduces Holder support for Java implementation of web services. This sample should demonstrate how this works. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2777) JavaScript errors in http://localhost:9990/ui/cloud/cloud-gadget.html precent contribution list from showing
JavaScript errors in http://localhost:9990/ui/cloud/cloud-gadget.html precent contribution list from showing Key: TUSCANY-2777 URL: https://issues.apache.org/jira/browse/TUSCANY-2777 Project: Tuscany Issue Type: Bug Components: Java SCA Tutorial Affects Versions: Java-SCA-1.4 Environment: Linux, Firefox 3.0.5 or konqueror, Sun JDK 1.6, Tuscany 1.4 Reporter: Dan Becker Customer (wouterh on IRC chat #tuscany on 2009/01/20) reports client side JavaScript errors that prevent the tutorial domain cloud from showing contributions. To recreate: cd tutorials\store\domain java -jar ../../../modules/tuscany-node-launcher-1.4.jar domain Visit http://localhost:9990/ui/cloud/ with browser. Customer sees no contribution list. (I was able to see contribution list on windows/firefox 3.0.5) When customer runs Firebug plugin and visits http://localhost:9990/ui/cloud/cloud-gadget.html, the plugin reports the following errors: [08:28] wouterh 2 errors for http://localhost:9990/ui/cloud/cloud-gadget.html [08:28] wouterh the same 2 I pasted earlier [08:29] wouterh redeclaration of const Generator [08:29] wouterh http://localhost:9990/ui/cloud-gadget/cloud-gadget.js [08:29] wouterh Line 474 [08:29] wouterh and [08:29] wouterh Reference is not defined [08:29] wouterh http://localhost:9990/ui/cloud/cloud-gadget.html [08:29] wouterh Line 66 Full transcript is available on irc chat #tuscany from 2009-01-20. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2754) NPE received when wsdlElement is incorrectly specified
[ https://issues.apache.org/jira/browse/TUSCANY-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12665198#action_12665198 ] Dan Becker commented on TUSCANY-2754: - I could not recreate this in the 1.x branch. The WsdlPortTypeDoesNotMatchTestCase in itest-validation shows how bad WSDL port types are caught. Perhaps your SCA contribution is read, resolved, and built in a different manner than this test case, if so, it would be good to see how your code is doing this. Also perhaps you can try with the 1.x branch to see if the problem still exists. NPE received when wsdlElement is incorrectly specified --- Key: TUSCANY-2754 URL: https://issues.apache.org/jira/browse/TUSCANY-2754 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-1.3 Environment: Tuscany 1.3.1 Reporter: Lou Amodeo Assignee: Dan Becker When one inadvertently specifies an incorrect wsdlElement service name as part of the wsdl.port a NPE is thrown rather than a validation exception. It also appears that in general there is no validation occurring for the wsdlElment namespace, service, port, or binding names. Instead NPE exceptions occur in different locations making it difficult to diagnose the problem. I think the wsdlElement's attributes need to be validated with the appropriate error messages emitted to identify the corrections required. This particular error can reproduced by specifying a service in wsdl.port that does not refer to a service in the contributed wsdl. java.lang.NullPointerException at org.apache.tuscany.sca.binding.ws.wsdlgen.WSDLServiceGenerator.configureWSDLDefinition(WSDLServiceGenerator.java:247) at org.apache.tuscany.sca.binding.ws.wsdlgen.BindingWSDLGenerator.createWSDLDocument(BindingWSDLGenerator.java:277) at org.apache.tuscany.sca.binding.ws.wsdlgen.BindingWSDLGenerator.generateWSDL(BindingWSDLGenerator.java:172) at org.apache.tuscany.sca.binding.ws.xml.BindingBuilderImpl.build(BindingBuilderImpl.java:55) at org.apache.tuscany.sca.assembly.builder.impl.ComponentServiceBindingBuilderImpl.buildServiceBindings(ComponentServiceBindingBuilderImpl.java:66) at org.apache.tuscany.sca.assembly.builder.impl.ComponentServiceBindingBuilderImpl.build(ComponentServiceBindingBuilderImpl.java:48) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2773) Tuscany models read/write invalid elements or attributes
[ https://issues.apache.org/jira/browse/TUSCANY-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12664695#action_12664695 ] Dan Becker commented on TUSCANY-2773: - https://issues.apache.org/jira/browse/TUSCANY-2754 seems related to this one, although 2754 only applies to invalid wsdlElement attrributes. I am working on that one. It seems like validation depends much on how you resolve the model. Tuscany models read/write invalid elements or attributes Key: TUSCANY-2773 URL: https://issues.apache.org/jira/browse/TUSCANY-2773 Project: Tuscany Issue Type: Improvement Components: Java SCA Assembly Model Affects Versions: Java-SCA-1.3 Environment: All platforms Reporter: Raymond Lai Assignee: Luciano Resende The ability to read/write invalid elements or attributes was first requested in Tuscany-2631. However, it's not containable for 1.3.3 and the original JIRA is closed. So I'm opening a new JIRA to track this requirement. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2470) Atom binding unit tests
[ https://issues.apache.org/jira/browse/TUSCANY-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker closed TUSCANY-2470. --- Atom binding unit tests --- Key: TUSCANY-2470 URL: https://issues.apache.org/jira/browse/TUSCANY-2470 Project: Tuscany Issue Type: Improvement Components: Java SCA ATOM Binding Extension Reporter: Dan Becker Assignee: Luciano Resende Fix For: Java-SCA-Next Attachments: TUSCANY-2470.patch Provide unit tests for testing and validating the atom binding modules of the Tuscany SCA tree. (This item is implied as a subset of the large scope Tuscany-2393 Complete Atom binding implementation JIRA.) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2477) Atom binding support for eTags, last-modified header
[ https://issues.apache.org/jira/browse/TUSCANY-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker closed TUSCANY-2477. --- Atom binding support for eTags, last-modified header Key: TUSCANY-2477 URL: https://issues.apache.org/jira/browse/TUSCANY-2477 Project: Tuscany Issue Type: New Feature Components: Java SCA ATOM Binding Extension Affects Versions: Java-SCA-Next Environment: All Reporter: Dan Becker Assignee: Luciano Resende Fix For: Java-SCA-Next Attachments: TUSCANY-2477-4.patch As stated in parent JIRA, there is a need to support the following features in the Atom binding - support for eTags, last-modified headers, complete support for location header - on the client side, caching using eTag and/or lastModified -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2548) Atom Feed sorting algorithm should depend on Updated field, not Published field
[ https://issues.apache.org/jira/browse/TUSCANY-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker closed TUSCANY-2548. --- Atom Feed sorting algorithm should depend on Updated field, not Published field --- Key: TUSCANY-2548 URL: https://issues.apache.org/jira/browse/TUSCANY-2548 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-1.3 Environment: All OSs, All JVMs Reporter: Dan Becker Assignee: Luciano Resende Priority: Minor Attachments: TUSCANY-2548.patch Atom Feed sorting algorithm should depend on Updated field, not Published field. According to the Atom Publishing Protocols, the Updated field of an entry is mandatory, and the Published field of an entry is optional. Many sites such as O'Reilly provide no publish date, and this field shows up as null in the Abdera content model. Therefore, the feed aggregation samples, demos, tutorials should sort on Updated rather than published. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2547) Update OReilly feed in Atom demos, samples, etc.
[ https://issues.apache.org/jira/browse/TUSCANY-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker closed TUSCANY-2547. --- Update OReilly feed in Atom demos, samples, etc. Key: TUSCANY-2547 URL: https://issues.apache.org/jira/browse/TUSCANY-2547 Project: Tuscany Issue Type: Bug Components: Java SCA Demos, Java SCA Samples, Java SCA Tutorial Affects Versions: Java-SCA-1.3 Environment: All OSs, All JVM Reporter: Dan Becker Assignee: Luciano Resende Priority: Minor Fix For: Java-SCA-Next Attachments: TUSCANY-2547.patch It looks like the O'Reilly site has changed the support and addresses of some of their Atom feeds. Specificly, the feed http://www.oreillynet.com/pub/feed/1 no longer has any title or entries. Substitute another feed such as http://www.oreillynet.com/pub/feed/35 (All Things OReilly) for the samples -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2108) Java 2 Security - ReallySmallRuntime AccessController blocks
[ https://issues.apache.org/jira/browse/TUSCANY-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker closed TUSCANY-2108. --- Java 2 Security - ReallySmallRuntime AccessController blocks Key: TUSCANY-2108 URL: https://issues.apache.org/jira/browse/TUSCANY-2108 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.1 Environment: Run with JDK 1.5, Windows XP system Reporter: Dan Becker Assignee: Raymond Feng Fix For: Java-SCA-Next Attachments: tuscany2108-2.txt, tuscany2108.txt Add Java 2 Security to SCA core accessed via ReallySmallRuntime. This can be seen by running the sample-calculator program with -Djava.security.manager for the Java application runtime. This JIRA is a preliminary prereq for JIRA TUSCANY-2030. That JIRA covers the code entry points via org.apache.tuscany.sca.host.embedded.impl.EmbeddedSCADomain.getService(EmbeddedSCADomain.java:138) and com.ibm.ws.soa.sca.runtime.impl.SimpleCompositeContextImpl.locateService(SimpleCompositeContextImpl.java:86) This JIRA covers all internal entry points that are accessed via Exception in thread main org.osoa.sca.ServiceRuntimeException: java.lang.NullPointerException at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:264) at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:69) at calculator.CalculatorClient.main(CalculatorClient.java:31) Caused by: java.lang.NullPointerException at org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntime.start(ReallySmallRuntime.java:116) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:118) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:109) at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:231) There needs to be AccessController.doPrivileged blocks around all sensitive code that creates a ClassLoader, accesses the file system via stream or URL, reads system properties and all other sensitive areas not covered by the security.policy file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2130) Promote Security Aware Tuscany article from internal wiki to external developer wiki pages
[ https://issues.apache.org/jira/browse/TUSCANY-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker closed TUSCANY-2130. --- Promote Security Aware Tuscany article from internal wiki to external developer wiki pages -- Key: TUSCANY-2130 URL: https://issues.apache.org/jira/browse/TUSCANY-2130 Project: Tuscany Issue Type: Improvement Components: Website Environment: Web Reporter: Dan Becker Assignee: Luciano Resende Priority: Minor Promote the Security Aware Programming in Tuscany article from the internal wiki (at http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Security+Aware+Programming+in+Tuscany) to the external developer pages. A suggested location is the developer hints section of the development guide (at http://cwiki.apache.org/TUSCANY/sca-java-development-guide.html) Wiki and HTML source code for the article is available at the first link given. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2237) Java 2 Security - Enhancements to run Itest bucket
[ https://issues.apache.org/jira/browse/TUSCANY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker closed TUSCANY-2237. --- Java 2 Security - Enhancements to run Itest bucket -- Key: TUSCANY-2237 URL: https://issues.apache.org/jira/browse/TUSCANY-2237 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.1 Environment: Java 1.5, Windows Reporter: Dan Becker Assignee: Raymond Feng Fix For: Java-SCA-Next Attachments: TUSCANY-2237-2.patch Must add proper Java 2 security to allow all Itests to run and pass JUnit testing. An example of a failing Itest occurs with CallableReferenceRemoteTestcase with Java 2 security enables. Here is an example AccessControlException: java.security.AccessControlException: access denied (java.util.PropertyPermission java.io.tmpdir read) at java.security.AccessControlContext.checkPermission(Unknown Source) at java.security.AccessController.checkPermission(Unknown Source) at java.lang.SecurityManager.checkPermission(Unknown Source) at java.lang.SecurityManager.checkPropertyAccess(Unknown Source) at java.lang.System.getProperty(Unknown Source) at org.apache.axis2.context.ConfigurationContext.cleanupTemp(ConfigurationContext.java:665) at org.apache.axis2.context.ConfigurationContext.terminate(ConfigurationContext.java:653) at org.apache.axis2.transport.http.AxisServlet.destroy(AxisServlet.java:449) at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceServlet.destroy(Axis2ServiceServlet.java:236) at org.apache.tuscany.sca.http.tomcat.ServletWrapper.destroyServlet(ServletWrapper.java:55) at org.apache.tuscany.sca.http.tomcat.TomcatServer.removeServletMapping(TomcatServer.java:510) at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.stop(Axis2ServiceProvider.java:308) at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceBindingProvider.stop(Axis2ServiceBindingProvider.java:98) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.stop(CompositeActivatorImpl.java:615) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.stop(CompositeActivatorImpl.java:513) at org.apache.tuscany.sca.node.impl.SCADomainProxyImpl.destroy(SCADomainProxyImpl.java:500) at org.apache.tuscany.sca.node.impl.SCANodeImpl.destroy(SCANodeImpl.java:441) at org.apache.tuscany.sca.itest.callableref.CallableReferenceRemoteTestCase.destroy(CallableReferenceRemoteTestCase.java:97) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.junit.internal.runners.BeforeAndAfterRunner.invokeMethod(BeforeAndAfterRunner.java:74) at org.junit.internal.runners.BeforeAndAfterRunner.runAfters(BeforeAndAfterRunner.java:65) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:37) at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) This is fixed by adding AccessController.doPrivileged blocks around the sensitive call -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2290) Java 2 Security enablement for Tuscany sample (part 1)
[ https://issues.apache.org/jira/browse/TUSCANY-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker closed TUSCANY-2290. --- Java 2 Security enablement for Tuscany sample (part 1) -- Key: TUSCANY-2290 URL: https://issues.apache.org/jira/browse/TUSCANY-2290 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-1.2 Environment: Windows, Java 1.5 Reporter: Dan Becker Assignee: Raymond Feng Fix For: Java-SCA-Next Attachments: TUSCANY-2290.3.patch Fix security issues that arise in Tuscany samples when Java 2 security is turned on via -java.security.manager -Djava.security.policy=tuscany.policy -Dpolicy.allowSystemProperty=true A typical exception might be for sample helloworld sdo ws Problems trying to access System properties: java.security.AccessControlException: access denied (java.util.PropertyPermission java.specification.version read) java.lang.NoClassDefFoundError at org.apache.tuscany.sca.databinding.sdo.SDODataBinding.introspect(SDODataBinding.java:61) at org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint$LazyDataBinding.introspect(DefaultDataBindingExtensionPoint.java:191) at org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint.introspectType(DefaultDataBindingExtensionPoint.java:246) at org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint.introspectType(DefaultDataBindingExtensionPoint.java:202) at org.apache.tuscany.sca.core.databinding.processor.DataBindingJavaInterfaceProcessor.processInterface(DataBindingJavaInterfaceProcessor.java:116) at org.apache.tuscany.sca.core.databinding.processor.DataBindingJavaInterfaceProcessor.visitInterface(DataBindingJavaInterfaceProcessor.java:58) at org.apache.tuscany.sca.interfacedef.java.impl.JavaInterfaceIntrospectorImpl.introspectInterface(JavaInterfaceIntrospectorImpl.java:113) at org.apache.tuscany.sca.interfacedef.java.impl.JavaInterfaceFactoryImpl.createJavaInterface(JavaInterfaceFactoryImpl.java:48) at org.apache.tuscany.sca.implementation.java.introspect.impl.ServiceProcessor.createService(ServiceProcessor.java:159) at org.apache.tuscany.sca.implementation.java.introspect.impl.ServiceProcessor.visitClass(ServiceProcessor.java:90) at org.apache.tuscany.sca.implementation.java.impl.JavaClassIntrospectorImpl.introspectClass(JavaClassIntrospectorImpl.java:72) at org.apache.tuscany.sca.implementation.java.impl.JavaImplementationFactoryImpl.createJavaImplementation(JavaImplementationFactoryImpl.java:53) at org.apache.tuscany.sca.implementation.java.xml.JavaImplementationProcessor.resolve(JavaImplementationProcessor.java:152) at org.apache.tuscany.sca.implementation.java.xml.JavaImplementationProcessor.resolve(JavaImplementationProcessor.java:63) ... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2436) Demo alert aggregator has Exception java.text.ParseException: Unparseable date
[ https://issues.apache.org/jira/browse/TUSCANY-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker closed TUSCANY-2436. --- Demo alert aggregator has Exception java.text.ParseException: Unparseable date -- Key: TUSCANY-2436 URL: https://issues.apache.org/jira/browse/TUSCANY-2436 Project: Tuscany Issue Type: Bug Components: Java SCA Demos Affects Versions: Java-SCA-1.2 Environment: Windows XP Java 1.6.0.04 Tomcat 6.0.14 Reporter: Dan Becker Priority: Minor Attachments: TUSCANY-2436.patch Demo alert aggregator has Exception java.text.ParseException: Unparseable date: 10-Jun-2007 16:34:03 When used with the given RSS samples in the demo (BBC and Engadget) the following 2 exceptions are visible in the server logs: getAlertSources(Dojo) Exception java.text.ParseException: Unparseable date: 10-Jun-2007 16:34:03 Exception java.text.ParseException: Unparseable date: 10-Jun-2007 16:34:03 getAllNewAlerts(Dojo) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2339) Java 2 Security - Provide Tuscany Maven profile to run vtest and itest with Java 2 security enabled
[
https://issues.apache.org/jira/browse/TUSCANY-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Becker closed TUSCANY-2339.
---
Java 2 Security - Provide Tuscany Maven profile to run vtest and itest with
Java 2 security enabled
---
Key: TUSCANY-2339
URL: https://issues.apache.org/jira/browse/TUSCANY-2339
Project: Tuscany
Issue Type: Improvement
Components: Java SCA Core Runtime
Environment: Maven profile should be operating system independent.
Reporter: Dan Becker
Assignee: Raymond Feng
Attachments: TUSCANY-2339.2.patch
Provide Tuscany Maven profile to run vtest and itest with Java 2 security
enabled. This profile should specify a security profile for Tuscany, and
should run vtest and itests with Java 2 security enabled.
Run the profile with
mvn -P security.
Suggested profile addition to Tuscany java/sca pom.xml
profile
idsecurity/id
modules
!-- moduledemos/module --
moduleitest/module
modulevtest/module
/modules
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version2.3.1/version
configuration
includes
include**/*TestCase.java/include
/includes
reportFormatbrief/reportFormat
useFilefalse/useFile
forkModeonce/forkMode
!-- Place tuscany.policy in your Java home
security directory. Alternatively, hardcode the file location here. --
argLine-Djava.security.manager
-Djava.security.policy=file:///${java.home}/lib/security/tuscany.policy
-Dpolicy.allowSystemProperty=true -Djava.security.debug=policy/argLine
/configuration
/plugin
/plugins
/build
/profile
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2754) NPE received when wsdlElement is incorrectly specified
[ https://issues.apache.org/jira/browse/TUSCANY-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker reassigned TUSCANY-2754: --- Assignee: Dan Becker NPE received when wsdlElement is incorrectly specified --- Key: TUSCANY-2754 URL: https://issues.apache.org/jira/browse/TUSCANY-2754 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-1.3 Environment: Tuscany 1.3.1 Reporter: Lou Amodeo Assignee: Dan Becker When one inadvertently specifies an incorrect wsdlElement service name as part of the wsdl.port a NPE is thrown rather than a validation exception. It also appears that in general there is no validation occurring for the wsdlElment namespace, service, port, or binding names. Instead NPE exceptions occur in different locations making it difficult to diagnose the problem. I think the wsdlElement's attributes need to be validated with the appropriate error messages emitted to identify the corrections required. This particular error can reproduced by specifying a service in wsdl.port that does not refer to a service in the contributed wsdl. java.lang.NullPointerException at org.apache.tuscany.sca.binding.ws.wsdlgen.WSDLServiceGenerator.configureWSDLDefinition(WSDLServiceGenerator.java:247) at org.apache.tuscany.sca.binding.ws.wsdlgen.BindingWSDLGenerator.createWSDLDocument(BindingWSDLGenerator.java:277) at org.apache.tuscany.sca.binding.ws.wsdlgen.BindingWSDLGenerator.generateWSDL(BindingWSDLGenerator.java:172) at org.apache.tuscany.sca.binding.ws.xml.BindingBuilderImpl.build(BindingBuilderImpl.java:55) at org.apache.tuscany.sca.assembly.builder.impl.ComponentServiceBindingBuilderImpl.buildServiceBindings(ComponentServiceBindingBuilderImpl.java:66) at org.apache.tuscany.sca.assembly.builder.impl.ComponentServiceBindingBuilderImpl.build(ComponentServiceBindingBuilderImpl.java:48) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2515) ANT script for zipcode-jaxws sample needs to download the wsdls
[ https://issues.apache.org/jira/browse/TUSCANY-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2515. - Resolution: Fixed It looks like you fixed this one based on commits to the trunk and revisions to build.xml. My guess is that you overlooked resolving the Jira. ANT script for zipcode-jaxws sample needs to download the wsdls --- Key: TUSCANY-2515 URL: https://issues.apache.org/jira/browse/TUSCANY-2515 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-Next Reporter: Raymond Feng Priority: Minor Fix For: Java-SCA-Next As the binary distro doesn't ship the WSDLs for the zipcode-jaxws sample. We need to add a task to the build.xml to download WSDLs before compile. Otherwise we see: Buildfile: build.xml run: [java] Exception in thread main org.osoa.sca.ServiceRuntimeException: org.apache.axis2.AxisFault: The system cannot infer the transport information from the / URL. [java] at org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:136) [java] at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:287) [java] at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154) [java] at $Proxy39.getWeatherByZipCode(Unknown Source) [java] at zipcode.ZipCodeServiceImpl.lookup(ZipCodeServiceImpl.java:59) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [java] at java.lang.reflect.Method.invoke(Method.java:597) [java] at org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:132) [java] at org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:107) [java] at org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61) [java] at org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:107) [java] at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:287) [java] at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154) [java] at $Proxy38.lookup(Unknown Source) [java] at zipcode.ZipCodeClient.main(ZipCodeClient.java:33) [java] Caused by: org.apache.axis2.AxisFault: The system cannot infer the transport information from the / URL. [java] at org.apache.axis2.description.ClientUtils.inferOutTransport(ClientUtils.java:73) [java] at org.apache.axis2.client.OperationClient.prepareMessageContext(OperationClient.java:302) [java] at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:174) [java] at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) [java] at org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker$1.run(Axis2BindingInvoker.java:128) [java] at java.security.AccessController.doPrivileged(Native Method) [java] at org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invokeTarget(Axis2BindingInvoker.java:126) [java] at org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invoke(Axis2BindingInvoker.java:94) [java] at org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:78) [java] ... 16 more [java] Java Result: 1 There is a workaround: run mvn build first. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2754) NPE received when wsdlElement is incorrectly specified
[ https://issues.apache.org/jira/browse/TUSCANY-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663017#action_12663017 ] Dan Becker commented on TUSCANY-2754: - Hello. Is there a basic WSDL that you could attach that demonstrates the problem? NPE received when wsdlElement is incorrectly specified --- Key: TUSCANY-2754 URL: https://issues.apache.org/jira/browse/TUSCANY-2754 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-1.3 Environment: Tuscany 1.3.1 Reporter: Lou Amodeo When one inadvertently specifies an incorrect wsdlElement service name as part of the wsdl.port a NPE is thrown rather than a validation exception. It also appears that in general there is no validation occurring for the wsdlElment namespace, service, port, or binding names. Instead NPE exceptions occur in different locations making it difficult to diagnose the problem. I think the wsdlElement's attributes need to be validated with the appropriate error messages emitted to identify the corrections required. This particular error can reproduced by specifying a service in wsdl.port that does not refer to a service in the contributed wsdl. java.lang.NullPointerException at org.apache.tuscany.sca.binding.ws.wsdlgen.WSDLServiceGenerator.configureWSDLDefinition(WSDLServiceGenerator.java:247) at org.apache.tuscany.sca.binding.ws.wsdlgen.BindingWSDLGenerator.createWSDLDocument(BindingWSDLGenerator.java:277) at org.apache.tuscany.sca.binding.ws.wsdlgen.BindingWSDLGenerator.generateWSDL(BindingWSDLGenerator.java:172) at org.apache.tuscany.sca.binding.ws.xml.BindingBuilderImpl.build(BindingBuilderImpl.java:55) at org.apache.tuscany.sca.assembly.builder.impl.ComponentServiceBindingBuilderImpl.buildServiceBindings(ComponentServiceBindingBuilderImpl.java:66) at org.apache.tuscany.sca.assembly.builder.impl.ComponentServiceBindingBuilderImpl.build(ComponentServiceBindingBuilderImpl.java:48) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2768) Create sample to demonstrate web services Holder support
Create sample to demonstrate web services Holder support Key: TUSCANY-2768 URL: https://issues.apache.org/jira/browse/TUSCANY-2768 Project: Tuscany Issue Type: Improvement Components: Java SCA Samples Affects Versions: Java-SCA-Next Environment: All Reporter: Dan Becker Assignee: Dan Becker Priority: Minor TUSCANY-2332 introduces Holder support for Java implementation of web services. This sample should demonstrate how this works. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2768) Create sample to demonstrate web services Holder support
[ https://issues.apache.org/jira/browse/TUSCANY-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker updated TUSCANY-2768: Attachment: sample-holder-ws-service.20090112.zip Demonstrates holder support in a branch 1.x environment. Requires TUSCANY-2332 fix (revision 733526). Create sample to demonstrate web services Holder support Key: TUSCANY-2768 URL: https://issues.apache.org/jira/browse/TUSCANY-2768 Project: Tuscany Issue Type: Improvement Components: Java SCA Samples Affects Versions: Java-SCA-Next Environment: All Reporter: Dan Becker Assignee: Dan Becker Priority: Minor Attachments: sample-holder-ws-service.20090112.zip TUSCANY-2332 introduces Holder support for Java implementation of web services. This sample should demonstrate how this works. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2332) reconsider non-support for Holders
[ https://issues.apache.org/jira/browse/TUSCANY-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2332. - Resolution: Fixed Resolved in branch 1.x via revision: 733526 . Test case that demonstrates holder support will be checked in under separate Jira. reconsider non-support for Holders -- Key: TUSCANY-2332 URL: https://issues.apache.org/jira/browse/TUSCANY-2332 Project: Tuscany Issue Type: Improvement Components: Java SCA Data Binding Runtime Reporter: Scott Kurz Assignee: Dan Becker Fix For: Java-SCA-Next Attachments: guessAndGreet.wsdl, sample-holder-ws-service.20081123.zip, SebastiensHolder.wsdl Though the Java annotations/API spec specifically says wrt WSDL- Java mapping: The JAX-WS mappings are applied with the following restrictions: • No support for holders I'd like to suggest that we look into enabling such support anyway, as this seems overly restrictive and prevents us from supporting existing WSDLs with inout data. At least I don't see how we'd map these WSDLs to Java and would think we'd be way better off relying on the mapping defined by JAX-WS which does use Holders. (Not sure what this statement in the spec was trying to accomplish.) I attached an example WSDL with two operations which we'd want to use Holders in the corresponding Java methods. One has a common child element of both input/output wrapper elem and the other has a common part of input/output message. (Maybe it would be better to bring this up before opening a JIRA, but I wanted to attach the WSDL.) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2741) [Documention] how to deploy as web app in 1.x environment
[ https://issues.apache.org/jira/browse/TUSCANY-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Becker resolved TUSCANY-2741. - Resolution: Fixed Also added a link to Ant's page at http://tuscany.apache.org/sca-java-user-guide.html. Ant's page is now available on the external site and has links to 3 samples which should help one get started with web applications [Documention] how to deploy as web app in 1.x environment -- Key: TUSCANY-2741 URL: https://issues.apache.org/jira/browse/TUSCANY-2741 Project: Tuscany Issue Type: Improvement Components: Website Affects Versions: Java-SCA-1.4 Reporter: haleh mahbod Assignee: ant elder Priority: Critical Fix For: Java-SCA-Next Many users have asked for better documentations and samples around how to deploy applications as webapp. An example is Phil Sykes who responded to the question for how to improve documentation. Can someone knowledgeable in this area pick this JIRA up? Can you please refer back to samples if any? If there are no good samples, please create a JIRA for that as well. Thanks -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
