Anne,Again I will advice again serializing the contexts using any form of serialization. This will not scale at all in a production environment.Again this approach will be error prone and as chamikara mentioned there will be too many information saved in the database.
I am looking at clustering cer
Hi Ann,
Yes. We had introduced Externalizable implementaitons for all of the
Context hierarchy objects sometime back. But this approach seemed to be
saving too much information on the database.
For example at some point there may be following context objects available in a running axis2 instance
Hi everyone,
A few days ago, I posted on a message on the user list regarding a
problem I was having with multipart boundaries being incorrect in Axis
1.4 (see copy of message below). To fix this problem, we commented
out a few lines of code in the class AttachmentsImpl.
The problem seems to be
Actually a small correction to my email.
It's incorrect to say that there is a bug within RPCMessageReceiver,java as it is only where the problem is visible. A closer look at the code reveals that
AxisMessage inAxisMessage = op.getMessage(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
inAxisMessage is
Hi,I have specified the RPCMessageReceiver as the Message Receiver in my services.xml.
The target method is "String greet(String name)"
When I send a request from my client, Axis2 throws an
java.lang.IllegalArgumentException: wrong number of arguments as the message receiver tries to invoked the
Hi Chamikara,
Thanks for the information.
Did you consider using java.io.Externalizable for the AXIS2 message context-related classes? (Having the work done by the AXIS2 objects would have simplified the actions that Sandesha needed to take in order to save the message context, so I am curious
[
http://issues.apache.org/jira/browse/AXIS-2402?page=comments#action_12424163 ]
ritesh tambat commented on AXIS-2402:
-
I am encountering the same problem. Digged a little further to find out that
the problem is with type of construct in th
When using MTOM, you define your binary content as xsd:base64binary
within your message element. At serialization time, MTOM automatically
extracts the binary data and attaches it in a separate MIME part. If
you want to predefine the type of binary content, then you can use the
xmime types defined
Excuse me Anne, but I have tried to use MTOM with document literal but I
didn´t know how. I don´t know how is the WSDL for support this.
When I have tried to use MTOM, the WSDL2Java have generated methods that
receive OMElement object as parameters. But I NEED that the stub has methods
that receiv
[ http://issues.apache.org/jira/browse/AXIS2-924?page=all ]
Nikhil Thaker updated AXIS2-924:
Attachment: JAXWSMessageReceiver.txt
I am attaching fix to this problem.
Current code creates a response context even if the AxisOperation has a
MessageExchan
As long as you're using Axis2, I suggest using MTOM rather than SwA.
Anne
On 7/28/06, Francisco Fernandez Velasco <[EMAIL PROTECTED]> wrote:
Thanks Rudolf. But seems that with Axis2 the generated Stub doesn´t have the
addAttachment method, so I don´t know how to send the image and I cannot
[
http://issues.apache.org/jira/browse/AXIS2-796?page=comments#action_12424095 ]
Mark Lepak commented on AXIS2-796:
--
I am having the same problem. When a WSDL is used that has a reletave
reference to a schema the schema is not found. The erro
I'm not familiar with the Handler concept. Can you please provide me with a link or an example on how to implement this? Also if there is a way of accessing the MessageContext in the Server class itself, that would be preferred? Thanks again!Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
[ http://issues.apache.org/jira/browse/AXIS2-891?page=all ]
Davanum Srinivas resolved AXIS2-891.
Resolution: Fixed
Applied a slightly modified version in rev 426539
thanks,
dims
> Allow the WS-Addressing action to be set, in the client, without als
I think Chamikaras approach of extracting the info into a seperate bean and then persisting it is a much cleaner approach and I belive it's less error prone as well.I think it's way better than trying to serialize the MessageContext.
Regards,RajithOn 7/28/06, Chamikara Jayalath <[EMAIL PROTECTED]>
Hi Ann,
I did some work on serializing message contexts and reconstructing
them. This was done as a part of the Sandesha2 Persistent Storage
Manager implementation. Unfortunately could not commit the code into
Apache due to a license issue (it was dependent on Hibernate). But will
try to host it s
Ability to load/init services during container startup
--
Key: AXIS2-940
URL: http://issues.apache.org/jira/browse/AXIS2-940
Project: Apache Axis 2.0 (Axis2)
Issue Type: Improvement
Tony,
Absolutely +1. Please open a jira enhancement issue.
thanks,
dims
On 7/28/06, Tony Dean <[EMAIL PROTECTED]> wrote:
I think users will want an option (load-on-startup=on|off) to either load
scope="application" services on container startup or upon the first request. I
personally would
Thanks Rudolf. But seems
that with Axis2 the generated Stub doesn´t have the addAttachment method, so I don´t
know how to send the image and I cannot use the DataHandler.
Thanks again. Regards
De: Rudolf Pailer
[mailto:[EMAIL PROTECTED]
Enviado el: viernes, 28 de julio
de 2
I think users will want an option (load-on-startup=on|off) to either load
scope="application" services on container startup or upon the first request. I
personally would want my service loaded and ready to go before the first
request is issued. Users will certainly be willing to take the hit w
Hello Francisco!
have a look at
http://www.mail-archive.com/axis-user@xml.apache.org/msg08732.html
regards
Rudolf
Von: Francisco Fernandez Velasco
[mailto:[EMAIL PROTECTED] Gesendet: Freitag, 28. Juli
2006 13:07An: axis-dev@ws.apache.orgBetreff: SwA Axis2
implementation swa
I need send an image to a webservice (document/literal) using SwA and not base64 enconding because of performance problems. I have defined the next WSDL following the WS-I Profile: http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schema
[ http://issues.apache.org/jira/browse/AXIS2-885?page=all ]
Brian DePradine updated AXIS2-885:
--
Attachment: newerpatch.txt
Hi,
Submitting a newer patch that sets the defaults in the existing endpoint
reference, if one exists. Otherwise, it creates a n
Client API does not remove OperationContext instances from configuration
context after MEP completes
Key: AXIS2-939
URL: http://issues.apache.org/jira/browse/AXIS
Hi Thilo;
Excellent and very valuable comments !!!
I tried to answer few of them pls see my comments below;
Thilo Frotscher wrote:
>
> Hello Axis2 team!
>
> I am trying to completely understand Axis2 phases, but while the concept
> seems simple at first glance, I find it actually quite confusin
25 matches
Mail list logo
