Paul Fremantle wrote:
Samisa
Congratulations. That is impressive!
Paul
On 10/21/05, *Samisa Abeysinghe* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi All,
After much effort, I am happy to tell you that we have a running
version of OM in SVN.
We can give an
[ http://issues.apache.org/jira/browse/AXISCPP-843?page=all ]
John Hawkins updated AXISCPP-843:
-
Component: WSDL processing - Doc
Version: 1.5 Final
Serialiser is using namespaces without first assigning them in the XML
By the way, I tried this test program with Guththila code in SVN, and it
works.
But when I use this through OM, it fails. :(
Thanks,
Samisa...
Dinesh Premalal wrote:
Hi,
I tried with Guththila. v.xml is your xml file ;)
[EMAIL PROTECTED]:~/Projects/Guththila-c-p3/test$ ./test v.xml
Hi All,
There are few more memory leaks present in the axis2 C code.
(Guththila leaks should be handled seperate IMO)
I would like to propose that we use the unit tests to isolate memory
leak problems as much as possible and fix those then and there. I would
like the allocation and
[ http://issues.apache.org/jira/browse/AXISCPP-822?page=all ]
nadir amra closed AXISCPP-822:
--
Fix Version: 1.6 Alpha
Resolution: Fixed
Possible improvements to the HTTPTransport::getHTTPHeaders() and the
HTTPTransport::flushOutput() methods -
Hi
Please see my comments below:
Thanks,
Ruchith
On 10/25/05, Thilina Gunarathne [EMAIL PROTECTED] wrote:
Hi,
- Added and commented code in OMTextImpl, to do line wrapping of base64
content (using 76 character length) , for others to review, this is
required to support Encrypt, Sign , MTOM
Hi,
In Axis1 there is a scope parameter in server-config.wsdd that controls
the instantiation of the impl class. Is there an appropriate parameter
in Axis2 or on which base the instantiation happens?
Thanks
Yves
Hi ;
Still we do not handling that , pls create a JIRA we will fix that in next
release.
Thanks,
Deepal
~Future is Open~
- Original Message -
From: Yves Langisch [EMAIL PROTECTED]
To: axis-dev@ws.apache.org
Sent:
Adding service scope control
Key: AXIS2-292
URL: http://issues.apache.org/jira/browse/AXIS2-292
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Components: core
Versions: 0.92
Reporter: Yves Langisch
There should be
Deepal,
Thanks, I'll give it a try.
Yves
On Tue, 2005-10-25 at 09:21 +0600, Deepal Jayasinghe wrote:
Hi Yvess;
The correct way is get the ServiceDescription from , MessageContxt and then
you can get the correct classloader for that service (which has all you lib
files) from
All,
I'm looking for a way to get the current MessageContext in the skeleton
class? In Axis2 this could be done with
AxisEngine.getCurrentMessageContext().
Thanks
Yves
[ http://issues.apache.org/jira/browse/AXIS2-291?page=all ]
Eran Chinthaka resolved AXIS2-291:
--
Resolution: Fixed
Fixed.
OMStaxWrapper throws unnecessary END_DOCUMENT event
---
Key:
hi
You can do that , but you need to do small modification add the following
method to the skeleton class , then that method will be called by
MessageReciver (called dependency injection)
class MySkel {
private MessageContext ctx;
public void init(MessageContext ctx){
this.ctx = ctx;
}
Steve Loughran wrote:
Rogan Dawes wrote:
Hi folks,
I recently attended a presentation at the OWASP (Open Web Application
Security Project) Conference in Washington, and the presenter showed an
attack scenario involving injection of repeated elements into the XML
document.
The idea is that if
Glen Daniels wrote:
Hey Steve:
Ooops wrong link:
http://www.w3.org/2002/ws/addr/testsuite/
It still offends me that WS-A can consider themselves nearly ready to
be final and yet they only have a few draft test cases. For example,
where is their wsa:To header with a ? string in
Can't add user defined phases before the PostDispatch phase
---
Key: AXIS2-294
URL: http://issues.apache.org/jira/browse/AXIS2-294
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: deployment
[ http://issues.apache.org/jira/browse/AXIS-2216?page=all ]
Ralf Hauser updated AXIS-2216:
--
Attachment: patch.txt
patch to be able to set such a cipher.
It's a one liner:
call.setProperty(JSSESocketFactory.SUPPORTED_CIPHER_SUITES,
[
http://issues.apache.org/jira/browse/AXIS2-294?page=comments#action_12355731 ]
Deepal Jayasinghe commented on AXIS2-294:
-
Hi Chamikara,
First of all it's NOT a bug it's a security feature, we had a long discussion
before we are doing so. And we
[
http://issues.apache.org/jira/browse/AXIS2-294?page=comments#action_12355734 ]
Chamikara Jayalath commented on AXIS2-294:
--
OK. Please make it a new feature :)
BTW it is great if it shows an error message other than an exception.
Thanx,
Who owns the apache implementation of javax.qname? Is there one single
source tree that is the master, with one self-contained jar file that
implements it for the benefit of gump-enabled things. Or does every
project get to reimplement it themselves and redist it inside their own
JAR files?
[
http://issues.apache.org/jira/browse/AXIS-2186?page=comments#action_12355749 ]
Stefano Meneghello commented on AXIS-2186:
--
Hi,
Axis 1.3 final gives the same error message for 1MB attachments
Stefano
AxisFault with DIME attachments greater
ClassCastException in AxisClient.getJAXRPCHandlerChain
--
Key: AXIS-2270
URL: http://issues.apache.org/jira/browse/AXIS-2270
Project: Apache Axis
Type: Bug
Environment: exists in axis 1.2.1 and code hasn't chaged
On 10/25/05, Steve Loughran [EMAIL PROTECTED] wrote:
Who owns the apache implementation of javax.qname?
IIRC xml-commons keeps a canonical version but it's probably best asking this question again on that list...
- robert
some random musings...
On 10/24/05, Eran Chinthaka [EMAIL PROTECTED] wrote:
Hi all,We all know that we have a small problem with our packaging of distros.
We were telling lot of things about this here and there, but no solidsolution so far.
IMHO this is part is of a bigger problem concerning
Hi folks!
This is an automatic reminder that the weekly Axis2 developer chat
will be occurring tomorrow, October 26, at:
7PM PDT, 10PM EDT, 2AM GMT, 8AM (next day) SLT, 12PM (next day) AEST
The chat takes place on the freenode IRC network, (use server
irc.freenode.net), on channel #apache-axis,
[
http://issues.apache.org/jira/browse/AXIS-1965?page=comments#action_12355872 ]
Jason Williams commented on AXIS-1965:
--
There seem to be several serialization related errors that are not easily
reproduceable, and are closed without any true fix. Is
Hi Robert and All,
robert burrell donkin wrote:
some random musings...
On 10/24/05, Eran Chinthaka [EMAIL PROTECTED] wrote:
Hi all,
We all know that we have a small problem with our packaging of distros.
We were telling lot of things about this here and
[
http://issues.apache.org/jira/browse/AXIS2-272?page=comments#action_12355888 ]
Douglas Hubler commented on AXIS2-272:
--
Spring is working on this as well, only very different approach
http://opensource2.atlassian.com/projects/spring/browse/SPR-371
Regression with polymorphism
Key: AXIS-2271
URL: http://issues.apache.org/jira/browse/AXIS-2271
Project: Apache Axis
Type: Bug
Components: Serialization/Deserialization
Versions: current (nightly)
Reporter: Steve Green
[ http://issues.apache.org/jira/browse/AXIS-2271?page=all ]
Steve Green updated AXIS-2271:
--
Attachment: polymorphism.wsdl
This wsdl is a modification of the wsdl from the polymorphism test case. Note
that it adds a wrapper type around the type intended
Hi all,
I'm Making the hierarchy as follows:
s/ServiceDescription/AxisService/
s/OperationDescription/AxisOperation/
s/ServiceGroupDescription/AxisServiceGroup/ according to the proposal.
This is some what a big refactoring which effect most of the code. So
please please do not commit anything
Hi All,
Please see my commens below:
On 10/26/05, Glen Daniels [EMAIL PROTECTED] wrote:
Hi Deepal, Sanjiva:
What I'm trying to say is that we should NOT hard-code the dispatch
order, we should have it simply exist as configuration in the default
axis2.xml file.
+1 .. Deepal what's
Hi glen and all;
As I understand we came to a conclusion that the only way to deploy handlers
using module. So if some one want to add a handler he has to create module
and write it module.xml correctly and engage that module. (I know the fact
that it make simple case harder). But I do not
here is my +1
Thanks,
Deepal
~Future is Open~
- Original Message -
From: Sanjiva Weerawarana [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: axis-dev@ws.apache.org
Sent: Wednesday, October 26, 2005 5:15 AM
Subject: Re:
What about the package name then? Are we going to retain description?
As the argument goes, as it is not meta data, description does not
sound correct.
Tanks,
Samisa...
Glen Daniels wrote:
For the record, I continue to really dislike
ServiceDescription/OperationDescription as class names
Hi Deepal:
As I understand we came to a conclusion that the only way to deploy
handlers using module. So if some one want to add a handler he has to
create module and write it module.xml correctly and engage that module.
(I know the fact that it make simple case harder). But I do not think we
Hi Ruchith:
I very much like the ability to quickly configure the handler chain
using axis2.xml. As long as nothing creates conflicts, why shouldn't we
allow this?
Are you talking about handlers in general?
If so... I was under the impression that with Axis2 the users will NOT
not have
Refactoring done and releasing the lock.
Thanks all for your help.
Eran Chinthaka wrote:
Hi all,
I'm Making the hierarchy as follows:
s/ServiceDescription/AxisService/
s/OperationDescription/AxisOperation/
s/ServiceGroupDescription/AxisServiceGroup/ according to the proposal.
This is some
38 matches
Mail list logo
