jbossws-cxf | JBossWS-CXF stack | SOAP library

by jbossws Java Version: 5.4.9.Final License: LGPL-2.1

X-Ray Key Features Code Snippets Community Discussions(5)Vulnerabilities Install Support

kandi X-RAY | jbossws-cxf Summary

jbossws-cxf is a Java library typically used in Web Services, SOAP applications. jbossws-cxf has no bugs, it has no vulnerabilities, it has build file available, it has a Weak Copyleft License and it has low support. You can download it from GitHub, Maven.

JBossWS-CXF stack (integration with Apache CXF)

Support

Quality

Security

License

Reuse

Support

jbossws-cxf has a low active ecosystem.

It has 7 star(s) with 36 fork(s). There are 5 watchers for this library.

It had no major release in the last 12 months.

jbossws-cxf has no issues reported. There are 13 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of jbossws-cxf is 5.4.9.Final

Quality

jbossws-cxf has no bugs reported.

Security

jbossws-cxf has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

jbossws-cxf is licensed under the LGPL-2.1 License. This license is Weak Copyleft.

Weak Copyleft licenses have some restrictions, but you can use them in commercial projects.

Reuse

jbossws-cxf releases are not available. You will need to build from source code and install.

Deployable package is available in Maven.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed jbossws-cxf and discovered the below as its top functions. This is intended to give you an instant insight into jbossws-cxf implemented functionality, and help decide if they suit your requirements.

Handle an HTTP GET request
Finds destination based on request URI
Get the destination registry from the bus
Initializes the request metrics
Consume the WSDL message
Returns jvm version from JVM specification
Create a ServiceDelegate
Create a service delegate to the web service
Overrides the default implementation of this class
Gets the full class name
Get a reference to a service class
Handles the callbacks
Send a message
This maps the relationships to the relationship type
Create the SOAP security context
Set the subject
Handle incoming message
Handle an event
Browse a GET request
Override the JBoss TargetInvoker
Invoke a SOAP message
Activate the datagrams
Derives the arguments from a SED command
Process SED command line
Customize endpoint
Handle the message

Get all kandi verified functions for this library.

jbossws-cxf Key Features

No Key Features are available at this moment for jbossws-cxf.

jbossws-cxf Examples and Code Snippets

No Code Snippets are available at this moment for jbossws-cxf.

Community Discussions

Trending Discussions on jbossws-cxf

Type 'com/fasterxml/jackson/datatype/jdk8/Jdk8Module' (current frame, stack[2]) is not assignable to 'com/fasterxml/jackson/databind/Module'

Use DefaultSSLSocketFactory in WildFly/CXF Webservice client

How can I enable RSA15 transport algorithm in WSS4J 2.2.3?

Add jai as wildfly module

Implementing WS-Security Using JBoss EAP 6.3 - Dfiferences between 6.3 and 7?

QUESTION

Type 'com/fasterxml/jackson/datatype/jdk8/Jdk8Module' (current frame, stack[2]) is not assignable to 'com/fasterxml/jackson/databind/Module'

Asked 2020-Feb-06 at 12:32

I upgraded my jackson libraries from 2.5.4 to 2.10.1 as you'll see below and I receive the following error:

...

ANSWER

Answered 2020-Feb-06 at 12:32

I ended up needing to exclude the jackson and resteasy libraries in multiple modules (jars) as well as at the root level in my jboss-deployment-structure.xml. The modules that I am specifying to exclude the libraries use the module that imports the libraries (i.e. where in my question I state A gradle build script of another jar that depends on the one above:).

Source https://stackoverflow.com/questions/59032599

QUESTION

Use DefaultSSLSocketFactory in WildFly/CXF Webservice client

Asked 2019-Sep-06 at 11:55

I'm hoping someone can help me with this. I'm using the following :

WildFly 9
jbossws-cxf-*-5.0.0.Final
cxf-core-3.0.5

and I am dealing with an integration issue with a partner endpoint related to SNI in the HTTPS handshake. Following along with another site (here) I have been able to create a custom SSLSocketFactory and set that as the default SSLSocketFactory, but then I ran into the issue where CXF does not use the default SSLSocketFactory(here). With that I have not found a way to inform CXF to use the default SSLSocketFactory through configuration.

By debugging I was able to set the httpsURLConnectionDefaultHostnameVerifier on the TLSClientParameters to true and confirmed that this resolves the issue. I have also seen a number of posts that imply that this value can be set via a configuration file(JBoss WS config or CXF config) or as a startup parameter, but I have not been able to find a way to do this.

