[GitHub] [ws-wss4j] coheigea merged pull request #67: Fix Build Status Icon in README.md

2022-12-22 Thread GitBox
coheigea merged PR #67: URL: https://github.com/apache/ws-wss4j/pull/67 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org

[GitHub] [ws-wss4j] free2create opened a new pull request, #67: Fix Build Status Icon in README.md

2022-11-14 Thread GitBox
free2create opened a new pull request, #67: URL: https://github.com/apache/ws-wss4j/pull/67 This fixes URL so build badge for master JDK11 is shown correctly. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

Fwd: Delivery Status Notification (Failure)

2014-09-11 Thread Gary Gregory
+1 (non-binding) to drop Java 5 (even drop 6 if you like). Gary On Thu, Sep 11, 2014 at 8:16 AM, Alexandr Klimov my-...@yandex.ru wrote: +1 09.09.2014, 12:04, Colm O hEigeartaigh cohei...@apache.org: +1 makes sense. Colm. On Mon, Sep 8, 2014 at 9:22 PM, Daniel Kulp

Re: [XmlSchema 2.0] Project Status?

2014-07-10 Thread Michael Pigott
Hi, I'm happy to take on an active role in the project if no one else is - I'm currently trying to automatically generate an XML parser based on the XBRL schema http://www.xbrl.org/2003/xbrl-linkbase-2003-12-31.xsd. I've tried XMLBeans and I've tried JAXP, but so far only XmlSchema has been

[XmlSchema 2.0] Project Status?

2014-07-09 Thread Michael Pigott
Hello Apache Web Services Developers, Last week I filed and provided a fix for https://issues.apache.org/jira/browse/XMLSCHEMA-33 (uploading the diff.zip yesterday). However, I haven't seen much traction on the JIRA ticket, and I am not sure who to reach out to. No lead developer is

[jira] [Closed] (WSS-341) the FIRST step check in SignatureTrustValidator.verifyTrustInCert ignore the enableRevocation status

2012-03-05 Thread Colm O hEigeartaigh (Closed) (JIRA)
the enableRevocation status -- Key: WSS-341 URL: https://issues.apache.org/jira/browse/WSS-341 Project: WSS4J Issue Type: Bug Affects Versions: 1.6.4

[jira] [Updated] (WSS-341) the FIRST step check in SignatureTrustValidator.verifyTrustInCert ignore the enableRevocation status

2012-02-17 Thread Colm O hEigeartaigh (Updated) (JIRA)
in SignatureTrustValidator.verifyTrustInCert ignore the enableRevocation status -- Key: WSS-341 URL: https://issues.apache.org/jira/browse/WSS-341 Project: WSS4J

[jira] [Updated] (WSS-341) the FIRST step check in SignatureTrustValidator.verifyTrustInCert ignore the enableRevocation status

2012-02-16 Thread Freeman Fang (Updated) (JIRA)
enableRevocation first before we check isCertificateInKeyStore(crypto, cert) the FIRST step check in SignatureTrustValidator.verifyTrustInCert ignore the enableRevocation status -- Key

[jira] [Updated] (WSS-341) the FIRST step check in SignatureTrustValidator.verifyTrustInCert ignore the enableRevocation status

2012-02-16 Thread Freeman Fang (Updated) (JIRA)
the enableRevocation status -- Key: WSS-341 URL: https://issues.apache.org/jira/browse/WSS-341 Project: WSS4J Issue Type: Bug

Status

2011-07-25 Thread Gregory_Bonk
I had some questions on using XML schema, but it seems that the project is dormant. I was wondering how to leverage XML Schema and a catalog file to tie together Springs auto WSDL generation and referencing imports with the XJC catalog mechanism. Thanks, Gregory Bonk Abercrombie Fitch

Status of 1.6 branch.....

2010-07-20 Thread Daniel Kulp
Colm, I asw just wondering what that status of the 1.6 branch is? Aka: how close to releasable is it? We're getting pretty close to CXF 2.3 and am trying to figure out if moving up to 1.6 will be a possibility or if we need to stay on 1.5.x. Let me know if there is anything that I can do

[jira] Resolved: (WSCOMMONS-417) Clarify the status of the JavaMail dependency

2010-05-14 Thread Andreas Veithen (JIRA)
with the Geronimo JARs. Therefore I'm going to close this issue. Note that Axis2 still overrides the dependency to use Sun's implementations. Clarify the status of the JavaMail dependency - Key: WSCOMMONS-417 URL: https

