Anne Thomas Manes wrote:
I trust you recognize
the value of clean separation between your application object model
and a database data model and the DAO design pattern.
Of course I do. My point is that I wanna write the interface layer
of my system in Java, not int WSDL, of course for the
Anne Thomas Manes wrote:
If your goal is point-to-point integration between a single client and
server, then the code-first development model is fine. But if your
goal is to implement a service-oriented system, enable reuse of
capabilities, reduce redundancy, and increase flexibility and
Fortunately axis2 guys improve the POJO deployment, they fixed some
things in 1.2 (also added some
annotations support), but it still requires somo work to be fully
functional.
Jarek,
When you get a chance, please let us know what breaks or does not work
via JIRA.
See 2603 and 1754. As a
Dennis Sosnoski wrote:
I haven't tried out the Axis2 POJO support, but in general anything
you do using POJOs directly is going to be both inflexible and very
limited in terms of the XML support.
With all respect, xml here is the tool, not the purpose. I would like to
expose my serwice
Glen Mazza wrote:
I believe that's called contract last development
No, IMO it depends on how you (miss)use the concept of contract or
interface,
not on which language you use to write the contract. I would be very
glad to be able to write the contract in Java and expose it as wsdl via
axis2
Dennis Sosnoski wrote:
But generally the idea of deploying POJOs directly is a very limited
approach, at best only suitable for small applications, and if you're
doing anything substantial you're probably going to need to start
controlling the XML conversions at some point.
No, why ? Do
Davanum Srinivas wrote:
When you get a chance, please let us know what breaks or does not work
via JIRA.
Sure, in a week or two I plan to have it analysed.
J.K.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
If I declare a (non-void) service method to throw an exception,
the resulting wsdl describes the corresponding exception
type as anyType, like this:
xs:complexType
xs:sequence
xs:element name=getWalletFault type=xs:anyType /
/xs:sequence
/xs:complexType
Is there a way to
pat wrote:
In case of axis2 1.1.1 this should help:
auth.setPreemptiveAuthentication(true);
The lack of documentation is disappointing , isn't it ...?
J.K.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
John Kristian wrote:
Is it sufficient to place Axis2 .jar files in the WEB-INF/lib of a web
application? (Assuming the web application is the only user of Axis2.)
Or must they go in Tomcat's global class loader?
Yes, WEB-INF/lib is sufficient. Axis2 (at least 1.1.1 which I use) comes
with
Glen Mazza wrote:
In Tomcat 5.5.x, at least, there is a common/lib (shared/lib is also OK)
directory you can place those two jars in, and they should be accessible
to the axis2.war (and its underlying services) upon restart of Tomcat.
Google for the two jar files you need--I think they come
I deploy a POJO service, which operates on records that contain fields
created from java.util.Date. In the resulting (automatically generated)
WSDL, those fields are defined like this:
xs:element name=statusLastUpdated type=xs:dateTime/
But when the service returns object with such a field set
Rainer Menzner wrote:
Hi,
my web service reproducibly runs out of Java heap space when I test it
under high load. It is most probably not a programming error nor is it
a bug in axis. I'm passing large files which then are processed by the
request.
Can I increase the heap space when
Krishnamoorthy J (HCL Financial Services) wrote:
Hi,
What is the option similar to wsdlFile property of service-config.wsdd
(Axis 1.4) in Axis 2?
How to get the custom WSDL file displayed instead of Axis generated
WSDL in Axis2 1.1.1?
Put the wsdl in the META-INF folder of the
I'm trying to create a web service from POJO and my own WSDL -
everything is is ok except one thing: I can't make axis use
the custom WSDL. The WSDL is actually the one automatically
generated by axis itsself with a few minor changes (just some
wsdl:documentation sections as for now). I put the
[EMAIL PROTECTED] wrote:
note The full stack trace of the root cause is available in the Apache To=
mcat/6.0.9 logs.
Have you followed this hint ?
My guess - you may lack log4j, but the logs shall tell you what's happening.
And I think the native library has nothing to do with your
Jarek Kucypera wrote:
Ok, I must put following parameter inside the service tag:
parameter name=useOriginalwsdltrue/parameter
g-sus, is there any comprehensive documentation of services.xml ?
J.K.
-
To unsubscribe, e-mail
Thomas michelbach wrote:
Hi,
I'm trying to pass the Authorization header via HTTP.
Is there a way to do that?
Yes there is, set this flag in the authenticator:
auth.setPreemptiveAuthentication(true);
J.K.
-
To
I created my service from POJO and now I need to parametrize the
resulting sevice and the WSDL: first I need to incject some textual
documentation about complex data types, it's fields and particualr port
types' methods, as wsdl:documentation tags. And second, I want to
influence the nillable
Derek Weeks wrote:
This constant does not appear to exist in Axis2 version 1.1 or 1.1.1.
Should the
constant be one of these?
Following is how it works for me with axis2 1.1.1
HttpTransportProperties.Authenticator auth = new
HttpTransportProperties.Authenticator();
Can somebody please show me a working example of client
side basic authentication with axis2 1.1.1 ?
Below is my current code (xmlbeans client) which does not work:
HttpTransportProperties.Authenticator auth = new
HttpTransportProperties.Authenticator();
auth.setUsername(test_user);
Hello everyone
I've moved from axis1 to axis2 1.1.1 lately and here are two issues I
encountered using wsdl2java commandline tool:
1) I fail to generate neither server nor client, when WSDL contains
include statement. To be specific, the WSDL is divided into two parts:
the main one describes
22 matches
Mail list logo
