AW: sesion managment, scope=soapsession
Hi Robert
But when I have to implement finding the correswponding instance of a class (an
object) myself, belonging to the incoming session request object, then I would
consider axis2-1.1 not beeing able to keep sessions appart from each other. And
again back to what I write. Why is the service group context id destroyed when
a second client calls MyService in scope=soapsession? Which makes in gact
client #1 fail with invalid service group context id
When I read literatur about tomcat, the session object is where instance data
can be stored, and it is up to tomcat to return the correct session object from
request.getSession(true). Does axis2-1.1 not support that?
Also, where can I learn about how WS-addressing supports sessions? Or is
WS-addressing not supporting sessions? Does WS-addressing not supporting the
addressing to unique session based instances of a service class object? (where
each session has its unique instance of a service class object).
What is the correct approach/code to have for each session exactly one instance
of a service class object established?
Josef
-Ursprüngliche Nachricht-
Von: robert lazarski [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 30. November 2006 13:12
An: axis-user@ws.apache.org
Betreff: Re: sesion managment, scope=soapsession
Stadelmann, Deepal describes well what Axis2 does and my recommendation is to
use axis2 for your session management if possible. You may find, however, that
it does not match your business case.
If it does not, you may consider rolling your own via something like UUID -
which WS-Addressing does in its own way - and your own ehcache or the like
storage. Its pretty easy and I've done it for many clients. The idea is simple:
you login, pass back a UUID, pass it back in for subsequent calls and use it as
the key to put / get your objects out of ehcache. Logout would invalidate the
session which ehcache can do itself after a choosen timeout. ehcache is used
with Hibernate and is simple and effective. Oh yeah - just ignore the idea if
that doesn't fit what you need.
HTH,
Robert
On 11/29/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
Hi Stadelmann ;
pls see my comments below;
Hi session-managers,
I'm running my client and server with modules addressing-1.1, logging,
soapmonitor-1.1 engaged and have set scope=soapsession
MyService.java got the additional methods
public void init(ServiceContext sCtx) {
this.sc = sCtx;
this.log.info(sc.toString()+ init() called );
}
public void destroy(ServiceContext sCtx) {
if(!this.sc.toString().equals(sCtx.toString())){
this.log.error(ServiceContext on init() and destroy() not
equal in );
}
this.log.info(sc.toString()+ destroy() called );
}
public void setOperationContext(OperationContext oCtx) {
this.oc = oCtx;
this.log.info(oc.toString()+ setOperationContext() called
);
}
We have removed this method (it was there in Axis2 1.0 , but we removed
that from Axis2 1.1), so we are no longer going to call this method . If
you want to get access to operation context , then you can do that as
follows;
MessageContext msgCtx = MessageContext.getCurrentContext ();
from msgCtx you can access any of the contexts you want .
I start client #1 which has the effect that MyService.init() is
called; so far so right!
Client #1 then loops and sends continously messages to MyService.echo()
I start client #2 which has the effect that MyService.destroy() is
called followed by MyService.init()
This has the effect that client #1 fails with an invalid group
context id exception
Is this a bug?
Nope. That is not a bug , soapsession has concept of time out , so once
it gets time out you will get that exception.
I have studied the architecture of axis2 and have drilled down in code
and I came down to where alle the service objects are finally called
at invokeBusinessLogic (inCtx, outCtx) with it's call to
method.invoke ( . . . )
good .
All reading in code and documentation did not answer my questions ***
How does Axis2 manage / support long-lasting-sessions to
server-objects bound to this session ? ***
Do I have to implement this myself on top of Axis2?
No , you can get support from Axis2 session management. If you have
Axis2 1.1 distribution there you can find a sample called Library sample
, which help you to understand most of the important factors.
1. I want to have a client-object exchanging OMElements with it's
service-class-object.
yes , doable
2. when the client starts the session, up on receiving the first
message, a unique instance of the service-class-object shall be
created at the server.
yes , that is what happen.
2a) 20 client objects shall mean we have instantiated 20
dedicated-server-objects
yes.
3. as long as this 20 service-class-object exists, in fact 20
wrapper-object to 20 external server
AW: sesion managment, scope=soapsession
Hi Deepal
pls see my coment below
-Ursprüngliche Nachricht-
Von: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 29. November 2006 17:27
An: axis-user@ws.apache.org
Betreff: Re: sesion managment, scope=soapsession
Hi Stadelmann ;
pls see my comments below;
Hi session-managers,
I'm running my client and server with modules addressing-1.1, logging,
soapmonitor-1.1 engaged and have set scope=soapsession
MyService.java got the additional methods
public void init(ServiceContext sCtx) {
this.sc = sCtx;
this.log.info(sc.toString()+ init() called );
}
public void destroy(ServiceContext sCtx) {
if(!this.sc.toString().equals(sCtx.toString())){
this.log.error(ServiceContext on init() and destroy() not
equal in );
}
this.log.info(sc.toString()+ destroy() called );
}
public void setOperationContext(OperationContext oCtx) {
this.oc = oCtx;
this.log.info(oc.toString()+ setOperationContext() called
);
}
We have removed this method (it was there in Axis2 1.0 , but we removed
that from Axis2 1.1), so we are no longer going to call this method . If
you want to get access to operation context , then you can do that as
follows;
MessageContext msgCtx = MessageContext.getCurrentContext();
from msgCtx you can access any of the contexts you want .
OK - i take this into consideration
I start client #1 which has the effect that MyService.init() is
called; so far so right!
Client #1 then loops and sends continously messages to MyService.echo()
I start client #2 which has the effect that MyService.destroy() is
called followed by MyService.init()
This has the effect that client #1 fails with an invalid group
context id exception
Is this a bug?
Nope. That is not a bug , soapsession has concept of time out , so once
it gets time out you will get that exception.
My client #1 runs continously, and sends arround 40 msg a second to the server.
When the second client starts, cline t#1 is still sending messages and so we do
not have a time-out condition. client #1 never times out.
BUT as I decribe, using the code shown, when client #2 starts
MyService.destroy()
is called followed by MyService.init() which has the effect that client #1
fails
thereafter with an invalid group context id exception
I have studied the architecture of axis2 and have drilled down in code
and I came down to where alle the service objects are finally called
at invokeBusinessLogic (inCtx, outCtx) with it's call to
method.invoke ( . . . )
good .
All reading in code and documentation did not answer my questions ***
How does Axis2 manage / support long-lasting-sessions to
server-objects bound to this session ? ***
Do I have to implement this myself on top of Axis2?
No , you can get support from Axis2 session management. If you have
Axis2 1.1 distribution there you can find a sample called Library sample
, which help you to understand most of the important factors.
I would appreciate an example on how to have a scenario as I describe.
When I read literature about tomcat, retriving a session object from the
clients request object, it seems that internals are figuring out which client
is calling and the rigth session object which acts as data store for the
session is returned/created.
How is that with AXIS2-1.1?
1. I want to have a client-object exchanging OMElements with it's
service-class-object.
yes , doable
2. when the client starts the session, up on receiving the first
message, a unique instance of the service-class-object shall be
created at the server.
yes , that is what happen.
When the MyService Object gets created I store the creation time for the
instance in a instance variable. And when multiple clients run without
scope=soapsession set, all clients return the same time stamp. So that
means for me! client #1 makes axis2 creating a first instance of a class,
and places the creation timestamp.
This is called an object, and client #2 sends his message to the same instance
the same object. When the call to client 2 returns, client #2 finds the same
time stamp as client #1 has. But when client #2 starts 10 seconds after client
#1,
I would expect that client #2 has a different object-creation-timestamp
then client #1 unless we talk to the same instance (which I cant use).
Josef
2a) 20 client objects shall mean we have instantiated 20
dedicated-server-objects
yes.
3. as long as this 20 service-class-object exists, in fact 20
wrapper-object to 20 external server process, and as long as this 20
external process exist it shall not be allowed that one single
service-class-object dies. for that reasioon the server-objects must
exist until it's dedicated client terminates the session esplicitly by
calling logout() on the server-object.
Nope , the behavior of soapsession is not like that. It has a notion of
time out. If the user does
Axis2 and WSDL20
Hi all , Does Aixs2 plan to support WSDL20 ? Currently is there any experimental stuff related to WSDL20? Thanks Jim
Re: [axis2] where to put native libraries?
Hi Paul, normally the shared libs is in the same folder of the jar file which uses them, so I guess it's a class loader issues. Michele Paul Fremantle wrote: Where is the shared lib normally? Certainly Axis2 is doing its own classloader. Paul On 12/10/06, Michele Mazzucco [EMAIL PROTECTED] wrote: Hi Paul, thanks for the prompt reply. Your guess looks like right, but why if I use that library from code non embedded in tomcat/axis2 it works fine without specifying anything? Thanks, Michele Paul Fremantle wrote: I guess you would need them in the PATH or LIBPATH that Axis2 has. I don't think you can put them in an AAR file. Paul On 12/10/06, Michele Mazzucco [EMAIL PROTECTED] wrote: Hi all, My web service is using a third party library which includes some native code (.so, .dll, etc.). I've put everything (jar and native libraries) in WEB-INF/lib of my aar file, however I get a UnsatisfiedLinkError. Any clue? Thanks, Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2]Re:[Sandesha2] Apache Sandesha2 1.1 released
Hi, Does anyone have any information on performance comparison between Sandesha with JMS for async messaging? I have not be able to find any benchmark data comparing different RM implementations and JMS. Any comment or information will be much appreciated. falom Chamikara Jayalath [EMAIL PROTECTED] 写道： Hi All, We are proud to announce the 1.1 release of Apache Sandesha2, WS-ReliableMessaging implementation for Apache Axis2. You can download this release from our official site at http://ws.apache.org/sandesha/sandesha2/ This release should be used with the Axis2 1.1 distribution which could be obtained from http://ws.apache.org/axis2/download.cgi Features of this release include: 1. Support for WS-ReliableMessaging in both client side and server side of Axis2. (according the the WS-ReliableMessaging specification February 2005). 2. Support upto the CD4 of the WSRM 1.1 specification being developed under OASIS. 3. Pluggable storage framework. 4. Configurable delivery assurances. In-order exactly once delivery assurance is guaranteed. Users can also instruct the system to stop ordering (this will give a higher performance). 5. Support for both SOAP 1.1 and 1.2. 6. Mechanisms to support WS-ReliableMessaging policy assertions in both server side and the client side. 7. Improved client API, which provides features for both general and advance users. 8. Sandesha Report functionality to get status information on Sandesha2 system and its sequences. 9. SandeshaListner feature to get informed when specific events happen (for example when a fault is retrieved or when a sequence times out). 10. Support for SecureConversation+RM 11. Test cases to test RM scenarios. 12. Documentation Please use this release and send your comments to [EMAIL PROTECTED] Thank you, Sandesha2 team - 抢注雅虎免费邮箱-3.5G容量，20M附件！
Re: [Axis2 v1.1]
Hi, Since your locale is DE you you will have to have errors_de.properties file available in the classpath in the org.apache.rampart package. Simply copy the content of this file [1] into the errors_de.properties file. Optionally you can translate messages :-) Thanks, Ruchith [1] https://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_1/modules/security/src/org/apache/rampart/errors.properties On 12/11/06, Daniel Wehrle [EMAIL PROTECTED] wrote: Hi, I tried to do a little Axis2 sample on my German Windows. I connect to a .Net web service using wssecurity, so I use rampart for the UsernameToken. But by sending a message I got an stack trace ending with: Caused by: _java.lang.RuntimeException_: Can't find bundle for base name org.apache.rampart.errors, locale de_DE at org.apache.rampart.RampartException.clinit(_RampartException.java:36_) What I am doing wrong? Thanks -- Daniel Wehrle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- www.ruchith.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: sesion managment, scope=soapsession
Hi Robert
I really like axis2-1.1 managing my sessions if this is foreseen and works. But
as you know, my sessions must each talk in a 1:1 relationship to a unique
instance of a service object. A service object which wraps my external server
and has a CORBA IOR to it, wheras CORBA IOR's are unique to each server
instantiated. A server is in this case an OpenVMS process serving exact 1
client session.
If axis2-1.1 can manage that, what session scope to I need? If as as said in a
reply to my problems, scope=soapsession fals short.
Given I am desiding to do it mysef as you recommend, a good idee if axis2 fails
to support such sessions correctly, would you then please be so kind and tell
me what you mean with ehcache? Maybe you can paste in a working client and a
working server code example for the sack of the community? Or maybe plaste that
into the official axis2-1.1 documentation. I am missing that working example
and I am running now some weeks behind project schedule.
In any case, thank you for your help.
Josef
-Ursprüngliche Nachricht-
Von: robert lazarski [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 30. November 2006 13:12
An: axis-user@ws.apache.org
Betreff: Re: sesion managment, scope=soapsession
Stadelmann, Deepal describes well what Axis2 does and my recommendation is to
use axis2 for your session management if possible. You may find, however, that
it does not match your business case.
If it does not, you may consider rolling your own via something like UUID -
which WS-Addressing does in its own way - and your own ehcache or the like
storage. Its pretty easy and I've done it for many clients. The idea is simple:
you login, pass back a UUID, pass it back in for subsequent calls and use it as
the key to put / get your objects out of ehcache. Logout would invalidate the
session which ehcache can do itself after a choosen timeout. ehcache is used
with Hibernate and is simple and effective. Oh yeah - just ignore the idea if
that doesn't fit what you need.
HTH,
Robert
On 11/29/06, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
Hi Stadelmann ;
pls see my comments below;
Hi session-managers,
I'm running my client and server with modules addressing-1.1, logging,
soapmonitor-1.1 engaged and have set scope=soapsession
MyService.java got the additional methods
public void init(ServiceContext sCtx) {
this.sc = sCtx;
this.log.info(sc.toString()+ init() called );
}
public void destroy(ServiceContext sCtx) {
if(!this.sc.toString().equals(sCtx.toString())){
this.log.error(ServiceContext on init() and destroy() not
equal in );
}
this.log.info(sc.toString()+ destroy() called );
}
public void setOperationContext(OperationContext oCtx) {
this.oc = oCtx;
this.log.info(oc.toString()+ setOperationContext() called
);
}
We have removed this method (it was there in Axis2 1.0 , but we removed
that from Axis2 1.1), so we are no longer going to call this method . If
you want to get access to operation context , then you can do that as
follows;
MessageContext msgCtx = MessageContext.getCurrentContext ();
from msgCtx you can access any of the contexts you want .
I start client #1 which has the effect that MyService.init() is
called; so far so right!
Client #1 then loops and sends continously messages to MyService.echo()
I start client #2 which has the effect that MyService.destroy() is
called followed by MyService.init()
This has the effect that client #1 fails with an invalid group
context id exception
Is this a bug?
Nope. That is not a bug , soapsession has concept of time out , so once
it gets time out you will get that exception.
I have studied the architecture of axis2 and have drilled down in code
and I came down to where alle the service objects are finally called
at invokeBusinessLogic (inCtx, outCtx) with it's call to
method.invoke ( . . . )
good .
All reading in code and documentation did not answer my questions ***
How does Axis2 manage / support long-lasting-sessions to
server-objects bound to this session ? ***
Do I have to implement this myself on top of Axis2?
No , you can get support from Axis2 session management. If you have
Axis2 1.1 distribution there you can find a sample called Library sample
, which help you to understand most of the important factors.
1. I want to have a client-object exchanging OMElements with it's
service-class-object.
yes , doable
2. when the client starts the session, up on receiving the first
message, a unique instance of the service-class-object shall be
created at the server.
yes , that is what happen.
2a) 20 client objects shall mean we have instantiated 20
dedicated-server-objects
yes.
3. as long as this 20 service-class-object exists, in fact 20
wrapper-object to 20 external server process, and as long as this 20
external process exist it shall not be
Re: Use Hibernate3 with Axis2
I use Hibernate inside the AAR just fine, though I do it via Spring managing the transactions. Assumming you are not using Spring, you can still use the same principles. The spring axis2 tutorial does mention hibernate and that should be a good starting point, with or without spring. http://ws.apache.org/axis2/1_1/spring.html#26 HTH, Robert On 12/10/06, Eric Chow [EMAIL PROTECTED] wrote: Hello, How can I use Hibernate3 with Axis2? I want to use Hibernate3(Annotation + EntityManager) in Axis2 AAR. Where should I put the persistence.xml, hibernate.cfg.xml and those POJO? All pack it in the AAR or somwhere ?? Best regards, Eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis 1.4 - DataHandler: second param is null
I'm using Axis-1_4 with apache-tomcat-5.5.20 and JDK 1.5.0_08
With wsdl2java I've generated skeleton/stub/impl for two different methods.
Both have DataHandler as return type and one or two DataHandlers as input
params.
The method which has two input params doesn't work properly because the second
argument is null, even if it is visible in the soap request that follows:
POST /axis/services/QueryHandler HTTP/1.0
Content-Type: multipart/related; type=text/xml;
start=EB09A043635184039EE39D58E26D5CB9;
.boundary==_Part_0_5910186.1165843911958
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.4
Host: localhost:8080
Cache-Control: no-cache
Pragma: no-cache
SOAPAction:
Content-Length: 4002
--=_Part_0_5910186.1165843911958
Content-Type: text/xml; charset=UTF-8
Content-Transfer-Encoding: binary
Content-Id: EB09A043635184039EE39D58E26D5CB9
?xml version=1.0 encoding=UTF-8?soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;soapenv:Bodyin0
href=cid:A9CD60060FF3B61443ADBE982A56CA4E xmlns=urn:QueryHandler/in1
href=cid:EDECEF261A3FCB6C3684BB17AF2B14AC
xmlns=urn:QueryHandler//soapenv:Body/soapenv:Envelope
--=_Part_0_5910186.1165843911958
Content-Type: image/jpeg
Content-Transfer-Encoding: binary
Content-Id: A9CD60060FF3B61443ADBE982A56CA4E
..JFIF.C..
...
((%$*0=3*-9.$%5H59?ADED)3KPJBO=CDA...C...A,%,AA..Q.v.5.!1.AQ.2a..Rq..#B.%.!1A.Q?..];..s.u.;..[EMAIL
PROTECTED]...g9.Q.b.q..3I...QB...\
H+..;..0..:..id..(S4.C+./...1jv:6M+
lM.04.#.s...RO..8%T...L..}%p.S)..*.-.%.*Bn..O.UuL)y.,.VV.^.R.om..+].A...-..[..{.2.`..m
.rv^..4...{.I[;U..Oq.ih.Z4o..D..zm..o.;..+Kv.i...^...jI.f.q.=...D.a%..i...
b.TT..g,n.r.;5.V..
...]:..m.(y0...iChA..1.32=XTV..\...h...Z...|...9xN.d:C.cN-...Ca#yd.gdqEx..`.O`c9\..#.ANm.u..u0.0:.y...L67..5..].%..x9.}..x.h.e.d..m.5..pfIT.QI..'.bSa...6...4A.p.2|U.*.$.h...qrF.W.+..J..W.x..:.Q.3N#..c...N...^b.m-9F'WX..\.%%._A..~.'..Um.b...
..X2\.oC...;.Q...Ob.P..G=.{.Z...N.t...t,...x..PCO..i!$...\Y2..8r.6..
..:^..V.;...=.Mc.i$
TZ6sjq-.|.Z.).,...uj.;IU.0M3...+Y..W...t.q.xt.H.5.QM...].B...i.\.m..Q@3..c.X...l.w[i..,=.'.H.CH...D1..9..yan.8.../.r..Q.K.)...N.[T..E.~.t.t.|.J.m.b
uU+Am..}...S..e.9|/.u4.1..;_d...q(i.iy`z..U`QE/.}$.FA..s..6Jy..P4+%.~p.rRI.E0..e.Y
..GX.\..c..V.!t44i..k...i5e..f...|..._(.
.ZB-6..S.%e.i.4..6[S..}J...b.q^s...f.^..s.PG...[.I..D.n.m..!..{(ahb.r|..
v...}3v
...xE6...'.}:v2~./.r.eC%..._.n...J.=.2..m.n.fK.)..|o.K..l.I.d..
.X.
...`...RI+S...Y.f.X.t..4].ewT9...).Q.Z$emuK..L.O.l...*I..P3H...mE..
7..K.3QM(EQ..Hlg.E..t;-.QD.Iw.-}.. .N..E. .vV*(.^.;.4(...Q
--=_Part_0_5910186.1165843911958
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-Id: EDECEF261A3FCB6C3684BB17AF2B14AC
?xml version=1.0 encoding=UTF-8?
Mpeg7 xmlns=urn:mpeg:mpeg7:schema:2004
xmlns:m7qf=urn:mpeg:mp7qf:schema:2006
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=urn:mpeg:mp7qf:schema:2006
http://141.39.14.53:8080/exist/M7v2schema.xsd;
DescriptionUnit sessionID=sessionID xsi:type=m7qf:SessionType
m7qf:UserDescription
User xsi:type=PersonType
Name
GivenNameBabette/GivenName
FamilyNameWagner/FamilyName
/Name
/User
/m7qf:UserDescription
m7qf:Query timeout=100
m7qf:RsPresentation maxPageEntries=5/
m7qf:Input
m7qf:MediaResource id=abi1 mimeType=image/jpeg uriRef=abi1.jpeg/
m7qf:QueryExpression
m7qf:SingleSearch exactMatch=false mediaIDREF=abi1
xsi:type=m7qf:QueryByExampleMediaType
m7qf:SortBy csRef=urn:dominantColor xsi:nil=true/
/m7qf:SingleSearch
/m7qf:QueryExpression
/m7qf:Input
/m7qf:Query
/DescriptionUnit
/Mpeg7
--=_Part_0_5910186.1165843911958--
HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=76993315CDBDB675E0D71742F4417CD2; Path=/axis
Content-Type: text/xml;charset=utf-8
Date: Mon, 11 Dec 2006 13:31:54 GMT
Connection: close
?xml version=1.0 encoding=UTF-8?soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
Re: out of memory issues. Can MTOM help ?
Hi, Do you have already a solution for this problem? I'm facing the same problem, that I get the following error transferring files greater than 2,5 Mb: 2006-12-11 15:17:18 StandardWrapperValve[action]: Servlet.service() for servlet action threw exception java.lang.OutOfMemoryError: Java heap space Can someone comment, on the issue how to transfer files greater than mentioned above? Is the memory allocation for example in JAVA_OPTS the only clue? kr, Philipp Marcel Casado schrieb: Hi, I have a service that extracts data from a sql table and builds objects from the results and then sends them back to the client. I use ADB but I'm running out of memory for large query results. I'm running the service onTomcat and I setup setenv JAVA_OPTS -Xmx1024m -Xms1024m .What I can do for large soap body messages ? Should the use of MTOM help me whit memory problems? Does any body an example of using MTOM to handle big XML objects ? I already took a look to the MTOM tutorial but is still not clear to me if this will solve the problem. Thanks, Marcel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[axis2]ws policy question
Hi Dims/Deepal I was in the morning axis2 tutorial presentation and it was definitely very helpful. I had asked a question related to the WS-policy implementation [neethi I guess] and I had some question on the facts Dims mentioned in that session abt the policy implementation. I have a sort of legacy application which I am web service enabling using axis. I need the dynamic deployment feature of axis2 [ie dropping the aar file with the WSDL in a folder ]. I create my own wsdl and the services.xmland the schema dynamically at runtime when the user chooses to deploy the legacy service as a Web service. I deal with the Raw xml in my java service class and it has one method say - public OMElement dothis(OMElement om). I let the axis modify the wsdl and hence will not use the useOriginalWSDL param. My WSDL can have n number of methods and I figure that at runtime from the legacy artifact/service the user is trying to deploy. But my java class is fixed as after I get the XML I know what to do with that to invoke the actual legacy service. When it comes to security we suggest the user to go and modify the services.xml and add the inflow and outflow xml blocks at the service level [as I have only one physical operation but n wsdl operation]. I have a major problem here - I want to specify those inflow/outflow security stuff based on the WSDL operation but thats not possible with the current design of services.xml. [remember as I said I have 1 physical operation and N wsdl operation]. I know for a fact that WS specification no way forces the WSDL operation name to be the same as the physical operation name. So In that case even if I come down to the level of deploying each operation in my legacy service as a individual Web services [so I am now at 1 to 1 mapping] still I want to have a separate WSDL operation name as from the java operation name [which is say allways dothis for me]. I want my inflow/outflow stuff to appear as a policy in the WSDL for that operation/service [now say 1 service will have one operation only] - I am not sure how axis will be able to match my java operation to the WSDL operation [If specify the security in the operation level]. My flow of service invocation is like as below: [my java class is like a proxy to the legacy services] axis engine my java class -legacy service1 axis engine my java class -legacy service2 . ... My java class is pregenerated fixed code which has only one method dothis which takes in the XML and knows which legacy artifact to call and how to get response back. So my question is Q1Do you suggest me [for WS-policy and operation level security] sake to change my design to 1 legacy service method as one Axis Web service? If I stick with legacy service as one web service then potentially a legacy service may have N wsdl operation and my java class has only one [as its generically handling all requests for any legacy service]. So my services xml has only one operation and I have to declare security policy only at the service level. Q2Also I am generating my own WSDL but letting Axis modify it - so I am hoping that the policy stuff should appear as pasrt of the Axis modified WSDL - right? [given I just specify the inflow/outflow sec parameters.] -- thanks Rishi
Re: [Axis2 v1.1] How can I get full XML from SOAP Request ?
Hi,
Thanks for your answers ... which, unfortunately, don't work. But I found a
solution.
For me, it seems to be a bug but, as I don't really know why it works...
The key is to access MessageContext's envelope not in the skeleton but in the
beginning of the MessageReceiverInOut and give it to the skeleton :
public void invokeBusinessLogic(org.apache.axis2.context.MessageContext
msgContext, org.apache.axis2.context.MessageContext newMsgContext)
throws org.apache.axis2.AxisFault{
try {
String fluxXML = msgContext.getEnvelope().toString();
// get the implementation class for the Web Service
Object obj = getTheImplementationObject(msgContext);
ECCMAServiceCondamnation10Skeleton skel =
(ECCMAServiceCondamnation10Skeleton)obj;
//Out Envelop
org.apache.axiom.soap.SOAPEnvelope envelope = null;
//Find the axisOperation that has been set by the Dispatch phase.
org.apache.axis2.description.AxisOperation op =
msgContext.getOperationContext().getAxisOperation();
if (op == null) {
throw new org.apache.axis2.AxisFault(Operation is not located, if this is
doclit style the SOAP-ACTION should specified via the SOAP Action to use the
RawXMLProvider);
}
java.lang.String methodName;
if(op.getName() != null (methodName = op.getName().getLocalPart()) != null){
if(remettreCondamnations.equals(methodName)){
testWS.RemettreCondamnationsReponse param11 = null;
//doc style
testWS.RemettreCondamnations wrappedParam =
(testWS.RemettreCondamnations)fromOM(
msgContext.getEnvelope().getBody().getFirstElement(),
testWS.RemettreCondamnations.class,
getEnvelopeNamespaces(msgContext.getEnvelope()));
param11 = skel.remettreCondamnations(wrappedParam, fluxXML) ;
envelope = toEnvelope(getSOAPFactory(msgContext), param11, false);
}
And now I've got the full XML request to work with !
John
Davanum Srinivas [EMAIL PROTECTED] a écrit :
Date: Fri, 8 Dec 2006 13:46:39 -0500
De: Davanum Srinivas [EMAIL PROTECTED]
À: axis-user@ws.apache.org
Objet: Re: [Axis2 v1.1] How can I get full XML from SOAP Request ?
See if it helps if you call contexteMessage.getEnvelope().build()
before you print it.
-- dims
On 12/8/06, John DeeBee wrote:
Hi,
I'm working on server-side from Axis2 v1.1 and I need to get the whole XML
request in my WS skeleton (and after) to make other XML parsing and to log
every message going in and out from my webapp.
In Axis2 v1.0, I wrote a method called setOperationContext() in my skeleton
which retireved the full XML request by using
messageContext.getEnveloppe().toString().
But now I'm working with v1.1 and it doesn't work anymore. So I delete my
setOperationContext() method and, in my WS operation, I write this code to
replace :
MessageContext contexteMessage =
MessageContext.getCurrentMessageContext();
setFluxXML(contexteMessage.getEnvelope().toString());
But contexteMessage.getEnvelope().toString() gives me only the beginning
and the end of the request, not the full content.
I tried to make a logging module as described in documentation but the
result is the quite the same. I have the full xml from WS response but not
for request.
Who have a solution before I getting mad ?
John
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions
! Profitez des connaissances, des opinions et des expériences des
internautes sur Yahoo! Questions/Réponses.
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son
interface révolutionnaire.
Axis 2's handling of RPC Parameter types
Hi there,
I've come across a problem with Axis 2's handling of RPC types.
If I set the input arguments in the Client to:
String handler=doThis;
Weather w=new Weather();
w.setTemperature((float)39.3);
w.setForecast(Cloudy with showers);
w.setRain(true);
w.setHowMuchRain((float)4.5);
Object[] args={ handler, w };
QName operation = new QName(http://ws.datacentre.company.com/xsd;,
handle);
Class[] returnTypes = new Class[] { Weather.class };
Object[] response =
serviceClient.invokeBlocking(operation,args,returnTypes);
System.out.println(reponse = +response+ type:
+response.getClass().getName());
And a service with the method:
public Object handle(String handler,Object object);
I find that the data I get is command:=doThis and object:=null
My intention is to build a generic web service that can take any type
(by upcasting to object) and through an internal XML document, be able
to map it to its real class so I can cast and perform operations on it
as defined by the XML (this is not SOAP - its BePel)
Is there any way of overcoming this? And I've noticed Axis does not
tell me about the problem - its justs passing in null refs...
Thanks,
John
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Axis 1.3 MessageContext.getOperation() returns null
Hi Folks, I am in a bit of a fix here. I have a few custom handlers that make use of the MessageContext.getOperation() method. Of late, the call to MessageContext.getOperation() has started returning a null. Went through the Java doc, wasn't much help, it says the method can return null, but doesn't say under what condition? A few questions regarding this: 1. Why is the operation not being set? 2. The Axis engine still seems to be able direct the call to the right service method. The interesting thing is that once the pivot is hit, the getOperation() always returns a proper value. 3. This seems to be happening with great regularity, I reckon I've tweaked something in the server-config.wsdd resulting in this changed behaviour. Any inputs/leads would greatly be appreciated. Cheers Rishi This message is intended for the addressee or its representative only. Any form of unauthorized use, publication, reproduction, copying or disclosure of the content of this e-mail is not permitted. If you are not the intended recipient of this e-mail message and its contents, please notify the sender immediately and delete this message and all its attachments subsequently.
databinding sample code
I am having trouble to get the databinding sample code to work. After adding Castor-1.0.5, jdom, stax-utils, and three Java files (StAXBuilder, StAXTextModifier, and StAXOutputter) I was able to get the code compiled. When I execute the client code by using Ant build pointing to the target run.client I got a null pointer error. Any suggestion is appreciated. Danny [java] org.apache.axis2.AxisFault: null; nested exception is: [java] java.lang.NullPointerException [java] at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO peration.java:308) [java] at samples.databinding.StockQuoteServiceStub.getStockQuote(StockQuoteServic eStub.java:141) [java] at samples.databinding.StockClient.main(StockClient.java:52) [java] Exception in thread main [java] Java Result: 1
custom types with non-java client
Hi, I'm fairly new at webservices, and I've been developing a webservice based on axis 1.4. To send back complex objects that I already had I'm using the castor serializer. I was wondering if some of my clients don't use java to access my webservices if it was still possible for them to get the XML? Dose somebody have a basic example? I found this on the web: http://mail-archives.apache.org/mod_mbox/ws-axis-user/200407.mbox/[EMAIL PROTECTED] Does this means that I have to modify my methods to send back basic types? Thanks for any help, Melanie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Setting the HTTP status code
Is it possible to set the HTTP status code on the way out of an Axis service? Like instead of 200 set it to HTTP 204? Thanks. Roshan Punnoose Phone: 301-497-6039 BEGIN:VCARD VERSION:2.1 N:Punnoose;Roshan FN:Punnoose, Roshan ADR;WORK:;2115 LABEL;WORK:2115 EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20050413T183207Z END:VCARD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Soap/RPC Corruption
Hi All I'm executing an axis 1.4 SOPA XML/RPC call where there return string has a '0D0A' (CR/LF) in one of the data elements. Axis is escaping the but not the . But I am expecting the whole return element to be wrapped in ![CDATA[ and have nothing escaped. I am getting: getHoroscopesByDateReturn xsi:type=xsd:stringlt;Horoscopeslt;Date2006-11-08lt;/Date... I am expecting the getHoroscopesByDateReturn xsi:type=xsd:string to actually be: getHoroscopesByDateReturn xsi:type=xsd:string![CDATA[HoroscopesDate2006-11-08/Date... Is this a bug with the line.separator parsing, or is there another option? Axis 1.4 Java 1.4 on (windows, solaris, linux) Xerses 2.8.0 Thanks, Duane
InflowConfiguration OutflowConfiguration deprecated
What is the best way to configure rampart programatically now? It seems that the previous configuration classes have been deprecated. The samples are still using those 2 classes thought... Thanks! George Stanchev ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Re: out of memory issues. Can MTOM help ?
Phillipp and Marcel, Make sure you know where the out of memory error is occurring. With a web service, you could be getting it on the client side as well as the service side depending on how you log it. Also, I've run into issues using TCP Mon in between the two when it runs out of memory. I solved that by upping the heap space as Marcel suggested on all parties involved. Hope this helps. Jon Philipp Perner wrote: Hi, Do you have already a solution for this problem? I'm facing the same problem, that I get the following error transferring files greater than 2,5 Mb: 2006-12-11 15:17:18 StandardWrapperValve[action]: Servlet.service() for servlet action threw exception java.lang.OutOfMemoryError: Java heap space Can someone comment, on the issue how to transfer files greater than mentioned above? Is the memory allocation for example in JAVA_OPTS the only clue? kr, Philipp Marcel Casado schrieb: Hi, I have a service that extracts data from a sql table and builds objects from the results and then sends them back to the client. I use ADB but I'm running out of memory for large query results. I'm running the service onTomcat and I setup setenv JAVA_OPTS -Xmx1024m -Xms1024m .What I can do for large soap body messages ? Should the use of MTOM help me whit memory problems? Does any body an example of using MTOM to handle big XML objects ? I already took a look to the MTOM tutorial but is still not clear to me if this will solve the problem. Thanks, Marcel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with Axis2 Codegen Wizard.
Hi, When accessing the Axis2 Codegen Wizard and filling the necessary details, together with the location for the WSDL file, I am getting the following error when hitting the 'finish' button: 'An error occurred while completing process - java.lang.InterruptedException:java.lang.RuntimeException: java.lang.reflect.InvocationTargetException'. Can you hint me on what is the problem please? I am attaching the WSDL file for your info. Thank you very much for your support aldo
Unwanted log messages
I have written a standalone Java app that calls a number of web services via Axis. I generated the clients using Apache's wsdl2java. The problem I am having is this: for each web service that is called from my client, Axis is logging messages to the log file that I have set up for our app on the server(log4j). As such, the log file is extremely large. Can someone tell me why this is happening and if there is a way to suppress Axis logging? Here is an example: 2006-12-11 09:27:12,351 - org.apache.axis.i18n.resource::handleGetObject(setMsgForm) 2006-12-11 09:27:12,351 - Setting current message form to: FORM_SOAPENVELOPE (currentMessage is now org.apache.axis.message.SOAPEnvelope) 2006-12-11 09:27:12,351 - Exit: SOAPPart ctor() 2006-12-11 09:27:12,351 - org.apache.axis.i18n.resource::handleGetObject(addBody00) 2006-12-11 09:27:12,351 - Adding body element to message... 2006-12-11 09:27:12,351 - Enter: Call::invoke() 2006-12-11 09:27:12,351 - MessageContext: setTargetService(UrnACHCreditService) 2006-12-11 09:27:12,351 - MessageContext: setServiceHandler(null) 2006-12-11 09:27:12,351 - org.apache.axis.i18n.resource::handleGetObject(targetService) Thanks very much, Bob Any questions? Get answers on any topic at www.Answers.yahoo.com. Try it now. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Apache Rampart 1.1 Released
Cool. Someone should update this page: http://ws.apache.org/axis2/modules/index.html with Rampart and Sandesha links. -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Sunday, December 10, 2006 9:54 PM To: axis-user@ws.apache.org Subject: Apache Rampart 1.1 Released Apache Rampart team is happy to announce the 1.1 release of Apache Rampart You can download the releases from: http://www.apache.org/dyn/closer.cgi/ws/rampart/1_1 Apache Rampart 1.1 is a toolkit that provides implementations of the WS-Sec* specifications for Apache Axis 1.1, based on Apache WSS4J 1.5.1 and the Apache AXIOM-DOOM 1.2.1 implementation. What is in this release There are two main Apache Axis2 modules provided with this release. * rampart-1.1.mar * This provides support for WS-Security and WS-SecureConversation features. rahas-1.1.mar This module provides the necessary components to enable SecurityTokenService functionality on a service. Apache Rampart 1.1 introduces a new configuration model based on WS-Policy and WS-Security Policy and it is important to note that Apache Rampart 1.0 style configuration is now deprecated and will not be available in next major version. Apache Rampart 1.1 can be successfully used with the next Apache Sandesha2 release targeted towards Apache Axis2 1.1 to configure WS-SecureConversation + WS-ReliableMessaging scenarios. The rampart module was successfully tested for interoperability with other WS-Security implementations. WS - Sec* specifications supported by Apache Rampart are as follows: * WS - Security 1.0 * WS - Secure Conversation - February 2005 * WS - Security Policy - 1.1 - July 2005 * WS - Trust - February 2005 * WS - Trust - WS-SX spec - EXPERIMENTAL Thank you for using Apache Rampart. The Apache Rampart team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Problem with Axis2 Codegen Wizard.
Hi, It will be helpful if you can attach your eclipse log file as well (I guess you are using eclipse codegen wizard) which should be in your workspace/.metadata directory. It should have a more meaningful stacktrace. BTW I don't see any WSDL attachment :) Ajith On 12/11/06, Aldo Mamo [EMAIL PROTECTED] wrote: Hi, When accessing the Axis2 Codegen Wizard and filling the necessary details, together with the location for the WSDL file, I am getting the following error when hitting the 'finish' button: 'An error occurred while completing process -java.lang.InterruptedException:java.lang.RuntimeException: java.lang.reflect.InvocationTargetException'. Can you hint me on what is the problem please? I am attaching the WSDL file for your info. Thank you very much for your support aldo -- Ajith Ranabahu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 and WSDL20
Hi, My guess is we can easily get rid of this flag since it is very easy to distinguish a WSDL 1.1 document from a 2.0 document :) Ajith On 12/11/06, Paul Fremantle [EMAIL PROTECTED] wrote: Jim Sure. If you look at the options for WSDL2Java you will see -wv (WSDL version). Paul On 12/11/06, jim ma [EMAIL PROTECTED] wrote: Hi all , Does Aixs2 plan to support WSDL20 ? Currently is there any experimental stuff related to WSDL20? Thanks Jim -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ajith Ranabahu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: custom types with non-java client
It depends on how Castor is serializing your objects. If Castor converts your objects into reasonably straightforward XML schema structures, it should work. What you don't want to do is use SOAP encoding to serialize the objects, because it has a tendency to produce XML that can't be easily processed by non-Java applications. Anne On 12/11/06, Melanie Courtot [EMAIL PROTECTED] wrote: Hi, I'm fairly new at webservices, and I've been developing a webservice based on axis 1.4. To send back complex objects that I already had I'm using the castor serializer. I was wondering if some of my clients don't use java to access my webservices if it was still possible for them to get the XML? Dose somebody have a basic example? I found this on the web: http://mail-archives.apache.org/mod_mbox/ws-axis-user/200407.mbox/[EMAIL PROTECTED] Does this means that I have to modify my methods to send back basic types? Thanks for any help, Melanie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
What's wrong with this tcpmon response?
Hello, Can someone identify what if anything is wrong with the below tcp response. The service method throws an AxisFault as declared and is returning a NPE as expected, but the client code just throws me an OMException encapsulating an IllegalStateException: Current state not START_ELEMENT. Thanks! Sathija. HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=5BDD5DDC6A14AA55FC0045247DD7ABF1; Path=/enetaware Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_334849F3E9B5911F6811658797561853; type=application/xop+xml; start=0.urn:uuid:[EMAIL PROTECTED]; start-info=text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Mon, 11 Dec 2006 23:29:16 GMT Connection: close bc5 --MIMEBoundaryurn_uuid_334849F3E9B5911F6811658797561853 content-type: application/xop+xml; charset=UTF-8; type=text/xml; content-transfer-encoding: binary content-id: 0.urn:uuid:[EMAIL PROTECTED] ?xml version='1.0' encoding='UTF-8'?soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header / soapenv:Bodysoapenv:Faultfaultcodesoapenv:Client/faultcodefaultstringNo devices have been retrieved; nested exception is: java.lang.NullPointerException: No devices have been retrieved/faultstringdetailExceptionorg.apache.axis2.AxisFault: No devices have been retrieved; nested exception is: java.lang.NullPointerException: No devices have been retrieved at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:184) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:493) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:324) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:234) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.emprisa.ena.webapp.filter.LicenseValidationFilter.doFilter(LicenseValidationFilter.java:197) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) /Exception/detail/soapenv:Fault/soapenv:Body/soapenv:Envelope 3b --MIMEBoundaryurn_uuid_334849F3E9B5911F6811658797561853-- 0 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis 2] What's wrong with this tcpmon response?
Resending as an Axis 2 post. Hello, Can someone identify what if anything is wrong with the below tcp response. The service method throws an AxisFault as declared and is returning a NPE as expected, but the client code just throws me an OMException encapsulating an IllegalStateException: Current state not START_ELEMENT. Thanks! Sathija. HTTP/1.1 500 Internal Server Error Server: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=5BDD5DDC6A14AA55FC0045247DD7ABF1; Path=/enetaware Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_334849F3E9B5911F6811658797561853; type=application/xop+xml; start=0.urn:uuid:[EMAIL PROTECTED]; start-info=text/xml;charset=UTF-8 Transfer-Encoding: chunked Date: Mon, 11 Dec 2006 23:29:16 GMT Connection: close bc5 --MIMEBoundaryurn_uuid_334849F3E9B5911F6811658797561853 content-type: application/xop+xml; charset=UTF-8; type=text/xml; content-transfer-encoding: binary content-id: 0.urn:uuid:[EMAIL PROTECTED] ?xml version='1.0' encoding='UTF-8'?soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;soapenv:Header / soapenv:Bodysoapenv:Faultfaultcodesoapenv:Client/faultcodefaultstringNo devices have been retrieved; nested exception is: java.lang.NullPointerException: No devices have been retrieved/faultstringdetailExceptionorg.apache.axis2.AxisFault: No devices have been retrieved; nested exception is: java.lang.NullPointerException: No devices have been retrieved at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:184) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:493) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:324) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:234) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.emprisa.ena.webapp.filter.LicenseValidationFilter.doFilter(LicenseValidationFilter.java:197) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) /Exception/detail/soapenv:Fault/soapenv:Body/soapenv:Envelope 3b --MIMEBoundaryurn_uuid_334849F3E9B5911F6811658797561853-- 0 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2 v1.1]
This seems to be a bug in Rampart. Sumedha also pointed this out here [1]. Please file a JIRA. Thanks, Ruchith [1] http://marc.theaimsgroup.com/?l=axis-devm=116583812603458w=2 On 12/11/06, Rodrigo Ruiz [EMAIL PROTECTED] wrote: Hi, I thought ResourceBundles were smart enough to use the default bundle when a specific one was not found; so, if errors.properties is present in the classpath, why does Rampart complain at all? Best regards, Rodrigo Ruiz Ruchith Fernando wrote: Hi, Since your locale is DE you you will have to have errors_de.properties file available in the classpath in the org.apache.rampart package. Simply copy the content of this file [1] into the errors_de.properties file. Optionally you can translate messages :-) Thanks, Ruchith [1] https://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_1/modules/security/src/org/apache/rampart/errors.properties On 12/11/06, Daniel Wehrle [EMAIL PROTECTED] wrote: Hi, I tried to do a little Axis2 sample on my German Windows. I connect to a .Net web service using wssecurity, so I use rampart for the UsernameToken. But by sending a message I got an stack trace ending with: Caused by: _java.lang.RuntimeException_: Can't find bundle for base name org.apache.rampart.errors, locale de_DE at org.apache.rampart.RampartException.clinit(_RampartException.java:36_) What I am doing wrong? Thanks -- Daniel Wehrle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- --- GRID SYSTEMS, S.A. Rodrigo Ruiz Parc Bit - Edificio 17 Research Coordinator 07121 Palma de Mallorca[EMAIL PROTECTED] Baleares - Spain Tel: +34 971 435 085 http://www.gridsystems.com/Fax: +34 971 435 082 --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- www.ruchith.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache Rampart 1.1 Released
Added info on Rampart ! The site should be updated in a little while. Thanks, Ruchith On 12/12/06, Spies, Brennan [EMAIL PROTECTED] wrote: Cool. Someone should update this page: http://ws.apache.org/axis2/modules/index.html with Rampart and Sandesha links. -Original Message- From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Sunday, December 10, 2006 9:54 PM To: axis-user@ws.apache.org Subject: Apache Rampart 1.1 Released Apache Rampart team is happy to announce the 1.1 release of Apache Rampart You can download the releases from: http://www.apache.org/dyn/closer.cgi/ws/rampart/1_1 Apache Rampart 1.1 is a toolkit that provides implementations of the WS-Sec* specifications for Apache Axis 1.1, based on Apache WSS4J 1.5.1 and the Apache AXIOM-DOOM 1.2.1 implementation. What is in this release There are two main Apache Axis2 modules provided with this release. * rampart-1.1.mar * This provides support for WS-Security and WS-SecureConversation features. rahas-1.1.mar This module provides the necessary components to enable SecurityTokenService functionality on a service. Apache Rampart 1.1 introduces a new configuration model based on WS-Policy and WS-Security Policy and it is important to note that Apache Rampart 1.0 style configuration is now deprecated and will not be available in next major version. Apache Rampart 1.1 can be successfully used with the next Apache Sandesha2 release targeted towards Apache Axis2 1.1 to configure WS-SecureConversation + WS-ReliableMessaging scenarios. The rampart module was successfully tested for interoperability with other WS-Security implementations. WS - Sec* specifications supported by Apache Rampart are as follows: * WS - Security 1.0 * WS - Secure Conversation - February 2005 * WS - Security Policy - 1.1 - July 2005 * WS - Trust - February 2005 * WS - Trust - WS-SX spec - EXPERIMENTAL Thank you for using Apache Rampart. The Apache Rampart team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- www.ruchith.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: InflowConfiguration OutflowConfiguration deprecated
Hi George, Now you can pragmatically configure Rampart using policy (combination of WS-SecurityPolicy and Rampart policy). This requires you to understand WS-SecurityPolicy ... I hopefully will be able to get some more documentation and examples posted next week (after my exams :-) ) Thanks, Ruchith On 12/12/06, George Stanchev [EMAIL PROTECTED] wrote: What is the best way to configure rampart programatically now? It seems that the previous configuration classes have been deprecated. The samples are still using those 2 classes thought... Thanks! George Stanchev ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. -- www.ruchith.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Rampart not available on Axis modules page
Modules page is now updated: http://ws.apache.org/axis2/modules/index.html Thanks, Ruchith On 12/8/06, sridhar vudutha [EMAIL PROTECTED] wrote: You can find them here. http://people.apache.org/~ruchithf/rampart-1.1-RC1/ On 12/8/06, Sathija Pavuluri [EMAIL PROTECTED] wrote: Thanks. Until that happens, where can I obtain the rampart nightly? Couldnt find it on the axis nightly page or WS4J site. Sathija. Hi Sathija, We are yet to release Rampart-1.1 for Axis2-1.1. The page will be updated when the release is done - most probably over the weekend. Thanks, Ruchith On 11/29/06, Sathija Pavuluri [EMAIL PROTECTED] wrote: Hello, Why is Rampart 1.1 (or whatever is the compatible version for Axis2 1.1) not listed/available for download on Axis Modules page? http://ws.apache.org/axis2/modules/index.html There are other pages on Axis2 website that point to this link for Rampart. Thanks, Sathija - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- www.ruchith.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- www.ruchith.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: sesion managment, scope=soapsession
Hi Stadelmann ; My client #1 runs continously, and sends arround 40 msg a second to the server. When the second client starts, cline t#1 is still sending messages and so we do not have a time-out condition. client #1 never times out. BUT as I decribe, using the code shown, when client #2 starts MyService.destroy() is called followed by MyService.init() which has the effect that client #1 fails thereafter with an invalid group context id exception hmmm, can you please help me to re-create the problem. If you can send me the sample services and clients that will be very helpful for me to fix the issue. I would appreciate an example on how to have a scenario as I describe. When I read literature about tomcat, retriving a session object from the clients request object, it seems that internals are figuring out which client is calling and the rigth session object which acts as data store for the session is returned/created. How is that with AXIS2-1.1? Will write a sample soon . When the MyService Object gets created I store the creation time for the instance in a instance variable. And when multiple clients run without scope=soapsession set, all clients return the same time stamp. So that means for me! client #1 makes axis2 creating a first instance of a class, and places the creation timestamp. That can not happen , there should be a separate service impl class for each client, Im 100% sure about that since I have tested that. :) This is called an object, and client #2 sends his message to the same instance the same object. When the call to client 2 returns, client #2 finds the same time stamp as client #1 has. But when client #2 starts 10 seconds after client #1, I would expect that client #2 has a different object-creation-timestamp then client #1 unless we talk to the same instance (which I cant use). Josef Are u keeping your value as a static ? I mean are u storing your value in a static variable ? Again - my clients 1 to 20 do continously send messages, each client in its thread - I am using NetBeans and I am just launching more then one client. So each client is fully busy sending. But each client gets responses from the same server object instance. And we have not a time-out condition as each client continously sends. Once we come to real clients where usesers invoke messages we wil care about timeouts. But as long as client code jsut loops in a for() we do not have time-outs, even not with 20 sessions, but in our example using scope=soapsession, we do not get that far, as client #1 runs until client #2 starts, which makes client #1 fail with invalid service group context id Josef Are you sending service group id in each request , or you juts send as new req ? If you want to go into same soapsession , then you need to send the serviceGroupID I have read in a dcoument about axis session managment @ http://www.developer.com/java/web/print.php/3620661 that axis2 is meant to be an enterprise web service engine, so it has to support session management. The article is little bit out dated , since we had few changes from Axis2 1.0 to 1.1 So where is a new articel reflecting the same topic? What values does this articel have among well undestood generics when I can not count on the little code fragments given. Also a previous mail has lead me to this articel. So how far is it outdated? Josef I will update that and publish soon. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis 2] What's wrong with this tcpmon response?
Hi Sathija ; Can you pls send me the req message as well. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis 2's handling of RPC Parameter types
My intention is to build a generic web service that can take any type
(by upcasting to object) and through an internal XML document, be able
to map it to its real class so I can cast and perform operations on it
as defined by the XML (this is not SOAP - its BePel)
Then what you have to do is write your service impl class to take
OMElement as method parameter , then om element can be anything. So your
method signature will be look like below;
public OMElement echo(OMElement ele){
/ do smt
}
Thanks
Deepal
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] How to Basic Authentication in client
Hi Tony,
We have renamed the BasicAuthentication calss to the following.
public static class Authenticator{
The following works.
HttpTransportProperties.Authenticator basicAuth
= new HttpTransportProperties.Authenticator();
basicAuth.setUsername(admin);
basicAuth.setPassword(admin);
Rgds,
Dimuthu.
- Original Message
From: Tony Fang [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Tuesday, December 12, 2006 10:20:03 AM
Subject: [Axis2] How to Basic Authentication in client
Hi, there
I found many users are using following to do the basic authentication:
// Add basic authentication
HttpTransportProperties.BasicAuthentication basicAuth
= new HttpTransportProperties().new BasicAuthentication();
basicAuth.setUsername(admin);
basicAuth.setPassword(admin);
options.setProperty(HTTPConstants.BASIC_AUTHENTICATION, basicAuth);
I can find the HttpTransportProperties class, but I can't find the nest
class BasicAuthentication,
I am using axis2 1.0 and axis2 1.1, both haven't this nested class. Can
some one help me to figure out why 1.0 and 1.1 haven't this class?
--
Regards
Tony
Want to start your own business?
Learn how on Yahoo! Small Business.
http://smallbusiness.yahoo.com/r-index
Re: [Axis2] How to Basic Authentication in client
Thanks
I run it well
2006/12/11, Dimuthu Leelarathne [EMAIL PROTECTED]:
Hi Tony,
We have renamed the BasicAuthentication calss to the following.
public static class Authenticator{
The following works.
HttpTransportProperties.Authenticator basicAuth
= new HttpTransportProperties.Authenticator();
basicAuth.setUsername(admin);
basicAuth.setPassword(admin);
Rgds,
Dimuthu.
- Original Message
From: Tony Fang [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Tuesday, December 12, 2006 10:20:03 AM
Subject: [Axis2] How to Basic Authentication in client
Hi, there
I found many users are using following to do the basic
authentication:
// Add basic authentication
HttpTransportProperties.BasicAuthentication basicAuth
= new HttpTransportProperties().new BasicAuthentication();
basicAuth.setUsername(admin);
basicAuth.setPassword(admin);
options.setProperty(HTTPConstants.BASIC_AUTHENTICATION,
basicAuth);
I can find the HttpTransportProperties class, but I can't find the nest
class BasicAuthentication,
I am using axis2 1.0 and axis2 1.1, both haven't this nested class.
Can some one help me to figure out why 1.0 and 1.1 haven't this class?
--
Regards
Tony
--
Check out the all-new Yahoo! Mail
betahttp://us.rd.yahoo.com/evt=43257/*http://advision.webevents.yahoo.com/mailbeta-
Fire up a more powerful email and get things done faster.
--
Regards
Tony
General Axis questions
Hi Axis folks, I'm new to Axis. And I have the following questions: 1) what version of Axis does Jboss (particulary 4.0) support? 2) I used Axis 1.4 to generate Java classes from my WSDLs. I re-peated the process using Axis 1.1 (since Jboss doesn't seem to support some of the libraries my classes need), however, I observe the intersting behavior that the classes generated by Axis 1.1 seem to make refernces to libaries existing only in Axis 1.2 +. Any ideas? Thanks, Ernie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