[jira] Resolved: (AXIS2C-1282) 1)reads all http headers from the request and adds them to the msg_ctx, they were missing. 2)Allows custumized http status and http headers for rest requests(don't affec

2009-12-18 Thread Nandika Jayawardana (JIRA)
and adds them to the msg_ctx, they were missing. 2)Allows custumized http status and http headers for rest requests(don't affect soap requests). 3) Adds missing http forbidden definitions

Transports 1.0.0 release status

2009-12-18 Thread Ruwan Linton
Folks, Tag has been created, and the artifacts are uploaded to the maven2 repository. I am having a bit of trouble on adding my public key into the KEYS file at [1], It says Permission denied :-( Any help will be much appreciated. [1] -

Transports 1.0.0 release status

2009-12-18 Thread Ruwan Linton
Folks, Tag has been created, and the artifacts are uploaded to the maven2 repository. I am having a bit of trouble on adding my public key into the KEYS file at [1], It says Permission denied :-( Any help will be much appreciated. [1] -

[jira] Updated: (AXIS2C-1402) AXIS2_PARAM_CHECK overwrite previously set error status

2009-12-08 Thread S.Uthaiyashankar (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2C-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar updated AXIS2C-1402: - Component/s: core/engine AXIS2_PARAM_CHECK overwrite previously set error status

[jira] Updated: (AXIS2C-1409) The AXIS2_PARAM_CHECK macro reset the env status when the param is OK

2009-12-08 Thread S.Uthaiyashankar (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2C-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar updated AXIS2C-1409: - Component/s: core/engine The AXIS2_PARAM_CHECK macro reset the env status when

[jira] Resolved: (AXIS2C-1409) The AXIS2_PARAM_CHECK macro reset the env status when the param is OK

2009-12-08 Thread S.Uthaiyashankar (JIRA)
the env status when the param is OK - Key: AXIS2C-1409 URL: https://issues.apache.org/jira/browse/AXIS2C-1409 Project: Axis2-C Issue Type: Bug Components: core

[jira] Assigned: (AXIS2C-1409) The AXIS2_PARAM_CHECK macro reset the env status when the param is OK

2009-12-08 Thread S.Uthaiyashankar (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2C-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar reassigned AXIS2C-1409: Assignee: S.Uthaiyashankar The AXIS2_PARAM_CHECK macro reset the env status when

[jira] Commented: (AXIS2C-1402) AXIS2_PARAM_CHECK overwrite previously set error status

2009-10-23 Thread Francois Mireaux (JIRA)
look in Axis2c tests but : - there are not many tests - they are not automated like with JUnit in Java - often, test says SUCCESS with env status to FAILURE - So It's seems we need a test framework which allows us to write more tests more easily. Which framework choose

[jira] Updated: (AXIS2C-1402) AXIS2_PARAM_CHECK overwrite previously set error status

2009-10-22 Thread Francois Mireaux (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2C-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francois Mireaux updated AXIS2C-1402: - Attachment: axis2_param_check.patch Content : 1 initialize env status

[jira] Created: (AXIS2C-1407) Loading an XML file always sets the env status to AXIS2FAILURE

2009-10-21 Thread Francois Mireaux (JIRA)
Loading an XML file always sets the env status to AXIS2FAILURE -- Key: AXIS2C-1407 URL: https://issues.apache.org/jira/browse/AXIS2C-1407 Project: Axis2-C Issue Type: Bug

[jira] Created: (AXIS2C-1408) axis2_dep_engine_load_client exits with the env status to AXIS2FAILURE

2009-10-21 Thread Francois Mireaux (JIRA)
axis2_dep_engine_load_client exits with the env status to AXIS2FAILURE --- Key: AXIS2C-1408 URL: https://issues.apache.org/jira/browse/AXIS2C-1408 Project: Axis2-C Issue

[jira] Created: (AXIS2C-1409) The AXIS2_PARAM_CHECK macro reset the env status when the param is OK

2009-10-21 Thread Francois Mireaux (JIRA)
The AXIS2_PARAM_CHECK macro reset the env status when the param is OK - Key: AXIS2C-1409 URL: https://issues.apache.org/jira/browse/AXIS2C-1409 Project: Axis2-C Issue Type

[jira] Commented: (AXIS2C-1409) The AXIS2_PARAM_CHECK macro reset the env status when the param is OK

2009-10-21 Thread Francois Mireaux (JIRA)
-1402. But is somebody works on the topic ? (I could carry on tracking problems with a correct AXIS2_PARAM_CHECK macro) The AXIS2_PARAM_CHECK macro reset the env status when the param is OK - Key: AXIS2C-1409

[jira] Commented: (AXIS2C-1409) The AXIS2_PARAM_CHECK macro reset the env status when the param is OK

2009-10-21 Thread S.Uthaiyashankar (JIRA)
, it will help us a lot. Please provide patch if you find the solutions to the problem. The AXIS2_PARAM_CHECK macro reset the env status when the param is OK - Key: AXIS2C-1409 URL: https

[jira] Commented: (AXIS2C-1409) The AXIS2_PARAM_CHECK macro reset the env status when the param is OK

2009-10-21 Thread S.Uthaiyashankar (JIRA)
. Ideally, we should not set status if param is OK. However, when that is removed, there are some functionality broken. I'll fix them and then remove setting the status. The AXIS2_PARAM_CHECK macro reset the env status when the param is OK

[jira] Reopened: (AXIS2C-1402) AXIS2_PARAM_CHECK overwrite previously set error status

2009-10-19 Thread S.Uthaiyashankar (JIRA)
the functionalities are fixed. AXIS2_PARAM_CHECK overwrite previously set error status --- Key: AXIS2C-1402 URL: https://issues.apache.org/jira/browse/AXIS2C-1402 Project: Axis2-C Issue Type: Bug

[jira] Created: (AXIS2C-1402) AXIS2_PARAM_CHECK overwrite previously set error status

2009-10-14 Thread S.Uthaiyashankar (JIRA)
AXIS2_PARAM_CHECK overwrite previously set error status --- Key: AXIS2C-1402 URL: https://issues.apache.org/jira/browse/AXIS2C-1402 Project: Axis2-C Issue Type: Bug Affects Versions

[jira] Resolved: (AXIS2C-1402) AXIS2_PARAM_CHECK overwrite previously set error status

2009-10-14 Thread S.Uthaiyashankar (JIRA)
set error status --- Key: AXIS2C-1402 URL: https://issues.apache.org/jira/browse/AXIS2C-1402 Project: Axis2-C Issue Type: Bug Affects Versions: 1.6.0 Reporter

Re: [axis2] Status on Axis2 1.5.1 and Rampart 1.5

2009-10-13 Thread Ruwan Linton
+1 for re-spining the votes. Thanks, Ruwan On Tue, Oct 13, 2009 at 5:24 AM, Nandana Mihindukulasooriya nandana@gmail.com wrote: Hi Glen Nandana/all, can you check what I did in Rampart and let me know if you foresee any problems with it? I'm going to respin Axis2 1.5.1 with this and

Re: [axis2] Status on Axis2 1.5.1 and Rampart 1.5

2009-10-13 Thread Andreas Veithen
On Mon, Oct 12, 2009 at 16:08, Glen Daniels g...@thoughtcraft.com wrote: Hi folks! OK, so here are the results of my weekend investigations.  The lockup when running the Rampart 1.5 tests with Axis2 1.5.1 was due to http connection starvation.  I've fixed two issues and everything works now,

Re: Transport-1.0 release status

2009-10-13 Thread Ruwan Linton
We are ready from the JIRA PoV to go for the release, I need to figure out the site and various other things together with a few code formatting. Once I am done with that will publish the RC. Thanks, Ruwan On Sun, Oct 11, 2009 at 10:04 PM, Ruwan Linton ruwan.lin...@gmail.comwrote: Folks, We

[axis2] Status on Axis2 1.5.1 and Rampart 1.5

2009-10-12 Thread Glen Daniels
Hi folks! OK, so here are the results of my weekend investigations. The lockup when running the Rampart 1.5 tests with Axis2 1.5.1 was due to http connection starvation. I've fixed two issues and everything works now, but I'd like to respin both Axis2 1.5.1 and Rampart 1.5 as a result. Details

Re: [axis2] Status on Axis2 1.5.1 and Rampart 1.5

2009-10-12 Thread Nandana Mihindukulasooriya
Hi Glen Nandana/all, can you check what I did in Rampart and let me know if you foresee any problems with it? I'm going to respin Axis2 1.5.1 with this and one other fix, and we should respin Rampart 1.5 as well. +1 for re-spining both Axis2 1.5.1 and Rampart 1.5. I checked the change in

[axis2] Status on Axis2 1.5.1 and Rampart 1.5

2009-10-12 Thread Glen Daniels
Hi folks! OK, so here are the results of my weekend investigations. The lockup when running the Rampart 1.5 tests with Axis2 1.5.1 was due to http connection starvation. I've fixed two issues and everything works now, but I'd like to respin both Axis2 1.5.1 and Rampart 1.5 as a result. Details

Transport-1.0 release status

2009-10-11 Thread Ruwan Linton
Folks, We have only 2 more issues to be fixed for the 1.0 release of the axis2 transports [1]. As soon as those issues are fixed I will pack an RC to test with synapse and axis2 1.5 and we will be able to get the release soon. [1] -

[jira] Commented: (WSCOMMONS-417) Clarify the status of the JavaMail dependency

2009-10-03 Thread Andreas Veithen (JIRA)
in the context of CXF, Daniel Kulp gave some additional arguments in support of the Geronimo implementations. See [1]. [1] http://markmail.org/message/xanxtu2s4ukjhn3k Clarify the status of the JavaMail dependency - Key: WSCOMMONS-417

Re: SMS transport status?

2009-09-22 Thread Charith Wickramarachchi
: Hi Charith, What is the status of the SMS transport? Can we include that in the transports 1.0 release that we are planning to do? Thanks, Ruwan -- Ruwan Linton Technical Lead Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 http://wso2.org/esb%0AWSO2 Inc.; http://wso2.org email

Re: SMS transport status?

2009-09-22 Thread Ruwan Linton
that will be useful with the SMPP implementation. Which i'll add in this week. thanks, Charith On Tue, Sep 22, 2009 at 10:32 AM, Ruwan Linton ruwan.lin...@gmail.com wrote: Hi Charith, What is the status of the SMS transport? Can we include that in the transports 1.0 release that we

Re: SMS transport status?

2009-09-21 Thread Ruwan Linton
Also, I assume that the udp and tcp transports are in good shape to go for the 1.0 release?? Am I correct Andreas? Thanks, Ruwan On Tue, Sep 22, 2009 at 10:32 AM, Ruwan Linton ruwan.lin...@gmail.comwrote: Hi Charith, What is the status of the SMS transport? Can we include

Re: [VOTE] [axis2] Release Axis2 1.5.1 (status)

2009-08-18 Thread Andreas Veithen
Glen, Dobri made some comments about the changes in the HTTP transport and I think we should take them into account. That is why I didn't vote yet. Andreas On Mon, Aug 17, 2009 at 16:48, Glen Danielsg...@thoughtcraft.com wrote: :-) So regarding this release - we don't seem to have many +1's

Re: [VOTE] [axis2] Release Axis2 1.5.1 (status)

2009-08-17 Thread Glen Daniels
:-) So regarding this release - we don't seem to have many +1's yet. As such, my plan is to rejigger it as Dennis suggests and re-publish this content (with only minor tweaks) as 1.5RC later today. Hopefully we can get that out to the world ASAP while trying to quickly resolve the

Re: jUDDI status meeting tomorrow Friday 14

2009-08-14 Thread Jeremi Thebeau
Works for me. Jeremi Kurt T Stam wrote: Hi guys, Let's meet up on IRC tomorrow 9am Chicago time/10 am Boston time / 4 pm Germany time (Jeremy does that work for you?). irc.freenode.net #juddi. Suggested Agenda: * Quick go around to see what everyone has been up to. * Check Jira to see

MEETING NOTES: jUDDI status meeting tomorrow Friday 14

2009-08-14 Thread Kurt T Stam
KurtStam: k let's do a quick go around then; I think Jeremi last since I think we'll talk about the testing the longest [10:02am] KurtStam: who wants to go first? [10:03am] tcunning: i can go first [10:03am] tcunning: right now i'm working on getting scout working with juddi v3 [10:03am]

Re: Status of ADB SOAP encoding and helper mode

2009-07-20 Thread Andreas Veithen
On Tue, Jun 30, 2009 at 07:05, Amila Suriarachchiamilasuriarach...@gmail.com wrote: On Sat, Jun 27, 2009 at 1:15 AM, Andreas Veithen andreas.veit...@gmail.com wrote: Hi devs, I would like to have more information about the status of two components of adb(-codegen): 1) SOAP encoding

Re: Status of ADB SOAP encoding and helper mode

2009-07-20 Thread Amila Suriarachchi
more information about the status of two components of adb(-codegen): 1) SOAP encoding support for ADB (see [1]). Last status that I see is that it is incomplete [2] or unsupported [3]. Can somebody clarify this? Note that the code that implements this is largely based on generated code

Re: how to get the http status code

2009-07-16 Thread Gordon Brown
Sorry, I replied to the wrong message, so try it again. Yes, I did some debugging, but this seems to be a bug in axis2/c library. Or maybe I need to do something like call some APIs so that the status will be set and so users can get the status? My question is this, does a user need

how to get the http status code

2009-07-15 Thread Vivian Wang
Hi There, I am using axis2/c to make web service client call, like this:   axiom_node_t * node = axis2_svc_client_send_receive(_wsf_service_client, _env, payload); After this, I am trying to use the following API to get the http status code,   AXIS2_EXTERN int AXIS2_CALL

Re: how to get the http status code

2009-07-15 Thread Rajika Kumarasiri
); After this, I am trying to use the following API to get the http status code, AXIS2_EXTERN int AXIS2_CALL axis2_svc_client_get_http_status_code(axis2_svc_client_t * svc_client, const axutil_env_t * env); I am expecting 408 for time out, 200 for success. However, I am always getting 0

Re: [Axis2] Transports status?

2009-07-11 Thread Andreas Veithen
...@sosnoski.com wrote: What's the status of the transports code compatible with Axis 1.5? Thanks,  - Dennis -- Dennis M. Sosnoski Java XML and Web Services Axis2 Training and Consulting http://www.sosnoski.com - http://www.sosnoski.co.nz Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298

Re: [Axis2] Transports status?

2009-07-11 Thread Dennis Sosnoski
for the project and make sure there is a minimum of documentation. - Fix some of the remaining open bugs. Andreas On Sat, Jul 11, 2009 at 02:08, Dennis Sosnoskid...@sosnoski.com wrote: What's the status of the transports code compatible with Axis 1.5? Thanks, - Dennis -- Dennis M. Sosnoski

Re: Status of ADB SOAP encoding and helper mode

2009-06-29 Thread Amila Suriarachchi
On Sat, Jun 27, 2009 at 1:15 AM, Andreas Veithen andreas.veit...@gmail.comwrote: Hi devs, I would like to have more information about the status of two components of adb(-codegen): 1) SOAP encoding support for ADB (see [1]). Last status that I see is that it is incomplete [2

Status meeting June 10 2009

2009-06-10 Thread Kurt T Stam
KurtStam: so beta is out [12:45pm] jfaath: yes [12:45pm] KurtStam: and we're getting some downloads and questions [12:45pm] KurtStam: which is good [12:46pm] tcunning: did it work in jboss? [12:46pm] KurtStam: hopefully we can learn from the issues [12:46pm] KurtStam: I got side tracked, but will

1.5 release status

2009-05-29 Thread Glen Daniels
Hi folks. Just FYI - I haven't officially announced the 1.5 release yet because I'm doing a few changes to the site (and hopefully the process around the site as well). The artifacts are in Maven already, however, and the dist is where you'd expect. :) I'll do the actual announcement tonight or

status meeting May 28, 2009

2009-05-28 Thread Kurt T Stam
KurtStam: so it looks like our beta3 list is nice and clean. [11:12am] KurtStam: I know Tom is still working on an end2end test for subscriptions [11:12am] KurtStam: Tom want to jump in? [11:12am] tcunning: sure [11:13am] tcunning: i'm just finishing up a test which sets subscriptions, changes

Re: [jira] Commented: (WSCOMMONS-417) Clarify the status of the JavaMail dependency

2009-04-13 Thread Asankha C. Perera
Andreas Do you know if its safe to exclude Geronimo JARs from Axiom-api .. its becoming a transitive dependency? thanks asankha

Re: JUDDI-206 status

2009-04-01 Thread Tom Cunningham
base a few days from now. -JF -Original Message- From: Tom Cunningham [mailto:tcunn...@redhat.com] Sent: Wednesday, March 25, 2009 1:00 AM To: juddi-dev@ws.apache.org Subject: Re: JUDDI-206 status I'm stuck on trying to run API_080_SubscriberSaveTest within eclipse. I'm getting

[jira] Commented: (WSCOMMONS-417) Clarify the status of the JavaMail dependency

2009-03-26 Thread Asankha C. Perera (JIRA)
Javamail v1.4.2 (which is the latest as of now and available on M2 Repos), and exclude the use of geronimo JARs altogether for the Commons Transports 1.0 release [1] http://forums.sun.com/thread.jspa?messageID=10657165 Clarify the status of the JavaMail dependency

RE: JUDDI-206 status

2009-03-25 Thread Jeff Faath
on it and we can touch base a few days from now. -JF -Original Message- From: Tom Cunningham [mailto:tcunn...@redhat.com] Sent: Wednesday, March 25, 2009 1:00 AM To: juddi-dev@ws.apache.org Subject: Re: JUDDI-206 status I'm stuck on trying to run API_080_SubscriberSaveTest within eclipse

JUDDI-206 status

2009-03-24 Thread Jeff Faath
Tom, Curious as to where you're at with saving subscriptions. I'm looking into the subscription results portion and I can only go so far without having saved subscriptions to work with. If you don't think you can get it done within a week, let me know. I may have to just get it done. Thanks,

status meeting March 18, 2009

2009-03-18 Thread Kurt T Stam
]Troy joined the chat room. [2:00pm] KurtStam_: it is a screenshot of a the UDDI Browser Portlet Proof of Concept [2:01pm] [1]Troy is now known as TroyHaaland. [2:01pm] tcunning: is it the one you sent around? [2:01pm] KurtStam_: anyway, want to go around for status update? [2:01pm] jfaath: cool

Re: status meeting this wed?

2009-03-17 Thread Kurt T Stam
...@gmail.com] Sent: Monday, March 16, 2009 10:19 AM To: juddi-dev@ws.apache.org Subject: status meeting this wed? Hey guys, Want to do a status meeting this Wednesday March 18? Does 11 am EST work for everyone? --Kurt

status meeting this wed?

2009-03-16 Thread Kurt T Stam
Hey guys, Want to do a status meeting this Wednesday March 18? Does 11 am EST work for everyone? --Kurt

status update on jUDDI tomorrow wed 2/11 - 11 am

2009-02-10 Thread Kurt T Stam
irc.freenode.org #juddi See you there! --Kurt

Status report on XmlSchema 2.0

2009-01-08 Thread Benson Margulies
So far, I've accomplished the following: 1) Consistent property names. 'name' is now always a name relative to the containing schema. 'QName' is now always the name relative to the schema collection: {tns}name. 'wiredName' is the name for use on the wire, as influenced by 'form' and 'ref'. 2)

[jira] Assigned: (AXIS2C-1282) 1)reads all http headers from the request and adds them to the msg_ctx, they were missing. 2)Allows custumized http status and http headers for rest requests(don't affec

2009-01-07 Thread Nandika Jayawardana (JIRA)
and adds them to the msg_ctx, they were missing. 2)Allows custumized http status and http headers for rest requests(don't affect soap requests). 3) Adds missing http forbidden definitions

[jira] Updated: (AXIS2C-1282) 1)reads all http headers from the request and adds them to the msg_ctx, they were missing. 2)Allows custumized http status and http headers for rest requests(don't affect

2008-12-19 Thread Manjula Peiris (JIRA)
the request and adds them to the msg_ctx, they were missing. 2)Allows custumized http status and http headers for rest requests(don't affect soap requests). 3) Adds missing http forbidden definitions

[jira] Created: (WSCOMMONS-417) Clarify the status of the JavaMail dependency

2008-12-18 Thread Andreas Veithen (JIRA)
Clarify the status of the JavaMail dependency - Key: WSCOMMONS-417 URL: https://issues.apache.org/jira/browse/WSCOMMONS-417 Project: WS-Commons Issue Type: Improvement Components: AXIOM

[jira] Commented: (WSCOMMONS-417) Clarify the status of the JavaMail dependency

2008-12-18 Thread Thilina Gunarathne (JIRA)
the activation, where they did not support some content-type bindings. +1 for switching completely to Sun mail+activation... Clarify the status of the JavaMail dependency - Key: WSCOMMONS-417 URL: https://issues.apache.org/jira

[jira] Commented: (WSCOMMONS-417) Clarify the status of the JavaMail dependency

2008-12-18 Thread Jarek Gawor (JIRA)
be good to use Geronimo jars over Sun. The Geronimo JavaMail implementation is much better now and we are pretty good about fixing bugs in it. Clarify the status of the JavaMail dependency - Key: WSCOMMONS-417 URL

[jira] Commented: (WSCOMMONS-417) Clarify the status of the JavaMail dependency

2008-12-18 Thread Andreas Veithen (JIRA)
a bit so that they get solved? Clarify the status of the JavaMail dependency - Key: WSCOMMONS-417 URL: https://issues.apache.org/jira/browse/WSCOMMONS-417 Project: WS-Commons Issue Type

[jira] Created: (AXIS2-4146) HTTP status code 400 is changed to 500

2008-11-24 Thread Markus Bussemer (JIRA)
HTTP status code 400 is changed to 500 -- Key: AXIS2-4146 URL: https://issues.apache.org/jira/browse/AXIS2-4146 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: transports Affects

Re: vote committer status Dave Parsons and Sara Mitchel

2008-11-13 Thread Chamikara Jayalath
Telephone : Internal (7) 245743 External 01962 815743 Internet : [EMAIL PROTECTED] From: Thomas McKiernan/UK/[EMAIL PROTECTED] To: sandesha-dev@ws.apache.org Date: 11/11/2008 16:13 Subject: vote committer status Dave Parsons and Sara Mitchel Hi all, I would like to propose that David Parsons

Re: vote committer status Dave Parsons and Sara Mitchel

2008-11-12 Thread Amila Suriarachchi
Park, Winchester, SO21 2JN Telephone : Internal (7) 245743 External 01962 815743 Internet : [EMAIL PROTECTED] From: Thomas McKiernan/UK/[EMAIL PROTECTED] To: sandesha-dev@ws.apache.org Date: 11/11/2008 16:13 Subject: vote committer status Dave Parsons and Sara Mitchel Hi all, I

vote committer status Dave Parsons and Sara Mitchel

2008-11-11 Thread Thomas McKiernan
Hi all, I would like to propose that David Parsons and Sara Mitchell get made apache committers for Sandesha2 Java. Between them they have raised and resolved many JIRA issues since the May time frame. Many thanks, Thomas -- Thomas McKiernan WebSphere

Re: vote committer status Dave Parsons and Sara Mitchel

2008-11-11 Thread Andrew K Gatford
] To: sandesha-dev@ws.apache.org Date: 11/11/2008 16:13 Subject: vote committer status Dave Parsons and Sara Mitchel Hi all, I would like to propose that David Parsons and Sara Mitchell get made apache committers for Sandesha2 Java. Between them they have raised and resolved many JIRA issues since

