wrong Host: HTTP request header when using HTTP proxy
---
Key: AXISCPP-998
URL: http://issues.apache.org/jira/browse/AXISCPP-998
Project: Axis-C++
Issue Type: Bug
Components:
utils have dependancies on axis2 core when it comes to class loading
Key: AXIS2C-243
URL: http://issues.apache.org/jira/browse/AXIS2C-243
Project: Axis2-C
Issue Type: Bug
Provide multiple entry points to a single DLL so that 1-1 relationship between
dlls and interface implementations can avoided.
--
Key: AXIS2C-244
Versioning of DLLs
--
Key: AXIS2C-245
URL: http://issues.apache.org/jira/browse/AXIS2C-245
Project: Axis2-C
Issue Type: Improvement
Reporter: Damitha Kumarage
We need to allow third parties to develop plugins,
Hi All,
Looking at the number of issues raised in Jira after the release of
0.93, I feel rather than rushing for a 1.0, we should release a 0.94,
(and may be few more 0.9*) before we do a 1.0.
For 0.94, we should look into memory leak fixes as planned and other
critical bugs in Jira as
Fixed subject prefix!
Samisa Abeysinghe wrote:
Hi All,
Looking at the number of issues raised in Jira after the release of
0.93, I feel rather than rushing for a 1.0, we should release a 0.94,
(and may be few more 0.9*) before we do a 1.0.
For 0.94, we should look into memory leak fixes
Hi,
On 9/1/06, Eran Chinthaka [EMAIL PROTECTED] wrote:
Unfortunately I do not agree with this.
Are you saying integration tests of Rampart and Axis2 should live in
Axis2? And you want to move Rampart out of Axis2?
For me these are two contradictory statements.
What if tomorrow, Sandesha,
Davanum Srinivas wrote:
+1 from me. Can we make it 1.5 instead of 1.1? There are just too many
changes :)
+1 for the next release, whatever the number it is.
I'm sure lot of users in our users list will love to get a release.
I'm not sure about the timeline, but let's try !!
-- Chinthaka
On Sun, 2006-09-03 at 21:54 -0400, Davanum Srinivas wrote:
URL: http://svn.apache.org/viewvc?rev=439555view=rev
Log:
1. Added ServiceObjectSupplier interface, thus, if an .aar contains a
ServiceObjectSuppler this will give the correct service object, at
deployment time as well as when
+1 to the release (and the comments from Eran)
David
On 04/09/06, Eran Chinthaka [EMAIL PROTECTED] wrote:
Davanum Srinivas wrote:
+1 from me. Can we make it 1.5 instead of 1.1? There are just too many
changes :)
+1 for the next release, whatever the number it is.
I'm sure lot of users in
What about neethi? With rahas, savan, security, sandesha, secpolicy
all being WS subprojects should neethi be also?
David
On 01/09/06, Eran Chinthaka [EMAIL PROTECTED] wrote:
Unfortunately I do not agree with this.
Are you saying integration tests of Rampart and Axis2 should live in
Axis2? And
I have no objection of calling its as 1.5 ,
btw if we do so that give us a wrong signal next Axis2 version will be
Axis2 2.0 ;-)
Thanks
Deepal
Davanum Srinivas wrote:
+1 from me. Can we make it 1.5 instead of 1.1? There are just too many
changes :)
-- dims
On 9/4/06, Deepal Jayasinghe
[ http://issues.apache.org/jira/browse/AXIS2-1060?page=all ]
Fabian Christ updated AXIS2-1060:
-
Attachment: example.zip
Hi,
this issue isn´t fixed in latest SVN. I attached a small example. The problem
is the underlying algorithm of the adb codegen.
[ http://issues.apache.org/jira/browse/AXIS2-831?page=all ]
Deepal Jayasinghe resolved AXIS2-831.
-
Resolution: Fixed
changes are in current SVN
wrong schematype generated for byte[] parameter in service operation
Hi All,I apologize from you all for not sending a mail on the following.
Let me explain the scenario,In an .aar, we can supply the service class name with the parameternamed ServiceClass. This will be a simple POJO.Looking at the AbstractMessageReceiver, there introduced anther
parameter named
Support for abstract types
--
Key: AXIS2-1108
URL: http://issues.apache.org/jira/browse/AXIS2-1108
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Components: wsdl
Reporter: Fabian Christ
nightly build 20060903
in the wsdl insider the .aar, generated by wsdl2java, the location values
for schema imports preserve the original xsd names, but the xsd included in
the .aar are still renamed to xsd0.xsd, xsd1.xsd... causing a schema not
found error at deploying
if a schema is
follow up about first issue:
changing ,manually the names of xsd0.xsd xsd1.xsd to the correct names
declared in the wsdl fixes the problem.
From: Roberto Roberto [EMAIL PROTECTED]
Reply-To: axis-dev@ws.apache.org
To: axis-dev@ws.apache.org
Subject: [AXIS2] wsdl2java import problems
Date:
[
http://issues.apache.org/jira/browse/AXIS2-850?page=comments#action_12432486 ]
Deepal Jayasinghe commented on AXIS2-850:
-
First I was unable to use your attachments , I can not understand how to
configure them and how to use them.
+1 for the next release. No objections for 1.5 nor for 1.1.
Thanks,
~Thilina
On 9/4/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
I have no objection of calling its as 1.5 ,
btw if we do so that give us a wrong signal next Axis2 version will be
Axis2 2.0 ;-)
Thanks
Deepal
Davanum Srinivas
[
http://issues.apache.org/jira/browse/AXIS2-1108?page=comments#action_12432496 ]
Davanum Srinivas commented on AXIS2-1108:
-
Fabian,
AXIS2-1060 has been fixed. Please try -g option.
-- dims
Support for abstract types
[
http://issues.apache.org/jira/browse/AXIS2-1060?page=comments#action_12432498 ]
Davanum Srinivas commented on AXIS2-1060:
-
please try -g option
WSDL2Java: Wrong handling of elements and complexTypes
+1 for Axis2 1.5On 9/4/06, Thilina Gunarathne [EMAIL PROTECTED] wrote:
+1 for the next release. No objections for 1.5 nor for 1.1.Thanks,~ThilinaOn 9/4/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote: I have no objection of calling its as
1.5 , btw if we do so that give us a wrong signal next Axis2
ant task for deploying aar file to running axis2 web application
Key: AXIS2-1109
URL: http://issues.apache.org/jira/browse/AXIS2-1109
Project: Apache Axis 2.0 (Axis2)
Issue
Hi, I use the Axis2 Code Generator for building a
non-blocking client. The *ServiceStub.java y *ServiceCallbackHandler.java are
included in an ejb deploy in Sun One 7.1.
The exception is thrown in line:
[
http://issues.apache.org/jira/browse/AXIS2-1060?page=comments#action_12432521 ]
Fabian Christ commented on AXIS2-1060:
--
Hi,
when using the -g option my small example runs. Thanks! :-)
Perhaps the -g option should become the default
+ for Axis2 1.1
-Jaliya
- Original Message -
From: Deepal Jayasinghe [EMAIL PROTECTED]
To: axis-dev@ws.apache.org
Sent: Monday, September 04, 2006 12:58 AM
Subject: [VOTE] Axis2 next release (Axis2 1.1)
Hi all;
Axis2 1.0 release on 05/05/2006 and it took about four month after that
+1
Best Regards,
Chamil Thanthrimudalige
On Sep 4, 2006, at 5:50 PM, Afkham Azeez wrote:
+1 for Axis2 1.5
On 9/4/06, Thilina Gunarathne [EMAIL PROTECTED] wrote: +1 for the
next release. No objections for 1.5 nor for 1.1.
Thanks,
~Thilina
On 9/4/06, Deepal Jayasinghe [EMAIL PROTECTED]
Resending the mail and looking forward for a reply at the earliest...
I tried the nightly builds and it seems to work fine for WSDL 2.0 with SOAP Binding. We are looking forward for the feature, WSDL2Code generating code given WSDL 2.0 with HTTP Binding. This will help us publish our WSDL 2.0
29 matches
Mail list logo
