Re: Deadline for ranking proposals Re: [GSoC] Time to rank the Google Summer of Code Proposals
Do I have to become a mentor even to view the proposals? Upon clicking on any links in [1], it is taking me to a page asking to become a mentor!! ++Vamsi On Wed, Apr 16, 2008 at 7:08 AM, Luciano Resende [EMAIL PROTECTED] wrote: This is a gentle reminder. We have untill April 18th midnight PDT to rank proposals. All mentors, please take a moment to rank proposals. [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Google+Summer+of+Code+%282008%29+Applications -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://people.apache.org/%7Elresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mirror of release artifacts
I think thats a separate issue but if its the reason we stopped using the mirrors then i think we need to start using them again. It may not be clearly documented yet but i think the current ASF/incubator policy is that releases MUST be distributed via the mirrors. ...ant On Tue, Apr 15, 2008 at 5:20 PM, Luciano Resende [EMAIL PROTECTED] wrote: How do we get stats from the number of downloads when using mirros ? On Tue, Apr 15, 2008 at 7:21 AM, Simon Laws [EMAIL PROTECTED] wrote: On Tue, Apr 15, 2008 at 2:20 PM, ant elder [EMAIL PROTECTED] wrote: WIth the changes to how the Incubator release artifacts get distributed via mirrors now I understood we were supposed to have our website download pages use a script accessing the mirrors. Looking back at the SCA 1.1 download page change history it did at one point do that (r17) but then it got changed back to the non-script approach. Anyone know why? Are there some issues with using the script/mirrors? ...ant Hi Distribution mirroring is part of incubator release best practice [1] so we should try and put this back in if we can. Happy to help to make this work if anyone can identify what the original issue was. If we can't identify a specific issue I would go for going back to the links from r17. Regards Simon [1] http://incubator.apache.org/guides/releasemanagement.html#distribution-mirroring -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://people.apache.org/%7Elresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache Tuscany committer status reaffirmation
No problem, I shall add your name to the list. We do actually review every commit so it is fine for you to directly commit instead of raising patches, you could post a note to the dev list if there's ones you're particularly nervous about. Thats actually easier as then no one needs to do the work to apply the patch, but its no biggie so if you're more comfortable using patches for now thats fine too. ...ant On Tue, Apr 15, 2008 at 5:55 PM, Brent Daniel [EMAIL PROTECTED] wrote: Ant, My preference would be to remain a committer. However, I am not sure when my schedule will allow for a deeper involvement. Lately, I have been submitting fixes in patches rather than committing directly. With a small number of fixes this isn't a big deal, and it ensures that at least one person reviews the fix, whereas a simple commit could be overlooked. I can certainly continue to work like this without committership, but would prefer to keep the ability to commit for when I am able to spend more time on the Tuscany code base. Brent On Sat, Apr 12, 2008 at 2:23 AM, ant elder [EMAIL PROTECTED] wrote: You are receiving this email because you are listed as an Apache Tuscany committer. Tuscany is looking to graduate in the near future and following Apache Incubator practice is cleaning up the committer list. Tuscany has 35 committers listed on the status file some of those have left and some were just listed there when the original proposal was accepted and have never even once committed anything. We've decided any one who has interacted with the project within the last 12 months will automatically remain a committer, anyone else will need to reply to this email to retain their committer status. These are the committers who've participated in the last 12 months and will automatically retain their committer status: adrianocrestani Adriano Crestani amita Amita Vadhavkar ajborleyAndrew Borley antelderAnt Elder bjohnsonBrady Johnson dkulp Dan Kulp frankb Frank Budinsky fuhwei Fuhwei Lwo giorgio Giorgio Zoppi isilval Ignacio Silva-Lepe jsdelfino Jean-Sebastien Delfino kelvingoodson Kelvin Goodson kwilliams Kevin Williams lresendeLuciano Resende mcombellack Mark Combellack myoder Michael Yoder edwardsmj Mike Edwards nashSimon Nash rsivaramRajini Sivaram rfeng Raymond Feng robbinspg Pete Robbins slaws Simon Laws svkrish Venkata Krishnan So, if you are not on that list but would like to retain your Tuscany committer status please reply to this email and let us know about how you would like to be involved with Tuscany. Also, if you are on that list but no longer want to stay a committer once Tuscany graduates you can also reply to this email and we'll remove your name. Many thanks, The Apache Tuscany PPMC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JAXB 2.1 and JDK level, was [VOTE] Release Tuscany Java SCA 1.2-incubating (RC4)
Somehow a version of JDK 1.6.0 got installed as the system JDK and was being selected ahead of the 1.5.0 that I installed. I fixed it by removing the 1.6.0 from my machine. I still don't know how it got there, but things work just fine now on 1.5.0. Yours, Mike. Adriano Crestani wrote: Folks, Sheepish grin - the surprise to me was to find that this is JDK 6 related - I thought I was using Sun 1.5.0_14. However - SOMEHOW my system is using Sun 1.6.0_03 - and I'm still trying to work out why! MS Windows? Adriano Crestani On Tue, Apr 15, 2 008 at 10:53 AM, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: Mike Edwards wrote: Jean-Sebastien Delfino wrote: You'll get this with some of the other samples too I think, if you use JDK 6 and don't place JAXB 2.1 in the lib/endorsed directory of your JRE. Try to do what the the error message is asking you to do :) Folks, Sheepish grin - the surprise to me was to find that this is JDK 6 related - I thought I was using Sun 1.5.0_14. However - SOMEHOW my system is using Sun 1.6.0_03 - and I'm still trying to work out why! Yours, Mike Check you PATH and JAVA_HOME? :) -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 1.2-incubating (RC4)
Raymond Feng wrote: It's related to JDK 6 which ships a version of JAXB impl by itself. Up to JDK 6 Update 3, the JDK ships with JAX-WS 2.0 (which includes JAXB 2.0), but Tuscany requires JAXB 2.1. There are two possible solutions to this problem: 1) Upgrade your JDK to 1.6.0_04 or above, which will include JAX-WS (and JAXB) 2.1 2) Copy the version 2.1 jaxb-api.jar or jaxws-api.jar (you can probably find them in your local maven repo) to JAVA_HOME/lib/endorsed to override the API jars that ship with the JDK 3) Use the -Djava.endorsed.dir=a folder containing our JAXB jars to override the JAXB from JDK 6. We need to add this to our FAQ or release note. Yes, this is a very good idea - best to make it plain that if they use 1.6.0, then it should be at 04 or above. Messing about with jars in the endorsed standards directory is not a great idea in my opinion, although I agree that it works. Thanks, Raymond -- OK, for me - panic over! Mike. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Latest continuum builds are failing due to test failures in itest/osgi-implementation with new test cases helloworld.sdo
Hi Rajini, Thanks for fixing the osgi-implementation build break so quickly. It is working for me now. The build then failed on osgi-contribution. However, I see that you have already committed a fix for this one too :-) The build is currently running on the Continuum server so we should hopefully see a successful build soon. Thanks, Mark -Original Message- From: Rajini Sivaram [mailto:[EMAIL PROTECTED] Sent: 15 April 2008 21:13 To: tuscany-dev@ws.apache.org Subject: Re: Latest continuum builds are failing due to test failures in itest/osgi-implementation with new test cases helloworld.sdo Sorry about that. I have committed a fix under revision 648396. Due to a difference in classloading between the IBM JDK that I was using for testing and the Sun(?) JDK on Continuum, an additional class was required to be visible from the test bundle, resulting in the NoClassDefFoundError. I was expecting to see a build failure report if the Continuum build failed after I checked in code. Is that completely turned off now? On 4/15/08, Mark Combellack [EMAIL PROTECTED] wrote: Hi, Over the last few days, the continuum build has been failing for the trunk of Tuscany. The problem is that two tests are failing in itest/osgi-implementation. The relevant error messages are: testJavaToOSGi(helloworld.sdo.SdoTestCase) Time elapsed: 0.424 sec ERROR! java.lang.NoClassDefFoundError at helloworld.sdo.client.HelloWorldClientComponent.getGreetings(HelloWorldCli en tComponent.java:33) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm pl .java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationIn vo ker.invoke(JavaImplementationInvoker.java:109) at org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke (P assByValueInterceptor.java:108) at org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindin gI nvoker.java:61) at org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke (P assByValueInterceptor.java:108) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvo ca tionHandler.java:286) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvo ca tionHandler.java:154) at $Proxy141.getGreetings(Unknown Source) at helloworld.sdo.SdoTestCase.testJavaToOSGi(SdoTestCase.java:81) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm pl .java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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.OldTestClassRunner.run(OldTestClassRunner.java: 35 ) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java: 62 ) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet( Ab stractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(Abstrac tD irectoryTestSuite.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(DelegatingMethodAccessorIm pl .java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(Surefir eB ooter.java:308) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:8 79 ) testOSGiToJava(helloworld.sdo.SdoTestCase) Time elapsed: 0.278 sec ERROR! java.lang.NoClassDefFoundError at helloworld.sdo.client.HelloWorldClientComponent.getGreetings(HelloWorldCli en tComponent.java:33)
Re: New Eclipse update site in SCA 1.2 release
On Tue, Apr 15, 2008 at 9:29 AM, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: ant elder wrote: In the 1.2 release candidate we've now an Eclipse update site. I can't find any mention of this happening anywhere, do we have any doc at all on it happening somewhere that I missed? ...ant We've been referring to it under different names, mostly 'plugin', as the update site is how Eclipse plugins are installed. A quick search gave me the following, but there's probably more: http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Release+-+Java+SCA+1.2 http://issues.apache.org/jira/browse/TUSCANY-2119 http://issues.apache.org/jira/browse/TUSCANY-2142 http://issues.apache.org/jira/browse/TUSCANY-2157 http://issues.apache.org/jira/browse/TUSCANY-2166 http://issues.apache.org/jira/browse/TUSCANY-2175 http://issues.apache.org/jira/browse/TUSCANY-2179 http://marc.info/?l=tuscany-devm=120650695831123 http://marc.info/?l=tuscany-devm=120656320414940 http://marc.info/?l=tuscany-devm=120694778015549 http://marc.info/?l=tuscany-devm=120699934118018 http://marc.info/?l=tuscany-devm=120613784003868 Sure but none of those actually mention having a new update site. All I'm saying is that IMHO something like this which is a whole new distribution artifact that gets its own mention in the release votes it would have been appropriate to have something like a hey I've made a new eclipse update site and added it to the 1.2 release type email to the dev list. ...ant
Re: [VOTE] Release Tuscany Java SCA 1.2-incubating (RC4)
Luciano Resende wrote: Please review and vote on the 1.2 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~lresende/tuscany/sca-1.2-RC4/ This includes the signed binary and source distributions, the RAT report, and the Maven staging repository. The eclipse updatesite for the Tuscany Eclipse plugins is available at: http://people.apache.org/~lresende/tuscany/sca-1.2-RC4/updatesite/ The release tag is available at : http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.2-RC4/ Looks OK to me, here is my +1. +1 from me - with the recommendation to update the FAQ and online documentation to make clear which versions of Java are recommended / known to work. Yours, Mike. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2165) Java runtime should inject service references to field with common name in absence of @Reference
[ https://issues.apache.org/jira/browse/TUSCANY-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589462#action_12589462 ] Vamsavardhana Reddy commented on TUSCANY-2165: -- TUSCANY-2165-revised-test.patch is only an updated test and so the test will fail. TUSCANY-2165.patch contains the fix for the problem. After applying this patch, the test will pass. You need to apply both patches. Sorry, if my posting two separate patches lead to any confusion. Java runtime should inject service references to field with common name in absence of @Reference - Key: TUSCANY-2165 URL: https://issues.apache.org/jira/browse/TUSCANY-2165 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams Priority: Minor Attachments: TUSCANY-2165-revised-test.patch, TUSCANY-2165.patch The Java AnnotationsAPIs specification Lines 1407, 1408, 1409, 1410 ... * References may also be injected via public setter methods even when the * @Reference annotation is not present. However, the @Reference * annotation must be used in order to inject a reference onto a non public * field. In the case where there is no @Reference annotation, the name of * the reference is the same as the name of the field or setter. The vTest: org.apache.tuscany.sca.vtest.javaapi.ReferenceAnnotationTestCase.atReference2 demonstrates this issue -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: distribution target-last-successful copies
Ok I've removed these in r648618. From all the comments it didn't seem like the copies these were providing were accessible now anyway. If we do need something like this on the continuum builds i'd be happy to help make a new build profile that the continuum builds could use. ...ant On Fri, Apr 11, 2008 at 9:31 AM, ant elder [EMAIL PROTECTED] wrote: On Thu, Apr 10, 2008 at 9:22 AM, ant elder [EMAIL PROTECTED] wrote: The current distribution build copies the binary artifacts to the target-last-successful folder which takes about 130Meg. I'm guessing this is something to do with the continuum builds but does anyone know for sure? If so could we change it so it only happens on the continuum machine (have the continuum build use a specific profile?), or if not can i just delete the copy task? ...ant OK maybe if I ask a different way... It looks like the target-last-successful copies aren't actually required anymore so unless i hear otherwise I'll remove the copy from the distribution pom.xml. ...ant
[NOTICE] Wang Feng voted as Tuscany committer
The Tuscany PPMC and Incubator PMC have voted for Wang Feng to become a Tuscany committer. Congratulations and welcome Wang Feng! ...ant
Re: [NOTICE] Wang Feng voted as Tuscany committer
Congratulations Wang Feng! Welcome! :) - Venkat On Wed, Apr 16, 2008 at 2:25 PM, ant elder [EMAIL PROTECTED] wrote: The Tuscany PPMC and Incubator PMC have voted for Wang Feng to become a Tuscany committer. Congratulations and welcome Wang Feng! ...ant
Re: [NOTICE] Wang Feng voted as Tuscany committer
Congrats Wang Feng!! ++Vamsi On Wed, Apr 16, 2008 at 2:25 PM, ant elder [EMAIL PROTECTED] wrote: The Tuscany PPMC and Incubator PMC have voted for Wang Feng to become a Tuscany committer. Congratulations and welcome Wang Feng! ...ant
Re: [NOTICE] Wang Feng voted as Tuscany committer
Welcome Wang Feng :). Ciao, Giorgio. --- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved. The ones who never yawn or say a commonplace thing, but burn, burn, burn like fabulous yellow roman candles exploding like spiders across the stars On The Road - Jack Kerouac - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [NOTICE] Wang Feng voted as Tuscany committer
The Tuscany PPMC and Incubator PMC have voted for Wang Feng to become a Tuscany committer. Congratulations and welcome Wang Feng! ...ant Congratulations and welcome, Wang Feng. Glad to have you on board. Yours, Mike. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can @ConversationID apply on private variable?
Gilbert Kwan wrote: In the spec of Java Common Annotations and APIs (http://www.osoa.org/download/attachments/35/SCA_JavaAnnotationsAndAPIs_V100.pdf?version=1), line 1710-1711 says 1710 @ConversationID 1711 private String ConversationID; I tried and got following warning: Apr 11, 2008 11:50:37 AM org.apache.tuscany.sca.implementation.java.introspect.impl.JavaIntrospectionHelper checkInvalidAnnotations WARNING: Invalid annotation @org.osoa.sca.annotations.ConversationID() is found on private java.lang.String org.apache.tuscany.sca.vtest.javaapi.annotations.scope.impl.IServiceImpl.conversationId Is it a spec or implementation error? Thanks Gilbert Gilbert, The intention was that injection should not occur onto private fields, for any artifact (Reference, Property, etc). The spec has errors and they need fixing - we will raise Issues in OASIS for these. Yours, Mike. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-2218) Endpoint URI resolution precedence for binding.ws reference is incorrect
[
https://issues.apache.org/jira/browse/TUSCANY-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsavardhana Reddy updated TUSCANY-2218:
-
Attachment: TUSCANY-2218-testcase.patch
TUSCANY-2218-testcase.patch: JUnit test.
Both the patches should be applied.
Endpoint URI resolution precedence for binding.ws reference is incorrect
Key: TUSCANY-2218
URL: https://issues.apache.org/jira/browse/TUSCANY-2218
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-1.0
Reporter: Lou Amodeo
Assignee: Vamsavardhana Reddy
Fix For: Java-SCA-Next
Attachments: TUSCANY-2218-testcase.patch, TUSCANY-2218.patch
I believe the order of Endpoint URI resolution precedence is incorrect for
binding.ws references. What I am seeing is that the uri attribute is taking
precedence over the location specified in the WSDL. The spec indicates that
the endpoint in the WSDL should take highest precedence.
Web Service Binding Spec
2.1.1 Endpoint URI resolution
71 The rules for resolving the URI at which an SCA service is hosted, or SCA
reference targets,
72 when used with binding.ws (in precedence order) are:
73 1. The URIs in the endpoint(s) of the referenced WSDL
74 or
75 The URI specified by the wsa:Address element of the wsa:EndpointReference,
76 2. The explicitly stated URI in the uri attribute of the binding.ws
element, which may be
77 relative,
78 3. The implicit URI as defined by the Assembly specification
In Axis2ServiceClient getPortLocation looks for uri first and returns it
ahead of wsdl location if present.
protected EndpointReference getPortLocationEPR(WebServiceBinding binding) {
String ep = binding.getURI(); WAS specific
if (ep == null binding.getPort() != null) {
List? wsdlPortExtensions =
binding.getPort().getExtensibilityElements();
for (final Object extension : wsdlPortExtensions) {
if (extension instanceof SOAPAddress) {
ep = ((SOAPAddress)extension).getLocationURI();
break;
}
if (extension instanceof SOAP12Address) {
SOAP12Address address = (SOAP12Address)extension;
ep = address.getLocationURI();
break;
}
}
}
return ep == null || .equals(ep) ? null : new EndpointReference(ep);
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-2218) Endpoint URI resolution precedence for binding.ws reference is incorrect
[
https://issues.apache.org/jira/browse/TUSCANY-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsavardhana Reddy updated TUSCANY-2218:
-
Patch Info: [Patch Available]
Fix Version/s: Java-SCA-Next
Assignee: (was: Vamsavardhana Reddy)
Unassigning so that a committer can pickup.
Endpoint URI resolution precedence for binding.ws reference is incorrect
Key: TUSCANY-2218
URL: https://issues.apache.org/jira/browse/TUSCANY-2218
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-1.0
Reporter: Lou Amodeo
Fix For: Java-SCA-Next
Attachments: TUSCANY-2218-testcase.patch, TUSCANY-2218.patch
I believe the order of Endpoint URI resolution precedence is incorrect for
binding.ws references. What I am seeing is that the uri attribute is taking
precedence over the location specified in the WSDL. The spec indicates that
the endpoint in the WSDL should take highest precedence.
Web Service Binding Spec
2.1.1 Endpoint URI resolution
71 The rules for resolving the URI at which an SCA service is hosted, or SCA
reference targets,
72 when used with binding.ws (in precedence order) are:
73 1. The URIs in the endpoint(s) of the referenced WSDL
74 or
75 The URI specified by the wsa:Address element of the wsa:EndpointReference,
76 2. The explicitly stated URI in the uri attribute of the binding.ws
element, which may be
77 relative,
78 3. The implicit URI as defined by the Assembly specification
In Axis2ServiceClient getPortLocation looks for uri first and returns it
ahead of wsdl location if present.
protected EndpointReference getPortLocationEPR(WebServiceBinding binding) {
String ep = binding.getURI(); WAS specific
if (ep == null binding.getPort() != null) {
List? wsdlPortExtensions =
binding.getPort().getExtensibilityElements();
for (final Object extension : wsdlPortExtensions) {
if (extension instanceof SOAPAddress) {
ep = ((SOAPAddress)extension).getLocationURI();
break;
}
if (extension instanceof SOAP12Address) {
SOAP12Address address = (SOAP12Address)extension;
ep = address.getLocationURI();
break;
}
}
}
return ep == null || .equals(ep) ? null : new EndpointReference(ep);
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [NOTICE] Wang Feng voted as Tuscany committer
On Wed, Apr 16, 2008 at 12:55 PM, Mike Edwards [EMAIL PROTECTED] wrote: The Tuscany PPMC and Incubator PMC have voted for Wang Feng to become a Tuscany committer. Congratulations and welcome Wang Feng! ...ant Congratulations and welcome, Wang Feng. Glad to have you on board. Yours, Mike. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Wang Feng. Congrats and welcome on board. Simon
Re: [NOTICE] Wang Feng voted as Tuscany committer
ant elder wrote: The Tuscany PPMC and Incubator PMC have voted for Wang Feng to become a Tuscany committer. Congratulations Wang Feng! -- Thanks, Dan Becker - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mirror of release artifacts
On Wed, Apr 16, 2008 at 8:41 AM, ant elder [EMAIL PROTECTED] wrote: I think thats a separate issue but if its the reason we stopped using the mirrors then i think we need to start using them again. It may not be clearly documented yet but i think the current ASF/incubator policy is that releases MUST be distributed via the mirrors. +1 http://incubator.apache.org/incubation/Incubation_Policy.html#Releases (last line) if you want to collect download statistics from a mirrored download then google/yahoo analytics is probably your best bet - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-2197) Conversations with OSGi services expire immediately
[ https://issues.apache.org/jira/browse/TUSCANY-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2197. - Resolution: Fixed Hi Jurgen. I'm marking this as resolved as Rajini applied the patch. Conversations with OSGi services expire immediately --- Key: TUSCANY-2197 URL: https://issues.apache.org/jira/browse/TUSCANY-2197 Project: Tuscany Issue Type: Bug Components: Java SCA OSGi Integration Affects Versions: Java-SCA-1.2 Environment: Windows XP, Eclipse 3.3.2 Reporter: Jürgen Schumacher Attachments: tuscany-implosgi-osgiannotation.patch This occurred with current revision from sca-java-1.2 branch. I use the Tuscany OSGi bundles created by itests/osgi-tuscany in Eclipse Equinox, the SCA domain is started in a BundleActivator of my test projects. When I use implementation.osgi for a conversational service, the first method call after the init method throws a org.osoa.sca.ConversationEndedException: Conversation 44c36d6c-68af-4ba9-a9ba-354ccc5dd9d0 has expired. I debugged this and it seems that is caused by org.apache.tuscany.sca.implementation.osgi.context.OSGiAnnotations, which uses Long.MAX_VALUE as the default values for maxAge and maxIdleTime which in turn causes an overflow in the initializeConversationAttributes() of org.apache.tuscany.sca.core.conversation.ExtendedConversationImpl. This results in a negative expirationTime which is of course always smaller than the current time. When I change the default values to -1 (as in org.apache.tuscany.sca.implementation.java.impl.JavaImplementationImpl), it works. See attached patch for modules/implementation-osgi. I'm not sure if this is the best or correct solution, but it may be a hint to someone with more knowledge about this code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [NOTICE] Wang Feng voted as Tuscany committer
Congrats, Wang Feng!! -- Thanks Regards, Ramkumar Ramalingam
[jira] Assigned: (TUSCANY-1867) @OneWay with String return type causes NullPointerException
[ https://issues.apache.org/jira/browse/TUSCANY-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam reassigned TUSCANY-1867: Assignee: Ramkumar Ramalingam @OneWay with String return type causes NullPointerException --- Key: TUSCANY-1867 URL: https://issues.apache.org/jira/browse/TUSCANY-1867 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.0 Environment: Windows XP Reporter: Simon Nash Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next I tried using @OneWay on a method with a String return type and I got a NullPointerException, like this: Exception in thread Axis2 Task java.lang.NullPointerException at org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvocationWorker.run(OutInAxisOperation.java:444) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:595) We should produce a better exception to tell the user what he/she has done wrong. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [NOTICE] Wang Feng voted as Tuscany committer
Congratulations Wang Feng and Welcome! Mark -Original Message- From: ant elder [mailto:[EMAIL PROTECTED] Sent: 16 April 2008 09:55 To: tuscany-dev Cc: [EMAIL PROTECTED] Subject: [NOTICE] Wang Feng voted as Tuscany committer The Tuscany PPMC and Incubator PMC have voted for Wang Feng to become a Tuscany committer. Congratulations and welcome Wang Feng! ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1867) @OneWay with String return type causes NullPointerException
[
https://issues.apache.org/jira/browse/TUSCANY-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589541#action_12589541
]
Ramkumar Ramalingam commented on TUSCANY-1867:
--
This JIRA talks about producing better exception message for those methods with
@OneWay annotations, when these method does not have void return type. The
best place to throw this exception would be in the
org.apache.tuscany.sca.interfacedef.java.impl.JavaInterfaceIntrospectorImpl
code as shown below, instead of allowing them to crop-up in the axis2 code.
boolean nonBlocking = method.isAnnotationPresent(OneWay.class);
if (nonBlocking) {
if (!(returnType == void.class)) {
throw new InvalidOperationException(
Method should return 'void' when declared with an
@OneWay annotation.,
method);
}
if (!(faultTypes.length == 0)) {
throw new InvalidOperationException(
Method should not declare exceptions with an
@OneWay annotation.,
method);
}
}
I'll attach a patch with this fix.
@OneWay with String return type causes NullPointerException
---
Key: TUSCANY-1867
URL: https://issues.apache.org/jira/browse/TUSCANY-1867
Project: Tuscany
Issue Type: Bug
Components: Java SCA Axis Binding Extension
Affects Versions: Java-SCA-1.0
Environment: Windows XP
Reporter: Simon Nash
Assignee: Ramkumar Ramalingam
Fix For: Java-SCA-Next
I tried using @OneWay on a method with a String return type and I got a
NullPointerException, like this:
Exception in thread Axis2 Task java.lang.NullPointerException
at
org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvocationWorker.run(OutInAxisOperation.java:444)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
We should produce a better exception to tell the user what he/she has done
wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-1881) Remote bidings attached to non-remotable services not reported as a warning in some cases
[ https://issues.apache.org/jira/browse/TUSCANY-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramkumar Ramalingam reassigned TUSCANY-1881: Assignee: Ramkumar Ramalingam (was: Simon Laws) Remote bidings attached to non-remotable services not reported as a warning in some cases - Key: TUSCANY-1881 URL: https://issues.apache.org/jira/browse/TUSCANY-1881 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model, Java SCA Problem Determination Affects Versions: Java-SCA-1.0 Environment: All Reporter: Simon Laws Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next I seem to remember in the past that adding remote bindings to services with interfaces not marked as remotable used to cause and error or a warning. This cropped up in the domain manager app which defines the following component. component name=DomainManagerComponent implementation.java class=org.apache.tuscany.sca.domain.impl.DomainManagerServiceImpl/ service name=DomainManagerInitService interface.java interface=org.apache.tuscany.sca.domain.DomainManagerInitService/ binding.sca/ /service service name=DomainManagerNodeEventService interface.java interface=org.apache.tuscany.sca.domain.DomainManagerNodeEventService/ binding.ws/ /service service name=DomainManagementService interface.java interface=org.apache.tuscany.sca.domain.management.DomainManagementService/ t:binding.jsonrpc / /service /component Where the DomainManagementService interface was not marked as remotable when it should have been (my mistake) but the interesting effect is that everything works except that no databindings are applied to the wires so parameters/return types are messed up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Handling exceptions for @OneWay Annotations
Hi, By working on TUSCANY-1881, i am just tyring to fix the issue for producing better exception message for those methods with @OneWay annotations, when these method does not have void return type. As mentioned in the specs Any method that returns void and has no declared exceptions may be marked with an @OneWay annotation. As a fix, I figured that org.apache.tuscany.sca.interfacedef.java.impl.JavaInterfaceIntrospectorImpl class needs to throw the exception in its getOperations() method as shown in my comments to TUSCANY-1881. But, I am not sure if this is the only place we need a fix for this issue? Please suggest -- Thanks Regards, Ramkumar Ramalingam
Re: Handling exceptions for @OneWay Annotations
Sorry for mentioning TUSCANY-1881.. the actual JIRA is TUSCANY-1867. -- Thanks Regards, Ramkumar Ramalingam
[jira] Assigned: (TUSCANY-2230) Test Cases for RequestContext API
[ https://issues.apache.org/jira/browse/TUSCANY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2230: --- Assignee: Simon Laws Test Cases for RequestContext API - Key: TUSCANY-2230 URL: https://issues.apache.org/jira/browse/TUSCANY-2230 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Assignee: Simon Laws Attachments: RequestContextJIRA2230.patch Test Cases for RequestContext's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2230) Test Cases for RequestContext API
[ https://issues.apache.org/jira/browse/TUSCANY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589572#action_12589572 ] Simon Laws commented on TUSCANY-2230: - Hi Yee-Kang I'm looking at applying this patch but having a little trouble. It seems that the patch file includes duplicate entries which results with undesirable results at my end (some files are twice as long as they should be). For example, if you open the patch you see that requestcontext/pom.xml appears twice. Can you try regenerating to remove these duplications? This seems to be a feature for the patches for 2231, 2232, 2233 also. Test Cases for RequestContext API - Key: TUSCANY-2230 URL: https://issues.apache.org/jira/browse/TUSCANY-2230 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Assignee: Simon Laws Attachments: RequestContextJIRA2230.patch Test Cases for RequestContext's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1881) Remote bidings attached to non-remotable services not reported as a warning in some cases
[ https://issues.apache.org/jira/browse/TUSCANY-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589562#action_12589562 ] Ramkumar Ramalingam commented on TUSCANY-1881: -- This JIRA talks about fixing the databinding issue that crops-up while the interfaces not marked as remotable in case of remote bindings to services. After discussing with Venkat, I understood that the datatransformation interceptor will not be inserted in the invocation chain if the target interface is not marked as remotable. Not having this interceptor will end up with binding specific data transformations not being done.. for example transformation of java object to OMElements in the case of axis2 binding. So if the json-rpc binding does have trouble with the arguments and returntypes because of the absence of transformations... that seems to the expected behaviour in this case. As a fix we will provide a warning in such scenarios. I'II attach a patch with a fix. Remote bidings attached to non-remotable services not reported as a warning in some cases - Key: TUSCANY-1881 URL: https://issues.apache.org/jira/browse/TUSCANY-1881 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model, Java SCA Problem Determination Affects Versions: Java-SCA-1.0 Environment: All Reporter: Simon Laws Assignee: Ramkumar Ramalingam Fix For: Java-SCA-Next I seem to remember in the past that adding remote bindings to services with interfaces not marked as remotable used to cause and error or a warning. This cropped up in the domain manager app which defines the following component. component name=DomainManagerComponent implementation.java class=org.apache.tuscany.sca.domain.impl.DomainManagerServiceImpl/ service name=DomainManagerInitService interface.java interface=org.apache.tuscany.sca.domain.DomainManagerInitService/ binding.sca/ /service service name=DomainManagerNodeEventService interface.java interface=org.apache.tuscany.sca.domain.DomainManagerNodeEventService/ binding.ws/ /service service name=DomainManagementService interface.java interface=org.apache.tuscany.sca.domain.management.DomainManagementService/ t:binding.jsonrpc / /service /component Where the DomainManagementService interface was not marked as remotable when it should have been (my mistake) but the interesting effect is that everything works except that no databindings are applied to the wires so parameters/return types are messed up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1997) Axis binding does not allow external configuration to increase the number of the maximum connections opened.
[ https://issues.apache.org/jira/browse/TUSCANY-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589574#action_12589574 ] Catalin Boloaja commented on TUSCANY-1997: -- It seems we can not use the patch provided for 1.0. Our code relies on the patch from TUSCANY-1893 and this one was not merged in the provided jars. Can we get a jar for 1.0 with the above patch merged into it ? Thank you, Catalin Boloaja Axis binding does not allow external configuration to increase the number of the maximum connections opened. Key: TUSCANY-1997 URL: https://issues.apache.org/jira/browse/TUSCANY-1997 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-Next Environment: Solaris , Windows , Websphere , Tomcat Reporter: Catalin Boloaja Assignee: Jean-Sebastien Delfino Fix For: Java-SCA-Next Attachments: tuscany-binding-ws-axis2-1.0-incubating-TUSCANY-1997.jar, tuscany-binding-ws-axis2-1.1-TUSCANY-1997.jar In a high volume situation the default setting for Axis2 is 2 connections per host. The default protocol being HTTP 1.1 , this means that only 2 POST requests can be issued at the same time. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Commented: (TUSCANY-2230) Test Cases for RequestContext API
I ran into this same problem last night when trying to apply this patch. I wonder if YK's patch tool is having trouble with adds. I remember the Subclipse tooling having a similar issue. As a workaround, I have found zip files of entirely new folders to be easy to integrate and commit. -- Kevin On Wed, Apr 16, 2008 at 8:23 AM, Simon Laws (JIRA) tuscany-dev@ws.apache.org wrote: [ https://issues.apache.org/jira/browse/TUSCANY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589572#action_12589572 ] Simon Laws commented on TUSCANY-2230: - Hi Yee-Kang I'm looking at applying this patch but having a little trouble. It seems that the patch file includes duplicate entries which results with undesirable results at my end (some files are twice as long as they should be). For example, if you open the patch you see that requestcontext/pom.xml appears twice. Can you try regenerating to remove these duplications? This seems to be a feature for the patches for 2231, 2232, 2233 also. Test Cases for RequestContext API - Key: TUSCANY-2230 URL: https://issues.apache.org/jira/browse/TUSCANY-2230 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Assignee: Simon Laws Attachments: RequestContextJIRA2230.patch Test Cases for RequestContext's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Deadline for ranking proposals Re: [GSoC] Time to rank the Google Summer of Code Proposals
Hi, I am interested in *co-mentoring* Integrate Google services in SCA compositions. Is there already a mentor for this project? Regards, Mario -Original Message- From: Luciano Resende [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 15, 2008 10:38 PM To: tuscany-dev@ws.apache.org Subject: Deadline for ranking proposals Re: [GSoC] Time to rank the Google Summer of Code Proposals This is a gentle reminder. We have untill April 18th midnight PDT to rank proposals. All mentors, please take a moment to rank proposals. [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Google+Summer+of+ Code+%282008%29+Applications -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deadline for ranking proposals Re: [GSoC] Time to rank the Google Summer of Code Proposals
Thanks for volunteering Mario. I'm going to add a note to the application as you don't have access to it. On Wed, Apr 16, 2008 at 7:55 AM, Antollini, Mario [EMAIL PROTECTED] wrote: Hi, I am interested in *co-mentoring* Integrate Google services in SCA compositions. Is there already a mentor for this project? Regards, Mario -Original Message- From: Luciano Resende [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 15, 2008 10:38 PM To: tuscany-dev@ws.apache.org Subject: Deadline for ranking proposals Re: [GSoC] Time to rank the Google Summer of Code Proposals This is a gentle reminder. We have untill April 18th midnight PDT to rank proposals. All mentors, please take a moment to rank proposals. [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Google+Summer+of+ Code+%282008%29+Applications -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [NOTICE] Wang Feng voted as Tuscany committer
ant elder wrote: The Tuscany PPMC and Incubator PMC have voted for Wang Feng to become a Tuscany committer. Congratulations and welcome Wang Feng! ...ant Congratulations Wang and Welcome! -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [(GSoC] Time to rank the Google Summer of Code Proposals
Ok. I subscribed the list. And now I'm sending an email for mentoring apache hadoop/sca Consider that my mentorship will end 30th June. Ciao, Giorgio. --- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved. The ones who never yawn or say a commonplace thing, but burn, burn, burn like fabulous yellow roman candles exploding like spiders across the stars On The Road - Jack Kerouac - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [NOTICE] Wang Feng voted as Tuscany committer
Congratulations Wang and Welcome! On Wed, Apr 16, 2008 at 8:17 AM, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: ant elder wrote: The Tuscany PPMC and Incubator PMC have voted for Wang Feng to become a Tuscany committer. Congratulations and welcome Wang Feng! ...ant Congratulations Wang and Welcome! -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deadline for ranking proposals Re: [GSoC] Time to rank the Google Summer of Code Proposals
Hi Vamsi, Yes, only mentors of a given organization can see the available proposals. On Wed, Apr 16, 2008 at 12:31 AM, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: Do I have to become a mentor even to view the proposals? Upon clicking on any links in [1], it is taking me to a page asking to become a mentor!! ++Vamsi On Wed, Apr 16, 2008 at 7:08 AM, Luciano Resende [EMAIL PROTECTED] wrote: This is a gentle reminder. We have untill April 18th midnight PDT to rank proposals. All mentors, please take a moment to rank proposals. [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Google+Summer+of+Code+%282008%29+Applications -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://people.apache.org/%7Elresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [NOTICE] Wang Feng voted as Tuscany committer
Wang, Feng, congratulations and welcome! (Wang is actually the last name :-). Raymond -- From: ant elder [EMAIL PROTECTED] Sent: Wednesday, April 16, 2008 1:55 AM To: tuscany-dev tuscany-dev@ws.apache.org Cc: [EMAIL PROTECTED] Subject: [NOTICE] Wang Feng voted as Tuscany committer The Tuscany PPMC and Incubator PMC have voted for Wang Feng to become a Tuscany committer. Congratulations and welcome Wang Feng! ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mirror of release artifacts
Distribution links pointing to the place below is enough ? http://www.apache.org/dist/incubator/tuscany/java/sca/1.1-incubating/ As for using google analytics for download information, this would be much easier, but can someone please show me an example that only count the actual downloads, instead of just page load/visit ? On Wed, Apr 16, 2008 at 5:58 AM, Robert Burrell Donkin [EMAIL PROTECTED] wrote: On Wed, Apr 16, 2008 at 8:41 AM, ant elder [EMAIL PROTECTED] wrote: I think thats a separate issue but if its the reason we stopped using the mirrors then i think we need to start using them again. It may not be clearly documented yet but i think the current ASF/incubator policy is that releases MUST be distributed via the mirrors. +1 http://incubator.apache.org/incubation/Incubation_Policy.html#Releases (last line) if you want to collect download statistics from a mirrored download then google/yahoo analytics is probably your best bet - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-2230) Test Cases for RequestContext API
[ https://issues.apache.org/jira/browse/TUSCANY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yee-Kang Chang updated TUSCANY-2230: Attachment: RequestContextJIRA2230Updated.patch Thanks, Simon. Here's the updated patch. Test Cases for RequestContext API - Key: TUSCANY-2230 URL: https://issues.apache.org/jira/browse/TUSCANY-2230 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Assignee: Simon Laws Attachments: RequestContextJIRA2230.patch, RequestContextJIRA2230Updated.patch Test Cases for RequestContext's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-2231) Test Cases for CallableReference API
[ https://issues.apache.org/jira/browse/TUSCANY-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yee-Kang Chang updated TUSCANY-2231: Attachment: CallableReferenceJIRA2231Updated.patch Updated patch. Test Cases for CallableReference API Key: TUSCANY-2231 URL: https://issues.apache.org/jira/browse/TUSCANY-2231 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Attachments: CallableReferenceJIRA2231.patch, CallableReferenceJIRA2231Updated.patch Test Cases for CallableReference's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-2232) Test Cases for ServiceReference API
[ https://issues.apache.org/jira/browse/TUSCANY-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yee-Kang Chang updated TUSCANY-2232: Attachment: ServiceReferenceJIRA2232Updated.patch Updated patch. Test Cases for ServiceReference API --- Key: TUSCANY-2232 URL: https://issues.apache.org/jira/browse/TUSCANY-2232 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Attachments: ServiceReferenceJIRA2232.patch, ServiceReferenceJIRA2232Updated.patch ServiceReference's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-2233) Test Cases for Conversation API
[ https://issues.apache.org/jira/browse/TUSCANY-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yee-Kang Chang updated TUSCANY-2233: Attachment: ConversationJIRA2233Updated.patch Updated patch. Test Cases for Conversation API --- Key: TUSCANY-2233 URL: https://issues.apache.org/jira/browse/TUSCANY-2233 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Attachments: ConversationJIRA2233.patch, ConversationJIRA2233Updated.patch Conversation's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-2233) Test Cases for Conversation API
[ https://issues.apache.org/jira/browse/TUSCANY-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yee-Kang Chang updated TUSCANY-2233: Attachment: ConversationJIRA2233.zip Zip of the code in case the patch still doesn't work. Thanks. Test Cases for Conversation API --- Key: TUSCANY-2233 URL: https://issues.apache.org/jira/browse/TUSCANY-2233 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Attachments: ConversationJIRA2233.patch, ConversationJIRA2233.zip, ConversationJIRA2233Updated.patch Conversation's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-2230) Test Cases for RequestContext API
[ https://issues.apache.org/jira/browse/TUSCANY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yee-Kang Chang updated TUSCANY-2230: Attachment: RequestContextJIRA2230.zip Zip of the code in case the updated patch still doesn't work. Test Cases for RequestContext API - Key: TUSCANY-2230 URL: https://issues.apache.org/jira/browse/TUSCANY-2230 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Assignee: Simon Laws Attachments: RequestContextJIRA2230.patch, RequestContextJIRA2230.zip, RequestContextJIRA2230Updated.patch Test Cases for RequestContext's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-2232) Test Cases for ServiceReference API
[ https://issues.apache.org/jira/browse/TUSCANY-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yee-Kang Chang updated TUSCANY-2232: Attachment: ServiceReferenceJIRA2232.zip Zip of the code in case the updated patch doesn't work. Thank you. Test Cases for ServiceReference API --- Key: TUSCANY-2232 URL: https://issues.apache.org/jira/browse/TUSCANY-2232 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Attachments: ServiceReferenceJIRA2232.patch, ServiceReferenceJIRA2232.zip, ServiceReferenceJIRA2232Updated.patch ServiceReference's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-2231) Test Cases for CallableReference API
[ https://issues.apache.org/jira/browse/TUSCANY-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yee-Kang Chang updated TUSCANY-2231: Attachment: CallableReferenceJIRA2231.zip Zip of the code in case the patch still doesn't know. Thanks. Test Cases for CallableReference API Key: TUSCANY-2231 URL: https://issues.apache.org/jira/browse/TUSCANY-2231 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Attachments: CallableReferenceJIRA2231.patch, CallableReferenceJIRA2231.zip, CallableReferenceJIRA2231Updated.patch Test Cases for CallableReference's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-2234) More tests for section 1.8 of SCA Java Annotations And APIs V100
[ https://issues.apache.org/jira/browse/TUSCANY-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams reassigned TUSCANY-2234: --- Assignee: Kevin Williams More tests for section 1.8 of SCA Java Annotations And APIs V100 Key: TUSCANY-2234 URL: https://issues.apache.org/jira/browse/TUSCANY-2234 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Gilbert Kwan Assignee: Kevin Williams Priority: Minor Attachments: T2234-vtest.new.zip, T2234.vtest.patch Add more tests for following sections 1.8.1 @AllowsPassByReference 1.8.3 @ComponentName 1.8.5 @Constructor 1.8.6 @Context 1.8.15 @Remotable -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-2235) RequestContext.getSecuritySubject() throws UnsupportedOperationException
RequestContext.getSecuritySubject() throws UnsupportedOperationException Key: TUSCANY-2235 URL: https://issues.apache.org/jira/browse/TUSCANY-2235 Project: Tuscany Issue Type: Bug Components: Java Spec APIs Reporter: Yee-Kang Chang This is part of the specification and should be supported? The vtest's RequestContextTestCase has a test that demonstrates this that's currently @Ignore. Thanks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mirror of release artifacts
On Wed, Apr 16, 2008 at 4:51 PM, Luciano Resende [EMAIL PROTECTED] wrote: Distribution links pointing to the place below is enough ? http://www.apache.org/dist/incubator/tuscany/java/sca/1.1-incubating/ no: releases must be downloaded from mirrors and not from the main apache server (see http://incubator.apache.org/guides/releasemanagement.html#release-distribution) As for using google analytics for download information, this would be much easier, but can someone please show me an example that only count the actual downloads, instead of just page load/visit ? it's not really possible to count downloads from mirrors. it is possible to count the number of times that the mirroring script is executed which is a reasonable proxy. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mirror of release artifacts
On Wed, Apr 16, 2008 at 9:15 AM, Robert Burrell Donkin [EMAIL PROTECTED] wrote: On Wed, Apr 16, 2008 at 4:51 PM, Luciano Resende [EMAIL PROTECTED] wrote: Distribution links pointing to the place below is enough ? http://www.apache.org/dist/incubator/tuscany/java/sca/1.1-incubating/ no: releases must be downloaded from mirrors and not from the main apache server (see http://incubator.apache.org/guides/releasemanagement.html#release-distribution) As for using google analytics for download information, this would be much easier, but can someone please show me an example that only count the actual downloads, instead of just page load/visit ? it's not really possible to count downloads from mirrors. it is possible to count the number of times that the mirroring script is executed which is a reasonable proxy. I agree this is a reasonable proxy. How can one obtain the number of times the mirroring script was executed ? - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-2234) More tests for section 1.8 of SCA Java Annotations And APIs V100
[ https://issues.apache.org/jira/browse/TUSCANY-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams closed TUSCANY-2234. --- Resolution: Fixed Fix Version/s: Java-SCA-Next More tests for section 1.8 of SCA Java Annotations And APIs V100 Key: TUSCANY-2234 URL: https://issues.apache.org/jira/browse/TUSCANY-2234 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Gilbert Kwan Assignee: Kevin Williams Priority: Minor Fix For: Java-SCA-Next Attachments: T2234-vtest.new.zip, T2234.vtest.patch Add more tests for following sections 1.8.1 @AllowsPassByReference 1.8.3 @ComponentName 1.8.5 @Constructor 1.8.6 @Context 1.8.15 @Remotable -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-2236) Unknown attibute causes StackOverflowError in XMLHelper.load()
Unknown attibute causes StackOverflowError in XMLHelper.load()
--
Key: TUSCANY-2236
URL: https://issues.apache.org/jira/browse/TUSCANY-2236
Project: Tuscany
Issue Type: Bug
Components: Java SDO Implementation
Affects Versions: Java-SDO-Next
Reporter: Raymond Feng
With this XSD:
xs:schema xmlns:ax21=http://types.move.ec3/xsd;
attributeFormDefault=qualified elementFormDefault=qualified
targetNamespace=http://types.move.ec3/xsd;
xmlns:xs=http://www.w3.org/2001/XMLSchema;
xs:complexType name=Comment
xs:sequence
xs:element minOccurs=0 name=body nillable=true
type=xs:string /
xs:element minOccurs=0 name=caption nillable=true
type=xs:string /
xs:element minOccurs=0 name=entryId nillable=true
type=xs:string /
xs:element minOccurs=0 name=owner nillable=true
type=xs:string /
xs:element minOccurs=0 name=reference nillable=true
type=xs:string /
xs:element minOccurs=0 name=tstamp nillable=true
type=xs:dateTime /
/xs:sequence
/xs:complexType
/xs:schema
And this XML:
ns:return xmlns:ns=http://services.move.ec3;
xmlns:ax21=http://types.move.ec3/xsd;
xmlns:_typens_=http://types.move.ec3/xsd;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
type=ec3.move.types.Comment
xsi:type=_typens_:Commentax21:bodyc/ax21:bodyax21:captionb/ax21:captionax21:entryId1/ax21:entryIdax21:ownera1/ax21:ownerax21:referencea1/ax21:referenceax21:tstamp2008-04-16T16:22:07.812Z/ax21:tstamp/ns:return
And this test case:
public void testLoad() {
HelperContext context = SDOUtil.createHelperContext();
InputStream is = getClass().getResourceAsStream(/comment.xsd);
context.getXSDHelper().define(is, null);
try {
context.getXMLHelper().load(XML);
} catch (StackOverflowError e) {
// FIXME: This test case is failing at this point
e.printStackTrace();
}
}
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XMLHandler.java:2466)
at
org.eclipse.emf.ecore.xmi.impl.SAXXMLHandler.handleObjectAttribs(SAXXMLHandler.java:72)
at
org.apache.tuscany.sdo.util.resource.SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler.handleUnknownFeature(SDOXMLResourceImpl.java:366)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XMLHandler.java:2466)
at
org.eclipse.emf.ecore.xmi.impl.SAXXMLHandler.handleObjectAttribs(SAXXMLHandler.java:72)
at
org.apache.tuscany.sdo.util.resource.SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler.handleUnknownFeature(SDOXMLResourceImpl.java:366)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XMLHandler.java:2466)
at
org.eclipse.emf.ecore.xmi.impl.SAXXMLHandler.handleObjectAttribs(SAXXMLHandler.java:72)
at
org.apache.tuscany.sdo.util.resource.SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler.handleUnknownFeature(SDOXMLResourceImpl.java:366)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XMLHandler.java:2466)
at
org.eclipse.emf.ecore.xmi.impl.SAXXMLHandler.handleObjectAttribs(SAXXMLHandler.java:72)
at
org.apache.tuscany.sdo.util.resource.SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler.handleUnknownFeature(SDOXMLResourceImpl.java:366)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XMLHandler.java:2466)
at
org.eclipse.emf.ecore.xmi.impl.SAXXMLHandler.handleObjectAttribs(SAXXMLHandler.java:72)
at
org.apache.tuscany.sdo.util.resource.SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler.handleUnknownFeature(SDOXMLResourceImpl.java:366)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XMLHandler.java:2466)
at
org.eclipse.emf.ecore.xmi.impl.SAXXMLHandler.handleObjectAttribs(SAXXMLHandler.java:72)
at
org.apache.tuscany.sdo.util.resource.SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler.handleUnknownFeature(SDOXMLResourceImpl.java:366)
at
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XMLHandler.java:2466)
at
org.eclipse.emf.ecore.xmi.impl.SAXXMLHandler.handleObjectAttribs(SAXXMLHandler.java:72)
at
org.apache.tuscany.sdo.util.resource.SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler.handleUnknownFeature(SDOXMLResourceImpl.java:366)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-2069) Missing serialization in DirectedGraph
[ https://issues.apache.org/jira/browse/TUSCANY-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Feng reassigned TUSCANY-2069: - Assignee: Raymond Feng Missing serialization in DirectedGraph -- Key: TUSCANY-2069 URL: https://issues.apache.org/jira/browse/TUSCANY-2069 Project: Tuscany Issue Type: Bug Components: Java SCA Data Binding Runtime Affects Versions: Java-SCA-1.0.1 Reporter: Greg Dritschler Assignee: Raymond Feng Fix For: Java-SCA-Next I have a service with a web service binding that processes its input using an SDO. The service works fine with one client. It also works fine if it is driven once by one client and then driven by multiple clients. But if it is driven initially by multiple clients (2 is enough), various failures occur in org.apache.tuscany.sca.databinding.impl.DirectedGraph. It appears there is a lack of synchronization in this class. Failure 1 - NPE java.lang.NullPointerException at org.apache.tuscany.sca.databinding.impl.DirectedGraph$Node.access$400(DirectedGraph.java:188) at org.apache.tuscany.sca.databinding.impl.DirectedGraph.getShortestPath(DirectedGraph.java:314) at org.apache.tuscany.sca.databinding.DefaultTransformerExtensionPoint.getTransformerChain(DefaultTransformerExtensionPoint.java:302) at org.apache.tuscany.sca.databinding.impl.MediatorImpl.getTransformerChain(MediatorImpl.java:162) at org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:76) at org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:183) at org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:59) at org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:88) at org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.transform(DataTransformationInterceptor.java:192) at org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:89) at com.ibm.ws.soa.sca.runtime.impl.RuntimeExtensionManager.invokeNextInterceptor(RuntimeExtensionManager.java:211) at com.ibm.ws.soa.sca.runtime.impl.RuntimeExtensionManager.processMessage(RuntimeExtensionManager.java:96) at com.ibm.ws.soa.sca.runtime.impl.RuntimeTuscanyInterceptor.invoke(RuntimeTuscanyInterceptor.java:154) at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.invokeTarget(Axis2ServiceProvider.java:852) at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceInOutSyncMessageReceiver.invokeBusinessLogic(Axis2ServiceInOutSyncMessageReceiver.java:119) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:42) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:147) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) Failure 2 - timeout (code is probably looping) WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[WebContainer : 0,5,main]. The stack trace of this thread when the timeout occurred was: java.util.HashMap.findNonNullKeyEntry(Unknown Source) java.util.HashMap.putImpl(Unknown Source) java.util.HashMap.put(Unknown Source) org.apache.tuscany.sca.databinding.impl.DirectedGraph.getShortestPath(DirectedGraph.java:296) org.apache.tuscany.sca.databinding.DefaultTransformerExtensionPoint.getTransformerChain(DefaultTransformerExtensionPoint.java:302) org.apache.tuscany.sca.databinding.impl.MediatorImpl.getTransformerChain(MediatorImpl.java:162) org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:76) org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:183) org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:59) org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:88) org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.transform(DataTransformationInterceptor.java:192) org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:89) com.ibm.ws.soa.sca.runtime.impl.RuntimeExtensionManager.invokeNextInterceptor(RuntimeExtensionManager.java:211)
[jira] Resolved: (TUSCANY-2069) Missing serialization in DirectedGraph
[ https://issues.apache.org/jira/browse/TUSCANY-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Feng resolved TUSCANY-2069. --- Resolution: Fixed I checked in a fix under 648763, please verify. Missing serialization in DirectedGraph -- Key: TUSCANY-2069 URL: https://issues.apache.org/jira/browse/TUSCANY-2069 Project: Tuscany Issue Type: Bug Components: Java SCA Data Binding Runtime Affects Versions: Java-SCA-1.0.1 Reporter: Greg Dritschler Assignee: Raymond Feng Fix For: Java-SCA-Next I have a service with a web service binding that processes its input using an SDO. The service works fine with one client. It also works fine if it is driven once by one client and then driven by multiple clients. But if it is driven initially by multiple clients (2 is enough), various failures occur in org.apache.tuscany.sca.databinding.impl.DirectedGraph. It appears there is a lack of synchronization in this class. Failure 1 - NPE java.lang.NullPointerException at org.apache.tuscany.sca.databinding.impl.DirectedGraph$Node.access$400(DirectedGraph.java:188) at org.apache.tuscany.sca.databinding.impl.DirectedGraph.getShortestPath(DirectedGraph.java:314) at org.apache.tuscany.sca.databinding.DefaultTransformerExtensionPoint.getTransformerChain(DefaultTransformerExtensionPoint.java:302) at org.apache.tuscany.sca.databinding.impl.MediatorImpl.getTransformerChain(MediatorImpl.java:162) at org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:76) at org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:183) at org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:59) at org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:88) at org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.transform(DataTransformationInterceptor.java:192) at org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:89) at com.ibm.ws.soa.sca.runtime.impl.RuntimeExtensionManager.invokeNextInterceptor(RuntimeExtensionManager.java:211) at com.ibm.ws.soa.sca.runtime.impl.RuntimeExtensionManager.processMessage(RuntimeExtensionManager.java:96) at com.ibm.ws.soa.sca.runtime.impl.RuntimeTuscanyInterceptor.invoke(RuntimeTuscanyInterceptor.java:154) at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.invokeTarget(Axis2ServiceProvider.java:852) at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceInOutSyncMessageReceiver.invokeBusinessLogic(Axis2ServiceInOutSyncMessageReceiver.java:119) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:42) at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:147) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) Failure 2 - timeout (code is probably looping) WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[WebContainer : 0,5,main]. The stack trace of this thread when the timeout occurred was: java.util.HashMap.findNonNullKeyEntry(Unknown Source) java.util.HashMap.putImpl(Unknown Source) java.util.HashMap.put(Unknown Source) org.apache.tuscany.sca.databinding.impl.DirectedGraph.getShortestPath(DirectedGraph.java:296) org.apache.tuscany.sca.databinding.DefaultTransformerExtensionPoint.getTransformerChain(DefaultTransformerExtensionPoint.java:302) org.apache.tuscany.sca.databinding.impl.MediatorImpl.getTransformerChain(MediatorImpl.java:162) org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:76) org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:183) org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:59) org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:88) org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.transform(DataTransformationInterceptor.java:192) org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:89)
[jira] Assigned: (TUSCANY-2113) Problem with fault comparison in DataTransformationInterceptor; maybe we should compare elem QNames, not type QNames?
[ https://issues.apache.org/jira/browse/TUSCANY-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Feng reassigned TUSCANY-2113: - Assignee: Raymond Feng Problem with fault comparison in DataTransformationInterceptor; maybe we should compare elem QNames, not type QNames? - Key: TUSCANY-2113 URL: https://issues.apache.org/jira/browse/TUSCANY-2113 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-1.1 Reporter: Scott Kurz Assignee: Raymond Feng Fix For: Java-SCA-Next There's a problem with how the fault matching in DTI uses the private DTI.typesMatch() method. I don't think it should be allowing a matching type name to return 'true', i.e. indicate a successful match. return matches(t1.getElementName(), t2.getElementName()) || matches(t1.getTypeName(), t2.getTypeName()); For one, I could have two distinct fault elems of the same type. In addition, also note that, if you have a fault element with anonymous type, the generated JAXB will look like: @XmlType(name = ..) so we will build up an XMLType with typeName equal to a namespace plus a null name.One problem with this is that there is no way to distinguish between two fault elems in the same NS, with anonymous types. I haven't given this a huge amount of thought so I mention this in case anyone thinks of other issues relating to some of the points I am making. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-2237) Java 2 Security - Enhancements to run Itest bucket
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 Fix For: Java-SCA-Next 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. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2113) Problem with fault comparison in DataTransformationInterceptor; maybe we should compare elem QNames, not type QNames?
[ https://issues.apache.org/jira/browse/TUSCANY-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589664#action_12589664 ] Raymond Feng commented on TUSCANY-2113: --- Hi, Scott. Do you have a test case handy for this issue? Thanks, Raymond Problem with fault comparison in DataTransformationInterceptor; maybe we should compare elem QNames, not type QNames? - Key: TUSCANY-2113 URL: https://issues.apache.org/jira/browse/TUSCANY-2113 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-1.1 Reporter: Scott Kurz Assignee: Raymond Feng Fix For: Java-SCA-Next There's a problem with how the fault matching in DTI uses the private DTI.typesMatch() method. I don't think it should be allowing a matching type name to return 'true', i.e. indicate a successful match. return matches(t1.getElementName(), t2.getElementName()) || matches(t1.getTypeName(), t2.getTypeName()); For one, I could have two distinct fault elems of the same type. In addition, also note that, if you have a fault element with anonymous type, the generated JAXB will look like: @XmlType(name = ..) so we will build up an XMLType with typeName equal to a namespace plus a null name.One problem with this is that there is no way to distinguish between two fault elems in the same NS, with anonymous types. I haven't given this a huge amount of thought so I mention this in case anyone thinks of other issues relating to some of the points I am making. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (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 updated TUSCANY-2237: Attachment: TUSCANY-2237.patch This file adds Java 2 security to cover ITests. I would like to co-review with a commiter before commiting. 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 Fix For: Java-SCA-Next Attachments: TUSCANY-2237.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. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (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 updated TUSCANY-2237: Patch Info: [Patch Available] 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 Fix For: Java-SCA-Next Attachments: TUSCANY-2237.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. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (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 ] Raymond Feng reassigned TUSCANY-2237: - Assignee: Raymond Feng 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.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. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (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:comment-tabpanelfocusedCommentId=12589684#action_12589684
]
Raymond Feng commented on TUSCANY-2237:
---
IMO, the following priviledged block is too wide. Can you find the offending
module and move the doPrivileged() to that module only?
Index:
modules/host-embedded/src/main/java/org/apache/tuscany/sca/host/embedded/impl/ReallySmallRuntime.java
-module.stop(registry);
+// Allow privileged access to stop MBeans. Requires
MBeanPermission in security policy.
+AccessController.doPrivileged(new PrivilegedActionObject() {
+public Object run() {
+module.stop(registry);
+return null;
+}
+});
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.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.
Re: How do you plug in validation monitoring?
Hi Simon, I looked at the new Monitor and Problem interfaces. What do getMessageId() and getMessageParams() actually return? is MessageId a way to categorize the error message? regards Hasan On Tue, Apr 15, 2008 at 10:59 AM, Hasan Muhammad [EMAIL PROTECTED] wrote: Hi Simon, I was wondering if i can cook up some validation test cases if they do not exist. Or should we wait until the monitor issue is resolved ? Hasan On Thu, Apr 10, 2008 at 4:34 PM, Hasan Muhammad [EMAIL PROTECTED] wrote: Hi Simon, I dont think using an underlying tuscany jdk logger would be useful to plugins as they may not want to log, rather show it somewhere else such as console etc. Tuscany can use an underlying logger in it's own monitor ( as it uses today). But i think the first approach of using a monitor is better along with the condition that it be made more usable by the plugins by giving them greater control. Another point is that tuscany should use ResourceBundle for validation messages as well. I dont think this is being done today. regards Hasan On Wed, Apr 9, 2008 at 1:22 PM, Simon Laws [EMAIL PROTECTED] wrote: On Wed, Apr 9, 2008 at 12:49 PM, Simon Laws [EMAIL PROTECTED] wrote: On Wed, Apr 9, 2008 at 12:00 PM, Hasan Muhammad [EMAIL PROTECTED] wrote: Hi Simon, I am on revision 634808. The ContributionServiceImpl has changed since then, and with the one that i have, it would lead through the CompositeProcessor instead of the CompositeDocumentProcessor. Hence the difference in exceptions.. Also, dont you think that with the error that you got should throw an exception with schema validation, rather than just a warning? Hasan On Wed, Apr 9, 2008 at 6:36 AM, Simon Laws [EMAIL PROTECTED] wrote: On Tue, Apr 8, 2008 at 2:58 PM, Hasan Muhammad [EMAIL PROTECTED] wrote: Hi Simon, Thank you for the good information. First up i am trying to verify whether the schema validation works when we point to our schemas. Can you let me know what is a simple error that i can introduce so that i can verify this? I tried doing this to my composite file (In block red): component name=MyServiceComponentNew implementation.java class=mysca.test.myservice.impl.MyServiceImpl/ *binding.ws/* property name=location source=$newLocation/ property name=year source=$newYear/ /component This resulted in the following exception, but i think this is part of the validation done by artifact processor and would result even if we comment out the schema validation. org.apache.tuscany.sca.contribution.service.ContributionReadException: Unexpected binding element found. It should appear inside a service or reference element at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.read(CompositeProcessor.java:373) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.read(CompositeProcessor.java:75) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.read(ExtensibleStAXArtifactProcessor.java:83) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.processReadPhase(ContributionServiceImpl.java:475) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:383) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:202) at com.ibm.ws.soa.sca.runtime.impl.DomainCompositeHelper.addContribution(DomainCompositeHelper.java:75) at com.ibm.ws.soa.sca.runtime.impl.SCAContainerComponentImpl.startComposite(SCAContainerComponentImpl.java:235) at com.ibm.ws.soa.sca.admin.runtime.tuscany.SCATuscanyRuntimeHandlerImpl.startModule(SCATuscanyRuntimeHandlerImpl.java:125) at com.ibm.ws.soa.sca.admin.runtime.impl.SCARuntimeImpl.start(SCARuntimeImpl.java:349) at com.ibm.ws.soa.sca.admin.runtime.impl.SCARuntimeImpl.start(SCARuntimeImpl.java:446) at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:331) at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:126) at
[jira] Assigned: (TUSCANY-2230) Test Cases for RequestContext API
[ https://issues.apache.org/jira/browse/TUSCANY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams reassigned TUSCANY-2230: --- Assignee: Kevin Williams (was: Simon Laws) Test Cases for RequestContext API - Key: TUSCANY-2230 URL: https://issues.apache.org/jira/browse/TUSCANY-2230 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Assignee: Kevin Williams Attachments: RequestContextJIRA2230.patch, RequestContextJIRA2230.zip, RequestContextJIRA2230Updated.patch Test Cases for RequestContext's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (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:comment-tabpanelfocusedCommentId=12589709#action_12589709 ] Dan Becker commented on TUSCANY-2237: - Yes, will do. Thanks for reviewing and keeping me honest. I will have an updated patch soon. 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.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. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-2230) Test Cases for RequestContext API
[
https://issues.apache.org/jira/browse/TUSCANY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Williams closed TUSCANY-2230.
---
Resolution: Fixed
I noticed the following empty test method in the RequestContext test case:
/**
* L863 br
* getServiceReference() - Returns the callable reference that represents
the service or callback reference that the request was invoked on.
* It is illegal for the service implementation to try to call the
setCallback() on a returned service reference.
*
* @throws Exception
*/
@Test
public void testGetServiceReference() throws Exception {
}
Do you intend to come back to this?
Test Cases for RequestContext API
-
Key: TUSCANY-2230
URL: https://issues.apache.org/jira/browse/TUSCANY-2230
Project: Tuscany
Issue Type: Test
Components: Java SCA Verification Tests
Reporter: Yee-Kang Chang
Assignee: Kevin Williams
Attachments: RequestContextJIRA2230.patch,
RequestContextJIRA2230.zip, RequestContextJIRA2230Updated.patch
Test Cases for RequestContext's vtest.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Closed: (TUSCANY-2230) Test Cases for RequestContext API
Thanks, Kevin. Yes, I do intend to come back to it. Had wanted to have
the specification clarified before I put in formal test cases.
---
[
https://issues.apache.org/jira/browse/TUSCANY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Williams closed TUSCANY-2230.
---
Resolution: Fixed
I noticed the following empty test method in the RequestContext test case:
/**
* L863 br
* getServiceReference() - Returns the callable reference that
represents the service or callback reference that the request was invoked
on.
* It is illegal for the service implementation to try to call the
setCallback() on a returned service reference.
*
* @throws Exception
*/
@Test
public void testGetServiceReference() throws Exception {
}
Do you intend to come back to this?
Test Cases for RequestContext API
-
Key: TUSCANY-2230
URL: https://issues.apache.org/jira/browse/TUSCANY-2230
Project: Tuscany
Issue Type: Test
Components: Java SCA Verification Tests
Reporter: Yee-Kang Chang
Assignee: Kevin Williams
Attachments: RequestContextJIRA2230.patch,
RequestContextJIRA2230.zip, RequestContextJIRA2230Updated.patch
Test Cases for RequestContext's vtest.
How to stop a service?
I'm trying to test ServiceUnavailableException (as part of vtest) -- to simulate that a service is unavailable and the Exception will be thrown. The current idea is to have a service started, invoke some operation, stop it, and then invoke some other operation to see if a ServiceUnavailableException will be thrown. Is there a way for us to stop a service in Tuscany? Or, there's better ways for us to test ServiceUnavailableException? Thank you!
[jira] Closed: (TUSCANY-2231) Test Cases for CallableReference API
[ https://issues.apache.org/jira/browse/TUSCANY-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams closed TUSCANY-2231. --- Resolution: Fixed Fix Version/s: Java-SCA-Next Test Cases for CallableReference API Key: TUSCANY-2231 URL: https://issues.apache.org/jira/browse/TUSCANY-2231 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Fix For: Java-SCA-Next Attachments: CallableReferenceJIRA2231.patch, CallableReferenceJIRA2231.zip, CallableReferenceJIRA2231Updated.patch Test Cases for CallableReference's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-2232) Test Cases for ServiceReference API
[ https://issues.apache.org/jira/browse/TUSCANY-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams reassigned TUSCANY-2232: --- Assignee: Kevin Williams Test Cases for ServiceReference API --- Key: TUSCANY-2232 URL: https://issues.apache.org/jira/browse/TUSCANY-2232 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Assignee: Kevin Williams Attachments: ServiceReferenceJIRA2232.patch, ServiceReferenceJIRA2232.zip, ServiceReferenceJIRA2232Updated.patch ServiceReference's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Building a Chinese Web Site for Tuscany
Hi, I noticed that a few folks from the Chinese community have started to contribute Chinese content for Tuscany at [1]. At this moment, the menu items have been translated into Chinese. Some of the links still point back to our English version. I suggest that we add a link on the official Tuscany website to link to it while the Chinese Tuscany community continue to build the content. I will put the 'work in progress, please contribute' in Chinese there to let the community know that this is work in progress and they are very welcome to contribute. [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Chinese+Web+Site Thanks, Raymond - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-2233) Test Cases for Conversation API
[ https://issues.apache.org/jira/browse/TUSCANY-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams reassigned TUSCANY-2233: --- Assignee: Kevin Williams Test Cases for Conversation API --- Key: TUSCANY-2233 URL: https://issues.apache.org/jira/browse/TUSCANY-2233 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Assignee: Kevin Williams Attachments: ConversationJIRA2233.patch, ConversationJIRA2233.zip, ConversationJIRA2233Updated.patch Conversation's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-2232) Test Cases for ServiceReference API
[ https://issues.apache.org/jira/browse/TUSCANY-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams closed TUSCANY-2232. --- Resolution: Fixed Fix Version/s: Java-SCA-Next Test Cases for ServiceReference API --- Key: TUSCANY-2232 URL: https://issues.apache.org/jira/browse/TUSCANY-2232 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Assignee: Kevin Williams Fix For: Java-SCA-Next Attachments: ServiceReferenceJIRA2232.patch, ServiceReferenceJIRA2232.zip, ServiceReferenceJIRA2232Updated.patch ServiceReference's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[vtest] Intermittent failures with @Scope tests
I am seeing an infrequent, intermittent failure in one of the @Scope vtests: GService-destroyGService Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.281 sec FAILURE! atScope1(org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotationTestCase) Time elapsed: 1.203 sec FAILURE! junit.framework.ComparisonFailure: null expected:[None] but was:[Unknown] at junit.framework.Assert.assertEquals(Assert.java:81) at junit.framework.Assert.assertEquals(Assert.java:87) at org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotationTestCase.atScope1(ScopeAnnotationTestCase.java:93) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75) at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36) at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) 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:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879) Results : Failed tests: atScope1(org.apache.tuscany.sca.vtest.javaapi.annotations.scope.ScopeAnnotationTestCase) Tests run: 5, Failures: 1, Errors: 0, Skipped: 0 --- Has anyone else seen this? -- Kevin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-2233) Test Cases for Conversation API
[ https://issues.apache.org/jira/browse/TUSCANY-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams closed TUSCANY-2233. --- Resolution: Fixed Test Cases for Conversation API --- Key: TUSCANY-2233 URL: https://issues.apache.org/jira/browse/TUSCANY-2233 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Assignee: Kevin Williams Attachments: ConversationJIRA2233.patch, ConversationJIRA2233.zip, ConversationJIRA2233Updated.patch Conversation's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-2238) Test Cases for Exception APIs
Test Cases for Exception APIs - Key: TUSCANY-2238 URL: https://issues.apache.org/jira/browse/TUSCANY-2238 Project: Tuscany Issue Type: Test Reporter: Yee-Kang Chang Attachments: ExceptionJIRA2238.patch vtest's test cases for the various Exceptions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-2238) Test Cases for Exception APIs
[ https://issues.apache.org/jira/browse/TUSCANY-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yee-Kang Chang updated TUSCANY-2238: Attachment: ExceptionJIRA2238.patch Test Cases for Exception APIs - Key: TUSCANY-2238 URL: https://issues.apache.org/jira/browse/TUSCANY-2238 Project: Tuscany Issue Type: Test Reporter: Yee-Kang Chang Attachments: ExceptionJIRA2238.patch vtest's test cases for the various Exceptions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-2238) Test Cases for Exception APIs
[ https://issues.apache.org/jira/browse/TUSCANY-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams updated TUSCANY-2238: Component/s: Java SCA Verification Tests Test Cases for Exception APIs - Key: TUSCANY-2238 URL: https://issues.apache.org/jira/browse/TUSCANY-2238 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Attachments: ExceptionJIRA2238.patch vtest's test cases for the various Exceptions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-2238) Test Cases for Exception APIs
[ https://issues.apache.org/jira/browse/TUSCANY-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Williams reassigned TUSCANY-2238: --- Assignee: Kevin Williams Test Cases for Exception APIs - Key: TUSCANY-2238 URL: https://issues.apache.org/jira/browse/TUSCANY-2238 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Assignee: Kevin Williams Attachments: ExceptionJIRA2238.patch vtest's test cases for the various Exceptions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Updated: (TUSCANY-2238) Test Cases for Exception APIs
Hi YK, Your patch files always seem to include duplicate entries. On Wed, Apr 16, 2008 at 3:19 PM, Yee-Kang Chang (JIRA) tuscany-dev@ws.apache.org wrote: [ https://issues.apache.org/jira/browse/TUSCANY-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yee-Kang Chang updated TUSCANY-2238: Attachment: ExceptionJIRA2238.patch Test Cases for Exception APIs - Key: TUSCANY-2238 URL: https://issues.apache.org/jira/browse/TUSCANY-2238 Project: Tuscany Issue Type: Test Reporter: Yee-Kang Chang Attachments: ExceptionJIRA2238.patch vtest's test cases for the various Exceptions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2113) Problem with fault comparison in DataTransformationInterceptor; maybe we should compare elem QNames, not type QNames?
[ https://issues.apache.org/jira/browse/TUSCANY-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589777#action_12589777 ] Scott Kurz commented on TUSCANY-2113: - I'm sorry I don't have a test case handy. If I look at itests, I see you could take: sca/itest/exceptions-cross-binding-ws/src/main/resources/wsdl/StockExceptionTest.wsdl and add another int, integer, or anonymous-typed fault and expand the test in that way. Problem with fault comparison in DataTransformationInterceptor; maybe we should compare elem QNames, not type QNames? - Key: TUSCANY-2113 URL: https://issues.apache.org/jira/browse/TUSCANY-2113 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-1.1 Reporter: Scott Kurz Assignee: Raymond Feng Fix For: Java-SCA-Next There's a problem with how the fault matching in DTI uses the private DTI.typesMatch() method. I don't think it should be allowing a matching type name to return 'true', i.e. indicate a successful match. return matches(t1.getElementName(), t2.getElementName()) || matches(t1.getTypeName(), t2.getTypeName()); For one, I could have two distinct fault elems of the same type. In addition, also note that, if you have a fault element with anonymous type, the generated JAXB will look like: @XmlType(name = ..) so we will build up an XMLType with typeName equal to a namespace plus a null name.One problem with this is that there is no way to distinguish between two fault elems in the same NS, with anonymous types. I haven't given this a huge amount of thought so I mention this in case anyone thinks of other issues relating to some of the points I am making. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [NOTICE] Wang Feng voted as Tuscany committer
Thanks everyone for the congratulations and welcome and I'm looking forward to the next exciting stage of the Tuscany community. Thanks, Wang Feng On 2008-04-16 16:55:10,ant elder [EMAIL PROTECTED] wrote: The Tuscany PPMC and Incubator PMC have voted for Wang Feng to become a Tuscany committer. Congratulations and welcome Wang Feng! ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to stop a service?
Look at the tearDown method on the contribution-multiple itest below. This might give you some ideas. https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/itest/contribution-multiple/src/test/java/test/ContributionTestCase.java On Wed, Apr 16, 2008 at 1:38 PM, Yee-Kang Chang [EMAIL PROTECTED] wrote: I'm trying to test ServiceUnavailableException (as part of vtest) -- to simulate that a service is unavailable and the Exception will be thrown. The current idea is to have a service started, invoke some operation, stop it, and then invoke some other operation to see if a ServiceUnavailableException will be thrown. Is there a way for us to stop a service in Tuscany? Or, there's better ways for us to test ServiceUnavailableException? Thank you! -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-2239) Support for mutually-exclusive intents
Support for mutually-exclusive intents -- Key: TUSCANY-2239 URL: https://issues.apache.org/jira/browse/TUSCANY-2239 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Runtime Reporter: Greg Dritschler The SCA Policy specification does not provide a means to define intents which are mutually exclusive. This is a noticeable omission when considering the intents in the SCA Transaction specification which are mutually exclusive by nature (managedTransaction vs. noManagedTransaction, propagatesTransaction vs. suspendsTransaction). There is a need to be able to define intents which are mutually exclusive and for the exclusion to be checked by the SCA runtime to avoid the error of specifying exclusive intents on a single artifact. In addition, there should be rules defined for the handling of mutually exclusive intents which are attached at different levels of a composite or a hierarchy of composites. I have attached a patch to provide the capability to define mutually exclusive intents. This is achieved using a new @excludes attribute on the intent/ element in definitions.xml. For example: intent name=propagatesTransaction constrains=implementation excludes=suspendsTransaction/ @excludes is a list of intents which are mutually-exclusive with the named intent. In order to be effective, a reciprocal definition needs to be made as shown below. intent name=suspendsTransaction constrains=implementation excludes=propagatesTransaction/ The patch makes no assumptions about the relationship of qualified intents to the base intent. Therefore exclusive relationships between qualified intents need to be spelled out. intent name=noManagedTransaction constrains=implementation excludes=managedTransaction managedTransaction.global managedTransaction.local/ A key part of the patch is that there now are two types of intent inheritance with respect to exclusive intents. There is a default inheritance between certain hierarchical elements within a composite. For example consider this snippet from a composite: component name=C1 requires=propagatesTransaction reference name=r1/ reference name=r2/ reference name=r3 requires=suspendsTransaction/ /component In this case the first two references inherit the default intent propagatesTransaction from the component element. However the third reference does not inherit it because it specifies an exclusive intent suspendsTransaction which overrides the component-level default. The second type of inheritance is used when inheriting intents from an implementation (e.g. introspected Java code, or an implementation composite). In this case the intents of the implementation cannot be overridden. Consider this example: component name=D1 implementation.composite name=CZ1/ reference name=r1 requires=suspendsTransaction/ /component Let's assume CZ1 contains the component C1 shown earlier and that it promotes the component reference C1/r1 as r1. C1/r1 has the intent propagatesTransaction. This intent is considered a requirement of the implementation and it cannot be overridden by the using composite. Therefore D1 is in error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-2239) Support for mutually-exclusive intents
[ https://issues.apache.org/jira/browse/TUSCANY-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Dritschler updated TUSCANY-2239: - Attachment: tuscany-2239.patch Support for mutually-exclusive intents -- Key: TUSCANY-2239 URL: https://issues.apache.org/jira/browse/TUSCANY-2239 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Runtime Reporter: Greg Dritschler Attachments: tuscany-2239.patch The SCA Policy specification does not provide a means to define intents which are mutually exclusive. This is a noticeable omission when considering the intents in the SCA Transaction specification which are mutually exclusive by nature (managedTransaction vs. noManagedTransaction, propagatesTransaction vs. suspendsTransaction). There is a need to be able to define intents which are mutually exclusive and for the exclusion to be checked by the SCA runtime to avoid the error of specifying exclusive intents on a single artifact. In addition, there should be rules defined for the handling of mutually exclusive intents which are attached at different levels of a composite or a hierarchy of composites. I have attached a patch to provide the capability to define mutually exclusive intents. This is achieved using a new @excludes attribute on the intent/ element in definitions.xml. For example: intent name=propagatesTransaction constrains=implementation excludes=suspendsTransaction/ @excludes is a list of intents which are mutually-exclusive with the named intent. In order to be effective, a reciprocal definition needs to be made as shown below. intent name=suspendsTransaction constrains=implementation excludes=propagatesTransaction/ The patch makes no assumptions about the relationship of qualified intents to the base intent. Therefore exclusive relationships between qualified intents need to be spelled out. intent name=noManagedTransaction constrains=implementation excludes=managedTransaction managedTransaction.global managedTransaction.local/ A key part of the patch is that there now are two types of intent inheritance with respect to exclusive intents. There is a default inheritance between certain hierarchical elements within a composite. For example consider this snippet from a composite: component name=C1 requires=propagatesTransaction reference name=r1/ reference name=r2/ reference name=r3 requires=suspendsTransaction/ /component In this case the first two references inherit the default intent propagatesTransaction from the component element. However the third reference does not inherit it because it specifies an exclusive intent suspendsTransaction which overrides the component-level default. The second type of inheritance is used when inheriting intents from an implementation (e.g. introspected Java code, or an implementation composite). In this case the intents of the implementation cannot be overridden. Consider this example: component name=D1 implementation.composite name=CZ1/ reference name=r1 requires=suspendsTransaction/ /component Let's assume CZ1 contains the component C1 shown earlier and that it promotes the component reference C1/r1 as r1. C1/r1 has the intent propagatesTransaction. This intent is considered a requirement of the implementation and it cannot be overridden by the using composite. Therefore D1 is in error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-2238) Test Cases for Exception APIs
[ https://issues.apache.org/jira/browse/TUSCANY-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yee-Kang Chang updated TUSCANY-2238: Attachment: ExceptionJIRA2238.zip Sorry, Kevin! I thought I fixed the problem. Thanks. Test Cases for Exception APIs - Key: TUSCANY-2238 URL: https://issues.apache.org/jira/browse/TUSCANY-2238 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Assignee: Kevin Williams Attachments: ExceptionJIRA2238.patch, ExceptionJIRA2238.zip vtest's test cases for the various Exceptions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 1.2-incubating (RC4)
Luciano Resende wrote:
Please review and vote on the 1.2 release artifacts of Tuscany SCA for Java.
The artifacts are available for review at:
http://people.apache.org/~lresende/tuscany/sca-1.2-RC4/
This includes the signed binary and source distributions, the RAT report,
and the Maven staging repository.
The eclipse updatesite for the Tuscany Eclipse plugins is available at:
http://people.apache.org/~lresende/tuscany/sca-1.2-RC4/updatesite/
The release tag is available at :
http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.2-RC4/
Looks OK to me, here is my +1.
I'm on vacation with extremely limited connectivity so I haven't been
able to give this as thorough a review as I normally would.
I built the source - OK.
I checked that TUSCANY-2220 was fixed - OK.
I tried running some samples - not OK.
Problem 1:
The sample helloworld-service-jms has the build.xml file from
helloworld-ws-service-jms. The test.jar variable is set to
sample-helloworld-ws-service-jms.jar which does not exist in this
sample's target directory. The project name is also incorrectly
listed as helloworld-ws-service-jms (minor issue). I corrected
these two errors in the build.xml file and the sample ran OK.
Problem 2 (minor):
I decided to check all the other sample build.xml files to see if
there were any similar problems. The sample helloworld-reference-jms
has a build.xml file with a project name of helloworld-ws-reference-jms
(minor issue). The test.jar variable is correctly set to
sample-helloworld-reference-jms.jar, so the sample runs OK.
Problem 3:
I found one more build.xml file with a similar problem. This was
implementation-pojo. My best attempts at doing a fix-up similar to
what I did for Problem 1 were not successful. I was able to resolve
the NoClassDefFoundError by editing build.xml, but then I got the
following messages:
F:\tuscany-1.2-rc4\tuscany-sca-1.2-incubating\samples\implementation-pojoant ru
n
Buildfile: build.xml
run:
[java] 17-Apr-2008 04:13:47 org.apache.tuscany.sca.contribution.processor.E
xtensibleStAXArtifactProcessor read
[java] WARNING: Element {http://pojo}implementation.pojo cannot be processe
d. ([row,col {unknown-source}]: [26,9])
[java] 17-Apr-2008 04:13:47 org.apache.tuscany.sca.contribution.processor.E
xtensibleStAXArtifactProcessor read
[java] WARNING: Element {http://pojo}implementation.pojo cannot be processe
d. ([row,col {unknown-source}]: [30,9])
[java] 17-Apr-2008 04:13:47 org.apache.tuscany.sca.assembly.builder.impl.Co
mpositeBuilderImpl$1 problem
[java] WARNING: No implementation for component: HelloWorldComponent
[java] 17-Apr-2008 04:13:47 org.apache.tuscany.sca.assembly.builder.impl.Co
mpositeBuilderImpl$1 problem
[java] WARNING: No implementation for component: HelloWorldComponent2
[java] 17-Apr-2008 04:13:47 org.apache.tuscany.sca.assembly.builder.impl.Co
mpositeBuilderImpl$1 problem
[java] WARNING: No implementation for component: HelloWorldComponent
[java] 17-Apr-2008 04:13:47 org.apache.tuscany.sca.assembly.builder.impl.Co
mpositeBuilderImpl$1 problem
[java] WARNING: No implementation for component: HelloWorldComponent2
[java] Exception in thread main org.osoa.sca.ServiceRuntimeException: No
service is declared on component HelloWorldComponent
[java] at org.apache.tuscany.sca.core.context.ComponentContextHelper.ge
tSingleService(ComponentContextHelper.java:297)
[java] at org.apache.tuscany.sca.core.context.ComponentContextImpl.crea
teSelfReference(ComponentContextImpl.java:157)
[java] at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.ge
tServiceReference(DefaultSCADomain.java:505)
[java] at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.ge
tService(DefaultSCADomain.java:418)
[java] at helloworld.HelloWorldClient.main(HelloWorldClient.java:30)
[java] Java Result: 1
BUILD SUCCESSFUL
Total time: 1 second
The final message says BUILD SUCCESSFUL but the preceding error
messages make me rather doubtful that this is true.
Are others able to recreate Problem 1 and Problem 3 from the rc4
binary distro when running the samples using ant scripts?
Despite these problems, I am willing to give this release a +1.
Problem 1 is easily fixable by the user (maybe this can be
documented somewhere). Problem 3 is more troubling, but if it only
affects implementation.pojo then I would be OK with the release
despite this issue. Any insights would be much appreciated.
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2074) Component Service not coming up.
[ https://issues.apache.org/jira/browse/TUSCANY-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589825#action_12589825 ] Sandeep Raman commented on TUSCANY-2074: I tried downloading another patch : 6.1.0.3-WS-WAS-IFPK33090 From the address: ftp://ftp.software.ibm.com/software/websphere/appserv/support/fixes/PK33090/6.1.0.3-WS-WAS-IFPK33090.pak But i Couldnt get this problem solved. I am using IBM websphere Express Version. 6.1.0.3. Any other suggestions? ..Sandeep Component Service not coming up. Key: TUSCANY-2074 URL: https://issues.apache.org/jira/browse/TUSCANY-2074 Project: Tuscany Issue Type: Test Components: Java SCA Tomcat Integration Affects Versions: Java-SCA-1.1 Environment: Windows , Tomcat 5.5 , Apache tuscany 1.1 , Java 5.0 Reporter: Sandeep Raman Priority: Critical Fix For: Java-SCA-Next Attachments: src.zip, two-ws-reference.jar, TwoWS.war Original Estimate: 72h Remaining Estimate: 72h summary of the Issue: I have an issue with the component service not coming up. below mentioned is my scenario. I have a JSP (default.jsp) which does the following: %@ page import=org.apache.tuscany.sca.host.embedded.SCADomain% %@ page contentType=text/html;charset=UTF-8 language=java % % SCADomain scaDomain = SCADomain.newInstance(RunTime.composite); System.out.println(RunTime Composite Started); % and the Runtime.composite is as follows: component name=TwoWSService implementation.java class=eai.Compose / service name=Compose interface=http://eai#wsdl.interface(TwoWSService) / binding.ws uri=http://localhost:8080/TwoWSService; / /service /component Now I create a war of all my Java classes , wsdl , composite files and with the default.jsp as the default run target. This war gets deployed in tomcat and the jsp page comes up. It creates a new instance of Runtime.composite too , but it doesnt seem to be starting the component service which i have mentioned in the composite file : binding.ws uri=http://localhost:8080/TwoWSService; /. -- Following Mails explain the scenario:: I see everything in console, like INFO: initContextPath: /TwoWS INFO: Added Servlet mapping: /TwoWSService Even if i try to Run my low lying services which i am composing it Runs fine and can see the output in the console.. The issue is the wsdl url which i need to publish and not able to find it anywhere. As per the samples , in my case http://localhost:8080/TwoWS/TwoWSService?wsdl should point to my wsdl, but tht doesnt seem to exist Regards Sandeep ant elder [EMAIL PROTECTED] wrote on 03/11/2008 05:03:44 PM: A difference between this and the calculator sample is the way the jsp gets the SCADomain object, the Tuscany jsp samples do: % SCADomain scaDomain = (SCADomain) application.getAttribute( org.apache.tuscany.sca.SCADomain); CalculatorService calculatorService = (CalculatorService)scaDomain.getService(CalculatorService.class, CalculatorServiceComponent); % whereas this code does: % SCADomain scaDomain = SCADomain.newInstance(RunTime.composite); System.out.println(RunTime Composite Started); % I've never tried that so i don't know if it will work. If Tuscany is activating the WS endpoint you should see the messages on the tomcat console about it, for example, with the calculator ws sample you see: INFO: ContextPath: /sample-calculator-ws-webapp and INFO: Added Servlet mapping: /AddServiceComponent so you can add those and you tomcat host and port to get http://localhost:8080//sample-calculator-ws-webapp/AddServiceComponent You can test thats working by appending ?wsdl to that and url and entering it in a browser which should return the wsdl document for the service. If you don't see the above messages then something is going wrong and the WS endpoint is not being registered correctly. ...ant On Tue, Mar 11, 2008 at 11:07 AM, Sandeep Raman [EMAIL PROTECTED] wrote: Hi, I have done pretty much in the same way as the sample. i need to see my wsdl , my component service which is running . I am not able to figure out the URL for the wsdl file. I am stuck up there, since all my external requests need this wsdl URL to process, any help or suggestion will be highly appreciated Regards Sandeep Raman ant elder [EMAIL PROTECTED] wrote on 03/11/2008 02:28:13 PM: On Tue, Mar 11, 2008 at 3:38 AM,
Re: [NOTICE] Wang Feng voted as Tuscany committer
Many congratulations and welcome on board! Simon Wang Feng wrote: Thanks everyone for the congratulations and welcome and I'm looking forward to the next exciting stage of the Tuscany community. Thanks, Wang Feng On 2008-04-16 16:55:10,ant elder [EMAIL PROTECTED] wrote: The Tuscany PPMC and Incubator PMC have voted for Wang Feng to become a Tuscany committer. Congratulations and welcome Wang Feng! ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-2239) Support for mutually-exclusive intents
[ https://issues.apache.org/jira/browse/TUSCANY-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkatakrishnan reassigned TUSCANY-2239: Assignee: Venkatakrishnan Support for mutually-exclusive intents -- Key: TUSCANY-2239 URL: https://issues.apache.org/jira/browse/TUSCANY-2239 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Runtime Reporter: Greg Dritschler Assignee: Venkatakrishnan Attachments: tuscany-2239.patch The SCA Policy specification does not provide a means to define intents which are mutually exclusive. This is a noticeable omission when considering the intents in the SCA Transaction specification which are mutually exclusive by nature (managedTransaction vs. noManagedTransaction, propagatesTransaction vs. suspendsTransaction). There is a need to be able to define intents which are mutually exclusive and for the exclusion to be checked by the SCA runtime to avoid the error of specifying exclusive intents on a single artifact. In addition, there should be rules defined for the handling of mutually exclusive intents which are attached at different levels of a composite or a hierarchy of composites. I have attached a patch to provide the capability to define mutually exclusive intents. This is achieved using a new @excludes attribute on the intent/ element in definitions.xml. For example: intent name=propagatesTransaction constrains=implementation excludes=suspendsTransaction/ @excludes is a list of intents which are mutually-exclusive with the named intent. In order to be effective, a reciprocal definition needs to be made as shown below. intent name=suspendsTransaction constrains=implementation excludes=propagatesTransaction/ The patch makes no assumptions about the relationship of qualified intents to the base intent. Therefore exclusive relationships between qualified intents need to be spelled out. intent name=noManagedTransaction constrains=implementation excludes=managedTransaction managedTransaction.global managedTransaction.local/ A key part of the patch is that there now are two types of intent inheritance with respect to exclusive intents. There is a default inheritance between certain hierarchical elements within a composite. For example consider this snippet from a composite: component name=C1 requires=propagatesTransaction reference name=r1/ reference name=r2/ reference name=r3 requires=suspendsTransaction/ /component In this case the first two references inherit the default intent propagatesTransaction from the component element. However the third reference does not inherit it because it specifies an exclusive intent suspendsTransaction which overrides the component-level default. The second type of inheritance is used when inheriting intents from an implementation (e.g. introspected Java code, or an implementation composite). In this case the intents of the implementation cannot be overridden. Consider this example: component name=D1 implementation.composite name=CZ1/ reference name=r1 requires=suspendsTransaction/ /component Let's assume CZ1 contains the component C1 shown earlier and that it promotes the component reference C1/r1 as r1. C1/r1 has the intent propagatesTransaction. This intent is considered a requirement of the implementation and it cannot be overridden by the using composite. Therefore D1 is in error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