Re: vote committer status Dave Parsons and Sara Mitchel

2008-11-11 Thread Paul Fremantle
01962 815743 Internet : [EMAIL PROTECTED] From: Thomas McKiernan/UK/[EMAIL PROTECTED] To: sandesha-dev@ws.apache.org Date: 11/11/2008 16:13 Subject: vote committer status Dave Parsons and Sara Mitchel Hi all, I would like to propose that David Parsons and Sara Mitchell get made

[jira] Created: (AXIS2C-1282) 1)reads all http headers from the request and adds them to the msg_ctx, they were missing. 2)Allows custumized http status and http headers for rest requests(don't affect

2008-11-03 Thread Luis Bilo (JIRA)
1)reads all http headers from the request and adds them to the msg_ctx, they were missing. 2)Allows custumized http status and http headers for rest requests(don't affect soap requests). 3) Adds missing http forbidden definitions

[jira] Updated: (AXIS2C-1282) 1)reads all http headers from the request and adds them to the msg_ctx, they were missing. 2)Allows custumized http status and http headers for rest requests(don't affect

2008-11-03 Thread Luis Bilo (JIRA)
Proposed patches. 1)reads all http headers from the request and adds them to the msg_ctx, they were missing. 2)Allows custumized http status and http headers for rest requests(don't affect soap requests). 3) Adds missing http forbidden definitions

jUDDI v3 status meeting Oct 29, 2008

2008-10-29 Thread Kurt T Stam
worked on 135, and will finish this before updating the persistence layer 142 and 145. Marcos Vinicius Marcos since you missed the call, can you reply to this email with your status? I think you worked on table prefix functionality (144). Can you take a look at 147 and tell me if this is something

Agenda of the Woden Status Telecon, 2008-10-07

2008-10-06 Thread Lawrence Mandel
As a reminder, the Woden status telecon will be held at 9am EST and are open to all. See [1] for call and IRC information. [1] http://ws.apache.org/woden/dev/index.html#Weekly+Status+Call Agenda 1. Open Action Items - Lawrence Mandel 2008-05-13 - John will close the M8 plan and create

Minutes of the Woden Status Telecon, 2008-09-16

2008-09-16 Thread Lawrence Mandel
) - John/Lawrence Lawrence: No status update. 3. Development Discussion - All John: I'm going to merge the serialization branch into trunk. There have been no complaints about the equivalence change so I'll move that into trunk as well. John: WRT the Maven refactoring we need to determine how

