October 2010 10:09:21 am Andreas Veithen wrote:
That would only work if one assumes that the HTML generated by the
Maven site only contains relative links. I don't think that's the
case. What we really need to do is to clean up the Maven site and get
Axis2 1.6 out.
If someone would just cp
Yes, that is what Dan suggested. We should try it, and if it works, case closed.
Andreas
On Mon, Oct 25, 2010 at 17:39, Benson Margulies bimargul...@gmail.com wrote:
There are .htaccess solutions to those issues.
On Mon, Oct 25, 2010 at 11:37 AM, Andreas Veithen
andreas.veit...@gmail.com
On Mon, Oct 25, 2010 at 18:27, Glen Daniels g...@thoughtcraft.com wrote:
On 10/25/2010 12:19 PM, jehanzeb.qay...@gmail.com wrote:
Please remove me from list.
Automatic unsub not working.
And what leads you to believe that? If you send mail to
dev-unsubscr...@ws.apache.org you will get a
On Mon, Oct 25, 2010 at 21:47, Daniel Kulp dk...@apache.org wrote:
On Monday 25 October 2010 3:44:42 pm Andreas Veithen wrote:
On Mon, Oct 25, 2010 at 21:36, Daniel Kulp dk...@apache.org wrote:
On Monday 25 October 2010 3:21:27 pm Andreas Veithen wrote:
I think Benson acted in good faith
Here is the vote for the Axiom 1.2.10 release. This is a maintenance
release that is primarily intended to support the next Abdera release.
List of issues:
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=12310250fixfor=12314861
The Maven staging area is at:
This vote has been open for more than 72 hours, with the following results:
5 binding +1 votes: Andreas Veithen, Ruchith Fernando, Thilina
Gunarathne, Samisa Abeysinghe, Sagara Gunathunga
2 non binding +1 votes: Nadir Amra, Senaka Fernando
1 binding 0 vote: David Illsley
Although David didn't
I just noticed that there is no more link from the WS homepage to
Axiom. There is no excuse for this one :-(
Andreas
On Mon, Oct 25, 2010 at 16:17, Daniel Kulp dk...@apache.org wrote:
On Monday 25 October 2010 10:03:49 am Sanjiva Weerawarana wrote:
Dan, +1 for moving the stuff but really, we
I noticed that jUDDI is still using the org.apache.ws staging profile
in Nexus to do their releases:
https://repository.apache.org/content/repositories/orgapachews-016/
Since jUDDI has been promoted to a TLP, this should be changed. Are
there still jUDDI folks on this list who can take over this
Thanks!
Andreas
On Sat, Nov 6, 2010 at 02:22, Kurt T Stam kurt.s...@gmail.com wrote:
On 11/5/10 6:07 PM, Andreas Veithen wrote:
I noticed that jUDDI is still using the org.apache.ws staging profile
in Nexus to do their releases:
https://repository.apache.org/content/repositories
On Tue, Nov 23, 2010 at 13:55, Daniel Kulp dk...@apache.org wrote:
Just to let everyone know, the comm...@ws.apache.org list is now active.
For those that are interested in the commit notices, please make sure you
subscribe to that list as they will no longer come here.
... and for all
On Tue, Nov 23, 2010 at 15:42, Jochen Wiedmann
jochen.wiedm...@gmail.com wrote:
On Tue, Nov 23, 2010 at 1:58 PM, Andreas Veithen
andreas.veit...@gmail.com wrote:
... and for all committers, please make sure that you are subscribed
***with your apache.org address*** to that list before doing
On Tue, Nov 23, 2010 at 15:54, Daniel Kulp dk...@apache.org wrote:
On Tuesday 23 November 2010 9:49:06 am Andreas Veithen wrote:
On Tue, Nov 23, 2010 at 15:42, Jochen Wiedmann
jochen.wiedm...@gmail.com wrote:
On Tue, Nov 23, 2010 at 1:58 PM, Andreas Veithen
andreas.veit...@gmail.com
+1 (binding)
Thanks,
Andreas
On Fri, Nov 26, 2010 at 18:16, Colm O hEigeartaigh cohei...@apache.org wrote:
To the Apache Web Services Community,
This is a call for votes for the wss4j-1.5.10 release. This release
contains an upgrade to use XML Security 1.4.4, some important fixes
for
On Mon, Nov 29, 2010 at 17:32, Daniel Kulp dk...@apache.org wrote:
On Sunday 28 November 2010 8:57:11 am Andreas Veithen wrote:
On Tue, Nov 23, 2010 at 15:54, Daniel Kulp dk...@apache.org wrote:
On Tuesday 23 November 2010 9:49:06 am Andreas Veithen wrote:
Because SVN notifications
On Tue, Jan 4, 2011 at 09:53, Amila Suriarachchi
amilasuriarach...@gmail.com wrote:
hi,
In order to add the inheritance support to POJO we need to find the Qname
from the string getting from the xsi:type.
here is an example
String xmlString = ns2:addPerson
to fail?
To: reposit...@apache.org
Ok, we have a fix for this already, so i'll update the RAO within the
next day or so.
On Wed, Jan 5, 2011 at 2:30 AM, Andreas Veithen
andreas.veit...@gmail.com wrote:
The issue still occurs after the outage yesterday.
Andreas
On Tue, Jan 4, 2011 at 20:51
+1 (binding)
Andreas
On Wed, Jan 12, 2011 at 19:14, Colm O hEigeartaigh cohei...@apache.org wrote:
To the Apache Web Services Community,
This is a call for votes for the wss4j-1.5.11 release. This release
contains some WS-Trust related fixes as well as a fix for a security
vulnerability
Benson,
Why would we use Maven 3, knowing that Hudson doesn't support it and
that XmlSchema builds fine with Maven 2?
Andreas
On Sat, Jan 22, 2011 at 21:06, Apache Hudson Server
hud...@hudson.apache.org wrote:
See https://hudson.apache.org/hudson/job/xmlschema-new-trunk-jdk15/6/changes
The changes related to Axiom are not critical for Axis2. They will
only become relevant when using a non standard Axiom implementation
such as the one provided by my DDOM project. This is out of scope for
the Axis2 1.6 release. If it is possible to build Axis2 trunk with
Neethi 2.0.x, then we
;-)
Dan
Thanks,
Ruwan
On Thu, Feb 3, 2011 at 4:24 PM, Andreas Veithen
andreas.veit...@gmail.comwrote:
The changes related to Axiom are not critical for Axis2. They will
only become relevant when using a non standard Axiom implementation
such as the one provided by my DDOM project
Here is the vote for the Axiom 1.2.11 release. This is a maintenance
release that is primarily intended to support the next Axis2 release.
List of issues:
http://tinyurl.com/69k4xr6
The Maven staging repository is at:
https://repository.apache.org/content/repositories/orgapachews-030/
Source
The Apache Axiom Team is pleased to announce the release of Axiom
1.2.11. The release is available for download at:
http://ws.apache.org/axiom/download.cgi
Apache Axiom is a StAX-based, XML Infoset compliant object model which
supports on-demand building of the object tree. It supports a novel
The very same idea of using an external tool instead of the export
plugin also came to my mind, but I didn't have the time to explore
this idea further. I'm +1 for this provided that the following
conditions are met:
1. We have volunteers to implement the Confluence solution. That seems
to be the
On Mon, Feb 14, 2011 at 21:18, Tom Jordahl tjord...@adobe.com wrote:
Hey Dan,
This is a suppression added by IntelliJ IDEA to suppress the highlighting of
unused methods or variables in a class.
How can an IDE come to the conclusion that a _public_ method is unused?
Why would Eclipse
of the site into a single
location.
On Mon, Feb 14, 2011 at 16:22, Daniel Kulp dk...@apache.org wrote:
On Sunday 13 February 2011 5:02:26 PM Andreas Veithen wrote:
The very same idea of using an external tool instead of the export
plugin also came to my mind, but I didn't have the time to explore
15, 2011 at 15:12, Amila Maha Arachchi ami...@wso2.com wrote:
Hi Andreas,
This occurred for the second time today. I have attached the file you
requested.
Thanks,
Amila.
On Tue, Feb 15, 2011 at 1:16 AM, Andreas Veithen andreas.veit...@gmail.com
wrote:
Can you please post the Surefire
I took over the task of porting Sandesha2 to Neethi 3. That turned out
to be trickier than Axis2 and Rampart. I have an issue with the
following code in XMLPrimitiveAssertionBuilder:
if (count == 0) {
return newPrimitiveAssertion(element, atts.isEmpty() ? null : atts);
.
Daniel Kulp
http://dankulp.com/blog
On Mar 19, 2011, at 6:03 AM, Andreas Veithen andreas.veit...@gmail.com
wrote:
Did you already request inclusion of org.apache.neethi in the Nexus
staging profile? I will likely do a 2.0.5 maintenance release to fix
some build problems in Axis2
Reason?
Andreas
On Mon, Mar 21, 2011 at 17:46, dk...@apache.org wrote:
Author: dkulp
Date: Mon Mar 21 16:46:09 2011
New Revision: 1083862
URL: http://svn.apache.org/viewvc?rev=1083862view=rev
Log:
Use slf4j instead of commons-logging
Modified:
Can we remove the lonely log statement from Neethi trunk and leave the
commons-logging vs. SLF4J discussion for 3.0.1?
Andreas
On Mon, Mar 28, 2011 at 17:34, Daniel Kulp dk...@apache.org wrote:
Neethi should now be all setup in Nexus for releases from there. Thus, I'd
like to get the
version change.
Obviously, the other important reason is out of the box OSGi support
for SLF4J.
Thoughts?
Colm.
On Mon, Mar 21, 2011 at 5:13 PM, Daniel Kulp dk...@apache.org wrote:
On Monday 21 March 2011 12:53:09 PM Andreas Veithen wrote:
Reason?
Well, 2.0.x didn't have any logging at all
Looks like the combination Maven 2.0.9 + uniqueVersion=false +
maven-source-plugin + mvn deploy + Nexus has an issue. I've changed
the Maven version for that job to 3.0.3 and now it works.
Andreas
On Mon, Mar 28, 2011 at 21:52, Apache Hudson Server
hud...@hudson.apache.org wrote:
See
-1
Since we upgraded to a recent version of the org.apache:apache
super-POM, we get two source distributions and two sets of
license/notice files in the artifacts. I'm going to fix this and
recreate the release artifacts.
Andreas
On Fri, Apr 1, 2011 at 19:28, Daniel Kulp dk...@apache.org wrote:
-1
Same reason as for 2.0.5.
Andreas
On Fri, Apr 1, 2011 at 19:30, Daniel Kulp dk...@apache.org wrote:
This is a vote to release Neethi 3.0.0
The changes from the first vote to this include updating the release notes and
some updates to the site.
This is a major upgrade to Neethi that
Also, the site doesn't conform to the Apache project branding guidelines.
Andreas
On Sat, Apr 2, 2011 at 20:24, Andreas Veithen andreas.veit...@gmail.com wrote:
-1
Same reason as for 2.0.5.
Andreas
On Fri, Apr 1, 2011 at 19:30, Daniel Kulp dk...@apache.org wrote:
This is a vote
I did the necessary changes. One final thing: should the URL of the
Web site be http://ws.apache.org/commons/neethi or
http://ws.apache.org/neethi?
Andreas
On Sat, Apr 2, 2011 at 21:09, Andreas Veithen andreas.veit...@gmail.com wrote:
Also, the site doesn't conform to the Apache project
context.
On Sun, Apr 3, 2011 at 10:34 AM, Andreas Veithen
andreas.veit...@gmail.com wrote:
Check the link for the project logo in the banner.
Andreas
On Sun, Apr 3, 2011 at 16:26, Benson Margulies bimargul...@gmail.com wrote:
Andreas,
Have you got a specific example of an absolute URL
This is a vote to release Neethi 2.0.5.
I fixed the distribution and site issues.
SVN tag:
https://svn.apache.org/repos/asf/webservices/commons/tags/neethi/3.0.0/
Maven staging repository:
https://repository.apache.org/content/repositories/orgapachews-064/
Release artifacts:
On Mon, Apr 4, 2011 at 15:09, Daniel Kulp dk...@apache.org wrote:
+1
On Sunday 03 April 2011 2:40:30 PM Andreas Veithen wrote:
This is a vote to release Neethi 2.0.5.
I'll assume this was for 3.0.0 since the subject and the tag and everything is
for 3.0.0. :-)
Yes, stupid copypaste
Kulp dk...@apache.org wrote:
On Monday 28 March 2011 2:40:15 PM Andreas Veithen wrote:
I think there is a flaw in the argument related to OSGi (or at least
something to clarify). You need to make a distinction between the API
against which you code and the actual implementation that you are
using
://www.apache.org/dev/freebsd-jails.html
On Mon, Apr 11, 2011 at 19:31, Joe Schaefer joe_schae...@yahoo.com wrote:
Everyone in the wheel group.
- Original Message
From: Andreas Veithen andreas.veit...@gmail.com
To: Infrastructure Apache infrastruct...@apache.org
Cc: dev dev@ws.apache.org
Sent
The Apache Web Services team is pleased to announce the availability
of the Apache Neethi 2.0.5 and 3.0.0 releases. They are available for
download at:
http://ws.apache.org/neethi/download.cgi
Apache Neethi provides general framework for the programmers to use WS
Policy. It is compliant with
MGwhy do the latest AXIOM and AXIS specifically exclude xerces-impl and
implement their own xml-schema parsers?
Axiom and Axis2 require Java 1.5 and can therefore safely rely on the
presence of a DOM parser in the JRE (which BTW is based on Xerces in
both Sun and IBM JREs). There is no need for
I've switched the build to Maven 3.0.3 (it was running with 2.0.9).
That seems to have solved the build failure (but I also wiped out the
workspace on at least one executor, which may have helped as well).
Andreas
On Wed, May 18, 2011 at 22:35, Apache Jenkins Server
hud...@hudson.apache.org
--
Key: XMLSCHEMA-3
URL: https://issues.apache.org/jira/browse/XMLSCHEMA-3
Project: XmlSchema
Issue Type: Bug
Affects Versions: XmlSchema 1.4.2, XmlSchema 1.4.6
Reporter: Andreas Veithen
Priority: Minor
Fix
I don't know if we really need a formal attic concept. We spent lots
of time discussing how to move Axis 1.x to the attic, but it is not
impossible [1] that we will see an Axis 1.4.1 maintenance release.
However, what would be useful is to have a disclaimer in JIRA stating
that the project is no
On Sat, Jun 4, 2011 at 21:45, Mark Thomas ma...@apache.org wrote:
On 04/06/2011 12:31, Mark Thomas wrote:
On 04/06/2011 12:06, Andreas Veithen wrote:
Hi,
I've cleaned up the dist area for the subprojects of Apache WS that
had not yet responded to the request. However I was unable to delete
On Sat, Jun 4, 2011 at 22:07, Mark Thomas ma...@apache.org wrote:
On 04/06/2011 21:02, Andreas Veithen wrote:
Axis2/C has not yet done any release since the migration to the Axis
TLP. 1.5.0 and 1.6.0 are the last two major releases. That should be
OK with respect to the archiving policy
On Sat, Jun 4, 2011 at 22:51, Mark Thomas ma...@apache.org wrote:
On 04/06/2011 21:45, Andreas Veithen wrote:
On Sat, Jun 4, 2011 at 22:07, Mark Thomas ma...@apache.org wrote:
On 04/06/2011 21:02, Andreas Veithen wrote:
Axis2/C has not yet done any release since the migration to the Axis
TLP
On Fri, Jun 17, 2011 at 21:23, Sanjiva Weerawarana
sanj...@opensource.lk wrote:
On Fri, Jun 17, 2011 at 8:49 PM, Daniel Kulp dk...@apache.org wrote:
Basically, with the modern versions of CXF and Metro, the wsgen/java2ws
tools
are really irrelevant except for TCK compliancy. I'm not sure if
, but commons-logging. Therefore we should go be to
the situation before r1083862. Correct?
Andreas
On Wed, Jun 22, 2011 at 23:28, Daniel Kulp dk...@apache.org wrote:
On Wednesday, June 22, 2011 11:26:20 PM Andreas Veithen wrote:
The Axiom trunk contains a couple of changes that I would like to
release
Here is the vote for the Axiom 1.2.12 release.
Release notes:
https://svn.apache.org/repos/asf/webservices/commons/tags/axiom/1.2.12/RELEASE-NOTE.txt
The Maven staging repository is at:
https://repository.apache.org/content/repositories/orgapachews-007/
Source and binary packages can be
The vote has been open for more than 3 days, and we got the three
required binding +1 votes. I'll proceed with the release.
Andreas
On Wed, Jul 6, 2011 at 21:01, ant elder ant.el...@gmail.com wrote:
+1
...ant
On Sat, Jul 2, 2011 at 8:58 PM, Andreas Veithen
andreas.veit...@gmail.com
afk...@gmail.com wrote:
+1
On Jul 3, 2011 1:29 AM, Andreas Veithen andreas.veit...@gmail.com wrote:
Here is the vote for the Axiom 1.2.12 release.
Release notes:
https://svn.apache.org/repos/asf/webservices/commons/tags/axiom/1.2.12/RELEASE-NOTE.txt
The Maven staging repository
Dan,
This change seems to cause a regression in Rampart:
Caused by: java.lang.IllegalArgumentException:
{http://schemas.xmlsoap.org/ws/2005/07/securitypolicy}Policy is not a
wsp:Policy element.
at
org.apache.neethi.PolicyBuilder.getPolicyOperator(PolicyBuilder.java:177)
at
Correct. I've fixed the incorrect test cases in Rampart and the build
is working fine now. That means that from my point of view, we can
start the 3.0.1 release.
Andreas
On Sat, Jul 9, 2011 at 05:01, Daniel Kulp dk...@apache.org wrote:
On Friday, July 08, 2011 11:22:58 PM Andreas Veithen wrote
FYI: Switched to Maven 2.2.1 (from 2.0.9) to make the build work again.
Andreas
On Thu, Jul 21, 2011 at 17:37, Apache Jenkins Server
jenk...@builds.apache.org wrote:
See https://builds.apache.org/job/wss4j-1.5/35/
-
To
On Mon, Jul 25, 2011 at 08:16, Sadeep Jayasumana gayansad...@gmail.com wrote:
Hi Devs,
In Apache Syanpse, we have a requirement to proxy an MTOM enabled web
service with minimum overhead. Large files (even in GB range) should be able
to go through Synapse without running it OOM.
To satisfy
On Thu, Jul 28, 2011 at 09:31, Sadeep Jayasumana gayansad...@gmail.com wrote:
Hi,
On Wed, Jul 27, 2011 at 5:39 PM, Andreas Veithen andreas.veit...@gmail.com
wrote:
On Wed, Jul 27, 2011 at 13:22, Sadeep Jayasumana gayansad...@gmail.com
wrote:
Hi,
On Wed, Jul 27, 2011 at 4:12 PM
That is related to the fact that the OMElement is actually an
OMSourcedElement. If the element is not expanded, then there is no
builder and build() is a no-op. Whether this is the expected behavior
in this particular case is subject to interpretation, given that the
Javadoc of the method is
On Thu, Aug 4, 2011 at 07:44, Amila Suriarachchi
amilasuriarach...@gmail.com wrote:
On Wed, Aug 3, 2011 at 11:18 PM, Andreas Veithen andreas.veit...@gmail.com
wrote:
That is related to the fact that the OMElement is actually an
OMSourcedElement. If the element is not expanded
+1
Thanks,
Andreas
On Fri, Aug 12, 2011 at 17:34, Colm O hEigeartaigh cohei...@apache.org wrote:
All,
This is a vote to release Apache WSS4J 1.5.12. 1.5.11 was released
last January so it's high time this was released.
Issues Fixed:
On Tue, Aug 16, 2011 at 17:44, Benson Margulies bimargul...@gmail.com wrote:
Based on email since we released 2.0, I've become convinced that it
was a mistake to leave the package names alone and change all the
APIs. There are a few outstanding JIRA. I propose to make a branch for
'urgent'
would probably be enough of a
reason.
On Tue, Aug 16, 2011 at 1:20 PM, Andreas Veithen
andreas.veit...@gmail.com wrote:
On Tue, Aug 16, 2011 at 17:44, Benson Margulies bimargul...@gmail.com
wrote:
Based on email since we released 2.0, I've become convinced that it
was a mistake to leave
, but would you
want that without the package renames?
On Tue, Aug 16, 2011 at 1:45 PM, Andreas Veithen
andreas.veit...@gmail.com wrote:
Indeed, Woden depends on XmlSchema as well.
How much time did it take you to port CXF to XmlSchema 2.0?
Andreas
On Tue, Aug 16, 2011 at 19:27, Benson
.
I could perhaps look into making the changes to woden, but would you
want that without the package renames?
On Tue, Aug 16, 2011 at 1:45 PM, Andreas Veithen
andreas.veit...@gmail.com wrote:
Indeed, Woden depends on XmlSchema as well.
How much time did it take you to port CXF to XmlSchema
+1
Andreas
On Wed, Sep 21, 2011 at 17:12, Daniel Kulp dk...@apache.org wrote:
We've fixed a few issues (5 bugs, 2 improvements) in XMLSchema 2.0 that I'd
like to get out in a release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311191version=12316384
The Maven
Jasintha,
The sample code doesn't really show what you are trying to achieve.
Obviously you wouldn't use Axiom to read the content of a file into a
String, so what is the actual use case?
Andreas
On Tue, Oct 25, 2011 at 06:48, Jasintha Dasanayaka jasint...@gmail.com wrote:
Hi Andreas
PayloadHelper.java method name is
getTextPayload(SOAPEnvelope envelope) that method uses above way to get
axiom child
you can find this code in synapse trunk class PayloadHelper.java line
number 199
Thanks Regards
/Jasintha
On Tue, Oct 25, 2011 at 11:58 PM, Andreas Veithen
andreas.veit...@gmail.com
No, the namespace repairing performed by the serialize and
serializeAndConsume methods is not configurable.
What is the use case for preserving a redundant namespace declaration
on a SOAP header?
Andreas
On Fri, Nov 18, 2011 at 03:23, Charith Wickramarachchi
charith.dhanus...@gmail.com wrote:
element(s) then
any in scope namespaces must be available and worst case every element will
re-serialize them. However under no condition is it correct to serialize a
child element and end up with malformed XML!
Sanjiva.
On Sat, Nov 19, 2011 at 10:28 PM, Andreas Veithen
andreas.veit...@gmail.com
when synapse forward them to the BE service they get omitted as they
are defined at SOAP Envelope level.
Maybe Synapse is not serializing the headers properly?
Sanjiva.
On Sun, Nov 20, 2011 at 10:55 PM, Andreas Veithen
andreas.veit...@gmail.com wrote:
Axiom never produces malformed XML. Who
, 2011 at 10:55 PM, Andreas Veithen
andreas.veit...@gmail.com wrote:
Axiom never produces malformed XML. Who said that??
Andreas
On Sun, Nov 20, 2011 at 17:59, Sanjiva Weerawarana
sanj...@opensource.lk wrote:
Isn't that a bug?
If I declare an NS at the Envelope node then that cannot
at SOAP Envelope level.
Maybe Synapse is not serializing the headers properly?
Sanjiva.
On Sun, Nov 20, 2011 at 10:55 PM, Andreas Veithen
andreas.veit...@gmail.com wrote:
Axiom never produces malformed XML. Who said that??
Andreas
On Sun, Nov 20, 2011 at 17:59, Sanjiva Weerawarana
sanj
Sanjiva,
Can you substantiate these claims by references to the spec or
concrete examples?
Andreas
On Tue, Nov 22, 2011 at 03:51, Sanjiva Weerawarana
sanj...@opensource.lk wrote:
Thanks for the clear writeup Andreas.
On Tue, Nov 22, 2011 at 12:41 AM, Andreas Veithen
andreas.veit...@gmail.com
22, 2011 at 4:00 PM, Andreas Veithen
andreas.veit...@gmail.com wrote:
Sanjiva,
Can you substantiate these claims by references to the spec or
concrete examples?
Andreas
On Tue, Nov 22, 2011 at 03:51, Sanjiva Weerawarana
sanj...@opensource.lk wrote:
Thanks for the clear writeup Andreas
:36 PM, Andreas Veithen andreas.veit...@gmail.com
wrote:
Well, the problem is that that specification actually contradicts what
you are saying. You can find the relevant quote in section 2.1 Data
Model:
An element E has namespace nodes that represent its namespace
declarations as well as any
-core/#sec-NamespaceContext
On Wed, Nov 23, 2011 at 10:25, Prabath Siriwardena prab...@wso2.com wrote:
Hi Andreas;
On Wed, Nov 23, 2011 at 2:41 PM, Andreas Veithen andreas.veit...@gmail.com
wrote:
Prabath,
This is yet another assertion that is not based on any kind of proper
argumentation
at 5:02 PM, Andreas Veithen andreas.veit...@gmail.com
wrote:
Assertion element is built, signed and added in to the SOAP Envelope.
That would mean that in order to validate the signature, one detaches
the assertion, calculates the signature and compares it with the
received signature. Where
to the EXACT xml from which the Axiom model was
built.
No one is asking for this to change default behavior. This is about making
Axiom more useful for a wider group of people and hence a perfectly
reasonable thing to do!
Sanjiva.
On Wed, Nov 23, 2011 at 2:41 PM, Andreas Veithen andreas.veit
If you are able to successfully load the properties as a resource
bundle with name com.resources.XMLInputFactory, then this means that
it is placed in a package called com.resources. Axiom will obviously
not find it there. It is expecting to find it in the default package.
Andreas
On Wed, Jan
The problem is a bit more complicated. If DOOM behaves strictly as
required by DOM, then responses from the STS are not serialized
correctly because Santuario assumes that all namespace declarations
are present. I debugged that yesterday but didn't get the time yet to
implement a temporary
I think that 2, 5, 6 and 7 should not be in the root site. These
things should be under the responsibility of each individual
subproject.
Andreas
On Mon, Jan 30, 2012 at 07:54, Sagara Gunathunga
sagara.gunathu...@gmail.com wrote:
Based on Andreas's suggestion on private list, I'm thinking to
On Mon, Jan 30, 2012 at 08:02, KasunG Gajasinghe kas...@wso2.com wrote:
On Mon, Jan 30, 2012 at 12:24 PM, Sagara Gunathunga
sagara.gunathu...@gmail.com wrote:
Based on Andreas's suggestion on private list, I'm thinking to develop
Maven based new site for WS. I have identified following
On Mon, Jan 30, 2012 at 08:07, Sagara Gunathunga
sagara.gunathu...@gmail.com wrote:
On Mon, Jan 30, 2012 at 12:32 PM, KasunG Gajasinghe kas...@wso2.com wrote:
On Mon, Jan 30, 2012 at 12:24 PM, Sagara Gunathunga
sagara.gunathu...@gmail.com wrote:
Based on Andreas's suggestion on private
Should be fixed now (see AXIOM-411). Thanks for reporting this issue.
Andreas
On Thu, Feb 23, 2012 at 15:26, Kasun Gajasinghe kasu...@gmail.com wrote:
Hi,
I've using Axiom for some work, and I've faced this issue that I think is a
bug in Axiom. The issue occurs when a given OMElement is
Axiom currently builds a patched version of the maven-shade-plugin to
work around MSHADE-105. If we release Axiom, then we also release that
patched version into Maven central (of course with a different
groupId/artifactId). Looking at the recent discussion between SOLR and
Commons CSV, this may
On Fri, Mar 9, 2012 at 14:14, Daniel Kulp dk...@apache.org wrote:
On Tuesday, March 06, 2012 02:10:03 PM Sagara Gunathunga wrote:
Hi all,
Due to AXIS2-5145 issue we need a Neethi 3.0.2 version for Axis2 1.6.2
release. Can some one update about current status of the code base and
3.0.2
to reproduce the issue ? (in order to
add an integration test).
Thanks
2012/3/8 Daniel Kulp dk...@apache.org:
On Wednesday, March 07, 2012 09:54:27 PM Andreas Veithen wrote:
Axiom currently builds a patched version of the maven-shade-plugin to
work around MSHADE-105. If we release Axiom, then we
Martin,
If the application code requests a factory for an Axiom implementation
that implements DOM and no such implementation is found, then Axiom
cannot simply return a default one (which would not implement DOM).
Andreas
On Mon, Mar 19, 2012 at 00:28, Martin Gainty mgai...@hotmail.com wrote:
I will work on this during the weekend.
Andreas
On Fri, Mar 23, 2012 at 14:20, Daniel Kulp dk...@apache.org wrote:
The shade plugin was released earlier this week so that issue should now be
resolved. Is there any chance of getting the Axiom release done soon so
that we can get the Neethi
Here is the vote for the Axiom 1.2.13 release.
Release notes:
https://svn.apache.org/repos/asf/webservices/commons/tags/axiom/1.2.13/RELEASE-NOTE.txt
The Maven staging repository is at:
https://repository.apache.org/content/repositories/orgapachews-003/
Source and binary packages can be
On Mon, Apr 2, 2012 at 19:04, Daniel Kulp dk...@apache.org wrote:
Andreas,
On Wednesday, March 28, 2012 10:39:27 PM Andreas Veithen wrote:
I will work on this during the weekend.
I saw a bunch of commits. Is a release of this happening real soon?
The vote for 1.2.13 is now open
anything network related, that could easily explain it.
(note: we don't have java 6 builds in Jenkins for Axiom, should we?)
Dan
On Monday, April 02, 2012 10:48:22 PM Andreas Veithen wrote:
Here is the vote for the Axiom 1.2.13 release.
Release notes:
https://svn.apache.org/repos/asf
Here is my own +1 vote.
The vote has been open for more than 72 hours and we had 3 binding +1
votes (Daniel, Sagara and myself) and 2 non-binding +1 votes (Ruwan
and Amila). I will proceed with the release.
Andreas
On Mon, Apr 2, 2012 at 22:48, Andreas Veithen andreas.veit...@gmail.com wrote
There was recently a discussion (I think on bo...@apache.org) about
the inclusion of binary artifacts in source distributions and I think
the conclusion was that such artifacts should not be included.
Shouldn't we just drop the Ant build stuff and create a Maven-only
source distribution?
Andreas
I tend to agree with Dan here. It would have made sense when 2.0 was
released. When Benson proposed it a year ago, it was already very
late. I think that now it is really too late.
Andreas
On Tue, May 22, 2012 at 3:17 PM, Daniel Kulp dk...@apache.org wrote:
Well, I more or less object now.
I think it makes sense to remove the Axiom support. There are two
reasons for that:
1. Axiom enables a couple of optimizations (deferred parsing,
pull-through and sourced elements) that don't exist in DOM. However, I
don't see how Woden (or code that uses Woden) would benefit from these
axiom.jar is an uber-JAR that contains the classes from axiom-api,
axiom-impl, axiom-dom and axiom-c14n. Also note that in Axiom 1.2.13,
some classes are included in both axiom-impl and axiom-dom, but with
different names, i.e. there is no 1:1 relationship between classes in
the JARs and classes
On Wed, Sep 5, 2012 at 8:25 AM, Amila Suriarachchi
amilasuriarach...@gmail.com wrote:
hi all,
I tested the $subject with the following code. Although we try to execute an
xpath for a small part it reads all the input stream.
System.out.println(Running Axiom perf test...);
1 - 100 of 1959 matches
Mail list logo
