org.apache.axis | Axis webservice framework integration for the Idega platform
kandi X-RAY | org.apache.axis Summary
kandi X-RAY | org.apache.axis Summary
Axis webservice framework integration for the Idega platform
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Returns an instance of the given IBOS session class
- Gets the http session
- Gets the http servlet request
- Get the servlet context
- Returns an IWUserContext
- Initialize this servlet
- Auto deploy the services
- Set Axis Axis
- Loads a bundle jar
- Gets the Axis engine
- Transforms WSDD into a WSDD document
- Get the service bean using the given interface
- Returns the IWApplicationContext
- Initialize the Applet
- Add a new page to the notebook
- Get the HTTP servlet response
- Stop the Applet
- Overrides the default get method
- Overrides the default post method
- Start the application
org.apache.axis Key Features
org.apache.axis Examples and Code Snippets
Community Discussions
Trending Discussions on org.apache.axis
QUESTION
I want to edit SendMessage Operation Code in existing AWS SQS Connector(V1.0.7) and wanna to build this editable connector and use it in WSO2 EI 6.4.0.
Reason to edit existing Code: Unable to post incoming payload into AWS SQS Queue often. For more reference click here
Steps I followed:
- I just downloaded AWS SQS Connector (V1.0.7) from GitHub by using Download Zip Option.
- after unzipping it, i did
mvn clean install
by navigate to directory called "esb-connector-amazonsqs-org.wso2.carbon.connector.amazonsqs-1.0.7" - Build Successful by using Apache maven 3.8.4 and got zip file inside "target" directory.
- I have taken that zip file and unzipped it to add below code in Send Operation
Just adding Endpoint Timeout Error handling to existing http call.
...ANSWER
Answered 2022-Jan-25 at 13:43Resolved above connector build issue and Now I can use custom built AWS SQS connector(V1.07) in WSO2 EI Server.
Steps:
- Open
sendMessage.xml
operation file directoryesb-connector-amazonsqs-org.wso2.carbon.connector.amazonsqs-1.0.7\src\main\resources\amazonSQS-message
- modified section like below.
- again goto directory
esb-connector-amazonsqs-org.wso2.carbon.connector.amazonsqs-1.0.7
wherepom.xml
resides - run
mvn clean install
in above directory. - after build successful, we can get
amazonsqs-connector-1.0.7.zip
file inside directoryesb-connector-amazonsqs-org.wso2.carbon.connector.amazonsqs-1.0.7\target
QUESTION
(previously it was working fine but don't what is changed ) When i am removing the default handler from synapse configs and adding my custom handler it is giving this error
...ANSWER
Answered 2022-Jan-13 at 08:36I think the problem is with the AuthenticationContext object. We populate the authContext object at the Authentication handler(in each authenticator [1]) and this object is used at the throttle handler[2]. when you replaced the Authentication handler with your custom handler, you might have missed populating this object. Try populating this object as [1].
[1] - https://github.com/wso2/carbon-apimgt/blob/v6.7.206/components/apimgt/org.wso2.carbon.apimgt.gateway/src/main/java/org/wso2/carbon/apimgt/gateway/handlers/security/oauth/OAuthAuthenticator.java#L301 [2] - https://github.com/wso2/carbon-apimgt/blob/v6.7.206/components/apimgt/org.wso2.carbon.apimgt.gateway/src/main/java/org/wso2/carbon/apimgt/gateway/handlers/throttling/ThrottleHandler.java#L193
QUESTION
In our company we use WSO2 EI V6.4. I made the configuration sur connect to azure service bus with this guide and all is working
Now we have to use the last patched version of EI 6.4, and when i made the same configuration, I get this error
...ANSWER
Answered 2021-Dec-21 at 22:17I have had similar problem and used version of qpid-jms-client-0.11.1
thats works for me. I get it from this Maven repository
QUESTION
I am just trying to post incoming payload to rabbitmq by using messageStore in WSO2 EI 6.6.0.
API-Code:
...ANSWER
Answered 2022-Jan-05 at 12:35If you want to send, just JSON message as payload to RabbitMQ, don't use message store. Message stores, are storing all synapse message context with payload for later processing - that is their purpose. So that is why you see in decoded RabbitMQ Payload not only the message, but also additional properties.
For sending JSON to RabbitMQ you can use just to a proper
endpoint
.
Look as this documentation sample.
I have also have made some sequance template
for more easy use of sending messages to rabitmq, so next you can may look at this helpful post, and adapt to your own needs.
QUESTION
I have been trying to understand why this is happening. My ESB does a call towards https://login.microsoftonline.com/ in order to obtain a token which I use to do a call towards an endpoint. The problem is that when a call is sent with my ESB I get:
...ANSWER
Answered 2021-Dec-02 at 09:20This issue was resolved. The problem was that https://sub-domain.dns.net?qparam=999999999 was using a json server with base configurations. It was working properly with Postman but for some reason it wasn't working with wso2 calls from MI. The issue was resolved on the client side with the proper configuration of the json server.
QUESTION
I want to call a soap web service using axis 1.4 to generate the source code: the response format is String and the request format is an xml sent in string format: the error encountered is as follows:
...ANSWER
Answered 2021-Oct-28 at 09:21I solved this problem by using and directly calling the URL of the soap web service with RestTemplate from spring boot.
QUESTION
I am trying to write a proxy in wso2 which, given an input in jason format, calls a webservice with a slightly different signature. I wrote a Javascript function to perform the transformation but I get the following error message:
[2021-10-23 14:21:14,520] ERROR {ScriptMediator} - {proxy:cambioStatoPratica} The script engine returned an error executing the inlined js script function mediate com.sun.phobos.script.util.ExtendedScriptException: org.mozilla.javascript.EcmaError: TypeError: Cannot call method "info" of undefined (#3) in at line number 3 at com.sun.phobos.script.javascript.RhinoCompiledScript.eval(RhinoCompiledScript.java:68) at javax.script.CompiledScript.eval(CompiledScript.java:92) at org.apache.synapse.mediators.bsf.ScriptMediator.mediateForInlineScript(ScriptMediator.java:395) at org.apache.synapse.mediators.bsf.ScriptMediator.invokeScript(ScriptMediator.java:290) at org.apache.synapse.mediators.bsf.ScriptMediator.mediate(ScriptMediator.java:258) at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:109) at org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:71) at org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158) at org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:228) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) at org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:375) at org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:434) at org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:182) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: org.mozilla.javascript.EcmaError: TypeError: Cannot call method "info" of undefined (#3) at org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3687) at org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3665) at org.mozilla.javascript.ScriptRuntime.typeError(ScriptRuntime.java:3693) at org.mozilla.javascript.ScriptRuntime.typeError2(ScriptRuntime.java:3712) at org.mozilla.javascript.ScriptRuntime.undefCallError(ScriptRuntime.java:3731) at org.mozilla.javascript.ScriptRuntime.getPropFunctionAndThisHelper(ScriptRuntime.java:2258) at org.mozilla.javascript.ScriptRuntime.getPropFunctionAndThis(ScriptRuntime.java:2251) at org.mozilla.javascript.gen._Unknown_Source__19._c_script_0(:3) at org.mozilla.javascript.gen._Unknown_Source__19.call() at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394) at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091) at org.mozilla.javascript.gen._Unknown_Source__19.call() at org.mozilla.javascript.gen._Unknown_Source__19.exec() at com.sun.phobos.script.javascript.RhinoCompiledScript.eval(RhinoCompiledScript.java:55) ... 16 more
this is the small eg simple proxy I wrote:
...ANSWER
Answered 2021-Oct-23 at 13:48Well, I've never worked with WSO2 myself, but let's take a look at the error message you're getting. It's this:
TypeError: Cannot call method "info" of undefined (#3) in at line number 3
The error seems clear enough. You're trying to call an info
method on something that's undefined
, and you can't call methods on undefined
.
Let's take a look at line 3 of your script, where the error tells us the problem is:
QUESTION
I am attempting to call the getContentStream() function in the FileNET/CMIS SOAP/web service. It takes 2 required parameters, a String for the repositoryID, and a String for the documentID. The rest of the parameters are optional. The method signature is this:
org.oasis_open.docs.ns.cmis.ws._200908.ObjectServicePort.getContentStream(
@WebParam(name="repositoryId", String arg0,
@WebParam(name="objectId", String arg1,
@WebParam(name="streamId", String arg2,
@WebParam(name="offset", BigInteger arg3,
@WebParam(name="length", BigInteger arg4,
@WebParam(name="extension", CmisExtensionType arg5) throws CmisException
In my Java code, I have this:
...
String guid = "";
guid = request.getParameter("guid").trim();
//Connect to FileNET/CMIS Web Service:
GetObject objRequest = new GetObject();
ObjectService objService = new ObjectService();
ObjectServicePort objectServicePort = objService.getObjectServicePort();
((SOAPBinding)((BindingProvider) objectServicePort).getBinding()).setMTOMEnabled(true);
((BindingProvider) objectServicePort).getRequestContext().put(BindingProvider.USERNAME_PROPERTY, "username");
((BindingProvider) objectServicePort).getRequestContext().put(BindingProvider.PASSWORD_PROPERTY, "password");
((BindingProvider) objectServicePort).getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, "https://filenet.web.address.there/openfncmis/services11/ObjectService");
// Call to getContentStream():
CmisContentStreamType cmisContentStreamType = objectServicePort.getContentStream(reposName, guid, "", null, null, null);
...
When I run the code, it is failing with the following error in the console:
[10/7/21 13:52:28:724 EDT] 000000db webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[action]: org.oasis_open.docs.ns.cmis.ws._200908.CmisException: CIL1500: The service cannot be completed.
Explanation: This error can occur for the following reasons:
An error in the IBM CMIS application
An error on the repository Action: See the HTTP response or the application server SystemOut.log file for more information and to review the stack trace for the exception. By default, the SystemOut.log file is in the [WAS_profile_location]/logs/[server]/logs subdirectory of the application server installation directory.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:88) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:57) at java.lang.reflect.Constructor.newInstance(Constructor.java:437) at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.createServiceException(MethodMarshallerUtils.java:1331) at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.demarshalFaultResponse(MethodMarshallerUtils.java:1142) at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitWrappedMethodMarshaller.demarshalFaultResponse(DocLitWrappedMethodMarshaller.java:680) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.getFaultResponse(JAXWSProxyHandler.java:626) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createResponse(JAXWSProxyHandler.java:566) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(JAXWSProxyHandler.java:432) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAXWSProxyHandler.java:213) at com.sun.proxy.$Proxy208.getContentStream(Unknown Source) at gov.ohio.jfs.wotcweb.actions.DisplayFileNETDocuments.execute(DisplayFileNETDocuments.java:131) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:425) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:228) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:449) at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1235) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:779) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478) at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:143) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:78) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:969) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1109) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:4144) at com.ibm.ws.webcontainer.webapp.WebAppImpl.handleRequest(WebAppImpl.java:2208) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1030) at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1817) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:382) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:465) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:532) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:318) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:88) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)
The FileNET Error Log indicates this:
[10/7/21 10:18:37:541 EDT] 000000c1 DALP8Exceptio E com.ibm.ecm.cmis.dal.p8.DALP8ExceptionHandler handleException null
...ANSWER
Answered 2021-Oct-19 at 21:22I figured out the problem!
For the 3rd argument, I had " ", when I should have had "null".
Now it works!
j.
QUESTION
I am using wso2 apim 3.1.0 I want to enable json schema validation for the json payload. I have referred to the belpw document for setting up json shema validation in wso2 apim https://m-saranki.medium.com/unboxing-json-schema-validator-320-2dd944dae6c0 . I am testing the below API for json schema validation
...ANSWER
Answered 2021-Oct-19 at 16:08- Explanation
I believe you are using wso2am-3.1.0 vanilla pack along with a custom sequence file which probably has a mediator using "json-eval($.)" expression. Please confirm. This is a known issue in the wso2am-3.0.0 and wso2am-3.1.0 vanilla packs.
This is becasue when we use json-eval($.) expression in a sequence in the /repository/deployment/server/synapse-configs/default/sequences directory and when it gets deployed, the synapse is setting the GsonJsonProvider [1] to represent the JSON inside the Jayway JsonPath[2].
Since the GsonJsonProvider is getting loaded, even if we remove the particular sequence file which has the json-eval($.) expression in a property mediator, the issue will still persists until we restart the server.
But, if we do not use the json-eval($.) expression at all in a sequence in the /repository/deployment/server/synapse-configs/default/sequences directory, we will not get the above error when we enable the JSON schema validation as the jsonsmartjsonprovider [3] is used to represent the JSON inside the Jayway JsonPath.
Since the JSON object representation is getting different in the error scenario, it throws the IllegalArgumentException in that case.
- Solution
You can approach one of the following solution as suggested below.
- This issue has been fixed in the latest WUM/updated pack. If you have the WSO2 subscription then you can get the latest update.
- You can deploy a new wso2am-3.1.0 vanilla pack and invoke the API calls without the sequence having json-eval($.) expression.
QUESTION
I am developing a couple of integrations (as Maven projects) between several defect management systems, one of which exposes services through WSDL, forcing me to consume them through WS. For the latter I succesfully developed the code for JDK-8 and everything works.
I am now in the middle of JDK migration from 8 to 11 and need to update the integration that makes use of WS. I understood that in Java 11 some EE libraries (including JAX-WS) were removed. I then surfed the Web in order to get rid of this problem, but after a couple of days of tests and cut-and-paste of depenendencies I still have the same problem: cannot instantiate the WS to interact to the final server (that is a CA SDM 14.1).
Currently I have the following error:
...ANSWER
Answered 2021-Oct-01 at 16:39In the Oracle release notes for Java 11, I found this:
other-libs ➜ JEP 320 Remove the Java EE and CORBA Modules
Remove the Java EE and CORBA modules from the Java SE Platform and the JDK. These modules were deprecated in Java SE 9 with the declared intent to remove them in a future release (JEP 320).
The following modules have been removed from Java SE 11 and JDK 11:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install org.apache.axis
You can use org.apache.axis 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 org.apache.axis 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
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page