Agenda of the Woden Status Telecon, 2008-09-16

2008-09-15 Thread Lawrence Mandel
As a reminder, the Woden status telecon will be held at 9am EST and are open to all. See [1] for call and IRC information. [1] http://ws.apache.org/woden/dev/index.html#Weekly+Status+Call Agenda 1. Open Action Items - Lawrence Mandel 2008-05-13 - John will close the M8 plan and create

WODEN-208 and WODEN-65 status

2008-08-20 Thread Sagara Gunathunga
Hi all, I think we can fix WODEN-208 issue for M9 , I have already updated the fix ,please review it .About the serialization, I implemented the remaining parts of OM based implementation also but still waiting for John's review. Meanwhile , I'm free to do some more issues , please assign

Agenda of the Woden Status Telecon, 2008-08-19

2008-08-19 Thread Lawrence Mandel
As a reminder, the Woden status telecon will be held at 9am EST and are open to all. See [1] for call and IRC information. [1] http://ws.apache.org/woden/dev/index.html#Weekly+Status+Call Agenda 1. Open Action Items - Lawrence Mandel 2008-04-29 - John will update the build publish

Minutes of the Woden Status Telecon, 2008-08-19

2008-08-19 Thread Lawrence Mandel
contributed some assertion validators. I'll follow up and review his contributions. Arthur: What's the status of the assertion coverage? John: We've only done a few. Sudhir Vishwanath has worked on a couple assertions as well. I still have work to do to handle extensions. 4. Other Business - All No other

