Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.
The following page has been changed by Deepal: http://wiki.apache.org/ws/FrontPage/Axis2/hackathon_14_06 New page: [08:52] The topic is 'Axis2 -Hackathon @ IU' (set by Deepal) [08:52] [freenode-info] please register your nickname...don't forget to auto-identify! http://freenode.net/faq.shtml#nicksetup: #apache-axis [08:53] gdaniels has joined [09:15] Deepal: what is the plan today [09:15] Deepal: going through the JIRAs ? [09:17] gdaniels: we should talk about the list Srinath mailed out [09:17] gdaniels: also go through the fault scenarios like we discussed yesterday [09:17] gdaniels: maybe we should start with that after 20-45 min of emailing/JIRA wrangling [09:18] Deepal: ok [09:21] chathura has joined [09:26] jaliya has joined [09:32] srinathp has joined [09:43] srinathp: BTW I am updating Class level comments for MessageContext ect [09:43] Deepal: great [10:10] azeez has joined [10:13] Deepal: we are discussing fault handling [10:13] Deepal: 5 different places [10:14] Deepal: client out ptha, client in path , server in path , server out path [10:14] Deepal: the service [10:14] Deepal: and see whether the client get the right thing [10:20] chathura: Nice [10:20] azeez: glen regarding the ServiceLifecycle mail... [10:21] azeez: is performance the main issue with the current approach? [10:22] azeez: on the nabble.com thread, the user seems to be complaining of a debug level message (NoSuchMethod) [10:23] azeez: that doesn't seem to be a problem.... [10:23] azeez: I don't think that AXIS2-2785 is a blocker [10:23] azeez has disconnected: "Leaving" [10:24] azeez has joined [10:25] azeez: glen regarding ur mail about init & destroy methods in ServiceLifecycle [10:25] azeez: the user seems to be concerned only about a debug level NoSuchMethodError message [10:26] azeez: I don't think AXIS2-2785 is a blocker [10:51] saminda has joined [10:51] saminda: Hi All [10:52] saminda: JIRAS 2316 & 2214 and mail on Client side Proxy configuration ; what would you think [10:54] dblevins has joined [10:55] jaliya: discussing fault handling, based on operation, transport, wsa:ReplyTo, wsa:FaultTo [11:08] Chinthaka has joined [11:09] srinathp: saminda onece we are done ... we will get back to you [11:12] saminda: thank you [11:12] srinathp: to where did you sent "mail on Client side Proxy configuration"? [11:13] srinathp: axis2 dev list? [11:14] gdaniels: currently looking at OutInAxisOperation.createFaultMessageContext() and being confused as to what it's doing [11:25] jaliya has disconnected: Read error: 110 (Connection timed out) [11:36] jgawor has joined [11:38] jaliya has joined [11:40] jgawor: hey, folks. is the following test org.apache.axis2.faults.FaultSerializationTest failing you? [11:48] azeez has disconnected: Read error: 113 (No route to host) [11:48] azeez_ has joined [11:52] saminda: axis-dev list [12:00] srinathp: jgawor you must have most uptodate OM [12:00] srinathp: most = must [12:01] srinathp: delete OM jars and rebuild to make sure [12:02] davidillsley has disconnected: Read error: 104 (Connection reset by peer) [12:06] jaliya has disconnected: Read error: 110 (Connection timed out) [12:07] azeez_ has disconnected: "Leaving" [12:11] azeez has joined [12:12] jaliya_ has joined [12:18] jgawor: srinathp: ok, thanks [12:26] azeez has disconnected: "Leaving" [12:46] Chinthaka: http://www.thetrojanhorse.com/CarryOutMenu.pdf [12:47] jaliya__ has joined [12:56] jaliya_ has disconnected: Read error: 110 (Connection timed out) [13:12] jaliya__ has disconnected: Read error: 110 (Connection timed out) [13:45] saminda has disconnected: "Ex-Chat" [13:48] saminda has joined [13:51] saminda: Hi [13:51] saminda: Testsuite: org.apache.axis2.faults.FaultSerializationTest [13:51] saminda: Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 0.759 sec [13:51] saminda: a test faliour in rev: Revision: 547333 [13:51] saminda: due to [13:51] saminda: Testcase: testFaultReason(org.apache.axis2.faults.FaultSerializationTest): FAILED [13:51] saminda: expected:<[myFaultReason]> but was:<[]> [13:51] saminda: junit.framework.ComparisonFailure: expected:<[myFaultReason]> but was:<[]> [13:51] saminda: at org.apache.axis2.faults.FaultSerializationTest.testFaultReason(FaultSerializationTest.java:98) [13:51] saminda: at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [13:51] saminda: at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. saminda: do you guys seen it too [14:19] srinathp: update your OM [14:19] Chinthaka has disconnected: Read error: 104 (Connection reset by peer) [14:19] srinathp: it only work with uptodate [14:20] srinathp: OM [14:20] saminda: I've updated it [14:20] saminda: I've fixed the proxy related Jiras but couldn't commit due to this test faliour [14:27] srinathp: :) great [14:27] srinathp: delete your OM jars and retyr [14:27] srinathp: that should fix fault serialization bug --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
