Hi,
I have been trying to consume an Axis2 web service that
returns binary data in base64 from a .NET client, and the
client is complaining about invalid characters in the
base64 string. I took a look at the string and actually
the base64 string is including '=' chars in the middle of
the st
I am having a good bit of success using the daily build from Monday.
I will update to a more recent one, next Monday.
In my test client, I am getting an error that I have not seen before:
Caught Throwable exception in runPointsCalculator:
java.lang.ExceptionInInitializerErrorjava.lang.Ex
ception
Hi Chinthaka,
thanks for your motivation ;)
Apologies, this is the first web service I implement, and therefor the first
touch with axis2. Everybody starts some time!
I really know that I have to learn a lot about axis2 and its concepts, and I'm
really willing to.
I came up with this issue at th
Please use the doc's in the download zip/tar till we fix the problem.
Yes, we have a problem with updating the version #'s in all the
html's. Hopefully we'll do better next time around. Sorry for the
inconvenience.
-- dims
On 6/16/06, knly browne <[EMAIL PROTECTED]> wrote:
Because the axis team
Hi,
Does any body code to convert and OMElement to a JDOM element and
vicevrese ?
Thanks in advance !
-Marcel Casado
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Ok, I must just be doing something silly but neither I nor
another experienced java/unix consultant can see the solution yet. Here’s
the problem:
Simply to avoid having to copy my java package dirs from apache-tomcat-5.5.17/webapps/utdEditor/WEB-INF/classes
to the equivalent axis classe
I have created proxy by using AXIS
hoever I am getting error
javax.net.ssl.SSLHandshakeException: unknown certificate
How I can resolve this error
Because the axis team doesn't have time to provide the means where developers understand the changes made to their API, and see to it that their solution is understood, NO these experts are just astronauts who code away and forget about use, or maybe its just made for them, who knows... but axis te
I'm getting the following error when I try to access
http://127.0.0.1:8080/axis/ via my browser. I'm using Axis 1.4 and
Tomcat 5.5. Does anyone have any idea what my problem is?
I had Axis working successfully a while back, then they re-imaged my
machine and I had to re-install everything. I be
robert lazarski wrote:
Currently I'm integrating an EJB app with Axis2 - thankfully as any
tomcat / servlet container web layer would. However, I came very close
to having to implement these services as EJB, which would have
required either JAX-WS or Axis 1.x , as Axis2 just isn't an option.
> Please post the WSDL
I am attaching it here.
--
Neil Aggarwal, JAMM Consulting, (214)986-3533, www.JAMMConsulting.com
FREE! Valuable info on how your business can reduce operating costs by
17% or more in 6 months or less! http://newsletter.JAMMConsulting.com
FileUpload.wsdl
Description: Bina
Hello:
I want to build a tool that has to talk to different webservices by
taking in the wsdl and invoke the webservcie by getting the relevant
inputs.
I have just started to look into axis. Wondering if there is any
documentation that talks about how to do the integration with axis2.
Thanks,
cbe
I have solved this one now. In case
someone else gets the same blank page, the solution is dirt-simple, but the
reasons are somewhat subtle:
Even though my JDK is at 1.5 and the happyaxis.jsp
shows that (which is what was fooling me):
Examining
System Properties
java.runtime.name=Java
While I agree completely, I have in fact been _required_ to implement
stateless session EJB's as Web Services using Axis 1.x under JBoss. The
idea is that you can do your DB transactions and rollbacks inside those
services, while hooking the service to a ejb-ref that is _stateful_
which can have st
The formal release came out quite recently, but the build was produced quite a while ago, and it's the one used in Geronimo.On 6/16/06,
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
yes but axis 1.4 was released very recently, in april 2006,
it is not too risky to use it in production ?
Mi
1- The service is defined as document/literal, but the SOAP request is using SOAP Encoding.2- Axis2 does not support SOAP Encoding.3- The WSDL has errors -- you must remove the namespace attributes from the and definitions.
AnneOn 6/16/06, Jan Bauer Nielsen <[EMAIL PROTECTED]> wrote:
Hi.Can anyo
When you do REST invocation, we do not look at the SOAPAction header or
WS-A headers in the server side. So the server side code couldn't
dispatch to the proper operation.
But if you change the toEpr to
http://localhost:7001/axis2/rest/MyService/MyAction, then it should
work. I presume MyAction is
GOBE HOBONA wrote:
>
> My interpretation of the original question was "why does Axis2 not
> support such features of the J2EE as Enterprise Java Beans (EJB 3.0
> specifically), annotations, persistence etc.?"
Axis2 supporting EJBs? My mind started malfunctioning :).
"..The approach of taking a J
[EMAIL PROTECTED] wrote:
> ok, filling my own thread all alone.
> Maybe my conclusions help somebody out there. This is what I realized:
>
> - The all-dominant hint was to work with the incoming MessageContext. In all
> my further trials I worked with the outgoing MessageContext, because I
> th
On Friday 16 June 2006 21:07, [EMAIL PROTECTED] wrote:
> Hi,
>
> I guess if you use the stubs generated using WSDL2Java then there is
> nothing much to do. Set the trust store property and trust store
> password property before invoking the client. Just leave the other
> properties as default it se
Hi all,
I'm uploading a file to a web service through an OperationClient (the
MEP is out-only). If I configure the operation client as
ANON_OUT_ONLY_OP it works fine, while if I configure it as
ANON_ROBUST_OUT_ONLY_OP the service executes correctly, however the
client gets:
org.apache.axis2.AxisF
Awesome, that's exactly what I was looking for. I generated a simple, unbloated service and client. The '-d none' should be in the help text for wsdl2java, but it isn't. Thanks!Ajith Ranabahu <[EMAIL PROTECTED]> wrote: Hi,Do a -d none to *not* databind.AjithOn 6/16/06, Andrew B <[EMAIL PROTECTED]>
My interpretation of the original question was "why does Axis2 not support
such features of the J2EE as Enterprise Java Beans (EJB 3.0 specifically),
annotations, persistence etc.?"
Personally, I think Axis2 offers a more transparent view of what is going on
"behind the scenes" than the J2EE
ok, filling my own thread all alone.
Maybe my conclusions help somebody out there. This is what I realized:
- The all-dominant hint was to work with the incoming MessageContext. In all my
further trials I worked with the outgoing MessageContext, because I thought,
that's what gets back to the c
Hi Tony,
> 1. OK, so Axis2 was designed with wsdl 2.0 in mind. And, thus you have
> a single input document and a single output document. We will most
> likely be interoperating with wsdl 1.1 services for a long while so I
> must remain compliant in my client application of choice.
Absolutely
"As I had mentioned, I had hoped to do this using HttpSession, but I
don't think it's possible. I really have no knowledge of SOAP or any of
the "guts" of Axis.. so really want to just use it to serve my Web
Service while I worry about the business logic of what the service
actually is supposed to
Hi !
why the official documentation is about axis 1.2 and the last release is
1.4 ?
Is it because the axis 1.2 version is considered by developpers as the
only one
stable ? Where can I then find the documentation for the 1.4 version ?
kind regards,
Michel
Michel Lequim
-Original Messa
I know this is an Axis user list and this might not be the right place to ask such question but I would like to hear your opinion regarding Axis, Burlap/Hessian, which one would you chose and why?. It seems to me that Hessian binary protocol might be lighter than XML web services but don't know if
Hi,
I guess if you use the stubs generated using WSDL2Java then there is nothing
much to do.
Set the trust store property and trust store password property before invoking
the client. Just leave the other properties as default it self.
System.setProperty("javax.net.ssl.trustStore",
"c
Eclipse's compiler, called JDT. Quoted from Tomcat's release notes:
In addition, Tomcat 5.5 uses the Eclipse JDT Java compiler for compiling
JSP pages. This means you no longer need to have the complete
Java Development Kit (JDK) to run Tomcat, but a Java Runtime Environment
(JRE) is suffici
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
[EMAIL PROTECTED] wrote:
> Hi, axis 1 & 2 work in a J2EE environment
I believe the original question was a misunderstanding of what J2EE
and axis are or do.
JBoss is a web server that implements the J2EE standard, but also
includes axis so
Hi Vali,
Axis 1.2 does not support serialization of Set attributes. You will have
to convert them to arrays.
While you stick to RPC/encoded style you will have no problem.
Document/literal does not allow references, and so it forgives loops in
your graph. This means that your "parent" field
Hi,
Do a -d none to *not* databind.
Ajith
On 6/16/06, Andrew B <[EMAIL PROTECTED]> wrote:
Thanks. Do I do this by just not specifying a data binding (-d) on
WSDL2Java? Or do I not use WSDL2Java at all in that case?
Also, if I use RawXMLProvider, can the message still handle binary
attachments
Thanks!
Now I just have one question left: if we want to customize verification to
perform additional checks, what is the best way to do it? For example, if we
want to check the signer certificate's validity dates and revocation
status... Should we use an additional handler ?
From: "Ruchith
Yes.. You can use MTOM with RawXMLInOutMessageReciever.
I'm not sure about the parameters to use WSDL2Java. IIRC it's possible to generate OM level (RawXML) code using WSDL2Java.
If your WSDL us simply you might be able to survive without using WSDL2Java.
~Thilina
On 6/16/06, Andrew B <[EMAI
Hi, axis 1 & 2 work in a J2EE environment
Michel Lequim
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
On Behalf Of Andrew Lindley
Sent: Friday, June 16, 2006 11:54 AM
To: axis-user@ws.apache.org
Subject: [AXIS2] J2EE Support
I was just wondering, why neither AXIS
I was just wondering, why neither AXIS, nor AXIS2 do support J2EE - is
this correct?
JBoss e.g. has this feature.
Is this information correct?
thanks,
--
---
Mag. Andrew Lindley
ARC Seibersdorf research GmbH
Research Studios Austria
Studio Digital Memory Engineering
Thurngasse 8/20, A-1090 Wie
Thanks a lot to you all!
bye :-)
monica
Hi All,
I have a few queries regarding Axis:
1. Does Axis 1.4 support MTOM and XOP?
2. How can I use JAXB 2.0 with Axis 1.4?
3. What is the road map for Axis 1.x? Is there any active development
going on or is everyone expected to move to Axis2.
4. Release notes for Axis 1.4
Sorry, apologies to me.
Chinthaka already commented on this:
http://marc.theaimsgroup.com/?l=axis-dev&m=115039522426623&w=2
> -Ursprüngliche Nachricht-
> Von: axis-user@ws.apache.org
> Gesendet: 15.06.06 23:53:28
> An: axis-user@ws.apache.org
> Betreff: [axis2] problem with Userexception
what is Tomcat Compiler ?
-Original Message-
From: Seak, Teng-Fong [mailto:[EMAIL PROTECTED]
Sent: Friday, June 16, 2006 2:11 PM
To: axis-user@ws.apache.org
Subject: Re: How to make Axis use Tomcat's compiler?
Still no answer? Are Axis's developers reading this mailing-list?
Seak,
Hi all,
is it possible to access/modify the message SOAP header by using a
ServiceClient only (i.e. without creating an OperationClient object)?
Thanks,
Michele
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands
Hi.
Can anyone explain to me why the following request gives me an internal
server error?
I have attached the wsdl file.
http://www.w3.org/2001/XMLSchema-instance";
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
soap:encod
Still no answer? Are Axis's developers reading this mailing-list?
Seak, Teng-Fong wrote:
Hello everybody,
I don't know if this post would be considered off-topic; I've posted
it to Tomcat several days ago but without any answer.
I'm trying to use Web service in Tomcat, ie with Axis.
sorry, I made a mistake in the last mail, here is what I wanted to say:
Hi,
we have the same problem of choosing a version of axis. the
timeout setting that does not work is one of our main reason to not
choose axis 2, the second is
that we fear that more bugs will be discovered in the future
yes but axis 1.4 was released very recently, in april 2006,
it is not too risky to use it in production ?
Michel Lequim
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Anne Thomas ManesSent: Friday, June 16, 2006 2:22
AMTo: axis-user@ws.apache.orgSubject: Re: [axis1]
Hi,
we have the same problem of choosing a version of axis for axis 2. the
timeout setting that does
not work is one of our main reason to not choose axis 2, the second is
that we fear that more bugs
will be discovered in the future because it is rather new.
have you find a way to make the t
47 matches
Mail list logo
