Indeed that helped. It is working now.
Thanks
Roger
Am 05.10.2011 um 18:10 schrieb Glen Mazza:
http://www.jroller.com/gmazza/entry/cxf_usernametoken_profile might help you.
Glen
On 10/05/2011 10:34 AM, Roger Gilliar wrote:
Hello,
I would like to replace the following code
--
On 10/05/2011 10:54 PM, Daniel Kulp wrote:
[...]
However, with the new API's at least the user can inject a smarter algorithm
in there that would better meet their needs.
Cool, thanks :-)
--
Alessio Soldano
Web Service Lead, JBoss
Thanks for the comments, all. I hacked the source code for 2.4.2,
putting in the fix in the method getAbsoluteAddress that was already in
the source code in the repository (and will presumably be there for
2.4.3). This made the problems disappear. Good job!
David Sills
-Original
On Thu, 06 Oct 2011 10:40:28 +0200
Alessio Soldano asold...@redhat.com wrote:
On 10/05/2011 10:54 PM, Daniel Kulp wrote:
[...]
However, with the new API's at least the user can inject a smarter
algorithm
in there that would better meet their needs.
Cool, thanks :-)
Yes, cool.
Hi,
we are experiencing a lot of OutOfMemory errors in productions under heavy
load with servicemix 3.3.2, cxf 2.2.6, jdk1.5, linux.
We use the a Cxf client generated from java annotations.
Analysing the problem with a profiler I found out that many messages
(NormalizedMessageImpl) are retained
Hi, I'm facing a problem and could not find a way to solve it, so I'm gonna
try to get help from you guys.
I have 2 apps deployed on Webpshere Server (same server, same cell) with app
security enabled (JAAS / LPTA), one that exposes a webservice and one that
will get the data from it.
The
Hi,
I'm using websphere 7 and I´m using the following code to generate a
LtpaToken2 inside the container:
private String getSecurityToken() {
byte[] token = null;
try {
// Get current security subject
Subject securitySubject =
Thanks Osvaldo.
I think that'll do, but where should I use it in order to CXF send the
lpta2token or lptatoken in Websphere 6.1 in the client call?
Thanks again.
On Thu, Oct 6, 2011 at 10:30 AM, Osvaldo Pina osvaldo.p...@gmail.comwrote:
Hi,
I'm using websphere 7 and I´m using the
Hi,
You can do that:
// Create a proxy to a access a jaxrs server
BookStore proxy = JAXRSClientFactory.create(http://books;, BookStore.class);
// add a cookie to a call
WebClient.client(proxy).cookie(getLtpaToken());
Ats,
Osvaldo Pina.
2011/10/6 Bernardo Corrêa
Yeah, that'll work with JAXRS, but I'm actually using JAXWS. I'll give it a
try, Change to JAXRS and try to do it.
Thanks a lot!
Bernardo.
On Thu, Oct 6, 2011 at 10:57 AM, Osvaldo Pina osvaldo.p...@gmail.comwrote:
Hi,
You can do that:
// Create a proxy to a access a jaxrs server
You can also do the same by registering a custom CXF out interceptor and
update Message.PROTOCOL_HEADERS property on the current message
So that will work for JAX-WS, there could be a simpler option may be...
Cheers, Sergey
On 06/10/11 15:17, Bernardo Corrêa wrote:
Yeah, that'll work with
Dan,
Thanks, but it seems like the EndpointReference instances can't be marshalled
via JAXB. Am I missing something?
Guy
On 6-okt-2011, at 04:15, Daniel Kulp wrote:
On Thursday, October 06, 2011 4:09:13 AM Guy Pardon wrote:
Dan,
Thanks! So how would a consumer interpret this reference
Hi Sergey,
This interceptor would be a client interceptor right? So I would be able to
set the cookie?
I think the solution Osvaldo suggested will throw an exception before I set
the cookie, because, isn't cxf gonna try to reach the wsdl before the cookie
is set?
Thanks
Bernardo.
BookStore
Hi
On 06/10/11 16:05, Bernardo Corrêa wrote:
Hi Sergey,
This interceptor would be a client interceptor right? So I would be able to
set the cookie?
Yes
I think the solution Osvaldo suggested will throw an exception before I set
the cookie, because, isn't cxf gonna try to reach the wsdl
Great! Using @XmlElement(required = true) and the -b binding-name
option kept the element required (minOccurs=1) and exposed it as an
Integer to the client.
Thanks!
--
View this message in context:
On Thursday, October 06, 2011 5:02:03 PM Guy Pardon wrote:
Dan,
Thanks, but it seems like the EndpointReference instances can't be
marshalled via JAXB. Am I missing something?
I think you need to cast it to the specific W3CEndpointReference subclass.
That should do it, I think.
Dan
Sory! I did it in a Jaxrs scenario! I realy don't know how to use
JaxWS clients...
Ats,
Osvaldo Pina.
On Thu, Oct 6, 2011 at 12:09 PM, Sergey Beryozkin sberyoz...@gmail.com wrote:
Hi
On 06/10/11 16:05, Bernardo Corrêa wrote:
Hi Sergey,
This interceptor would be a client interceptor
That's OK, Osvaldo. You helped a lot with the lpta2Token and the security
snippet.
Now what I'm trying is this:
Subject securitySubject = WSSubject.getRunAsSubject();
message.put(SecurityContext.class,
createSecurityContext(securitySubject));
I'm in an Interceptor and
Thanks guys. It woked. I used Osvaldo's snippet to get LtpaToken2 and the
above code to put the cookie:
MapString, ListString headers = CastUtils.cast((Map)
message.get(Message.PROTOCOL_HEADERS));
ListString cookies = new ArrayListString();
cookies.add(LtpaToken2= +
Hi all,
We're using code based on the CXF 2.4 STS provider framework. After
upgrade to CXF 2.4.2, we're seeing bizarrely fluctuating namespace
declarations on the RequestedSecurityToken element.
Usually (and with 2.4.1, always) we get this:
RequestSecurityTokenResponseCollection
Hello,
I'm a complete newby to CXF.
I realize that usually web services are deployed as part of the web
application.
I have to have web services started by a windows service.
I'm able to execute the web services but I'm wondering how can I shut them
down?
I don't seem to be able to get a handle to
Someone else can probably answer your question, but a Windows service
version of Tomcat is available[1], and you can place your web service as
a WAR in Tomcat[2], and then just simply shut down and start up the
Tomcat Windows service. That would probably give you a lot more
flexibility in
22 matches
Mail list logo