Has anyone else been able to accomplish this and if so can you share how?

...

ANSWER

Answered 2019-Sep-06 at 11:55

So the only answer I could find to this particular issue was pretty brute force/ugly, but here goes in hopes it may save someone some pain later.

I created a custom SSLSocketFactory and set that as the default at startup.
This factory will return a custom connection implementation that extends the CXF extend the SOAPConnectionImpl that will set setUseHttpsURLConnectionDefaultSslSocketFactory to true on the TLSClientParameters.
This is set on the URLConnectionHTTPConduit in turn
Lastly I had to use a ThreadLocal class to hold the host name which is used by the custom SSLSocketFactory

Source https://stackoverflow.com/questions/57516364

QUESTION

How can I enable RSA15 transport algorithm in WSS4J 2.2.3?

Asked 2019-Jul-17 at 21:23

I'm upgrading a SOAP web service client to JDK 11 and WSS4J 2.2.3 (w/o CXF/Spring). The java code uses the 'stand-alone' approach to handle encryption and fails to decrypt the incoming response because it is encrypted using RSA15. The algorithm was disabled by default as of release 2.0.0 but the migration guide suggests that it is possible to enable the algorithm by setting the WSHandlerConstants.ALLOW_RSA15_KEY_TRANSPORT_ALGORITHM property to "true". How can I do this??

I've looked at the WSS4J code and can see that the RequestData object is instantiated from WSSecurityEngine class in the WSS4J framework and I don't see a hook that would allow me to set the allowRSA15KeyTransportAlgorithm property to 'true'. I've been able to put a break-point in eclipse and change the value to ensure it works as expected and it does. I've searched the web and the closest thing I found was a similar question with no apparent answer here Allow the RSA v1.5 Key Transport Algorithm for WildFly / JBossWS / CXF / WSS4J stack. I've tried to revert WSS4J back to version 1.6 which allows the algorithm but then it failed with a different error "WRONG_DOCUMENT_ERR: A node is used in a different document than the one that created it". This seems to occur when using WSS4J 1.6 with any version of jaxws (external to JDK). The only way I can think to solve this is by hacking into the WSS4J 2.2.3 dependency and setting the property default to "true" in the RequestData class but I really don't want to do that.

...

ANSWER

Answered 2019-Jul-17 at 21:23

After a good bit of tracing.. I managed to find it for ya.

This is what I discovered by working backward through the stack trace and looking at the source:

Starting where the exception is thrown at org.apache.wss4j.dom.processor.EncryptedKeyProcessor.handleToken(EncryptedKeyProcessor.java:131)

Source https://stackoverflow.com/questions/57082448

QUESTION

Add jai as wildfly module

Asked 2017-Mar-15 at 11:05

I have a java bean project, I need to use jai, so I add a maven depedendency

...

ANSWER

Answered 2017-Mar-15 at 11:05

I can solve this problem without adding jars to ext of jvm

Code:

Source https://stackoverflow.com/questions/42789579

QUESTION

Implementing WS-Security Using JBoss EAP 6.3 - Dfiferences between 6.3 and 7?

Asked 2017-Jan-27 at 08:05

Recently I worked out a SOAP Web Service/WS-Security solution using JBoss EAP 7 and its JBossWS version (with CXF). This reference was very helpful:

https://docs.jboss.org/author/display/JBWS/WS-Security

The solution is based on a WSDL file that contains a WS-SecurityPolicy.

Now I've been asked to implement a solution based on the same WSDL file, but using JBoss EAP 6.3.

JBoss EAP 7 is the only version of JBoss EAP that I've worked with thus far. I would like to avoid re-inventing the wheel, so to speak, so I'm looking for a hopefully minimal set of configuration changes from the EAP 7 solution.

Does anyone have recommendations for doing this? I've struggled even to find documentation or tutorials, in part because I'm unclear about which version of WildFly, JBossWS, and JBossWS-CXF is included in a JBoss EAP 6.3 installation.

...

ANSWER

Answered 2017-Jan-27 at 08:05

In order to find out which component have been integrated into every JBoss EAP version, open the following URL: https://access.redhat.com/articles/112673

You can check also The WS-Security introduction page on the CXF website

Source https://stackoverflow.com/questions/41877992

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install jbossws-cxf

You can download it from GitHub, Maven.
You can use jbossws-cxf like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the jbossws-cxf component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: