Hi Asankha,
From what I've seen, most of the performance problems with
Axis2/Rampart lay outside of WSS4J. Rampart could certainly do a better
job of optimizing its use of WSS4J - for example by not going through
the overhead of constructing an AXIOM DOM representation of the message
and pass
't do policy based validations.
Would be glad if you could please confirm it.
Thanks & regards.
-Prabath
Dennis Sosnoski wrote:
Following up on some earlier discussions of Axis2/Rampart WS-Security
performance, devWorks has now published my latest article in the Java
Web Services ser
Following up on some earlier discussions of Axis2/Rampart WS-Security
performance, devWorks has now published my latest article in the Java
Web Services series, comparing Axis2/Rampart with Metro WS-Security
performance: http://www.ibm.com/developerworks/java/library/j-jws11/ The
results are ve
Amila Suriarachchi wrote:
On Tue, Jan 5, 2010 at 12:06 PM, Dennis Sosnoski <mailto:d...@sosnoski.com>> wrote:
Hi Amila,
It's definitely best to use minOccurs=1 for primitives.
nillable=true is *not* a good choice in general, and I'd recommend
you instead
Hi Amila,
It's definitely best to use minOccurs=1 for primitives. nillable=true is
*not* a good choice in general, and I'd recommend you instead go with
minOccurs=0 for object types.
Why is nillable=true bad? 1. It requires the element to still be present
in the message, adding unnecessary b
Try my series on developerWorks:
http://www.ibm.com/developerworks/java/library/j-jws4/
http://www.ibm.com/developerworks/java/library/j-jws5/
http://www.ibm.com/developerworks/java/library/j-jws6/
http://www.ibm.com/developerworks/java/library/j-jws7.html
The first three work with direct config
Hi Prabath,
That's interesting, and I'll mention it to people, but I was looking
specifically for a way of doing this in Axis2.
Thanks,
- Dennis
Prabath Siriwardena wrote:
Dennis Sosnoski wrote:
Is there any way to make WS-Security work with JAX-WS?
You can use WSAS [1] t
[
https://issues.apache.org/jira/browse/AXIS2-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski updated AXIS2-4487:
---
Attachment: library.wsdl
WSDL causing NPE.
> JAXB code generation fails with multi
Components: databinding
Affects Versions: 1.5
Reporter: Dennis Sosnoski
Attachments: library.wsdl, library.wsdl, types.xsd
JAXB code generation fails with NPE when multiple schemas are present in the
WSDL (with one imported into another):
[java] Exception in thread "
[
https://issues.apache.org/jira/browse/AXIS2-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski updated AXIS2-4487:
---
Attachment: types.xsd
library.wsdl
WSDL with imported schema in a separate
he.org/jira/browse/AXIS2-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski reassigned AXIS2-4028:
--
Assignee: Dennis Sosnoski
>
wsdl2java with JiBX binding cannot unwrap inte
[
https://issues.apache.org/jira/browse/AXIS2-4486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski updated AXIS2-4486:
---
Attachment: types.xsd
library.wsdl
WSDL and imported schema
> JAXB w
[
https://issues.apache.org/jira/browse/AXIS2-4486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski updated AXIS2-4486:
---
Attachment: JaxbUnwrapLibraryStub.java
Generated client stub class.
> JAXB with unwrapp
: databinding
Affects Versions: 1.5
Reporter: Dennis Sosnoski
Attempting to use the -uw WSDL2Java option with jaxbri data binding generates
code with missing methods. See the attached JaxbUnwrapLibraryStub.java, where
various toEnvelope() methods are missing. Here's the output from t
Is there any way to make WS-Security work with JAX-WS? I haven't been
able to find one - there's no services.xml with JAX-WS, and security
policy in the WSDL appears to be ignored (and stripped from the WSDL
supplied by the service).
- Dennis
--
Dennis M. Sosnoski
Java XML and Web Services
A
[
https://issues.apache.org/jira/browse/AXIS2-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski reassigned AXIS2-3642:
--
Assignee: Dennis Sosnoski
> jibx libs coming in Axis2 distrib are renamed while st
I'd think at least this Jira should be addressed before a 1.5.1 release:
https://issues.apache.org/jira/browse/AXIS2-4434 Another documentation
issue is that the documentation on transports is no longer accurate, and
should either be corrected (presumably by pointing to the transports
project l
[
https://issues.apache.org/jira/browse/AXIS2-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski reassigned AXIS2-4434:
--
Assignee: Glen Daniels
> JavaDocs broken both on site and in distribut
Glen Daniels wrote:
...
IMO, this would be a bad idea. The goal of the kind of modularity we have,
or at least one of the goals, is to enable the components to version and
release at different rates. Unless there were incompatible API changes
(which certainly do happen) we should be able to rel
Glen Daniels wrote:
Hi Dennis:
Dennis Sosnoski wrote:
Whether officially led by WSO2 or not, certainly most of the direction
of the project has come from people associated with WSO2 and/or the Sri
Lanka university...
I agree re: most of the committership having historically been from
dependent projects.
Totally +1 for fixing the Web site stuff up. If the docs are messed up
then we should do a 1.5.1 release.
Sanjiva.
On Thu, Jul 23, 2009 at 5:04 AM, Dennis Sosnoski <mailto:d...@sosnoski.com>> wrote:
I'm starting to wonder about the health of the A
I'm starting to wonder about the health of the Axis2 project, and
thought it might be useful to initiate a discussion on this topic.
The 1.5 release of Axis2 took 8 months from initial proposal to when it
finally escaped out the door, and the results frankly don't seem to
reflect the amount of
0 from me, too. Since there's no recent release of the transport code to
even try out it's difficult to judge the quality of his work.
- Dennis
Andreas Veithen wrote:
0. Since I don't know Charith personally, I can only base my decision
on the contributions and discussions on the public mail
I'm not exactly sure what you're trying to do, Demetris. I haven't been
following this thread, but if you're trying to generate code from WSDL
on a mobile client you're probably going to have a very difficult time
of it no matter what tool you use - JiBX's code generation from schema
is only in
Versions: 1.5
Reporter: Dennis Sosnoski
The org.apache.axis2.description.AxisDescription JavaDocs say "This method sets
the policy as the default of this AxisDescription instance. Further more this
method does the followings.
(1) Engage whatever modules necessary to execute ne
: documentation
Affects Versions: 1.5
Reporter: Dennis Sosnoski
The online link to the JavaDocs is broken for 1.5. From page
http://ws.apache.org/axis2/ this link points at
http://ws.apache.org/1_5/api/index.html but this page does not exist.
Furthermore, the axis2-1.5-docs.zip has only a
Are you supposed to be able to engage a module such as Rampart at the
operation level in client code (rather than for the service as a whole)?
I've tried the following, which looks like it should work based on the API:
// find the rampart module from configuration
ServiceCli
Maven site for the project and make sure there is a
minimum of documentation.
- Fix some of the remaining open bugs.
Andreas
On Sat, Jul 11, 2009 at 02:08, Dennis Sosnoski wrote:
What's the status of the transports code compatible with Axis 1.5?
Thanks,
- Dennis
--
Dennis M. Sosnoski
J
What's the status of the transports code compatible with Axis 1.5?
Thanks,
- Dennis
--
Dennis M. Sosnoski
Java XML and Web Services
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Client stub generation attaches policies from the WSDL to the relevant
messages, but does not engage modules (such as Rampart for
WS-SecurityPolicy handling). This means application code needs to engage
the modules as appropriate before using the service.
Is this a design decision or a bug (or
Amila Suriarachchi wrote:
On Fri, Jul 10, 2009 at 5:20 AM, Dennis Sosnoski <mailto:d...@sosnoski.com>> wrote:
The WSDL2Java codegen for server-side deployment appears to ignore
any WS-Policy information in the WSDL (unlike the client-side code
generation, which build
The WSDL2Java codegen for server-side deployment appears to ignore any
WS-Policy information in the WSDL (unlike the client-side code
generation, which builds code to attach the policy information to the
appropriate description components). Are there any plans to include
WS-Policy information i
Can a WS-SecurityPolicy be configured on a particular message used by a
service? I've seen that the policy can be applied to a particular
operation by embedding it inside the services.xml description of that
operation, and assume the same can be done at the message level by using
child element
[
https://issues.apache.org/jira/browse/AXIS2-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722098#action_12722098
]
Dennis Sosnoski commented on AXIS2-2929:
You might want to give Jibx2Wsdl a tr
In running performance tests with Rampart I've found that just having
the Rampart module engaged on the client appears to cause the OM to be
expanded for every message, even if no WS-Security processing is
required. This results in a major performance hit. The whole point of
AXIOM is supposed t
[
https://issues.apache.org/jira/browse/AXIS2-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski reassigned AXIS2-4303:
--
Assignee: Dennis Sosnoski
> Jibx sample does not work both in the current trunk
[
https://issues.apache.org/jira/browse/AXIS2-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski resolved AXIS2-4303.
Resolution: Fixed
Fix Version/s: 1.5
Fixed by http://svn.apache.org/viewvc?rev
/AXIS2-4321
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: admin console
Affects Versions: 1.5
Environment: Linux, Sun 1.5.0_15-b04 JVM
Reporter: Dennis Sosnoski
Priority: Blocker
After building the axis2.war (using the
Thanks, Nandana - that did it.
- Dennis
Nandana Mihindukulasooriya wrote:
First build the following modules and then try to build at the root level.
modules/tool/axis2-mar-maven-plugin
modules/tool/axis2-aar-maven-plugin
thanks,
Nandana
On Tue, Apr 21, 2009 at 11:50 AM, Dennis Sosnoski
I'm trying to build from the 1.5 branch ('mvn clean install'), and
consistently get:
Downloading:
http://ws.zones.apache.org/repository2/org/apache/axis2/axis2-mar-maven-plugin/1.5/axis2-mar-maven-plugin-1.5.jar
Downloading:
http://repo1.maven.org/maven2/org/
Amila Suriarachchi wrote:
Here the main idea was to share the same transports between Axis2 and
synapse. The idea of an axis2 transport is to use as an adapter
between axis2 and the actual transport (i.e http, smtp, JMS etc). In
fact Axis2 transport uses respective libraries for these standa
Jarek Gawor wrote:
...
2) Move the base, local, tcp, and http transport modules back to Axis2
and release them with Axis2. That way the transports project would
only have the 'optional' transport modules and we wouldn't have to
release the transports for/with Axis2.
+1 for this approach. Ha
If transports is using these Axis2 interfaces I don't see the point of
having it as a separate project. I thought the reason for moving
transports outside of Axis2 was to allow it to be used for other
purposes. How is that going to work if the code is assuming the Axis2
environment?
The only
Do we have a compatible Rampart version for testing? There seem to be
some major problems with the handling of WS-SecurityPolicy embedded in
WSDL for 1.4.1, and if we could test 1.5 with a compatible Rampart
version *before* we release 1.5 (rather than the usual approach of
releasing an Axis2 v
,
You should go into the tools folder and build the
axis2-aar-maven-plugin and the axais-mar-maven-plugin first. Then
build axis2 from the root level.
Thanks,
Keith.
On Fri, Mar 6, 2009 at 12:57 PM, Dennis Sosnoski <mailto:d...@sosnoski.com>> wrote:
Ok, so that's not the cause
e tag should be versioned 1.4.1
while the branch stays on 1.4-SNAPSHOT.
Thanks,
Keith,
On Fri, Mar 6, 2009 at 12:33 PM, Dennis Sosnoski <mailto:d...@sosnoski.com>> wrote:
I did a fresh checkout of the Java 1.4 branch from svn in order to
retrofit some code. When I try runn
I did a fresh checkout of the Java 1.4 branch from svn in order to
retrofit some code. When I try running "mvn install", I get:
Downloading:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/axis2/axis2-mar-maven-plugin/1.4-SNAPSHOT/axis2-mar-maven-plugin-1.4-SNAPSHOT.jar
Downl
I'm trying to update the mvn build to the current JiBX development code,
but the JiBX repository is not on the current list and the instructions
output by mvn when the jar is not found don't work (it says to use "mvn
install:install-file ..." - but this gives an error message "POM
'org.apache.a
Thanks, that fixes the build on 1.6.
- Dennis
Jarek Gawor wrote:
This does not fail on Java 5. Anyway, committed a simple/temporary fix
to the test.
Jarek
On Tue, Oct 28, 2008 at 3:20 PM, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:
I'm unable to build Axis2, after a fresh ch
I'm unable to build Axis2, after a fresh checkout from svn, using "mvn
clean install". It consistently fails during the SAAJ module build, with
an error on the SAAJResultTest:
---
Test set: org.apache.axis2.saaj.SAAJRes
Hi Lasantha,
Axis2 is based on using a StAX pull parser for the actual document
processing, along with a build-on-demand document model (AXIOM). The
actual details of data binding are handled by the data binding tool, so
the Axis2 code can avoid any assumptions about the structure of the
resu
Having the Axis2 client communicating with an Axis 1 service operate
twice as fast as an Axis2 client communicating with an equivalent Axis2
service is certainly surprising. Do you know the size of the messages
you're sending? For large messages the actual data handling (where Axis2
should be v
The performance advantage of Axis2 over Axis(1) is mostly because
Axis(1) converts every message to DOM form. Axis2 instead handles most
data by using some form of data binding, which converts to and from Java
objects with much better performance than a DOM. In cases where the full
DOM represen
+1
- Dennis
Brian De Pradine wrote:
+1
Cheers
Brian DePradine
Web Services Development
IBM Hursley
External +44 (0) 1962 816319 Internal 246319
If you can't find the time to do it right the first time, where will
you find the time to do it again?
*Dustin Amrhein <[EMAIL PROT
Andreas Veithen wrote:
...
Moving to Java 1.5 doesn't necessarily mean to abandon support for
Java 1.4. I am currently working on a project for a company that still
uses Java 1.4 (and I think there are lots of them). We needed a
library to generate MS Project files, but the only one we could
From my experiences working with companies moving to Axis2 I'd say
about half are still using JDK 1.4. If they can't count on that support
being maintained I think they're likely to reconsider adopting Axis2.
Just having an archived 1.3 version of Axis2 won't be enough to convince
them, unless
Hi Saminda,
In order to use JiBX data binding you need to use the JiBX binding
compiler to modify your compiled classes with the added code needed by
JiBX. This error is saying that the classes you're using at runtime have
not been modified by the binding compiler.
If you compare the before-
I think linking to external sites is great for added howtos and
tutorials, but documentation for basic features of the Axis2 framework
should ship with the framework distribution.
- Dennis
Sanjiva Weerawarana wrote:
> Why? Duplicate docs are PITA to maintain. How about sticking a link
> somewh
ot; projects founder on
> not actually seeing what works and what doesn't.
> For some reason I thought there was already work on DIME and TCP in Axis2.
> But I've never actually looked at the code so I'm probably wrong.
>
> Paul
>
> On 10/8/07, Dennis Sosnoski <
came up with something significantly better then it would be worth
> doing.
>
> Paul
>
> On 10/8/07, Dennis Sosnoski <[EMAIL PROTECTED]> wrote:
>
>> Hi Paul,
>>
>> I think it's an interesting possibility. I've been trying to find out
>>
Hi Paul,
I think it's an interesting possibility. I've been trying to find out
what .Net is currently using for their net.tcp transport, but that's
proving difficult. The Sun proposal is at least well-defined.
I wish they'd asked for comments and started a discussion rather than
just making somet
Sanjaya Karunasena wrote:
On Friday 28 September 2007, Dennis Sosnoski wrote:
From my testing so far, it
looks like "Fast Infoset" actually runs a little /*slower*/ than text
XML when client and server are on the same system.
Well, the advantage here is the size of the mes
is
--
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Sanjaya Karunasena wrote:
On Thursday 27 September 2007, Dennis Sosnoski wrote:
I wanted to do s
I wanted to do some performance tests with Fast Infoset, but can't find
anything about how to use this feature. There should probably be
something added to the documentation, since this was one of the new
features listed for the 1.3 release.
Anyone know how to turn this on?
- Dennis
--
Denn
I'd like to merge this change on trunk into the 1.3 branch:
http://svn.apache.org/viewvc?view=rev&rev=559788 Anyone object?
Thanks,
- Dennis
--
Dennis M. Sosnoski
SOA and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-05
: Bug
Components: databinding
Affects Versions: nightly
Reporter: Dennis Sosnoski
Assignee: Dennis Sosnoski
Exceptions thrown during marshalling are wrapped, first in a JiBXException and
then in an XMLStreamException. When stack trace details are output, such as
+1. I've suggested in the past that Rampart should really be merged back
into Axis2, since it's essentially a required component and having it as
a separate project only adds administrative overhead with no noticeable
benefit.
- Dennis
--
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2
[
https://issues.apache.org/jira/browse/AXIS2-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513498
]
Dennis Sosnoski commented on AXIS2-2964:
The problem I was seeing was that the conversion of the exception
[
https://issues.apache.org/jira/browse/AXIS2-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski resolved AXIS2-2686.
Resolution: Cannot Reproduce
Tried setting this option for both ADB and JiBX
[
https://issues.apache.org/jira/browse/AXIS2-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski updated AXIS2-2964:
---
Attachment: xmlbeans-sample.zip
> XMLBeans fault handling not sending data to cli
: databinding
Affects Versions: 1.2, nightly
Reporter: Dennis Sosnoski
Priority: Critical
Attachments: xmlbeans-sample.zip
The attached project builds and executes properly under Axis2 1.1.1. Under 1.2
and the current 1.3 code the exception data is not sent back from
)
Issue Type: Bug
Affects Versions: nightly
Reporter: Dennis Sosnoski
Priority: Minor
The war file created by the Ant build.xml in the webapp directory includes jars
which should not be needed at runtime, including axis2-adb-codegen.jar,
axis2-codegen.jar, and jibx
AXIS2-2962
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: nightly
Environment: Maven 2.0.7, Java 1.5.0_11, Linux
Reporter: Dennis Sosnoski
Priority: Critical
The war file generated in the modules/distribution/target directo
[
https://issues.apache.org/jira/browse/AXIS2-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski reassigned AXIS2-2952:
--
Assignee: Deepal Jayasinghe (was: Dennis Sosnoski)
Not in my realm - I assume the
Thanks, Afkham - builds correctly now.
- Dennis
Dennis Sosnoski wrote:
I'm getting a compile failure on the clustering module:
...ChannelSender.java[29,7]
org.apache.axis2.clustering.tribes.ChannelSender is not abstract and
does not override abstract method sendToGroup(java.lang.Thro
I'm getting a compile failure on the clustering module:
...ChannelSender.java[29,7]
org.apache.axis2.clustering.tribes.ChannelSender is not abstract and
does not override abstract method sendToGroup(java.lang.Throwable) in
org.apache.axis2.clustering.MessageSender
svn update says At revision
mvn clean install -Drelease
This will create distributions under modules/distribution/target.
/sumedha
On 7/13/07, *Dennis Sosnoski * <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
I get (for "mvn clean install"):
BUILD ERROR
The plugin 'org.a
quot;There is
discussion of this on the users list and there are open issues in MNG.",
but although I found many instances of problem reports none seemed to
have a solution.
- Dennis
Deepal Jayasinghe wrote:
Hi Dennins;
First download maven2 (2.0.7) and then run - mvn clean intall
Then can someone provide maven2 setup and build directions? Everything I
can find says only maven(1) is supported:
http://ws.apache.org/axis2/faq.html#d3
http://ws.apache.org/axis2/svn.html#maven
http://ws.apache.org/axis2/siteHowTo.html
- Dennis
Deepal Jayasinghe wrote:
Hi Dennis,
We move
It looks like the maven build is broken in trunk. I now get the failure:
BUILD FAILED
File.. /home/dennis/.maven/cache/maven-jar-plugin-1.6.1/plugin.jelly
Element... ant:fail
Line.. 53
Column 19
You must define currentVersion in your POM.
Total time: 13 seconds
Finished at: Fri Jul 13
[
https://issues.apache.org/jira/browse/AXIS2-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski closed AXIS2-2670.
--
> A problem in the simpleType reference handling with the Axis2 JiBX unwrap
[
https://issues.apache.org/jira/browse/AXIS2-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski updated AXIS2-2670:
---
Fix Version/s: (was: nightly)
1.3
> A problem in the simpleT
[
https://issues.apache.org/jira/browse/AXIS2-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski closed AXIS2-2669.
--
> JiBX serialization can generate malformed
[
https://issues.apache.org/jira/browse/AXIS2-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski updated AXIS2-2669:
---
Fix Version/s: (was: nightly)
1.3
> JiBX serialization can gener
[
https://issues.apache.org/jira/browse/AXIS2-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski closed AXIS2-2549.
--
> Sample quickstartjibx cannot be compiled with Ant1.6.5. Throws
I'm personally not convinced that this is a good approach, since it
starts users off on the wrong path. The whole POJO approach, while great
for demos, is fundamentally limited and certainly not a good approach to
use in real web services. So should it be the first thing users see?
- Dennis
Amila Suriarachchi wrote:
On 6/12/07, *Dennis Sosnoski* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
...This should be changed so
that there doesn't need to be a message data object type for
faults with
no content (corresponding to an exception that
Amila Suriarachchi wrote:
On 6/12/07, *Dennis Sosnoski* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
I think it would be much cleaner to fix the code generation
handling, so
that the same exception can be used by multiple methods. Why
complicate
t
I think it would be much cleaner to fix the code generation handling, so
that the same exception can be used by multiple methods. Why complicate
the interface with multiple classes for the same data?
So my response to Glen's questions would be that the message name should
be based on just the
+1 for adopting these guidelines for Axis2 Java.
- Dennis
Samisa Abeysinghe wrote:
To add something, APR people have defined a set of guidelines for
versioning: http://apr.apache.org/versioning.html
Though APR is a C project, there would be somethings to take form that
- specially API compati
Amila Suriarachchi wrote:
On 5/26/07, *Dennis Sosnoski* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
...the compile error in the generated stub for callback
classes when asynchronous is enabled (5-18 email):
http://marc.info/?t=11788556981&r
Hi Amila,
Changing the subject to match the content.
From my personal experience there are the issues that we've already
discussed, where as far as I can see unwrapping is badly broken. First
there's the issue with multiple schemas in the WSDL which you said you'd
fixed, and then the compile
[
https://issues.apache.org/jira/browse/AXIS2-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498984
]
Dennis Sosnoski commented on AXIS2-2686:
I'll give it a try myself with some ADB code, to try to dete
[
https://issues.apache.org/jira/browse/AXIS2-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498972
]
Dennis Sosnoski commented on AXIS2-2686:
I have a difficult time believing that this has anything to do with
et me ask you - do you think the current stuff on the 1.2 branch
has already resolved the "badly broken" parts enough to release it?
And if not what particular JIRAs would you fix there?
--Glen
Dennis Sosnoski wrote:
Hi dims,
I think it's been clear for some time that the 1.2 rel
Hi dims,
I think it's been clear for some time that the 1.2 release is badly
broken. If you really think the solution is a 1.3 release, and that that
wouldn't break as many things as it fixes, then we should push to get
one out quickly. And if 1.3 *does* break a bunch of things, well then
the
[
https://issues.apache.org/jira/browse/AXIS2-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski resolved AXIS2-2453.
Resolution: Fixed
Fix Version/s: nightly
Fixed by http://svn.apache.org/viewvc?view
[
https://issues.apache.org/jira/browse/AXIS2-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski updated AXIS2-2669:
---
Fix Version/s: nightly
> JiBX serialization can generate malformed
[
https://issues.apache.org/jira/browse/AXIS2-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski resolved AXIS2-2669.
Resolution: Fixed
Fixed by http://svn.apache.org/viewvc?view=rev&rev=539405 in t
[
https://issues.apache.org/jira/browse/AXIS2-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Sosnoski resolved AXIS2-2670.
Resolution: Fixed
Fix Version/s: nightly
Fixed by http://svn.apache.org/viewvc?view
1 - 100 of 490 matches
Mail list logo