Re: [GSoC] XPath Project Status.

2008-08-06 Thread Dumindu Pallewela
Hi, Please find my commnets inline. Dumindu. On Tue, Aug 5, 2008 at 9:04 AM, Varuna Jayasiri [EMAIL PROTECTED]wrote: Hi, The XPath engine now supports most of the generally used XPath expressions. Expressions such as path expressions, predicates, unions, conditional expressions,

[GSoC] XPath Project Status.

2008-08-04 Thread Dumindu Pallewela
Hi Varuna, I see that you've done quite a job implementing XPath by now. Could you please update the list on what you have done already and what remains to be completed. Thanks, Dumindu. -- Dumindu Pallewela Cinergix - Share, Reuse, Innovate cinergix.com

Re: [GSoC] XPath Project Status.

2008-08-04 Thread Varuna Jayasiri
Hi, The XPath engine now supports most of the generally used XPath expressions. Expressions such as path expressions, predicates, unions, conditional expressions, namespaces, etc have been implemented as we have discussed and planned. For example expressions such as the following could be

2008-08-05 Woden Status Telecon Cancelled

2008-08-04 Thread Lawrence Mandel
The 2008-08-05 Woden status telecon has been cancelled. Please send status to the dev list. Thanks, Lawrence - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

2008-07-22 Woden Status Telecon Cancelled

