On Thu, 2 Dec 2010 17:10:44 -0500, Daniel Kulp
wrote:
> It sounds like the schemaLocation attribute on the jaxb:bindings
> nodes aren't
> pointing to the correct schema if you are dealing with an imported
> schema. I
> would double check those.
>
> It definitely should work if you get all the s
BTW, I found a workaround for not having it being displayed for every
service.
I inject the map that is based on path and has a list of URI's. In my
provider I check and get the correct list of URI's and pass them into my
custom NamespacePrefixMapper in the createMarshaler() method.
Very cumbers
It sounds like the schemaLocation attribute on the jaxb:bindings nodes aren't
pointing to the correct schema if you are dealing with an imported schema. I
would double check those.
It definitely should work if you get all the schemaLocations and xpaths
working properly.
Dan
On Thursday 02
Yes. My clumsy comment was really directed at JAXB and not CXF.
JAXB's lack of support for interfaces is another big one, IMO.
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Thursday, December 02, 2010 8:56 AM
To: users@cxf.apache.org
Cc: Jason Chaffee
Subject: Re:
Hi,
Sorry if this is the wrong place to ask this, but I have a question
about JAXB class name customization.
My problem is quite simple, in one of the schema imported by the WSDL
I've been given two local element definitions have the same name, like
this :
I really have no idea on this. The thread names all start with "qtp". Does
that have any context to you? There isn't anything in the CXF codebase that
has that letter combination.
Dan
On Thursday 02 December 2010 3:24:30 am Vladislav Krejcirik wrote:
> Hi, I am using cxf-protobuf 0.3, C
On Thursday 02 December 2010 6:40:58 am Jürgen CXF User wrote:
> Hi,
> thanks Daniel for your fast response. Is my understanding right that I have
> to create for each differnently configured web service client instance an
> own bus instance?
No. You can have one bus with many different client ob
Thanks! BTW, Spring Security 3.1 is coming out in December and it will
support mixing multiple http security configurations. Allowing you to have a
form login security for regular web pages and also having a webservice that
responds to a basic authentication.
--
View this message in context:
htt
Just FYI, when working with proxies you can do :
if (response == null) {
Client client = WebClient.client(proxy);
if (client.getResponse().getStatus() == 302) {
String location =
client.getResponse().getMetadata().getFirst("Location").toString();
// create new proxy/webclient,
I'm using Spring 3.0.5 and Spring security 3.0.5.
Ok, I see that I get a status of 302 back, because I'm being redirected to
the login page by Spring Security. However, I did provide the correct
user/pass on the JAXRSClientFactory. So, it's most likely Spring Security
that's not getting the user/
On Thursday 02 December 2010 12:31:51 am Jason Chaffee wrote:
> Another problem with this solution is that will add the define root
> namespaces for all xml returned by all services even if those services
> will never use those namespacesvery clumsy, IMO.
Yea. This is an issue with JAXB. :-
Hi
I think you need to remove 'v1' in the initial address you're passing in to
the JAXRSClientFactory, the proxy will get it from ContentImportServiceImpl.
I'm not sure why 'null' is returned though - perhaps because the target
server returns 200 or 204 with the empty body ? Is it a CXF server ?
Hi,
Newbie question: I keep getting the proxy return null, e.g. in the test
below when I call importProxy.ping() or importContent. If I call the ping()
method in the browser, everything work ok. I have the following
configuration.
Any suggestions on this one?
Thanks!
Marc
@Test
public void te
On Thursday 02 December 2010 4:35:05 am Andrew Dinn wrote:
> On 12/01/2010 09:32 PM, Daniel Kulp wrote:
> > If you have the WebServiceContext injected, just call:
> >
> > context.getEndpointReference()
> >
> > and that should be it.
>
> That's all very well if something can be convinced to invok
Guys,
I am working with ws-security and I see strange things happening.
The soap header is signed and has a time stamp.
In my SecurityCallbackHandler I log a message when entering the handle() method.
This handler is used both for checking the request message signature/timestamp
and the signing
Ouch, that would be a nice one for the documentation. :-)
Thanks for the quick reply!
Marc
--
View this message in context:
http://cxf.547215.n5.nabble.com/Basic-authentication-jaxrs-client-tp3289261p3289345.html
Sent from the cxf-user mailing list archive at Nabble.com.
Hi
jaxrs:client has username & password attribute, I was using jaxws:client
schema when working on it.
cheers, Sergey
On Thu, Dec 2, 2010 at 12:10 PM, mschipperheyn wrote:
>
> Hi,
>
> I've set up a jaxrs server with spring security. Now, I want to create a
> client to write some unit tests. I t
Thanks to all. I will experiment with these ideas...
Sent from my iPad
On 2-dec.-2010, at 10:35, Andrew Dinn wrote:
> On 12/01/2010 09:32 PM, Daniel Kulp wrote:
>> If you have the WebServiceContext injected, just call:
>>
>> context.getEndpointReference()
>>
>> and that should be it.
>
> Tha
Hi,
I've set up a jaxrs server with spring security. Now, I want to create a
client to write some unit tests. I thought this would be a 5 minute job, but
I haven't been able to find information on how to create a basic
username/password configuration for it.
http://www.mysite.com.br:90/services/
Hi,
thanks Daniel for your fast response. Is my understanding right that I have
to create for each differnently configured web service client instance an
own bus instance?
If I am wrong, could you please provide me a brief code snippet?
Thank you very much.
Jürgen
--
View this message in context:
A SOAP fault is returned to the client.
See section 12 "Error Handling" here:
http://www.oasis-open.org/committees/download.php/16790/wss-v1.1-spec-os-SOAPMessageSecurity.pdf
For example:
faultcode: wsse:FailedAuthentication
faultstring: The security token could not be authenticated or authoriz
Having a custom CXF invoker is probably one option, it should be able to
ensure the right Method is invoked,
another option is to register a custom CXF ServletFilter which would provide
a custom HttpServletRequest which would in turn manipulate the request body
such that CXF is made to believe it i
Just out of curiosity... How should you handle an authorization fault like
missing authentication, wrong credentials or not authorized in the ws-security
case.
For http auth protocols we use 401 and 403 response codes. How is this handled
in the ws security case? Or does the spec only say how
No I have only getGreeting implemented and want that every other wrong
request is directed to getGreeting.
If one requests getGreeting2 it directs him to getGreeting.
On Thu, Dec 2, 2010 at 11:34 AM, Sergey Beryozkin wrote:
> Do you actually have getGreeting2 implemented ? Example, do you have
Do you actually have getGreeting2 implemented ? Example, do you have two
SOAP endpoints, one implementing getGreeting and one getGreeting2 and you
want the consumers of getGreeting2 be able to work with the old
getGreeting() ?
cheers, Sergey
On Thu, Dec 2, 2010 at 9:43 AM, Manoel Farrugia wrote:
> By outputting the EncodingType like above, we are wasting
> bandwidth by outputting redundant information, but it is completely valid.
It may be a waste of bandwidth, but the Basic Security Profile spec requires it:
http://www.ws-i.org/Profiles/BasicSecurityProfile-1.1.html#UsernameTokenNonce
Hi Jason
You might want to try setting an outTransformElements property either on the
default or your custom provider, and configure it to ignore certain
namespaces. If it does not help then registering a custom XMlStreamWriter
might do
cheers, Sergey
On Thu, Dec 2, 2010 at 5:31 AM, Jason Chaffe
I can even scrap the idea of Interceptors if there is a better way to
do my wanted job!
Instead of receiving soap:ServerNo such operation: getGreeting2 (HTTP
GET PATH_INFO: /HelloWorldWebServices/HelloWorldPort/getGreeting2) I
want to see the getGreeting response!
How can I do it in CXF Web Servi
On 12/01/2010 09:32 PM, Daniel Kulp wrote:
If you have the WebServiceContext injected, just call:
context.getEndpointReference()
and that should be it.
That's all very well if something can be convinced to invoke the service
first. But this is a chicken and egg situation. What can you do if
Hi, I am using cxf-protobuf 0.3, CXF framework 2.3 and Protobuf-java 2.3 in my
web application, which runs on Tomcat 7.
I create 2 services with these steps:
*1.*
30 matches
Mail list logo