[
https://issues.apache.org/jira/browse/AXIS-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran reassigned AXIS-546:
---
Assignee: (was: Steve Loughran)
unassigning; I deny all knowledge
java2wsdl ant task
[
https://issues.apache.org/jira/browse/AXIS-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran reassigned AXIS-893:
---
Assignee: (was: Steve Loughran)
unassigning; I deny all knowledge
axis complains about
Antoine Levy-Lambert wrote:
Hello Stefan,
it looks like the intention of the developers of commons-jelly-tags-soap
was to use two distinct saaj jars and two distinct jaxrpc jars,
one from axis, and one from geronimo.
The project.xml [1] of commons-jelly-tags-soap suggest that the gump
build
Steve Loughran wrote:
Jongjin Choi wrote:
My point is that the JAX-RPC and JAX-WS impl in a Java EE 5 container
should use same SAAJ impl. If not, two implementation of one interface
co-exists and that may cause some problem.
I agree with you. SAAJ is SAAJ but SAAJ impl of Axis 2 is based
Sanjiva Weerawarana wrote:
Folks, there's going to be a big group of Axis2 and Synapse guys from
WSO2 at ApacheCon Europe in June. Would others be interested in getting
together for some f2f/hacking work at the hackathon?
I think it'd be mighty useful.
Maybe, I'm flying in to dublin on
Jongjin Choi wrote:
My point is that the JAX-RPC and JAX-WS impl in a Java EE 5 container
should use same SAAJ impl. If not, two implementation of one interface
co-exists and that may cause some problem.
I agree with you. SAAJ is SAAJ but SAAJ impl of Axis 2 is based on
Axiom. Isn't it?
I think
Sanjiva Weerawarana wrote:
On Thu, 2006-04-27 at 20:15 +1200, Dennis Sosnoski wrote:
I'll update to jibx-*-1.1beta2.jar by this weekend. I assume this is
okay, to get around the SNAPSHOT issue. I'd prefer to leave the final
1.1 release until sometime in May, after I've had a chance to do more
Sanjiva Weerawarana wrote:
On Tue, 2006-03-21 at 21:55 +, Steve Loughran wrote:
One caveat. Once you get to 1.0, you are making some promise of stability.
I am still trying to get code that worked with 0.93 working on 0.95
snapshot, it looks like the dynamic classloading stuff is using
Ajith Ranabahu wrote:
Hi Steve,
I know the exact problem and we are planning to address it. We have
already planned the major components (such as axiom and policy) to be
released before the 1.0. These components are fairly stable and can be
released without a problem.
So it's going to be based
Sanjiva Weerawarana wrote:
On Wed, 2006-03-22 at 16:14 +0600, Ajith Ranabahu wrote:
Hi,
I think chathura answered your questions yesterday.
Checkout the archive at
http://marc.theaimsgroup.com/?l=axis-devm=114292862001333w=2
BTW Chathura is still a student. Still opensource mailing lists are
Soumadeep wrote:
Hi Ruchith,
:) it's not a question of binding anyone to anything, everyone is free to do
what they want but as an individual one needs to be committed to a cause, in
this case help the community to get the best possible output within a
timeframe, it's self discipline . My
Sanjiva Weerawarana wrote:
On Wed, 2006-03-22 at 11:16 +, Steve Loughran wrote:
Hey, I have that @work too. Proxies, you understand.
I have to put my laptop up on the WLAN as a guest for the day, which
means going to the
appropriate IT page and registering a guest (me) under
Eran Chinthaka wrote:
What is the dependency we have on maven snapshots ? ;-)
And maven released 1.1 and even 2.0 long time back.
I updated the dependency settings last week to the main releases of stuff.
one funny is that there is an XmlSchema1.0 in the m2 repository, but not
the
: deployment
Versions: 0.95
Environment: cold and damp.
Reporter: Steve Loughran
Priority: Minor
I keep my web directory under SCM. This is what I see at deployment time
151 INFO org.apache.axis2.deployment.DeploymentEngine - Invalid service CVS
due to Invalid service META-INF
Sanjiva Weerawarana wrote:
Most definitely +1! Axis2 is now ready for prime time .. and we need
much wider user feedback to make it move to the next level. We won't get
that until we release 1.0.
I propose we change 0.96 below to the label 1.0RC to signal to everyone
that this is our planned
Glen Daniels wrote:
Hi Steve:
I've been trying to get axis2 to build on gump. primarily to stop
anyone making changes incompatible with my project. It will also catch
out problems nobody has missed, and that includes tests that fail.
+1!
There are currently three tests failing on axiom.
that latter thin is an unrealistic goal, because the
faults are so different.
-- Chinthaka
On 11/18/05, Steve Loughran [EMAIL PROTECTED] wrote:
Sanjiva Weerawarana wrote:
On Thu, 2005-11-17 at 21:58 +, [EMAIL PROTECTED] wrote:
Author: dims
Date: Thu Nov 17 13:58:06 2005
New Revision: 345338
I've been trying to get axis2 to build on gump. primarily to stop anyone
making changes incompatible with my project. It will also catch out
problems nobody has missed, and that includes tests that fail.
There are currently three tests failing on axiom. Unless/until they are
fixed, axis2
Afkham Azeez wrote:
Hi Folks,
I encountered a somewhat critical situation, where if we use Sun's
JavaMail API implementation, instead of Geronimo's JavaMail API
implementation, parsing of MIME Encoded messages fails. The initial
failure occurs in the javax.mail.internet.ContentType class, where
Thilina Gunarathne wrote:
H...Too bad...
It seems the content-types generated by the two implementations are not
interoperable.. Did you try using SUN Mail in both the client and server
sides.
The relevant Content-Type header valueis;
multipart/related;
Giuseppe Picone wrote:
I should implement an HTTP redirection (307 code) with Axis 1.3, both
from client side and from server side.
I must do the redir with Axis because it depends from the SOAP content.
I need Howto and some tip.
I'll appreciate also some example code
Thanks
Giuseppe
Sanjiva Weerawarana wrote:
AFAIK no one has so far signed up to doing a WSRF impl over Axis2. If
you're willing to do it that's very cool!
When you're ready we can create a new maven module for that code or if
its more appropriate you can talk to Muse folks and ask them what their
plans are.
Sanjiva Weerawarana wrote:
On Fri, 2006-02-24 at 19:15 -0500, Srinath Perera wrote:
If we had constructor
public ServiceClient(ConfigurationContext configContext) throws AxisFault
Note that this idea is generally nonsensical: you want a client for a
service but don't say for what service.
[
http://issues.apache.org/jira/browse/AXIS-2420?page=comments#action_12367773 ]
Steve Loughran commented on AXIS-2420:
--
I'm not personally happy with the Java1.5 proxy stuff
-it now triggers a reverse DNS lookup whenever you try opening a connection
Paul Fremantle wrote:
Steve
The answer is that there is no single set of imports that we can use in Java
that uses backport if its there in JDK 1.4 and the in-built JDK 5 stuff
otherwise.
So we had to either fix Axis2 to be JDK5+ only, or use backport. We chose
backport for the widest
Davanum Srinivas wrote:
plz give me a start and i'll wrap up :)
-- dims
On 2/21/06, Steve Loughran [EMAIL PROTECTED] wrote:
Davanum Srinivas wrote:
yes, it's missing. can you please help by adding one?
I can start it, but may not lack the competence to finish it.
We need ws-commons first
Chathura Ekanayake wrote:
Hi Steve and all,
What are the functionalities you would expect from the management interface.
I have currently implemeted the functionalities provided by the Axis2
admin page so that those tasks can be performed using APIs. Below are
some functionalities I have
Is it my imagination, or does Axis2 not build in gump. I dont see a
descriptor there?
: 0.95
Reporter: Steve Loughran
When Axis2 starts up the transports, they open up an http listener by default.
This may be what people want if they are doing fully async messaging, but if
they are not (and the majority of SOAP users are not), then it is just another
security risk
: deployment
Versions: 0.95
Reporter: Steve Loughran
Serving up WSDL from an endpoint is an entirely optional feature of SOAP. If I
choose not to do it, the endpoint is still valid.
But Axis2 will fail if it cannot get the WSDL. Specifically, if there is no
configuration pointing
Davanum Srinivas wrote:
yes, it's missing. can you please help by adding one?
I can start it, but may not lack the competence to finish it.
We need ws-commons first
Chathura Ekanayake wrote:
I am busy working on the management interface. I have implemented a web
services based interface to expose the management functionalities as well.
And a servlet web application to manage remote engines by connecting to them
using the remote URL. I exposed the
Srinath Perera wrote:
Hi Eran;
- Resource framework implementation (WS-RF) and Enterprise web services
such as JSR 109 support
- Completion of interop tests
This is done.
Do we have a WSRF impl for Axis2? where can I find more info .. I
guess chathura will be intersting on knowing more
I
Having got my code to compile again, I am now surprised to see that my
unit tests are failing because I dont have the concurrent backport,
which the SimpleHttpServer needs:
java.lang.NoClassDefFoundError:
edu/emory/mathcs/backport/java/util/concurrent/BlockingQueue
at
Sanjiva Weerawarana wrote:
Hi Dug,
This sounds like a major re-arch of Axis 1.x. Do you see this being part
of Axis 1.(x+1) or more say Axis1 2.0?
From a project perspective, its perfectly fine and healthy to have
multiple versions of a major project going (proof: HTTPD and Tomcat) but
it
I see that on SVN_HEAD, the old Client class is no more.
What do I have to do to migrate some code that extended Client to move
to the 0.94 architecture?
-steve
ps, I'm planning on trying to bring up a java1.5 version of Gump in the
next few weeks; if I do that then we'll have my code
Sanjiva Weerawarana wrote:
I'd like to nominate Trebor for committer status in Axis2- he has been
contributing to Axis2 for a while and has now taken on grander and more
glorious tasks on too ;-).
Here's my vote: +1.
Sanjiva.
+1
Come joint the team, Trebor!
Ant build file broken; expects ${lib,dir} to be set
---
Key: AXIS2-417
URL: http://issues.apache.org/jira/browse/AXIS2-417
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Versions: 0.95
Reporter: Steve Loughran
Srinath Perera wrote:
+1 for the proposal
1) in the binary distribution shall we have the security and RM
modules included. that way we have the complete WS-Stack re lase. (Or
may be we can have a separate dist for that).
2) I believe we should consider XML Beans or JAXB as our principal
data
Eran Chinthaka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
This is a proposal for packaging Axis2 distros, which may be effective
from the next release
Axis2-version.jar will contain the code from
* common
* xml
* core
* adb
* wsdl
So whenever
Sanjiva Weerawarana wrote:
I'd like to add a bit more to this:
(1) Instead of axis2.jar for the base jar, how about axis2-core.jar?
+1
(2) Can we also plan on importing the various axis2-{foo}-{version}.jar
files into ibiblio? Then anyone (e.g., Synapse) who wants a specific
version of the
Eran Chinthaka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I think Steve started some time back on implementing faults for Axis2.
And I think its not completed and integrated. Shall we remove that
code from this release also, as its not being used ? I have few other
questions
Davanum Srinivas wrote:
Dong,
Could u please try with ojb? (http://db.apache.org/ojb/). We still
have not got word from Apache Legal about LGPL. and i am told that it
is not a difficult task to move from ojb to hibernate later if
necessary.
thanks,
dims
You could also use EJB3, which is
Dong Liu wrote:
Hi, Steve,
I would like to see what you have done and refer to them. What I am
doing now is about manageability of BPEL processes which is related to
normal web services, and the WS-Resources as well. I am so glad that
so many guys here are interested in the persistence of web
Dong Liu wrote:
Hi, folks,
I agree with Ajith's opinion about this persistence module for axis2.
I think the persistence module should not be restrict to certain
databases or frameworks. According to Paul's question, I would select
the first choice, and maybe a little beyond that. My current
Rajith Attapattu wrote:
Hi All,
I have seen some intrest in clustering but I see that there is no
ongoing discussion or any clear requirments on this topic.
What I would like to do is to start some discussion and gather some
momentum around this so we can flush out the
[
http://issues.apache.org/jira/browse/AXIS-2355?page=comments#action_12361367 ]
Steve Loughran commented on AXIS-2355:
--
This is why it is so dangerous to use any implementation-driven WSDL creation
process for your public interface: any change
Davanum Srinivas wrote:
Team,
Here's my view.
A default server generated by WSDL2Java and a client generated by
WSDL2Java should *NOT* have any type of sessions enabled by default.
There should be nothing on the wire which would indicate a session is
being used (No WS-A refp's, no cookies).
Rajith Attapattu wrote:
I looked in to WADI and how it can be used within Axis2 to provide
clustering support.
WADI provides web session clustering, by installing itself as an
HttpSession Manager for a particular Context/WebApp.
Ajith confirmed that in Axis2 a service grp context is used in
Chathura Herath wrote:
+1 and i got a feeling this would come handy when we are doing the WSRF stuff.
THanks
Chathura
I already am doing WSRF stuff. So far: read only properties, single or bulk.
Later: WS-N.
I'm not sure I believe enough in the lifecycle bits to implement it, but
WS-N will
Davanum Srinivas wrote:
Folks,
Can we please vote David as committer to take care of Axis 1.x.
Here's my +1
thanks,
dims
+1
Tom Jordahl wrote:
Axis logs very little by default. Do you have DEBUG or INFO logging turned on
in a commons-logging.properties file somewhere?
Axis2 is pretty verbose. My client junit logs are full of
615 INFO org.apache.axis2.deployment.AxisConfigBuilder - no custom
dispatching
robert burrell donkin wrote:
i really hate to do this but i have to -1
http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/core/src/org/apache/axis2/fault/AbstractFaultCode.java
the ASF cannot risk shipping code with dubious provinence.
- robert
no its my fault, it wasnt
[EMAIL PROTECTED] wrote:
Author: dims
Date: Thu Dec 1 16:18:00 2005
New Revision: 351535
URL: http://svn.apache.org/viewcvs?rev=351535view=rev
Log:
Move the whole offending (LGPL-tained) package out to stevel's scratch area.
Added:
Davanum Srinivas wrote:
+1 Steve. Please go ahead and check them in again with clean headers.
done in the archive, I havent moved them in to trunk as I will let
whoever is doing the release make the decision on whether to put it in
or not.
To be honest, at the current state of the fault
[
http://issues.apache.org/jira/browse/AXIS2-312?page=comments#action_12358649 ]
Steve Loughran commented on AXIS2-312:
--
to be precise, its /services/ ; if you look at the dispatching code (which I
moved around a bit, but didnt change), the app search
Tony Dean wrote:
Steve,
So you place all your jars in axis2/WEB-INF/lib? Is it ok to redistribute an
updated axis2.war with my jars included?
Thanks.
well, I dont call it axis2.war. I make my own webapp which includes all
the relevant axis2 libraries, and the appropriate bit of web.xml
Sanjiva Weerawarana wrote:
On Tue, 2005-11-22 at 13:38 +, Steve Loughran wrote:
I actually create .aar files with no .class in them, just the
declaration, and make sure the real classes are in the same webapp.
Why do you do that? Is there a particular reason you don't want to
package up
Eran Chinthaka wrote:
3AM GMT seems problematic for Steve and Paul.
I wasnt complaining about the time, I was just questioning which day the
3am was dure.
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
The Axis2 ChatBot wrote:
Hi folks!
This is an automatic reminder that the weekly Axis2 developer chat
will be occurring tomorrow, November 23, at:
7PM PST, 10PM EST, 3AM GMT, 9AM (next day) SLT, 2PM (next day) AEST
Presumably that 3AM GMT is next day too
Tony Dean wrote:
What is the Axis2 best practice for packaging a complex web service application
that spans multiple jars? Essentially, to create an Axis2 web service
endpoint, you must create a single jar with the following contents:
meta-inf/services.xml
meta-inf/services.wsdl
Davanum Srinivas wrote:
Team,
Default is now 0.93-SNAPSHOT
You can now edit etc/project.properties to set the version # to what
ever you want (OR) set using MAVEN_OPTS:
set MAVEN_OPTS=-Daxis2_version=0.93-dev
I personally prefer the MAVEN_OPTS so that project.properties is not
accidentally
robert burrell donkin wrote:
On 11/19/05, *Eran Chinthaka* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
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
how about naming the current release 0.93-SNAPSHOT ? that way Maven's
snapshot logic kicks in for things downstream of the project? This is
what I have been doing internally for some time,
-steve
Sanjiva Weerawarana wrote:
On Thu, 2005-11-17 at 21:58 +, [EMAIL PROTECTED] wrote:
Author: dims
Date: Thu Nov 17 13:58:06 2005
New Revision: 345338
URL: http://svn.apache.org/viewcvs?rev=345338view=rev
Log:
This is the last chance we are gonna get to muck around with package names...so
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 contains
seemingly gratuitous ServiceGroup reference parameters. Why?
Eran Chinthaka wrote:
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
Steve Loughran wrote:
2. Addresses with ?name=value parts are not handled properly in the POST
header or dispatch.
(a) the ?name=value bit of the URL is duplicated in the POST.
this is fixed, but dispatch is still broken. Look. If the service URL
has a / in it, then ? string stripping
The protected EndpointReference to; field in Call has disappeared,
breaking my subclassing.
1. what has it been replaced by.
2. remember, everything you make protected is implicitly part of the
API. Make things private if you dont want people to use them.
-steve
Eran Chinthaka wrote:
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
Sanjiva Weerawarana wrote:
On Thu, 2005-11-03 at 12:59 +, Steve Loughran wrote:
IIRC, there are different interpretations for different usages/specs
(XPath, XQuery, Schema, etc.), but it might be that this has been
cleaned up by now and is more consistent. We needed the option for Axis 1
Steve Loughran wrote:
Sanjiva Weerawarana wrote:
On Thu, 2005-11-03 at 12:59 +, Steve Loughran wrote:
IIRC, there are different interpretations for different usages/specs
(XPath, XQuery, Schema, etc.), but it might be that this has been
cleaned up by now and is more consistent. We
Glen Daniels wrote:
Hi folks:
The second choice wouldn't be element.getNamespace(), it would be
the default namepace. Both choices are valid depending on context,
which is why I believe there was a switch on the Axis1 version of
this logic (something like enableDefaultNS or something).
Sanjiva Weerawarana wrote:
On Tue, 2005-11-01 at 12:39 -0500, Glen Daniels wrote:
The second choice wouldn't be element.getNamespace(), it would be the
default namepace. Both choices are valid depending on context, which is
why I believe there was a switch on the Axis1 version of this logic
Glen Daniels wrote:
Steve Loughran wrote:
I am looking at how to turn the text contents of a SOAPFaultSubCode
into a QName.
Is there a utility function to map string-qname in the context of an
Element?
If there isn't yet, we should add one (Axis 1's MessageElement has this,
and it's
Glen Daniels wrote:
Is there a utility function to map string-qname in the context of
an Element?
If there isn't yet, we should add one (Axis 1's MessageElement has
this, and it's generally hugely useful).
I've done it, just dont know
Thanks Steve!
1. where to put it
Shouldn't it
Glen Daniels wrote:
Is there a utility function to map string-qname in the context of
an Element?
If there isn't yet, we should add one (Axis 1's MessageElement has
this, and it's generally hugely useful).
I've done it, just dont know
Thanks Steve!
1. where to put it
Shouldn't it
What is the maven goal to
-create the big jar of everything
-upload this and its pom to the local .m1 repository
I am having problems getting the output of a local build into the input
of the (m2-ant-task based) work I am doing.
the default goal uploads the many jar files as a separate
I have axis2 building under java1.5, and DOM 3. The extra methods in the
interfaces are just stubs, but it compiles.
Trouble is, I can't check this stuff in without 1.4 builds breaking,
because one of the new methods uses a datatype that is only in dom3.
Otherwise we could stick the stuff
Davanum Srinivas wrote:
Steve,
could we do a branch make the updates there to get a clearer picture?
- build against dom3
- try support dom2 at runtime
- update both the SAAJ and DOMImpl (to SAAJ 1.3 and DOM3)
once we have stuff working we can merge back to trunk.
would make sense. I havent
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 marking every impl class as
Davanum Srinivas wrote:
Steve,
all org.w3c imports are ONLY in org.apache.axis2.om.impl.dom.*
package. This can be ripped out w/o affecting xml module.
I'm checking. OK, the files that changed there were
AttrImpl, DocumentImpl, DOMImplementationImpl, NodeImpl, ParentNode,
TextImpl
and in
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. Because that way
I could map from Xom to OMElement without printing everything to a
StringBuffer and parsing it again.
-steve
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?
Specifically:
1. All the bits of a SOAPFAult, including random XML
easily added to AxisFault, along with headers. Can put this stuff in
when
I am looking at the current axis fault stuff. Is anybody actively
working on this, or am I free to add enhancements?
Specifically:
1. All the bits of a SOAPFAult, including random XML
2. Axis1 features: stack trace extractions, hostname, http error codes.
3. Tweak how we map from a java
I am trying to fix axis2 to work on servlets 2.3 again. Step one,
(uncommited) is to bind the build to servletapi-2.3.jar, and not geronimo.
This shows up the sole problem as ServletBasedOutTransportInfo, which is
used in
CommonsHTTPTransportSender. invoke
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
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?
Sanjiva Weerawarana wrote:
Ooops wrong link:
http://www.w3.org/2002/ws/addr/testsuite/
Sanjiva.
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
Tom Jordahl wrote:
Evlogi,
Can you try to reproduce the problem without Axis in the mix - just
plain Java code? It sure sounds like there is a daylight savings time
issue in the JVM on the client, nothing to do with Axis at all.
--
Tom Jordahl
I've always found TZ handling in Axis very
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 the web service client
[
http://issues.apache.org/jira/browse/AXIS2-282?page=comments#action_12332275 ]
Steve Loughran commented on AXIS2-282:
--
1. speedup is good, but remember that UUIDs have the requirement of being
unique. Bad things happen when something generates non
Davanum Srinivas wrote:
Me Neither. We need to fix it.
-- dims
On 9/30/05, Tom Jordahl [EMAIL PROTECTED] wrote:
Simon Fell wrote:
It seems incredable to me, that you need to generate 20x more files
than
Axis 1.1, yet its considered acceptible, Am I the only one that thinks
this is
Davanum Srinivas wrote:
Yes. We imply that we should have our own databinding :)
-- dims
-0
I find that Xom and Xpath work quite nicely. The good thing about Xom is
that it is already highly performance tuned, and you can provide your
own factory to create a graph of your custom classes,
Glen Daniels wrote:
* If we read an appropriately annotated WSDL (a la
wsa:UsingAddressing/), we should definitely generate stuff that does
send the headers (i.e. turns on the switch).
Is that really an extension to WSDL to say addressing required?
Interesting. How exactly do you declare
[
http://issues.apache.org/jira/browse/AXIS2-240?page=comments#action_12331706 ]
Steve Loughran commented on AXIS2-240:
--
Isnt there some per-webapp temp-dir-property for exactly this purpose -to
provide a temp dir for a webapp?
Problem in deploying
I'm not building against SVN_HEAD with an unsatisfied dependency;
Jaxen1.1 beta 7,
build:end:
Attempting to download jaxen-1.1-beta-7.jar.
WARNING: Failed to download jaxen-1.1-beta-7.jar.
BUILD FAILED
File..
/home/slo/.maven/cache/maven-multiproject-plugin-1.4.1/plugin.jelly
Simon Fell wrote:
on http://ws.apache.org/axis2/ the download now, and download it links
for the 0.92 release take you to
http://ws.apache.org/axis2/releases.html which only has 0.9 0.91.
Cheers
Simon
Given that you are on the mail list, can I add feature reqs to your
tcptrace/proxytrace
[
http://issues.apache.org/jira/browse/AXIS-2242?page=comments#action_12330936 ]
Steve Loughran commented on AXIS-2242:
--
Can I add that the POST request clearly says HTTP/1.1, and the HTTP1.1 spec
cleary says
All HTTP/1.1 applications MUST be able
robert burrell donkin wrote:
I'd glad that the team decided to release the last cut as 0.9.2 rather than
1.0 Alpha and I'd like to explain my reasons in a little more depth (now
that the release is cut). I think everyone appreciates the efforts that have
been put into get this far.
IMHO Axis2
1 - 100 of 243 matches
Mail list logo