2008-07-21 Thread Lawrence Mandel
The 2008-07-22 Woden status telecon has been cancelled. Please send status to the dev list. Thanks, Lawrence - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Agenda of the Woden Status Telecon, 2008-07-08

2008-07-08 Thread John Kaputin (gmail)
status because still I don't have a way to participate for status telecon. 1.) In WSDLWritter I already completed more than 90% of works in both DOM and OM implementations. Only remaining task is to fix the test cases. 2.) Since I've been working on Woden for last few months ,now I can

Re: Agenda of the Woden Status Telecon, 2008-07-08

2008-07-08 Thread Sagara Gunathunga
try to read a WSDL 1.1 doc with Woden. Would you like to have a go at this? regards, John. On Tue, Jul 8, 2008 at 8:17 PM, Sagara Gunathunga [EMAIL PROTECTED] wrote: Hi all, I just want to update about my current status because still I don't have a way to participate for status

Re: Refactoring status

2008-07-07 Thread Jeremy Hughes
@ws.apache.org To woden-dev@ws.apache.org cc Subject Refactoring status Hello, just to report what I have done and what is left. I have refactored woden-api, woden-om, woden-dom and created woden-ant and woden-commons. As of yet, I have just refactored the source and not the tests. I have

Re: Refactoring status

2008-07-07 Thread John Kaputin (gmail)
with option 3. Lawrence Jeff MAURY [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 06/26/2008 06:13 AM Please respond to woden-dev@ws.apache.org To woden-dev@ws.apache.org cc Subject Refactoring status Hello, just to report what I have done and what is left. I have refactored

Re: Refactoring status

2008-07-03 Thread John Kaputin (gmail)
of following conventions where possible. I'd also go with option 3. Lawrence Jeff MAURY [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 06/26/2008 06:13 AM Please respond to woden-dev@ws.apache.org To woden-dev@ws.apache.org cc Subject Refactoring status Hello, just to report what

Re: Refactoring status

2008-07-03 Thread Jeff MAURY
@ws.apache.org To woden-dev@ws.apache.org cc Subject Refactoring status Hello, just to report what I have done and what is left. I have refactored woden-api, woden-om, woden-dom and created woden-ant and woden-commons. As of yet, I have just refactored the source and not the tests. I

[jira] Created: (AXIS2-3879) Ability to change the http status code in the response being sent to the client

2008-06-30 Thread nikki (JIRA)
Ability to change the http status code in the response being sent to the client --- Key: AXIS2-3879 URL: https://issues.apache.org/jira/browse/AXIS2-3879 Project: Axis 2.0

Re: Changing the http status code in the response

2008-06-28 Thread Saminda Abeyruwan
improvement. Thank you! Saminda On Sat, Jun 28, 2008 at 2:42 AM, Nikki Payne [EMAIL PROTECTED] wrote: Hello I am running a service on Axis2 v1.4 I am attempting to change the HTTP status code in the reponse back to the client, but have been unsuccessful so far. Here's what I am doing : I get

  1   2   3   4   5   6   7   8   9   >