Hi
Maybe a complete different solution approach. Instead of extending this
functionality into CXF itself you could delegate this to the STS component
(running in a seperate VM) which has been introduced in CXF 2.5.
The STS allows you to implement custom security token provider and if needed
Hi
On 07/12/11 00:42, Steve Karlovic wrote:
Hello,
How can I have the WADL generator produce and describe which endpoints
throw exceptions? Also, I would like definition of the exception
represented in the same WADL where the response and request objects can be
found if possible.
The older
Hi Dan,
From here, I've gathered that the problem is that the encryptionName is
null, however I'm unsure what the encryptionName should be (should it be
alice (the username), the encryption certificate alias, something else?)
and also where this property would be propagated from (I currently
What version of CXF are you using + can you include the incoming message?
Colm.
On Tue, Dec 6, 2011 at 6:46 PM, DSL dlapr...@gmail.com wrote:
Has anyone seen this error on a web service when decrypting the
incomding message:
2011-12-06 13:37:18,100 ERROR [STDERR] (http-127.0.0.1-8080-2)
Thank you for your quick response, I have included the information you
requested below:
Environment:
Jboss AS 5.1.0, jbossws-cxf 3.4.0 which uses ( cxf 2.3.0 )
Incoming message:
soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;
I don't see anything obviously wrong with it. Do you have a
stack-trace? Would it be possible to try with a more up-to-date
version of CXF (even 2.3.7)?
Colm.
On Wed, Dec 7, 2011 at 1:24 PM, DSL dlapr...@gmail.com wrote:
Thank you for your quick response, I have included the information you
Hi all,
I would like to submit a question since I have noticed an inconsistency
between WSDL generated by org.apache.cxf.tools.java2ws.JavaToWS and
response sent by CXF.
I have a service like this:
@WebService(endpointInterface = be.eft.cbkv3.ws.WSExampleService,
serviceName =
Thank you for your prompt response!
Great!
http://cxf.apache.org/docs/transformationfeature.html
is just what I need!
By the way, are you concerned about the processing costs on the client side
Not yet..software is not mature enough to really worry about this
now...in general our xml output is
The original email contained the stacktrace, and I am tied to the
jboss web service stack.
On Wed, Dec 7, 2011 at 8:36 AM, Colm O hEigeartaigh cohei...@apache.org wrote:
I don't see anything obviously wrong with it. Do you have a
stack-trace? Would it be possible to try with a more up-to-date
Thanks for the quick response Colm. The links you provided and information
were a tremendous help.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Unable-to-acquire-token-from-STS-using-SymmetricKey-key-type-tp5053667p5056123.html
Sent from the cxf-user mailing list archive at
Thanks for the response Sergey. I will try out using beans for parameters.
If I want to describe two possible responses for 200 OK, for example an
error message (based on a ResponseError bean) and another with actual
results (based on a ResponseResult bean). Is there a way I can annotate the
Does anyone know why I'm unable to map query parameters via @QueryParam to an
object? For example, if I enter:
http://127.0.0.1/search?term=javamax=10offset=10
Only the term parameter is captured. Below are the relevant pieces of code.
@Path(/search)
public class SearchService {
...
...
Hi,
I want to test a JAXRS client calling a REST service with json encoding. The
service is configured with dropRootElement and now the client fails because
it expects the root element there.
How can I tell the client proxy to stop looking for the root element?
Thanks
Guy
Hi,
I faced the problem in custom conduit selector scenario.
Use case: custom conduit selector (extends AbstractConduitSelector) resolves
endpoints dynamically (using external ServiceRegistry).
When address is resolved, resolved address cannot be set to
AbstractConduitSelector.endpoint,
Hi Guy
On 07/12/11 14:49, Guy Pardon wrote:
Hi,
I want to test a JAXRS client calling a REST service with json encoding. The service is
configured with dropRootElement and now the client fails because it expects
the root element there.
How can I tell the client proxy to stop looking for the
Hi Sergey, thanks for the awesome (and quick response). What you suggested
worked great. I overrode this method:
@Override
protected boolean isSupported(Class? type, Type genericType, Annotation[]
annotations) {
if(String.class.equals(type)) {
return false;
} else {
Hi
On 07/12/11 16:35, Steve Karlovic wrote:
Thanks for the response Sergey. I will try out using beans for parameters.
If I want to describe two possible responses for 200 OK, for example an
error message (based on a ResponseError bean) and another with actual
results (based on a ResponseResult
Does anyone know why I'm unable to map query parameters via @QueryParam to
an object? For example, if I enter:
http://127.0.0.1/search?term=javamax=10offset=10
Only the term parameter is captured. Below are the relevant pieces
of code.
@Path(/search)
public class SearchService {
unfortunately i can't, i'm implementing a specific use case as part of the
requirement. I'm considering implementing my own custom saml action to
replace the provided saml action.
--
View this message in context:
http://cxf.547215.n5.nabble.com/cxf-and-saml1-0-tp5034076p5056693.html
Sent from
Could you confirm what version of WSS4J you are using?
Colm.
On Wed, Dec 7, 2011 at 2:37 PM, DSL dlapr...@gmail.com wrote:
The original email contained the stacktrace, and I am tied to the
jboss web service stack.
On Wed, Dec 7, 2011 at 8:36 AM, Colm O hEigeartaigh cohei...@apache.org
After some more CXF debuggging:
This is what the top of the document looks like in the working case,
when getNamespaceURI() does not return null:
?xml version=1.0 encoding=UTF-8?
xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:tns=example.com targetNamespace=example.com
On Wednesday, December 07, 2011 2:43:11 PM rouble wrote:
After some more CXF debuggging:
This is what the top of the document looks like in the working case,
when getNamespaceURI() does not return null:
?xml version=1.0 encoding=UTF-8?
xs:schema
I am using cxf to generate java code from a wsdl.
The wsdl is protected by authentication so I could not produce the code
directly from the wsdl.
Instead I made A copy of the wsdl and put it on my local machine.
When trying to create the service to make the web service call I need to use
wsdl
After further debugging it seems like it may be the xml validation during
marshalling that is causing issues. I changed the schema to make the field
that I was having problems with not be required. I also added a print
statement in the client to alert me to the event that the field was empty or
There is an option in jaxb marshaller to escape those white space
characters by setting its property jaxb.encoding to UTF-8. If you
have a direct access to the marshaller you could just do
marshaller.setProperty(jaxb.encoding, UTF-8)
If you use jaxws endpoint in CXF, you can achieve the same
Hi,
I was wondering if you can try running your scenario with jetty
instead of tomcat and see if this also leads to the same problem. The
reason why I am asking this is that I have seen some buffering issue
with tomcat in the past.
thanks.
regards, aki
2011/11/30 Daniel Eriksson
Hi
On 07/12/11 17:46, Davis Ford wrote:
Hi Sergey, thanks for the awesome (and quick response). What you suggested
worked great. I overrode this method:
@Override
protected boolean isSupported(Class? type, Type genericType, Annotation[]
annotations) {
if(String.class.equals(type))
This is a java first service, so CXF is generating the faulty schema.
We have two (almost identical) boxes, with tomcat. On one this issue
is reproducible, on the other it is not. The war file is the same.
Any tips on how to debug this further? It seems to be related to how
CXF generates the
Hi
On 07/12/11 18:10, Dan King wrote:
Does anyone know why I'm unable to map query parameters via @QueryParam to
an object? For example, if I enter:
http://127.0.0.1/search?term=javamax=10offset=10
Only the term parameter is captured. Below are the relevant pieces
of code.
@Path(/search)
New to CFX and JAX-WS so please forgive my basic ignorance. I might be asking
the wrong questions.
Is there a way to associate multiple WSDL URIs with a WebServiceProvider?
I am trying to right a generic provider that can handle invocations of
operations defined in different WSDLs. I know I can
... much appreciated.
Thanks!
Steve
On Wed, Dec 7, 2011 at 9:56 AM, Sergey Beryozkin sberyoz...@gmail.comwrote:
Hi
On 07/12/11 16:35, Steve Karlovic wrote:
Thanks for the response Sergey. I will try out using beans for parameters.
If I want to describe two possible responses for 200 OK,
Sounds great.
I have wrapped all the required output into a single custom class using
subclasses as necessary. It now generates the xsd at wadl query. This also
optimizes bandwidth by omitting unnecessary fields.
The url:
http://pathToMyMethod?_wadl_type=xml
returns the xsd I require, but it is
Thanks. It is the answer me looking.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Setting-Http-conduit-using-spring-configuration-file-tp2644363p5057667.html
Sent from the cxf-user mailing list archive at Nabble.com.
33 matches
Mail list logo
