Hi...
Is there a "generic" way of deserializing an OMElement, irrespective of the
content type (message type)?
Say, for instance, that one uses JSON and XML alternatively for serializing
an OMElement. Must they get the actual content (and how?via
element.toString()?) and then call the appropriate
I would build your aars with ant or maven. That plugin has issues, or
at least it did a couple years ago when we were using it. We couldn't
build an aar without including the dependent libraries in it, and there
were several issues with the UI. Maybe these issues have been
addressed.
Good lu
Hi everyone,
I tried following Axis 2 plugins for eclipse:
- Code generator
- Service Archive
Code generator works fine all the time. But somehow, Service Archive plugin
has some problem.
At the beginning it works fine. But after sometime, when we select Service
Archive option,
and push next but
We tested the snapshots for both 1.6.2 and 1.7, and found similar
performance limitations. Our db query returns in a few seconds however
Axis2 adds around 15 seconds to the response time. We¹ll do some profiling
to see if we can see where the time is being spent.
Regards
Alan
On 11/17/11 2:07
On Thu, Nov 17, 2011 at 11:32 AM, Andreas Veithen wrote:
> Here are the things that we need to get done to do the Axis2 1.6.2 release:
>
> 1. Finish the 1.6.1 release cycle by releasing Sandesha2 1.6.1. The
> branch is in a releasable state, so the required effort is relatively
> limited.
> 2. Re
Here are the things that we need to get done to do the Axis2 1.6.2 release:
1. Finish the 1.6.1 release cycle by releasing Sandesha2 1.6.1. The
branch is in a releasable state, so the required effort is relatively
limited.
2. Release Axiom 1.2.13. There are 3 remaining issues in scope for
that rel
Brando
These issues impact the throughput you can achieve - for example if you are
retrieving an array of complex types (which we are). The fix to this
appears to reduce the time taken to retrieve data by a factor of 4-5. Even
on a notebook PC our database query retrieves 1000 records in a coupl
Hi Alan,
On Thu, Nov 17, 2011 at 10:46 AM, Alan Clark wrote:
>
> Our application (using 1.6.1) is being severely performance limited by the
> caching problems reported in #5119, #4878 and #4524. We understand that
> these are resolved in 1.6.2 however would very much appreciate knowing when
> th
The response is actually not an MTOM message but a SwA message.
Probably you have enabled both. In that case SwA takes precedence over
MTOM because MTOM is simply an alternative serialization of an XML
message while SwA is a different type of message. In addition, SwA
doesn't allow the SOAP stack t
Alan,
What are #5119, #4878 and #4524?
We're migrating from 1.5.1 to Axis 1.6 and performance is one of our
main concerns.
Thank You.
Brando
From: Alan Clark [mailto:alan.d.cl...@telchemy.com]
Sent: Thursday, November 17, 2011 1:47 PM
To: java-user@axis.apache.org
Subject: Expected re
Wondering if you have enabled the following?
To enableMTOM globally for all services, users can set the "enableMTOM"
parameter to True in the Axis2.xml. When it is set, all outgoing
messages will be serialized and sent as MTOM optimized MIME messages. If
it is not set, all the binary data in the b
Our application (using 1.6.1) is being severely performance limited by the
caching problems reported in #5119, #4878 and #4524. We understand that
these are resolved in 1.6.2 however would very much appreciate knowing when
this would be available. We would also be quite happy to test this releas
Hi,
Only Axis2 1.7(current trunk) support the JDK 5 Enum[1] objects.
[1] https://issues.apache.org/jira/browse/AXIS2-3967
On Thu, Nov 17, 2011 at 8:51 PM, Public Network Services <
publicnetworkservi...@gmail.com> wrote:
> Hi...
>
> I am trying to convert a POJO with 3 simple fields (of type St
Dear all,
I am experiencing the following problem with an Axis2 service: Upon a service
request, my service should return a SOAP message with an MTOM attachment. I
enabled XOP in the Axis2 configuaration. All messages are returned as
XOP+MTOM responses, but the attachment is encoded as Base64
Hi...
I am trying to convert a POJO with 3 simple fields (of type String, Enum
and Object) into an AXIOM OMElement, using Axis2 1.6.1.
The POJO serialization code, as suggested by related Axis2 sample code, is
as follows:
public OMElement toXML()
{
XMLStreamReader reader = BeanUtil.getPullParse
Hi.
I'm currently experiencing troubles trying to generate code for wsdl with
the following definition:
...
It contains an attribute and an element with equal names, and axis
generates two property with equal names.
16 matches
Mail list logo
