OK! As soon as I can I'll try CXF 2.1 and I'll send you a feedback!
Thanks.
Davide
--
View this message in context:
http://www.nabble.com/WebServiceContext-not-injected-in-endpoint-tp15708465p15731308.html
Sent from the cxf-user mailing list archive at Nabble.com.
Hi,
I'm experiencing a rather strange problem using the latest version of
CXF. I'm creating a web service by generating code from a hand-written
WSDL which works fine in all our tests, but now we have received a
notification from one of our customers that the WSDL that is outputted
does not
We're made a lot of changes in this area for 2.1. If you're willing to move
to a 2.1 snapshot, I'm willing to work with you to figure out how to do what
you need to do.
On Thu, Feb 28, 2008 at 6:30 AM, Tony Burdett [EMAIL PROTECTED] wrote:
Hi,
I'm in the process of porting my service from
willem.jiang wrote:
After went through the JaxWsServerFactoryBean codes, I think you need to
modify the invoker factory construction argument.
Here are the codes.
Object implementor = new GreeterImpl();
String address = http://localhost:9000/SoapContext/SoapPort;;
Hi Benson,
Thanks for the response. I've nothing to tie me to any particular
version, so I'm more than happy to use a 2.1 snapshot. I believe that
all I actually need to do is configure my service to recognise the
additional types I want it to use. But where I would even start doing
this
You are right, Its unfortunate that the ciphersuite 3DES_EDE_CBC_SHA
isn't enabled by default since this is a strong and commonly used
ciphersuite.
I suspect it is an oversight.
Do you want to raise a JIRA on this? (should be easily fixed)
I'll raise one if you want, but thought it would be nice
In 2.1, you'd create a DefaultTypeMapping object, add your mappings, and
then push that into an AegisContext object. You'd then push the AegisContext
object into the AegisDatabinding object. You'll really need to be looking at
CXF source. Look at the AegisContext class and the AbstractEncodingTest
Dan,
Does this one still look fixable and would it be possible to patch 2.0.x
with the fixes to get functional WSDL generation in this case?
Thanks again for your endeavours in resolving these issues,
Phil :n.
On Wed, 2008-02-27 at 16:48 -0500, Daniel Kulp wrote:
This looks exactly like
Okay, sounds like the certs were as we suspected then :-)
If you were proposing a WSS4J enhancement request for x509TokenProfile
1.1 then perhaps it might be worth throwing a query to the WSS4J mail
list?
Obviously for this sort of extension we shouldn't add the logic into CXF
itself.
Cheers,
As a matter of fact, it works for even 2.0.4. I tried it yesterday, this
context got injected and I could get request back indirectly from it.
Well, I used Spring bean for all my test.
On 2/28/08 3:07 AM, Davide Gesino [EMAIL PROTECTED] wrote:
Hi Dan,
I have used this CXF 2.1 snapshot.
Quick question:
Are those elements top level elements or do they just occur inside
other structures (like xsd:sequence/xsd:choice)?
It it's the former, then they are NOT supposed to have
minOccurs/maxOccurs constraints at all. Both should actually be
dropped.If you check section 3.3.2 of
I was unable to find config options to specify the source/class/resource
directories for the java2wsdl or java2ws maven plugins. Currently the
plugins output both source and class files in same directory. Also
java2ws outputs source/class files under the project directory, rather
than
Hi,
All these elements are part of a xsd:sequence, so that shouldn't be the
problem. I'll try to find time to create a small test case, though
unfortunately my time currently rather limited. I'm using 2.0.4 anyway, which
is also what we use in production.
Matthias
-Ursprungligt
Davide,
How is your bus/cxf stuff configured? Are you using the defaults or are
you specifically using the spring imports to import very specific
things?
If it's the latter, you will need to import:
META-INF/cxf/cxf-extension-jaxws.xml
as well.
If it's the former, that sounds like a
No idea.
Couple suggestions:
1) What version of maven are you using? You may need 2.0.7. Not really
sure.
2) Can you run with -X flag and look at the Classpath that is printed
just before the javac command? It should have:
On Wednesday 27 February 2008, Brad Harper wrote:
Can this be done using JAXB? These nillable attributes are the bane
of my existence... Is there anyway to make them go away?
Depends on where in the schema and who is generating them
The nillables in the actual java beans that you return
I'm going to assume you are using CXF 2.0.4 or the 2.1 snapshots If
not, definitely update as what I'm about to describe applies to code
enhanced for that version
It SOUNDS like you are using a wrapped doc/literal wsdl, which is fine.
However, in that case, the wsdl message only
How could I change the endpoint addresses of all service calls in cxf?
I am trying to switch the endpoint address from https://myhost/websvc to
http://myhost/websvc
Is there a 1-line configuration to do that?
Steps 1 and 2 of here[1] are how I downloaded and compiled CXF. Perhaps that
might be of help.
Glen
[1] http://www.jroller.com/gmazza/date/20080225
dkulp wrote:
No idea.
Couple suggestions:
1) What version of maven are you using? You may need 2.0.7. Not really
sure.
2) Can
I'm unsure if you're trying to change the URL that a SOAP client is using, or
a the URLs being employed by the web service.
If the former, Step 7 of [1] might help you. You can use dependency
injection to feed a URL to your SOAP client, and use the Java code in Step
#7 to dynamically change the
Never mind, this is definitely not working. Looking into it.
Dan
On Thursday 28 February 2008, Daniel Kulp wrote:
Davide,
How is your bus/cxf stuff configured? Are you using the defaults or
are you specifically using the spring imports to import very specific
things?
If it's the
I just wanted to let everyone know that I've deployed a new CXF 2.1
snapshot that has an updated java_first_jaxws sample that includes using
an interface and a Map object as parameters/returns to methods on the
interface.
Since those have been common issues lately, I'd greatly appreciate it
Suddenly I am getting this error:
2008-02-28 13:47:02,631 ERROR [STDERR] - Feb 28, 2008 1:47:02 PM
org.apache.cxf.phase.PhaseInterceptorChain doIntercept
INFO: Application has thrown exception, unwinding now: Class
javax/xml/ws/WebServiceContext violates loader constraints
It was working fine
Looks like there are two different jaxws-api jars being picked up
somehow.That's definitely what I'd check for.
Not sure why it would start happening today unles you are on a 2.1
snapshot using maven or something. I did a deploy with some updated
WebServiceContext injection code this
Hi,
I am using CXF version 2.0.4-incubator in an application that implements
the JAX-WS ProviderSource interface. The application throws a
SOAPFaultException on error, but the client gets the HTTP message below,
which does not have a SOAP Envelope and hence cannot be parsed.
The code snippet
Well, I still can't figure out what changed.
But JBoss does include that class in jboss-jaxws.jar.
Removing the CXF version (jaxws-api-2.0.jar) from
my install solved the problem.
Is there a list of JARs to avoid for a JBoss install?
I would suspect most of the API-type JARs would be
duplicated
I need some help with Websphere 6.1.x and CXF2.0.4. I wrote a simple service
and client using CXF and getting below exception when a Client code invokes
the service.
Can anyone help me out?
[2/28/08 17:22:26:334 EST] 0023 PhaseIntercep I
org.apache.cxf.phase.PhaseInterceptorChain
Hi Glen,
I am implementing the client side, so [1] is more relevant.
I can see that the URL is changed at
bp.getRequestContext().
put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, endpointURL);
What I want to make it happen is that I could change the endpoint address in
cxf.xml
Forwarding to cxf-user list (email accidentally just went to
Christopher)
Am Donnerstag, den 28.02.2008, 21:58 -0500 schrieb Glen Mazza:
Possibly, but I don't think you should do that in a CXF-specific manner
that you are envisioning. (I don't know of a CXF-specific manner
myself.)
It
When I call the service as a client, it takes 5 seconds to load. I am not sure
whether it takes 5 seconds to create the service or it takes 5 seconds to look
up for ciper filters.
Feb 29, 2008 2:14:42 PM
org.apache.cxf.service.factory.ReflectionServiceFactoryBean buildServiceFromWSDL
INFO:
I already did that using jakarta commmons-configuration, I think it is
better to move to Spring which is more appropriate.
Thanks for the help.
- Original Message -
From: Glen Mazza [EMAIL PROTECTED]
To: cxf-user cxf-user@incubator.apache.org
Sent: Friday, February 29, 2008 11:07 AM
31 matches
Mail list logo
