I'm using WebSphere 6.1 with the EBJ3 Feature Pack installed. Does anyone know what jar I need to include in my project from the AppServer folder of my WebSphere installation in order to be able to use the #WebService annoation? I cannot seem to find it. Thanks.
You will require either:
The webservice Feature Pack for Websphere 6.1 http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21264563
A JAXWS implementation, such the Reference Implementation http://jax-ws.java.net/
Pay attention to the order of installation of the Websphere Feature Packs
WAS_HOME/lib/j2ee.jar
Note that in WAS 7.0+, all JARs needed for development are located in WAS_HOME/dev/.
WAS_HOME/plugins/ - com.ibm.jaxws.tools_6.1.0.jar
You may also need to include com.ibm.jaxb.tools, com.ibm.ws.runtime and org.apache.axis2 jars too.
Related
I am looking out for suggestions on the recent vulnerability(https://blogs.apache.org/security/entry/cve-2022-42889) which is also coming from the wso2 IS 5.11 binary downloaded from(https://github.com/wso2/product-is/releases/tag/v5.11.0) and the carbon libraries we are using in custom plugins like:
<groupId>org.wso2.carbon.identity.framework</groupId><artifactId>org.wso2.carbon.identity.mgt</artifactId>
<version>5.18.187</version>
<groupId>org.wso2.carbon.identity.framework</groupId>
<artifactId>org.wso2.carbon.identity.application.authentication.framework</artifactId>
<version>5.18.187</version>
<groupId>org.wso2.carbon.identity.framework</groupId>
<artifactId>org.wso2.carbon.identity.provisioning</artifactId>
<version>5.18.187</version>
As there any upgrades to these which is compatible with wso2 IS v5.11?
From wso2 advisories, it is mentioned that the vulnerability has no impact on the products [1] since the preconditions are not met and the team promises of fixing the vulnerable versions and (paid) customers will be able to obtain it through their security update once it is available. Along with this effort, the public fix will be done for the current public branch and will be available if you build the product-is from the repository. The timeline for the public fix is yet to be known.
And the suggested upgrade would be to 1.10.0 of Apache Commons Text library for 5.11.0.
This library comes to Identity server 5.11 pack mainly through Forget me tool. And in the latest release (wso2is-6.0.0), forget me tool has been externalized[2] which could be used in the product on demand.
Refer:
[1] https://docs.wso2.com/display/Security/CVE-2022-42889
[2] https://is.docs.wso2.com/en/latest/deploy/remove-references-to-deleted-user-identities/#building-the-identity-anonymization-tool
Is there somewhere I can download a plain Apache Felix with all the bundles required for running the latest Jetty 9?
I've been trying to do this by following the Jetty documentation to no avail, it's like trying to put together a puzzle where you don't know where the missing pieces are. Some of the bundles you get from Maven, others from the lib folder from a Jetty installation, and others you download from Eclipse Orbit.
NOTE: it would be great if the Jetty project just provided a zip file with all needed bundles for OSGi on each release, or even better, create a FatJar bundle, that by just releasing a FullJetty bundle would start the whole thing without having a zillion bundles that you never really use directly.
If you just take a look at the Apache Karaf project it's a OSGi Container based on Felix/Equinox and brings Jetty along with Pax-Web as service Layer.
The most benefit of this server is that you just don't need to care much about all those infrastructure bundles and just unpack it and develop your OSGi application with it.
I installed WSO2 Developer Studio 3.2.0 on Eclipse Kepler. I have created an ESB Config Project and defined a proxy service in this project. In this proxy definition there are inSequence, outSequence and faultSequence parts each including set of mediators.
I have created a Carbon Application project and added the artifact as a dependency. After deployment, in final *.car file, I see that the proxy service definition is changed in a way that outSequence does not include any mediators. At deployment stage, outSequence content is emptied. What could be the problem?
First of all, WSO2 Dev Studio is not compatible with Eclipse Kepler. Recommended Eclipse version is Eclipse Juno SR2.
You will experience this problem if you have entered incorrect properties or parameters for a mediator in your OutSequence of the Proxy service. This issue is now fixed in upcoming WSO2 Dev Studio 3.5 version where it will provide you an error message when there is such incorrect or incompatible property/parameter is used.
Therefore please use latest Developer Studio 3.5 version and retry the example.
Hope this helps!!
Thanks and Regards,
Harshana
i created a ws client using wsconsume tool of jboxx 4.2.2 (it's mandatory that i use jboss 4.2.2 for my project).
When i archived and deployed the jar, and used it in my project, it threw a class not found exception.
After the investigation, it turned out that required jaxb libraries are not included in jboss 4.2.2 by default.
I can simply copy the required libraries in from the client folder to server/default/lib from , but i was wondering if there is a configuration i can change to include the client folder by default?
sidenote: i find it strange that i can generate the client but not be able to deploy it without copying the jaxb libraries or adjusting the config, am i missing something?
After the investigation, it turned out that required jaxb libraries are not included in jboss 4.2.2 by default.
Yes. JBoss 4 is ancient, and pre-dates JAXB 2.
i was wondering if there is a configuration i can change to include the client folder by default?
No, you'll need to include the required libraries either in your application itself, or in server/default/lib.
i find it strange that i can generate the client but not be able to deploy it without copying the jaxb libraries or adjusting the config
Generating code is just an exercise in outputting text. It doesn't in itself require the libraries that it generates code to use.
We are migrating a web application from JBoss 4.2.3 to JBoss 6. The application needs to control the order in which jars are searched for classes during classloading. This was achieved in JBoss 4.2.3 by hacking EARDeployer class in jboss.jar to add jars to the DeploymentInfo object in a specific order.
Is there a way to achieve the same result in JBoss 6?
Ales Justin over at JBoss was able to help me through this. Our conversation can be found here: Link