I have an JAVA application EAR file, which contains EJB(3.1 annotaiton based) and WS(JAX-WS annotation based) modules. When I deploy this on weblogic it get's deployed properly without any issue, but when I try to deploy the same ear on websphere 8.5.5.0 it's not getting deployed. It gets hung in the step "Installation of MyAPp started." and doesn't move further and no errors in log as well.
The EAR doesn't have any JAR reference, all it contains is around 5 EJB and 50 web service modules(both EJB and WS has annotations). If I create the EAR with 5 EJB and 10 WS modules then it gets deployed after long time.
Is there any specific setting I need to do to get this deployed?
Thanks.
Related
I am migrating to Wildfly 8.2 from JBoss 5.1, I am deploying a Web Service using the resteasy and some EAR which has the code to get the requested data from the DB. Both the EAR which has multiple (6) JARs, but when I call the Web Service, it is not able to find the EAR and refer it's JARs
14:57:48,183 INFO [stdout] (default task-4) InitialContextFactory not defined - using default: org.jnp.interfaces.NamingContextFactory
14:57:48,184 ERROR [stderr] (default task-4) javax.naming.NameNotFoundException: bpc/AccountManagementService -- service jboss.naming.context.java.bpc.AccountManagementService
I have 2 separate deployment of EAR and WAR and both of them are deployed simultaneously and they both get deployed without any hassle.
Why are then not able to integrate is my issue right now.
If you migrated from jboss 5 to wildfly, you have to adjust your jndi lookups.. You are getting a NameNotFoundException, so probably you are performing a lookup using the old jndi syntax..
When you startup your server, the log will show you different jndi names for your ejbs..
If you are looking for an ejb from a war, and both of them are not bundled in the same ear, then you have to use the java:global naming type..
For example, assuming that AccountManagementService is an interface, annotate it with #Remote, and search it from your war using the following jndi syntax
java:global/earName/ejb-jar-name/AccountManagementService!com.example.AccountManagementServiceImpl
See if this document helps (Modify JNDI lookup code section) https://docs.jboss.org/author/display/AS71/Order+Application+Migration+from+EAP5.1+to+AS7
I resolved this issue by adding jboss-deployment-structure.xml in my WAR file under the web-inf folder
by adding dependency like
dependencies>
<module name="deployment.MY_EAR.ear.MY_EJB_JAR.jar"/>
</dependencies>
I have similar issue.
I am migrating from weblogic to wildfly.
One JAR which has only one property file and one EAR, both are deployed simultaneously without any issue.
From EAR application, need to access the property file from the JAR.
This is working fine in weblogic but wildfly not identifying the property file.
I'd like to write a axis2 webservice for deploying BPEL Processes on a Apache ODE.
At the moment I have two main issues/questions.
I wrote a simple WS that creates a file.
It works fine in eclipse with a integrated apache tomcat with axis2.
But if I run the service on the exact same server without ecplise it won't work and I get 'Unhandled IOException' Errors, although I have the handling implemented (otherwise ecplise would cry about it all the time).
EDIT: I solved it by not uploading the service.aar with axis2 but putting it in the /webapps folder.
How do I get access to the folder were I need to put the BPEL files?
Is it obligatory that the service runs on the same server as the ODE?
EDIT: Getting access to the folder on the same server is an easy one with 1.
How do I transfer files with a webservice?
Better: How do I implement it?
Regarding 2) you can use the deployment API exposed by ODE. This allows for transfering deployment units (zip files containing BPELs, WSDLs, DDs) via SOAP to ODE and starting the deployment.
The WSDL is available at http://.../processes/DeploymentService?wsdl, on the default installation that would be http://localhost:8080/ode/processes/DeploymentService?wsdl
I am trying to deploy our proprietary web service application (WAR) into Weblogic 11g server. I have created the WAR using Eclipse Indigo and Java 1.6.
I got the below error,
Messages An error occurred during activation of changes, please see
the log for details. Error encountered during prepare phase of
deploying WebService module 'TWSWebSec.war'. When processing
WebService module 'TWSWebSec.war'. Can't find wsdl
/wsdls/wsc10/wscoor.wsdl When processing WebService module
'TWSWebSec.war'. Can't find wsdl /wsdls/wsc10/wscoor.wsdl
The deployment has been successfully installed.
I tried with a hack of creating wscoor.wsdl into the specified folder and created a new WAR, this time the error was that it is a premature closure of file, which meant the file is identified and there is nothing in the file to read.
After this, i tried to input manually the service, interfaces, operation as per the created Service endpoint interfaces/ Web services, this time i got the error
An error occurred during activation of changes, please see the log
for details. Error encountered during prepare phase of deploying
WebService module 'TWSWebSec.war'. When processing WebService module
'TWSWebSec.war'. Can't find wsdl
/wsdls/wsc11/wstx-wscoor-1.1-wsdl-200702.wsdl When processing
WebService module 'TWSWebSec.war'. Can't find wsdl
/wsdls/wsc11/wstx-wscoor-1.1-wsdl-200702.wsdl The deployment has
been successfully installed.
Am I missing anything here? Is it a configuration problem? Do I need to update any JARs I use?
Please help. Also let me know if more information required?
I post this because there is a chance that you may be in a case that is similar to what I experienced. I had the same error (i.e. "can't find wsdl") yesterday afternoon when trying to make WebLogic deploy a client created with Eclipse's web service generator using CXF. It just never worked. Today I replaced that client with one made one using WebLogic's generator, also in Eclipse, where it is found under Oracle, WebLogic, Web and Service Client. That worked for me. It seems that WebLogic uses Metro and not CXF. There is certainly nothing wrong with CXF but it does not seem to make a good pair with WebLogic.
Best regards Johannes
I generated a Soap Service from a WSDL and now I need to deploy it to my existing application which uses embedded tomcat (I.E. I have a class which extends TomcatServeletContainer and a main class which instantiates that class and starts the server).
I see many examples for how to deploy an axis service to a standalone tomcat using a WAR, or a WSDD, but I don't see how to wire it together myself. I assume I have to define a servelet in the web.xml and provide some other glue. Any assistance or pointers to appropriate documentation would be most appreciated.
Thanks!
-Carl
Have you been able to get this to work?
I've been trying to build a webservice (in a standalone war-file containing the axis jars (w/dependencies)+server-config.wsdd) using maven. I really don't want to make any calls to the AdminClient at all (meaning not to install Axis).
I've generated the server side sources from a WSDL using the axistools-maven-plugin, and everything seems to work ok until I have deployed the service. http://localhost:8080/myApp/services gives me the name of the service and two exposed methods. But clicking the wsdl link displays an Axis error message telling me "Could not generate WSDL! There is no SOAP service at this location".
Is it at all possible to build a standalone Axis webservice this way using maven?
Yes, you will need build your application the same way you would for a WAR but programmatically inform tomcat where you exploded war lives.
Everything else should be the same as the standard servlet spec.
When starting Jetty 8.1.17 through Arquillian my Servlet 3.0 Annotations do not get processed. The webapp seems to not work (i.e. #Path mappings do not respond). Deploying the same .war file to the standalone jetty 8.1.17 works.
Why?
I thought this would have something to do with the component "arquillian-jetty-embedded". This seems never to have been published for "8". But even when using it by building it local this won't resolve the issue.
While the sources are there: https://github.com/arquillian/arquillian-container-jetty/tree/master/jetty-embedded-8 they never made it into the maven central.
Furthermore http://arquillian.org/modules/arquillian-jetty-embedded-7-container-adapter/ implies that this would work for 7 and 8.
I also tried to add the container-dependency of
container 'org.eclipse.jetty:jetty-annotations:8.1.17.v20150415'
and using jettyPlus configuration. Still no success.