[
https://issues.apache.org/jira/browse/AXIS2C-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manjula Peiris updated AXIS2C-488:
--
Attachment: patch.txt
This patch completes processing username token ,timestamp and encryption
Hello,
Is it possible to have AXISCPP generate outgoing XML requests without
any formatting, i.e. all in one line and without any (nonsignificant)
whitespace?
Cheers
Franz
begin:vcard
fn:Dr. Franz Fehringer
n:Fehringer;Franz
org:ISO Software Systeme
Engine have a dependancy on http transport
--
Key: AXIS2C-525
URL: https://issues.apache.org/jira/browse/AXIS2C-525
Project: Axis2-C
Issue Type: Bug
Components: core/clientapi, core/engine,
Hello,
I'm trying to use client-side SSL in the 0.96 distribution for windows.
After setting ENABLE_SSL = 1 in ..\build\win32\configure.in I used nmake to
compile Axis2/C with ssl support as described in the Axis2/C Manual,
chapter 12.
In the 0.96 source distribution the files ssl_stream.h and
send with correct prefix ..
Hello,
I'm trying to use client-side SSL in the 0.96 distribution for windows.
After setting ENABLE_SSL = 1 in ..\build\win32\configure.in I used nmake to
compile Axis2/C with ssl support as described in the Axis2/C Manual,
chapter 12.
In the 0.96 source
Hi Michael,
[EMAIL PROTECTED] writes:
In the 0.96 source distribution the files ssl_stream.h and ssl_utils.h
requested to be in ..\modules\core\transport\http\sender\ssl are
missing.
It is a bug in Axis2/C 0.96 release :(, IRC there is a bug in that
option as well. I updated document in current
Hi Senkbeil,
Those two headers are not in the 0.96 distribution. I suppose it was a
mistake.
However, as I can see, those files were not changed since 0.96 release.
Hence you should be able to build safely, if you take those files from
the svn.
Dumindu.
[EMAIL PROTECTED] wrote:
Hello,
Hello Dinesh,
after successful compiling with the headers from svn (i had to do a little
change on axis2_ssl_utils_initialize_ctx in ssl_utils.h since in 0.96 there
is no second parameter), I'm now trying to run it with apache web server
2.2.4 and mod_ssl.
The echo sample works fine with normal
[
https://issues.apache.org/jira/browse/AXIS2C-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manjula Peiris updated AXIS2C-488:
--
Attachment: patch2.txt
This patch removes some printfs and fixes some memory leaks.please
Franz,
Open JIRA indicating what you want done and why...
Nadir K. Amra
Franz Fehringer [EMAIL PROTECTED] wrote on 02/07/2007 03:19:47 AM:
Hello,
Is it possible to have AXISCPP generate outgoing XML requests without
any formatting, i.e. all in one line and without any (nonsignificant)
Hi Michael,
[EMAIL PROTECTED] writes:
after successful compiling with the headers from svn (i had to do a little
change on axis2_ssl_utils_initialize_ctx in ssl_utils.h since in 0.96 there
is no second parameter), I'm now trying to run it with apache web server
2.2.4 and mod_ssl.
I'm sure
SSL client segfaults
-
Key: AXIS2C-526
URL: https://issues.apache.org/jira/browse/AXIS2C-526
Project: Axis2-C
Issue Type: Bug
Components: core/clientapi, core/transport
Affects Versions: Current (Nightly)
[
https://issues.apache.org/jira/browse/AXIS2C-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Premalal resolved AXIS2C-526.
Resolution: Fixed
SSL client segfaults
-
Key:
Dinesh Premalal [EMAIL PROTECTED] writes:
hmm..It gave me a segfault (with current svn head) :(
fixed !. You could try a new svn checkout.
thanks,
Dinesh
--
Dinesh Premalal
[EMAIL PROTECTED]
WSO2, Inc.; http://www.wso2.com/
GPG Key ID : A255955C
GPG Key Finger Print : C481 E5D4 C27E DC34
Hi devs,
I have integrated the Rampart/C and security-policy for all the features
Rampart supporting up to now.(UsernameToken,Timestamp and encryption.)
This can be downloaded from
https://svn.apache.org/repos/asf/webservices/axis2/scratch/c/security-policy/c
This is the major change I have
Hello Dinesh,
thanks a lot! I will try this.
Another question: Does Axis2/C support SSL client certificates? I did not
find any statement about this in the doc. Or is this planned for the
future?
Greetings from germany, Michael
From: Dinesh Premalal [EMAIL PROTECTED]
Sent: 08.02.2007
Manjula Peiris wrote:
Hi devs,
I have integrated the Rampart/C and security-policy for all the features
Rampart supporting up to now.(UsernameToken,Timestamp and encryption.)
This can be downloaded from
https://svn.apache.org/repos/asf/webservices/axis2/scratch/c/security-policy/c
This is the
Integrate the security-policy scratch area with the Rampart/C svn trunk
---
Key: AXIS2C-527
URL: https://issues.apache.org/jira/browse/AXIS2C-527
Project: Axis2-C
Issue
[
https://issues.apache.org/jira/browse/AXIS2-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-1804.
--
Resolution: Fixed
issue is fixed in current SVN
Error in generated WSDL file - wsaw
[
https://issues.apache.org/jira/browse/AXIS2-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-1777.
--
Resolution: Fixed
changes are in the current svn code base
Unused attachments object
[
https://issues.apache.org/jira/browse/AXIS2-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470839
]
Nick Gallardo commented on AXIS2-2125:
--
I've addressed this in a different way just yesterday in a different
[
https://issues.apache.org/jira/browse/AXIS2-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-1742.
--
Resolution: Fixed
made the changes Ravi Luthra suggested.
Null Pointer Exception
Hi Sumedha,
Thanks for the suggestion but I don't have write access to /etc/hosts
on that machine so I'll have to ask dims (or perhaps infra) to do
that. It seems strage that I'd need to make the change because that
hostname does appear in the notification e-mails:
Building machine hostname:
[
https://issues.apache.org/jira/browse/AXIS2-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-1756.
--
Resolution: Fixed
fixed the issue
504465
NPE when trying to infer the inTransport
[
https://issues.apache.org/jira/browse/AXIS2-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Birtles updated AXIS2-2122:
Attachment: AxisService.patch
The attached patch should solve the problem in 2 ways.
1. added a
Hi Rujith,
Certainly this is a very interesting discussion and helping me a lot in
understanding some of Axis2 internals.
Please find my comments below.
Regards,
Sanjaya
On Wednesday 07 February 2007 03:53, Rajith Attapattu wrote:
[RA] Yes, pessimistic locking is expensive and slow. If we
[
https://issues.apache.org/jira/browse/AXIS2-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470875
]
Deepal Jayasinghe commented on AXIS2-1580:
--
If you have a wsdl file , then pls do not use
Hi Chamikara,
Please see my comments below.
Regards,
Sanjaya
On Wednesday 07 February 2007 10:32, Chamikara Jayalath wrote:
Hi Sanjaya, Rajith, All,
Having a dedicated getClusterManager() method in the AxisConfigurator kind
of implies that the ClusterManager setting will be a special part
Hi Sanjaya, All,
So this implies that we need to keep the setProperty, getProperty methods of
the ClusterManager. Rajith ?
There is another reason. What about the service state. The service authors
will simply put the properties to the context classes and expect them to be
replicated. A single
[
https://issues.apache.org/jira/browse/AXIS2-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-1606.
--
Resolution: Fixed
applied the patch.
- pls chcek and confirm whether it works for
[
https://issues.apache.org/jira/browse/AXIS2-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-1940.
--
Resolution: Fixed
Hi Michele;
Well I am using sendRobust most of the time and I have
[
https://issues.apache.org/jira/browse/AXIS2-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470893
]
Deepal Jayasinghe commented on AXIS2-1991:
--
Hi Josef ;
Could you please attach whatever the necessary
Hi axi2 guru,
I am trying to use Soap over Jms with Axis2. I manage to generate the java
client with the wsdl2java tool and to send the message over the jms server.
Now I have a problem on the server side. The server is expecting the following
information in the jms message header:
Content_Type
[
https://issues.apache.org/jira/browse/AXIS2-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-1864.
--
Resolution: Invalid
Axis 2 expects single custom WSDL for all services in
[
https://issues.apache.org/jira/browse/AXIS2-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-1638.
--
Resolution: Fixed
I improved the session handling a bit yesterday ,not the issue
[
https://issues.apache.org/jira/browse/AXIS2-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marietta Lovendhal updated AXIS2-2127:
--
Attachment: axis2-patch.patch
Attached the patch.
Reviewed and made minor
Reviewed and made minor corrections to files in xdocs.
--
Key: AXIS2-2127
URL: https://issues.apache.org/jira/browse/AXIS2-2127
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/AXIS2-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470948
]
James Shiell commented on AXIS2-1864:
-
Could you please describe why you believe this to be invalid?
Axis 2
On 05/02/07, Jeremy Hughes [EMAIL PROTECTED] wrote:
On 05/02/07, David Illsley [EMAIL PROTECTED] wrote:
I don't think we can drop the old version without doing a release in
which they are deprecated... so I'd move to deprecate the 04/08 before
1.2 and remove them after.
As for the 06/01, do
[
https://issues.apache.org/jira/browse/AXIS2-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470962
]
Federica Ciotti commented on AXIS2-1835:
I'm trying to do the same, I've just updated my axis2 with the
[
https://issues.apache.org/jira/browse/AXIS2-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Birtles updated AXIS2-2122:
Attachment: AxisService.patch
small error in previous patch file
Generation of soap:address in
[
https://issues.apache.org/jira/browse/AXIS2-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dustin Amrhein updated AXIS2-2115:
--
Attachment: patch.txt
Client code in MDQ needs to be able to resolve imported XSD
Sameera,
We've implemented ws-trust/ws-secconv/ws-rm w/o needing to extend the
API. So please take it out of the equation.
thanks,
dims
On 2/7/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
Hi Dims, Deepal
Actually the idea is to develop a custom ping module with appropriate
handlers.
I don't think it's needed. I've done it before by changing continuum
properties files. But can't remember exactly what i did...
thanks,
dims
On 2/7/07, David Illsley [EMAIL PROTECTED] wrote:
Hi Sumedha,
Thanks for the suggestion but I don't have write access to /etc/hosts
on that machine so
[
https://issues.apache.org/jira/browse/AXIS2-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas reassigned AXIS2-2122:
---
Assignee: Deepal Jayasinghe
Generation of soap:address in wsdl files when
[
https://issues.apache.org/jira/browse/AXIS2-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470977
]
Davanum Srinivas commented on AXIS2-2120:
-
Gee,
Could you please check if you can avoid touching the kernel
Deepal,
Unfortunately the current cluster implementation cannot be implemented as a
module.
That is bcos it is very difficult to do the functionality in a handler.
If you at the clustering impl there is very little impact on the core.
Only 3 null checks at the most and minimum of one null check
Deepal,
I tried this approach and failed badly.
If it is only a IN_ONLY operation it is very difficult to figure out when to
determine if an invocation is over or not.
For IN_OUT we can have handler in the inflow and outflow, but certainly
difficult in the above scenario.
rajith
On 2/7/07,
Can't you use flowComplete() in the In_ONLY case?
David
On 07/02/07, Rajith Attapattu [EMAIL PROTECTED] wrote:
Deepal,
I tried this approach and failed badly.
If it is only a IN_ONLY operation it is very difficult to figure out when to
determine if an invocation is over or not.
For IN_OUT we
Yep. David beat me to it :)
On 2/7/07, David Illsley [EMAIL PROTECTED] wrote:
Can't you use flowComplete() in the In_ONLY case?
David
On 07/02/07, Rajith Attapattu [EMAIL PROTECTED] wrote:
Deepal,
I tried this approach and failed badly.
If it is only a IN_ONLY operation it is very
David and Dims,
Sorry I should have been more clear. What I meant by end of invocation is to
identify when the business logic has finished executing.
Bcos during the course of web service operation, the web service could be
updating state.
So does flowComplete() get executed after this ??
I
[
https://issues.apache.org/jira/browse/AXIS2-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Barrett resolved AXIS2-2087.
-
Resolution: Fixed
Thanks, Roy. Committed revision 504591.
Incorporate new validation checks
Transport level information does not match with SOAP Message namespace URI
--
Key: AXIS2-2129
URL: https://issues.apache.org/jira/browse/AXIS2-2129
Project: Axis 2.0 (Axis2)
That's a difficult question to answer... flowComplete is called by the
AxisEngine after the MessageReceiver returns from invoke(). So in the
general case, yes, flowComplete will occur after the business logic is
complete.
If, however, the MessageReceiver does work on a separate thread and
Need more clarification for a message
-
Key: AXIS2-2130
URL: https://issues.apache.org/jira/browse/AXIS2-2130
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: kernel
If it's that expensive, and given that it probably gets even more
difficult if one client can easily hit the same service multiple times
concurrently, would it be a reasonable limitation for the first
version that the MessageReceivers which return before the business
logic is complete are not
Need improvement on a message
-
Key: AXIS2-2131
URL: https://issues.apache.org/jira/browse/AXIS2-2131
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: kernel
Environment: No
Incorrect useage of the message
---
Key: AXIS2-2132
URL: https://issues.apache.org/jira/browse/AXIS2-2132
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Environment: No special
David,
I certainly think it's a resonable limitation. And we should document it
clearly.
But even in the case of HTTP sessions doesn't this problem exist? If a
service author passes the HTTPSession to a different thread, other than the
current thread of control, and a object in the scope of the
[
https://issues.apache.org/jira/browse/AXIS2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471034
]
Lahiru Sandakith commented on AXIS2-2072:
-
Hi Stuart,
This would suggest that the pre-built plugin that I
[
https://issues.apache.org/jira/browse/AXIS2-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471041
]
footh commented on AXIS2-2125:
--
Thanks Nick, that makes more sense to match what is being done on the
synchronous
Axis2 WSDL2JAVA created skeleton does not alow multiple parts where one part is
body and another destined for soap header
-
Key: AXIS2-2133
[
https://issues.apache.org/jira/browse/AXIS2-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471063
]
Gee Chia commented on AXIS2-2120:
-
Dims:
I appreciate your reminder to consider different implementation
David,
If it's that expensive, and given that it probably gets even more
difficult if one client can easily hit the same service multiple times
concurrently
It is expensive, but it maybe useful in certain uses cases. As you pointed
if there is a long running service invocation, then waiting
Having container and service management sounds totally reasonable and
sounds like it allows the cluster management to be decoupled from the
kernel which I think is probably a good thing.
David
On 07/02/07, Rajith Attapattu [EMAIL PROTECTED] wrote:
David,
If it's that expensive, and given
[
https://issues.apache.org/jira/browse/AXIS2-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471071
]
footh commented on AXIS2-2125:
--
Actually, upon reflection, the synchronous call only throws an AxisFault when
you have
[
https://issues.apache.org/jira/browse/AXIS2-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471079
]
Nick Gallardo commented on AXIS2-1800:
--
Rich,
The caching here will really help performance. When looking at
[
https://issues.apache.org/jira/browse/AXIS2-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Thaker reassigned AXIS2-2115:
Assignee: Nikhil Thaker
Client code in MDQ needs to be able to resolve imported XSD
[
https://issues.apache.org/jira/browse/AXIS2-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471103
]
Davanum Srinivas commented on AXIS2-2120:
-
Gee,
As a general rule, we *prefer* to talk about design and
If only we can figure out a way *not* to define the cluster manager
interface in kernel...i'd be happier. can't we extend the
notifications stuff that we are doing now?
-- dims
On 2/7/07, David Illsley [EMAIL PROTECTED] wrote:
Having container and service management sounds totally reasonable
[
https://issues.apache.org/jira/browse/AXIS2-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dustin Amrhein updated AXIS2-2115:
--
Attachment: patch2.txt
Attaching new patch due to merge conflict.
Client code in MDQ needs
[
https://issues.apache.org/jira/browse/AXIS2-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Thaker resolved AXIS2-2115.
--
Resolution: Fixed
patch commited,
Revision # 504702
Client code in MDQ needs to be able to
Dims,
The cluster manager interface (proposal bought by chamikara and chathura)
seem to be the only agreeable solution that came out of the whole
disscussion. I am not saying that there is no other way and certainly open
for suggestions :)
The problem with notifications is, that replication
I don't see any clustering code in Geronimo kernel or tomcat kernel or
anywhere else (HTTPD?) Guess, i will have to read thru all the emails
again :) will get back after that.
thanks,
dims
On 2/7/07, Rajith Attapattu [EMAIL PROTECTED] wrote:
Dims,
The cluster manager interface (proposal
From the recent discussion, I believe the container managed version
could manage without any kernel changes. It's the service managed
version which might need the ClusterManager interface in kernel as the
service code would have to have at least an interface to drive. It
can't (I think) simply
SAAJ soapfault creation uses wrong locale for soapreason
Key: AXIS2-2134
URL: https://issues.apache.org/jira/browse/AXIS2-2134
Project: Axis 2.0 (Axis2)
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AXIS2-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Rheinheimer updated AXIS2-2134:
Attachment: patch.txt
SAAJ soapfault creation uses wrong locale for soapreason
[
https://issues.apache.org/jira/browse/AXIS2-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471169
]
David R. Kraus commented on AXIS2-1574:
---
I originally communicated an issue (Axis2-1706) which had to do with
[
https://issues.apache.org/jira/browse/AXIS2-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471171
]
David R. Kraus commented on AXIS2-1706:
---
The error I am experiencing with RPCInOnlyMessageReceiver is
Big +1. In addition, we want to try to implement clustering using
multiple technologies- Tribes is just one. JGroups is another (which
cannot be committed here because its LGPL).
I'm sure IBM and others probably have proprietary clustering technology
they'd like to plug in for clustering and not
The ping response is a best effort. The default is to say it reached
the msg receiver so all is ok. Obviously that's not always true- e.g.,
class load errors can occur after that. (Or imagine the service is
implemented by a BPEL script- one of the external services may be
missing.)
So a given
+1 indeed!
However, for community health, let's everyone please be a bit tolerant /
patient / extra polite when asking the other to review/correct. I'm
referring to the tone of the emails .. we're all here to make axis2
great so there's no need to assume otherwise from anyone. (Yes this goes
for
I think i'd like to see a patch before we go further. Am not convinced
this is the best approach. We could do a custom dispatcher that could
insert a java dynamic proxy[1] under certain conditions (custom soap
header?) to get the same kind of behavior.
Thanks,
dims
[1]
+1
This is a capability my clients have often wanted. I'm not sure I see
the need to do it at the MessageReceiver level, though. The approach
I've thought about is to use handlers. The handlers could not only
respond to a ping, but could also supply useful information about the
actual state
Hey Sanjaya,
It is indeed turning out to be a good conversation.
comments inline.
Regards,
Rajith
On 2/7/07, Sanjaya Karunasena [EMAIL PROTECTED] wrote:
[SK] So why not use Synapse? Of course there is an option of embedding a
simple but a fast load balancer as the default load balancer.
[
https://issues.apache.org/jira/browse/AXIS2-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe reopened AXIS2-1835:
--
return a java.lang.List return a java.lang.IllegalArgumentException: null rcl
Hi All;
I also like if we can do cluster management w.o changing the kernel ,
and in the meantime I do not like to have the notification capability as
well. If you are trying to do so , then we need to notify whenever we
change a property , context changes etc etc.. , so that going to cost us
a
[
https://issues.apache.org/jira/browse/AXIS2-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chatra Nakkawita resolved AXIS2-2127.
-
Resolution: Fixed
Reviewed and committed. Thanks Marietta.
Chatra
Reviewed and made
Hi Deepal,
What kind of notifications do u mean ?
We will need to listen to event changes like context creation, removal and
property updates. But this does not hv to be done in every property get, set
method call if ask the service authors to do something like following (as
Rajith mentioned),
Hi Rujith,
Please fine my comments inline.
Regards,
Sanjaya
On Thursday 08 February 2007 09:10, Rajith Attapattu wrote:
Hey Sanjaya,
It is indeed turning out to be a good conversation.
comments inline.
Regards,
Rajith
On 2/7/07, Sanjaya Karunasena [EMAIL PROTECTED] wrote:
[SK] So
Hi Chamikara ;
Hi Deepal,
What kind of notifications do u mean ?
I was talking about the Observer interface I was talking about , when
you add,remove or change a module or service then Axis2 will notify the
observers. So I thought dims was suggesting to extend that.
We will need to listen
Hi Rajith,
On 2/8/07, Rajith Attapattu [EMAIL PROTECTED] wrote:
Hey Sanjaya,
It is indeed turning out to be a good conversation.
comments inline.
Regards,
Rajith
On 2/7/07, Sanjaya Karunasena [EMAIL PROTECTED] wrote:
[SK] So why not use Synapse? Of course there is an option of
[
https://issues.apache.org/jira/browse/AXIS2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-1748.
--
Resolution: Fixed
Fixed the issue in the current code base
To have this feature you
[
https://issues.apache.org/jira/browse/AXIS2-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-1719.
--
Resolution: Fixed
issue is fixed in the current SVN
array-type bean property: null
[
https://issues.apache.org/jira/browse/AXIS2-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-1835.
--
Resolution: Fixed
Hi
Please Get the latest SNAPSHOT and try.
I invoked the service
When an wsdl (1.1) is in aar, dispatching would not work.
-
Key: AXIS2-2135
URL: https://issues.apache.org/jira/browse/AXIS2-2135
Project: Axis 2.0 (Axis2)
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AXIS2-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saminda Wishwajith Abeyruwan updated AXIS2-2135:
Attachment: version.aar
When an wsdl (1.1) is in aar, dispatching
[
https://issues.apache.org/jira/browse/AXIS2-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471218
]
Deepal Jayasinghe commented on AXIS2-1786:
--
Hi ;
I tried to download the service aar file but I couldn't ,
98 matches
Mail list logo
