are there too much differences between the
2 servlets?
On 11/26/05, Eran Chinthaka [EMAIL PROTECTED] wrote:
Hi Devs,
It has been some time that we wanted to implement REST support for Axis2.
For some reason this got delayed. But I think we are moving towards 1.0, its
better to do
Sanjiva Weerawarana wrote:
On a related note, can we stop forcing people to use /services/* for the
service names? I noticed that SteveL finds that not acceptable and I
imagine that there will be many places where the admin wants to map some
other URL path to get to the Axis2 SOAP servlet. I
Make Axis2 context path configurable
Key: AXIS2-312
URL: http://issues.apache.org/jira/browse/AXIS2-312
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Components: core
Reporter: Eran Chinthaka
Priority: Minor
Hi Devs,
It has been some time that we wanted to implement REST support for
Axis2. For some reason this got delayed. But I think we are moving
towards 1.0, its better to do that.
I myself with Thilini volunteer to do that, of course with your help.
We will be adhering to the rules found in
Forwarding with correct Prefix
Original Message
Subject:
WS Policy, Axis2 Core and Modules
Date:
Wed, 23 Nov 2005 03:04:38 -0600
From:
Sanka Samaranayake [EMAIL PROTECTED]
Reply-To:
Hi devs,
Hope you all can remember I proposed a hachathon before ApacheCon on
9th, December. Seems like we can do it. I will be available together
with Ajith, Deepal and Saminda on 9th. I think Glen also will be there.
(Glen, will you ?).
So lets have a hackathon on 9th December, i.e. one day
3AM GMT seems problematic for Steve and Paul.
Steve and Paul, if you are keen on participating on Axis2 chat, we can
do some modifications to the chat times. We *didn't* have any active
involvements in previous chats from UK, so thats why this time is.
But if you say you can come, we all are ok
Generated stubs do not consistent with Call
---
Key: AXIS2-307
URL: http://issues.apache.org/jira/browse/AXIS2-307
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: databinding
Reporter: Eran Chinthaka
Assigned
= new String("test");
it still produces:
xmlns="" Context="test" .../...
I think this is not quite right, maybe it should be the same as the
situation where we specify two string values as the key and the value.
Thanks,
Ruchith
On 11/22/05, Ruchith Fernando
There was a conference on Java, Apache and XML in Germany last week.
One of my friends has conducted a session on Axis2 and lot of people
were very much interested on Axis2. I just wanted to draw your attention
to one of the questions that was raised during that session.
One of the attendees
Until I read the loong email,
did u read the javadoc comment, I wrote carefully for the method :
public static XMLStreamReader createPullParser(QName adbBeansQName,
Object[] properties, Object[] attributes) ?
Ruchith Fernando wrote:
Hi Devs,
I'm playing with the Axis2 ABD stuff and I hope
" set definitely will
not support any combination, but supports most of the frequently used
stuff.
Anyway, if there is a requirement to implement a new thing, I'm happy
to help.
-- Chinthaka
Ruchith Fernando wrote:
On 11/22/05, Eran Chinthaka [EMAIL PROTECTED] wrote:
Un
How abt just SNAPSHOT ?
Anyway, I also prefer to put SNAPSHOT either as 0.93-SNAPSHOT or
SNAPSHOT. I think its not crrect to have a fix number in the
project.xml, as it is now.
-- Chinthaka
Steve Loughran wrote:
how about naming the current release 0.93-SNAPSHOT ? that way Maven's
snapshot
Well, isn't that one of the things we want. For example, when Synapse
or Sandesha2 depends on Axis2 and they want to get the latest jar. I
think thats the best.
We can have a nightly buid mechanism and make it available via maven.
- Chinthaka
Davanum Srinivas wrote:
SNAPSHOT seems to
Hi all,
As you know Ruchith is doing an implementation of DOM on OM. We have a
small problem in keeping this implementation.
(ns:module= maven module)
It was in the XML module for some time, but later moved to SAAJ module
to resolve a problem with JDK 1.5. But I feel like the DOM impl do not
I also getting this. :(
Glen Daniels wrote:
I'm seeing this failure:
Unable to obtain goal [multiproject:install-callback] --
C:\Projects\Axis2\etc\maven.xml:71:33: ant:depend srcdir attribute
must be non-empty
Talked to dims, who suggested I delete etc/maven.xml, which seemed to
do the
Well, isn't that one of the things we want. For example, when Synapse or
Sandesha2 depends on Axis2 and they want to get the latest jar. I think
thats the best.
We can have a nightly buid mechanism and make it available via maven.
- Chinthaka
Davanum Srinivas wrote:
SNAPSHOT seems to check
Hi Trebor,
If you like to contribute we are more than happy to welcome you in. I
think you gonna implement In-Only
MEP (Fire and Forget) and polish up Robust
In-Only, we have implemented.
So please create a JIRA on this and go ahead with the implementation.
If you need any help, just don't
Steve,
Let me answer the first question (only ;-) )
Steve Loughran wrote:
I've just got my code moved up to SVN head, and things are not
dispatching right. I've been looking through the tracelogs and here
are some issues to raise
1. In the response to an operation, the reply to address
Can we know the participants to this chat as its night here for Sri
Lankans ?
Anyway, I don't think I can make it to the chat this time. Sorry :-(
The Axis2 ChatBot wrote:
Hi folks!
This is an automatic reminder that the weekly Axis2 developer chat
will be occurring tomorrow, November 16, at:
Yes this should be garbage collected.
When I was first implementing addressing, I initialy followed how
addressing implemented for axis 1.x. But later I changed the design.
+1 to remove.
Sanjiva Weerawarana wrote:
See $subject. This class does not appear to be used *anywhere*! Is that
just some
RelatesTo is a special type of header from headers. Other headers were
extension of EPR of String.
That was the reason to put that in to a special package. I'm ok with
moving that up.
Sanjiva Weerawarana wrote:
Why do we have RelatesTo in its own package when the other addressing
stuff is in
Hi Steve,
Let me explain the reason behind this change and I was about to explain
this to the community.
Steve Loughran wrote:
The protected EndpointReference to; field in Call has disappeared,
breaking my subclassing.
1. what has it been replaced by.
2. remember, everything you make
Paul, Ant and all,
Good suggestion. Well I like to see both Axis2 and Synapse co-exist
without a problem. Its true that Axis2 doesn't depend on Synapse, but
from Axis2 point of view, if we can do something useful for one of the
main projects that depends on Axis2, I think that will be good.
But,
Paul Fremantle wrote:
Ok folks
1) I will remove processingFault and inFaultFlow.
2) I think we can remove MessageInformationHeaders from the interface
3) I'm not sure I agree that the isResponse is never useful in a pure Axis2
context. Is it not an aspect of a pure SOAP message which direction
Hi devs,
Most of the axis2 devs will be coming to ApacheCon US this time. So that
would be a great time for all of us.
But myself, Ajith, Deepal, Saminda and hoefully Sanjiva will be coming
to US on 8th. So if possible, we can have a pre-ApacheCon hackathon on
9th Dec.
Just a thought !! What do
! SOAPMsgCtxt can remain as part of Synapse rather than
Axis2
thoughts?
On 11/11/05, Eran Chinthaka [EMAIL PROTECTED] wrote:
Paul Fremantle wrote:
Ok folks
1) I will remove processingFault and inFaultFlow.
2) I think we can remove MessageInformationHeaders from
Hi Srinath,
can't wedo this by changing the toEPR in the Call api and invoke the
method ? Sorry if I understood this wrong.
for example;
call.setTo(eprOne)
call.ivokeBlocking(.);
call.setTo(eprTwo)
call.invokeBlocking(...)
Srinath Perera wrote:
Hi All;
Shall we add a support to users
, then they
will just walk away. Or maybe they will figure out how to use XMLBeans.
Maybe.
Just my 2 cents.
--
Tom Jordahl
--
*From:* Eran Chinthaka [mailto:[EMAIL PROTECTED]]
*Sent:* Wednesday, November 02, 2005 9:06 PM
*To:* axis-dev@ws.apache.org
*Subject:* Re
One more comment.
Can you all remember that we agreed to have a "Simple" data binding
framework for Axis2, during the second Axis2 f2f ? We were very clear
that we didn't want a full data binding tool. (Glen, Dims you all were
there too.)
So Tom, its unfair for you to expect *everything* from
Hmm,
I like to name this method as getTextAsQName().
Actually I was initialy confused what you need to do, but after the code
snippet from Steve I understood the real requirement.
I can't understand why you are passing a String to the resolveQName
method if this methid is *in* the OMElement. I
Steve Loughran wrote:
Davanum Srinivas wrote:
Should we break out the DOM2/DOM3 stuff from xml module? just like we
did for saaj?
well, the issue is that both the OMElement and the SAAJ stuff declare
that they implement the dom interfaces, and you cannot build them on
java1.5 without
A BIG +1 from me for Glen's comments.
As Glen explained the base API should be as simple as possible and it
should not depend on any of the things like security/transaction/RM,
etc,
Paul, why do you wanna do that (I know you must be having a good
reason), when you can do the same thing using
implements DOM and OM interfaces.
+1.
Thanks
Ruchith
On 10/28/05, Eran Chinthaka [EMAIL PROTECTED] wrote:
Steve Loughran wrote:
Davanum Srinivas wrote:
Should we break out the DOM2/DOM3 stuff from xml module? just like we
did for saaj
Steve Loughran wrote:
On the subject of data binding, it would suit me nicely if you could
easily build an OMElement graph from a DOM or SAX tree.
What do you mean here ? Are you asking for a special OMElement which
wraps any data binding object, as Dennis explained.
Because that way I
Davanum Srinivas wrote:
URL: http://people.apache.org/~dims/axis2-clover/
Should we move all the interop tests in integration module from
org.apache.axis2.interop package to just interop?
Since they are *axis2* interop stuff, can't we keep them as it is. But
Dims, you must be having a good
Steve Loughran wrote:
I am looking at the current axis fault stuff. Is anybody actively
working on this, or am I free to add enhancements?
I was working on this and I know this is not complete. If you can
please please go ahead and do it.
Specifically:
1. All the bits of a SOAPFAult,
[ 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 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
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
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
Hmm, does this mean we will have no problem in running threads in J2EE
environments ? Hmm, if thats the case, this is a good idea. ( this
doesn't mean we should pop up threads here and there ;-) ). .
The two scenarios we are using threads are in invoke non-blocking case
and Async Message
OMStaxWrapper throws unnecessary END_DOCUMENT event
---
Key: AXIS2-291
URL: http://issues.apache.org/jira/browse/AXIS2-291
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: om
Reporter: Eran Chinthaka
Sanjiva Weerawarana wrote:
NOTE: I'm talking about Axis2 modules (.mar files) and not maven modules
in Axis2 :).
We currently use the name of the module foo to locate the .mar file
for it (foo.mar). That approach does not permit versioning of modules,
which I think is going to be critical for
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 solid
solution so far.
So I'd like to propose two things, for you to start with. Do not take
these hard and these are just ideas came to my mind which
[EMAIL PROTECTED] wrote:
webservices/axis2/trunk/java/modules/xml/src/org/apache/axis2/om/impl/dom/DOMImplementationImpl.java
The name DomImplementationImpl seems bit weird for me. What does that
mean ? DomImplementationImplementation ??
Sorry, if I'm missing something here ...
Ok, this is what I think.
Its better to split codegen module in to two. One module contain the
stuff that are required in the runtime of the engine. For example,
RPCCall, ADBPullParser (need to change the name). And the other module
will contain the stuff that are not required in the engine
Ohh, I'm the one who did both things. Let me defend myself :-)
ant elder wrote:
Regarding Glen's 2nd point, I'd noticed it did seem a bit slow creating the
out MC in AbstractInOutSyncMessageReceiver (code now moved to the
Utils.createOutMessageContext).
InOutSyncReceiver and
Axis2 UUID Generator is too slow
Key: AXIS2-282
URL: http://issues.apache.org/jira/browse/AXIS2-282
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Components: core
Reporter: Eran Chinthaka
Fix For: 0.93
According
onto the original
unique id.
On 10/14/05, Eran Chinthaka [EMAIL PROTECTED] wrote:
Ohh, I'm the one who did both things. Let me defend myself :-)
ant elder wrote:
Regarding Glen's 2nd point, I'd noticed it did seem a bit slow creating
the
out MC
[
http://issues.apache.org/jira/browse/AXIS2-261?page=comments#action_12331961 ]
Eran Chinthaka commented on AXIS2-261:
--
Repeating of WS-A headers now fixed when resolving Axis2-278. Please check now
and comment on this issue.
duplicate WS
[
http://issues.apache.org/jira/browse/AXIS2-279?page=comments#action_12331958 ]
Eran Chinthaka commented on AXIS2-279:
--
By definition, message context is per message per MEP. Its not meant to be used
for multiple invocations.
So
Can some one please please remove [EMAIL PROTECTED]
from SVN commits mailing list.
[EMAIL PROTECTED] wrote:
Failed to deliver to '[EMAIL PROTECTED]'
SMTP module(domain [67.103.182.217]) reports:
host 67.103.182.217 says:
550 5.1.1 [EMAIL PROTECTED]... User unknown
Reporting-MTA:
I just deleted my jaxen jar and ran maven. For me maven is dowloading
the dependency from the correct place without a problem.
Davanum Srinivas wrote:
it should be picked up from here -
http://people.apache.org/~dims/maven/jaxen/jars/
-- dims
On 10/10/05, Steve Loughran [EMAIL
[
http://issues.apache.org/jira/browse/AXIS2-274?page=comments#action_12331724 ]
Eran Chinthaka commented on AXIS2-274:
--
Today I wrote a test method for the InHandler and put that in to the
AddressingInHandlerTest. I also was about to say that even
[
http://issues.apache.org/jira/browse/AXIS2-274?page=comments#action_12331665 ]
Eran Chinthaka commented on AXIS2-274:
--
Well, I as the intial implementor of WS-A, knows that there are some problems
with the addressing implementation
[
http://issues.apache.org/jira/browse/AXIS2-221?page=comments#action_12331667 ]
Eran Chinthaka commented on AXIS2-221:
--
Thilina,
When you send some reference parameters to the server, as reference parameters
in the replyTo epr, they will send back
I used the Object model found in wsdl2java for giving the ?wsdl
generation. Basically I extracted information from the service.aar and
filled the javax.wsdl.* objects.
But since you have completed the WOM writer stuff, Can I directly
populate WOM stuff for ?wsdl generation ?
-- Chinthaka
[
http://issues.apache.org/jira/browse/AXIS2-274?page=comments#action_12331668 ]
Eran Chinthaka commented on AXIS2-274:
--
I just checked the code on this, but couldn't find any problem as you
mentioned.
Can you please provide me with a test case
[ http://issues.apache.org/jira/browse/AXIS2-273?page=all ]
Eran Chinthaka closed AXIS2-273:
Resolution: Duplicate
Add Spring Support
--
Key: AXIS2-273
URL: http://issues.apache.org/jira/browse/AXIS2-273
Jaya
On 10/7/05, Eran Chinthaka (JIRA) [EMAIL PROTECTED] wrote:
[
http://issues.apache.org/jira/browse/AXIS2-74?page=all
]
Eran Chinthaka resolved AXIS2-74:
-
Fix Version: 0.93
Resolution: Fixed
I'm really "proud" to resol
[ http://issues.apache.org/jira/browse/AXIS2-176?page=all ]
Eran Chinthaka updated AXIS2-176:
-
Fix Version: 0.93
(was: 0.91)
Description: It has been found that some well known MTOM interop endpoints
wouldn't support
[ http://issues.apache.org/jira/browse/AXIS2-176?page=all ]
Eran Chinthaka resolved AXIS2-176:
--
Resolution: Fixed
Assign To: Saminda Wishwajith Abeyruwan
Saminda has fixed this some time back.
Giving chunking on/off support for MTOMized
[ http://issues.apache.org/jira/browse/AXIS2-49?page=all ]
Eran Chinthaka reassigned AXIS2-49:
---
Assign To: Ruchith Udayanga Fernando
implementing DOM on AXIOM
-
Key: AXIS2-49
URL: http://issues.apache.org
[ http://issues.apache.org/jira/browse/AXIS2-256?page=all ]
Eran Chinthaka resolved AXIS2-256:
--
Fix Version: 0.93
Resolution: Fixed
Fixed.
OMDocument.serialize -- serializeAndConsume, OMDocument.serializeWithCache
-- serialize
[
http://issues.apache.org/jira/browse/AXIS2-261?page=comments#action_12331478 ]
Eran Chinthaka commented on AXIS2-261:
--
I did a small change in the addressing handler so that now each and every
addressing header will contain the addressing namespace
[
http://issues.apache.org/jira/browse/AXIS2-254?page=comments#action_12331481 ]
Eran Chinthaka commented on AXIS2-254:
--
I fixed this. Chamil can you please check on this and resolve, if the bug is no
more. Thanks.
Axis2 crashes when invoked using
[ http://issues.apache.org/jira/browse/AXIS2-74?page=all ]
Eran Chinthaka resolved AXIS2-74:
-
Fix Version: 0.93
Resolution: Fixed
I'm really proud to resolve this issue on behalf of all the OMers. Thanks ALL
the guys who helped to make our OM
Here is my +1.
Dinesh has done a good job with Gutthila.
Samisa Abeysinghe wrote:
Hi All,
I would like to nominate Dinesh Premalal to be an Axis2/C committer.
He had contributed so much to Axis C++ with his Guththila C++
implementation as well as he is the original author of the Guththila
Some more thoughts.
As Ajith mentioned, there are some XMLBeans stuff within the WSDL module
(madule - maven module). I'd like to keep the WSDL module clean from
them and to move them to the codegen package (as Ajith proposed). So the
codegen module will contain our data binding
Hi Srinath and Simon,
The problem Simon is having is not due to the itest plugin. See the
error, its a test failure. I fixed it just now. Simon can you please
check on that by getting an update and building again.
Chinthaka
Srinath Perera wrote:
see maven part in the
[ http://issues.apache.org/jira/browse/AXIS2-257?page=all ]
Eran Chinthaka resolved AXIS2-257:
--
Resolution: Invalid
Please report this bug in Axis 1.x. This is Axis2 JIRA.
WSDL2Java fails to create correct proxy code for web methods with too
[
http://issues.apache.org/jira/browse/AXIS2-256?page=comments#action_12331240 ]
Eran Chinthaka commented on AXIS2-256:
--
I think this renaming should be done not only for OMDocument, but also for
OMNode as well. I did that and committed.
All the devs
Title: [axis2] turning off WS-A
Do you want to disable addressing for the whole engine, per service
basis, or per operation basis ?
Simon Fell wrote:
I'm calling a service that doesn't require
WS-Addressing, using an Axis2.0 client generated from the WSDL is there
anyway to tell
[
http://issues.apache.org/jira/browse/AXIS2-261?page=comments#action_12331241 ]
Eran Chinthaka commented on AXIS2-261:
--
I know its a nice to have thing. This requires some sort of normalization in
OM. When a parent has some children which has
Hi,
All the devs and users please remember that the meaning of serialize has now
changed completely. Now its the other way round. When we serialize that means
we serialize with cache. So be careful
serialize() -- serializeAndConsume()
serializeWithCache() -- serialize().
So please
Improving SOAP Fault classes
Key: AXIS2-265
URL: http://issues.apache.org/jira/browse/AXIS2-265
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Components: core
Reporter: Eran Chinthaka
Priority: Minor
Make
[
http://issues.apache.org/jira/browse/AXIS2-246?page=comments#action_12331088 ]
Eran Chinthaka commented on AXIS2-246:
--
Hi Steve,
I tried to reproduce this bug. I ran the EchoRawXMLOnTwoChannelsSyncTest since
it has the setWSAAction method being
[
http://issues.apache.org/jira/browse/AXIS2-235?page=comments#action_12331089 ]
Eran Chinthaka commented on AXIS2-235:
--
Can the RM IN handler itself send the ack, without asking the message receiver
to send it, without making the existing MEP much
+1. Welcome aboard !!
Ajith Ranabahu wrote:
+1 from me.
On 10/3/05, Saminda Abeyruwan [EMAIL PROTECTED]
wrote:
+1
mate
Saminda
Srinath Perera wrote:
+1 welcome!!
On 10/2/05, Chamikara Jayalath [EMAIL PROTECTED]
wrote:
+1 for Chamil
Chamikara
On 10/2/05, Thilina
[ http://issues.apache.org/jira/browse/AXIS2-251?page=all ]
Eran Chinthaka resolved AXIS2-251:
--
Fix Version: 0.93
Resolution: Fixed
Thanks Yves for pointing out the bug. Fixed it.
XML comments in transmitted documents cause
Fixed the link. Sorry I have fixed that in my local machine but has
forgotten to commit that.
Davanum Srinivas wrote:
we need to fix it...here's the correct url:
http://ws.apache.org/axis2/download.cgi
thanks,
dims
On 9/29/05, Simon Fell [EMAIL PROTECTED] wrote:
on
[ http://issues.apache.org/jira/browse/AXIS2-217?page=all ]
Eran Chinthaka updated AXIS2-217:
-
Fix Version: 0.93
(was: 0.92)
javax.xml.stream.XMLStreamException while receiving Soap Envelope (at
invokeBloking
[ http://issues.apache.org/jira/browse/AXIS2-214?page=all ]
Eran Chinthaka updated AXIS2-214:
-
Fix Version: 0.93
(was: 0.92)
Sandesha2 with Axis2
Key: AXIS2-214
URL: http
[ http://issues.apache.org/jira/browse/AXIS2-167?page=all ]
Eran Chinthaka updated AXIS2-167:
-
Fix Version: 0.93
(was: 0.92)
WSE Samples implementation for Axis2, for interop testing
You
can download the release from:
http://ws.apache.org/axis2/download.cgi
What's in this release?
This release includes the following features:
Complete XML infoset support for AXIOM
AXIOM, a SOAP specific streaming XML infoset model for SOAP
1.1/1.2 messages
Support for one-way
Hi All,
Seems like people do prefer and like to see 0.92 rather than
1.0-alpha.
So I'd like to propose to release 0.92 tomorrow, 26th.
Here is my +1.
-- Chinthaka
Hi Devs,
We are getting good response to Axis2 and seems like we are actually
getting good momentum too. And lot of people would like to see a stable 1.0.
I would like to see a clear path for Axis2 towards 1.0. So please help
us to define the features we require for 1.0-alpha which will
Hi Devs,
I'm proud to announce that Axis2.war file is now over 14mb :-( . Personally I don't
like it as this leads people to think that our engine is huge and not
light weight anymore.
The reason for this is the jars we are shipping with the war. Look at
the image for jars and its sizes.
Hi,
Since we are done with all the stuff that were planned to do for alpha,
I would like to cut the release on 24th. I know that our tiny little
data binding code is not there yet, but i think that will take sometime
and lets have it in the next release in a more stable manner.
So lets
go ahead
-- Chinthaka.
Srinath
On 9/23/05, Eran Chinthaka [EMAIL PROTECTED] wrote:
Hi,
Since we are done with all the stuff that were planned to do for alpha, I
would like to cut the release on 24th. I know that our tiny little data
binding code is not there yet, but i think
Thilina,
Let me look in to this. Do you have a test case for this, so that I can
simply see what has happened and fix it, if broken.
-- Chinthaka
Thilina Gunarathne wrote:
Hi,
I was earlierusing addressing submission (which was the
default in Axis2) for the Kandula2 impl. It worked
Thilina,
Can you resolve Axis2-126 also with this commit.
Thanks,
Chinthaka
[EMAIL PROTECTED] wrote:
Author: thilina
Date: Fri Sep 23 09:30:06 2005
New Revision: 291167
URL: http://svn.apache.org/viewcvs?rev=291167view=rev
Log:
Making the AXIOM work without Java Mail Activation
Changed the
Reporter: Eran Chinthaka
Assigned to: Deepal Jayasinghe
( Reporting from the mail
http://marc.theaimsgroup.com/?l=axis-devm=112739016113007w=2 )
I am deploying the latest Axis2 built from source to BEA 8.1 sp3 on
Windows XP. I had success using Axis2 when deployed as a stand-alone
war, but when
JIRA created on this http://issues.apache.org/jira/browse/AXIS2-240.
Young, can you please continue on this with Deepal and upload your
patch.
Thanks,
Chinthaka
Davanum Srinivas wrote:
Great! Please log a JIRA bug report with your suggested diff.
thanks,
dims
On 9/22/05, Young, Wayne
Do we need WSDL 2.0 support for 1.0 ? I'm just asking the consensus,
please do not hammer me :-( .
Tom Jordahl wrote:
I would say
that any Axis2 1.0 would have
to fully support WSDL 1.1 and WSDL 2.0 generation (from Java) and
consumption
(to Java). I dont think we are there
Sanjiva Weerawarana wrote:
On Fri, 2005-09-23 at 14:46 -0400, Tom Jordahl wrote:
I would say that any Axis2 1.0 would have to fully support WSDL 1.1
and WSDL 2.0 generation (from Java) and consumption (to Java). I
don’t think we are there yet, particularly on the WSDL 2.0
Thilina,
I made a small change. Can you please check that again.
Chinthaka
Thilina Gunarathne wrote:
Hi,
I was earlierusing addressing submission (which was the
default in Axis2) for the Kandula2 impl. It worked fine. Butwhen i
triedto do the same stuff using wsa-final it started to
Eran Chinthaka wrote:
Sanjiva Weerawarana wrote:
On Fri, 2005-09-23 at 14:46 -0400, Tom Jordahl wrote:
I would say that any Axis2 1.0 would have to fully support WSDL 1.1
and WSDL 2.0 generation (from Java) and consumption (to Java). I
don’t think we are there yet
Wow, what a change a small image has done to the mailing list. I haven't
seen this much of response to issues in JIRA (kidding ... ;-) )
Dims, you are having some creative designing skills too.
Anyway, I like the second version of the image, u've done after Venkat's
suggestion. But, as Sanjiva
901 - 1000 of 1356 matches
Mail list logo
