Hi Paul,
Do you know if with the Secure conversation i can force the client
to send the username token only the first time without having the login
operation, or
I still need this entry point?
Is there any usefull documentation on the rampart secure conv.
implementation?
Thanks,
Nencho
Craig
There are some options that might be interesting:
* JIBX allows you to bind to existing POJOs by specifying a simple binding file
* ADB has a helper mode where it will generate POJOs and leave the
XML gorp in other files.
* JAXB generates pretty clean nice POJOs.
Paul
On 5/2/07,
Nencho
Yes, the conversation initiation will happen on the first call - no
matter what operation.
I think there are good samples in Rampart. They are the best approach
to getting started with Rampart.
Paul
On 5/2/07, Nencho Lupanov [EMAIL PROTECTED] wrote:
Hi Paul,
Do you know if with the
Hi, we're fairly new to Axis2 in general but lately we've been writing a
small web service to test the Sandesha2 WS-RM stack with Axis2. We have
however two questions:
1. Is it normal that it takes about 15 seconds to make 10 synchronous
requests? We are just calling a simple Web service
Toon
I'm surprised you are getting those results. The Sandesha2 code isn't
tuned and the timing parameters are not optimized for fast exchange,
but without Sandesha2 the Axis2 calls should take about 100ms for 10
calls.
Do you have some sample code I can try?
Also I don't understand the
Hi list,
how can I specify something like the -Ebindingfile option with the ant
task ?
TIA and regards
Armin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
We have pom.xml for almost all modules.
All modules built using m2 are pushed to the SNAPSHOT repo.
There is at least 1 sample (jaxws-calculator) in 1.2 that uses m2
Please check the 1.2 final for WSDL2Java and AAR plugins that work and
report JIRA issues if they don't work as you expect them to.
Paul
Thanks for your reply. You're right about the timing, seems there was a
communication problem with my colleague, my appologies. I just tried it
without Sandesha and it is indeed quite fast.
To get back to the listener question what I mean is the seperate listener
logic which comes with
I don't think the ant task has ever been updated to support -Exxx data
binding extension options. You can just use WSDL2Java directly, though,
with an Ant javac:
java classpathref=axis-classpath fork=true
classname=org.apache.axis2.wsdl.WSDL2Java
!-- -o parameter sets the
Toon,
as you said the listener uses port 6060 by default, but by providing a
custom configuration context you can change. Furthermore, you can use
the same configuration context across different ServiceClient(s) or even
use the same ServiceClient across different invocations.
Michele
On Wed,
==
Axis2 book
==
I am pleased to announce that our new Axis2 book was published
last week. It contains nearly 600 pages and covers all aspects
of Web Service development using Axis2. Topics include:
- Web Service fundamentals (SOAP, WSDL, Code-First vs. Contract-First)
- First
Toon
Two things:
1) you can modify the default Sandesha timing parameters by editing
the module.xml inside META-INF in sandesha2.mar. The default timing
parameters are:
RetransmissionInterval 6s (6000ms)
InactivityTimeout 60s
2) When you do setUseSeparateListener, Axis2 does not spawn a new
Also I want to secure my message also and I found that Rampart and MTOM have
memory problems.
Not that I know.. Can you please be more specific and report these
problems with samples or test cases, so that we can fix if there is
any..
- When I used ADB and MTOM I could see that if I don't
Congratulations!
I was so impressed I blogged it!
Paul
On 5/2/07, Thilo Frotscher [EMAIL PROTECTED] wrote:
==
Axis2 book
==
I am pleased to announce that our new Axis2 book was published
last week. It contains nearly 600 pages and covers all aspects
of Web Service
Dennis,
pity ! Thank you, anyway.
Regards
Armin
Dennis Sosnoski wrote:
I don't think the ant task has ever been updated to support -Exxx data
binding extension options. You can just use WSDL2Java directly,
though, with an Ant javac:
java classpathref=axis-classpath fork=true
Hi All ,
I am trying the rampart sample that comes with the distro.
I am going with sample01, only that i wanted it to be slightly different:
I change the sp:IncludeToken attribute, so instead of:
sp:SignedSupportingTokens xmlns:sp=
http://schemas.xmlsoap.org/ws/2005/07/securitypolicy;
Hi
I just downloaded eclipse 3.2.1 and was trying to create a web service using
WST plugin,
I think this plugin uses axis 1.3,
does anyone know how to upgrade it to use axis 2?
Is there any document explaining this
Ashish
Hello,
I'm new to Axis. I'm using the latest version, 1.2, and I've created a
simple web service that takes three strings and returns a string.
I created a client using wsdl2java. It works fine, but it creates three
source files that are 5M in size. Is this expected behaviour, or is it
a clue
Hi,
I've been working with a project that was built around Axis 1.2. The
source repository contains only the Axis-generated class files, no
source code. So I've had to do some guesswork. Would like to upgrade to
Axis 2 but there's a bit I haven't figured out yet. This project
contains a number of
I believe we are throwing better exceptions now...if you post the wsdl
in a bug report, we can take a look to confirm that it is indeed an
rpc/encoded wsdl which we don't support.
thanks,
dims
On 5/1/07, wolverine my [EMAIL PROTECTED] wrote:
Hi!
I encounter the following error when tried to
Hi Chamikara,
Upon further review, I don't believe this is a Sandesha2 issue. The
operation is generated without a CallbackReceiver value set in the ADB
generated stub. If I set a default CallbackReceiver in my client code,
everything works fine. Maybe the operation should have a default
:
Thanks, there was a problem with castor -1.1 jar and/or classpath.
I downloaded Castor-1.1.1 jars and put this time all the downloaded jars
into the classpath and then ant generate.service worked OK.
The first time i had only castor-1.1.jar in classpath.
however ant run.client (command from
Thanks, but I resolved the issue: see code below*
Craig Hickman, Sr. Architect ADP
Working with the previous Axis1 I was able to write a very easy
implementaion for a ServiceRouter and ServiceProcessor that worked for
exposing all my services through a properties lookup and hiding the Axis1
Can't answer your second question, but the first one may be no. The
bottom of page 1 of the below article states Managing a SOAP session
requires you to engage addressing modules on both the server side and
client side:
http://www.developer.com/java/web/article.php/3620661
Hopefully a more
You can manage the sessions yourself by generating your own token via a
return value and mandate the passing of it back in a future calls, but then
you have to manage the token yourself. That does have the advantage of after
a few days work its stable and flexible. I've done that with both
I got this working.
For posterity's sake:
you need to have a 'get' and 'set' for each param in your bean.
instead of
class MyBean
{
public String str0;
public int n0;
}
use
class MyBean
{
private String str0;
private int n0;
public String getStr() { return str0;
Hi Jony ,
That was one of the issue with annogen, but we have fixed the issue in 1.2
Please try with Axis2 1.2.
Thanks
Deepal
jony wrote:
I got this working.
For posterity's sake:
you need to have a 'get' and 'set' for each param in your bean.
instead of
class MyBean
{
public String
I'm using axis2 v1.1.1
I'm embedding axis2 in my webapp following the example shown here:
http://www.redhat.com/magazine/021jul06/features/apache_axis2/
I'm following what the article calls Use Case 2. I've added the Axis
servlet to my web.xml:
?xml version=1.0 encoding=UTF-8?
web-app
At the Maven2 repository at
http://repo1.maven.org/maven2/org/apache/axis2/axis2/, all dependencies get
properly placed into my lib directory, but the dependencies apart from axis2
itself don't get updated in the Eclipse .classpath.
Have dependencies like axiom only been declared as provided or
Hi
I have a WSDL file, and i created all the java classes using WSDL2Java, and
was writing a client program as below,
MapsLimsTransactionsLocator locator = new MapsLimsTransactionsLocator();
MapsLimsTransactionsBindingStub stub = new
MapsLimsTransactionsBindingStub(new URL(
It has something to do with SOAPVersion
ftp://www6.software.ibm.com/software/developer/library/ws-reliablemessaging200403.pdf
the good news is that if you're still using Axis 1.x you can override the
SingleSOAPVersion attribute with the correct version(SOAP 1.1 version that wont
produce these
(Part 2)
public static AxisService createClientSideAxisService(Definition
wsdlDefinition,
QName wsdlServiceName,
String portName,
I am using Axis 1.4 and getting the above error.
Thanks,
Prasad
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I filed a JIRA concerning that subject:
http://issues.apache.org/jira/browse/AXIS2-2600
Ulf
- Original Message -
From: asinghal123 [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Tuesday, May 01, 2007 7:25 PM
Subject: targetnamespace hard-coded in code generated through WSDL2Java
This may be related to AXIOM internally (I don't know if AXIOM is used
in Axis 1, however). I googled the error message and it seems like the
only thing that could cause that error message to occur (search on The
attachments stream within [1]) is that you called *both* getPart() and
The xsd:any (there's only one) will map to a single OMElement -- which
may in turn contain anything. Therefore, the xsd:any is the last
element (only element) in your sequence).
Anne
On 5/2/07, no spam [EMAIL PROTECTED] wrote:
ok, but this seems to be thinking of an xsd:any element as the
When you have a project that depends on the axis2 artifact and you do a mvn
deploy, all of the Axis2 JARs (e.g. axis2-adb, axis2-codegen, etc...) get
imported automatically into the WAR file as specified in my pom.xml, which
I'd expect to happen.
Why, though, do these JARs not get stored in my
Axis2 Eclipse plug-in is available here
http://ws.apache.org/axis2/tools/index.html which can used now.
From: Lahiru Sandakith [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 02, 2007 10:24 PM
To: axis-user@ws.apache.org
Subject: Re: axis 2 and eclipse
38 matches
Mail list logo