Missing WSDL - weblogic.developer.interest.webservices.general(Archived)

Hello everyone, I'm having difficulties with WLS 10.0 recognizing a web service that was built from the command line using jwsc. The service builds into a war perfectly fine and deploys fine w/o error to WLS. However, when you look at the deployed WAR within the Console, the Console reports that there is no web service.
JWSC generates the necssary artifacts and they are packaged in the WAR.
Any thoughts?
thank you
Chris

Related

WL Server not recognizing jwsc-built web service

Hello everyone, I'm having difficulties with WLS 10.0 recognizing a web service that was built from the command line using jwsc. The service builds into a war perfectly fine and deploys fine w/o error to WLS. However, when you look at the deployed WAR within the Console, the Console reports that there is no web service.
As a workaround, I am able to import the web service into Workshop as a new web service project. I am then able to successfully bulid, deploy, and test this web service from within workshop. Workshop has generated it's own ant build scripts, which work great. I unfortunately can't use those scripts within our automated bulid environment.
So, what exactly is WLS looking for in order to recognize the web service?
Thanks
Chris

Axis Client Invoking WebServices on Tomcat within WLS8.1sp2

Hi,
I am working on a project in which I have encountered a strange ClassCastException behaviour. Here's the scenario:
We have created a client.jar which uses Axis 1.1 to invoke Web Services on Tomcat 4.1. The jar file works fine when used within a normal Java application.
However, once the it is used in a Weblogic 8.1sp2, I continue to encounter ClassCastException error. We have written a EJB that will call the APIs provided by this client.jar file. This jar file will then try to invoke web services on another server that is running Tomcat and return the information requested. For some reason, it always throws ClassCastException and it always seems to use the web services library provided by Weblogic. We have also explicitly used the Apache Axis libraries to create the web services objects instead of relying on the generic Java XML-RPC.
Appreciate any advice.
Thanks,
Simon

WSDL

I am trying to create my first web service using Weblogic. I created the ejbs and
used ant to build and deploy. I basically copied the Weblogic rpc-style examples
web service. Everything worked great. However, if try to add more methods to
my ejb, rebuild and redeploy the WSDL does not ever seem to change to reflect
the new methods. Any Ideas???
Thanks
Tedie

Application can't be deployed in WLS 10.3.5

Hi.
I have an EAR app working in WLS 10.0 for years. The application contains a set of web services using XMLBeans classes as parameters and return types.
Triying to migrate the application to WLS 10.3.5 I'm getting the following error during DEPLOY:
The xxxx (Class used as parameter to the service) is an interface, and JAXB can't handle interfaces.
As I said, the class was generated by XMLBeans.
I tried to develop a foo ear application with the same features (Web Services using XMLBeans classes), thinking the problem was some mistake in the project adjustments. But I got the same error.
The signature of the method containg the parameter is like this:
*#WebMethod*
public InsertElementResDocument insert(InsertElementReqDocument request)
I'm using Weblogic 10.3.5 OEPE as IDE.
I would like to know if it is not possible to develop this kind of application in WLS 10.3.5, once in WLS 10.0 works perfectly.
Does anyone could help me?
Thanks a lot. 
Hello,
Check this out..
Replace
<jxb:globalBindings generateValueClass="false">
with
<jxb:globalBindings generateValueClass="true">
in schema-bindings.xml file and test the migration again.
HTH,
Raj Mareddi
http://www.freeoraclehelp.com

cannot redeploy app ... without specifying the path operand

I am getting an error trying to deploy an EAR to a Glassfish 4.1 server. I can successfully export the EAR directly to a .ear and then deploy it using the Glassfish admin console. However, if I try to Run the Java EE 7 application's web component - either via Run or via Debug mode - I get the following error: Cannot deploy DemoHighchartsEAR - deploy is failing=Cannot redeploy app, DemoHighchartsEAR without specifying the path operand.  I have no idea what this means. My EAR contains a Web component in a Dynamic Web project, along with a Java EE Web service resource and today an EJB utilizing a set of utility classes and JPA access to an Oracle 12c database using Hibernate 4.3.6. The EJB with Hibernate were added today; I had no issues deploying the EAR when it did not include the EJB project. Software configuration: - I am running Eclipse OEPE 12.1.3.4 based on Eclipse Luna, using version 7.3.4.201502282121 of the GlassFish tools plugin. My Java EE 7 installation uses SP1 and my GlassFish installation is version 4.1 (open source edition). Can anyone tell me what this message means and where I can make a change to work around it? I am confused in that if I export the EAR file, it will deploy to Glassfish. UPDATE: I've re-factored the entire application so that it is a single Dynamic Web project. I can export the WAR file to GlassFish just fine, but still cannot launch the project via Eclipse's IDE. The error message is identical. In the Eclipse error log, I get the following:  What is the "path operand"? Thanks in advance....
Refer bug.https://java.net/jira/browse/GLASSFISH-4666
I don't see the relationship between GLASSFISH-4666 and the problem I've encountered. 4666 was marked resolved in 2009 - I'm using 2015 software.
Perhaps the issue is how you originally deployed your app.  According to the documentation for redeploy (https://docs.oracle.com/cd/E19798-01/821-1758/redeploy-1/index.html) if you originally deployed your app by referencing a file (such as a war or ear), then subsequent calls to redeploy (which is what I believe Eclipse is doing for you) will demand the path operand.  If, however, you originally deploy your app by referencing the dir containing the exploded war files, then subsequent calls to redeploy do not need the path operand.
A similar bug is not fixed.https://java.net/jira/browse/GLASSFISH-21403

Categories

Resources