QNAME Class
My class path:
bla bla...;D:\bea70\weblogic700\server\lib\webserviceclient.jar
Yet when I try compile the sample WebService example from(http://dev2dev.bea.com/managed_content/direct/webservice/index.html)
(SwA (SOAP with Attachments) example:) the client.java is the only file that will
not compile. I have set my CLASSPATH to incude the webserviceclient.jar.
ERROR:
D:\bea70\weblogic700\samples\server\src\examples\filetransfer>javac Client.java
Client.java:12: cannot resolve symbol
symbol : class QName
location: package namespace
import javax.xml.rpc.namespace.QName;
Hi
The package of the QName class been changed. It should be
javax.xml.namespace.QName.
we will update the example on dev2dev.
Thanks for finding it out
Ajay
Ivan Sager <[email protected]> wrote in message
news:3d46fc0a$[email protected]..
>
My class path:
bla bla...;D:\bea70\weblogic700\server\lib\webserviceclient.jar
Yet when I try compile the sample WebService examplefrom(http://dev2dev.bea.com/managed_content/direct/webservice/index.html)
(SwA (SOAP with Attachments) example:) the client.java is the only filethat will
not compile. I have set my CLASSPATH to incude the webserviceclient.jar.
ERROR:
D:\bea70\weblogic700\samples\server\src\examples\filetransfer>javacClient.java
Client.java:12: cannot resolve symbol
symbol : class QName
location: package namespace
import javax.xml.rpc.namespace.QName;
Similar Messages
-
Problem with axis2 and QName class
Hello,
We have deployed AXIS2 library with a library project (J2EE server component) as it is specify by a SAP guide. We deployed the sda file correctly and we know how to reference this library in Portal Application and J2ee Module WEB or EJB.
The problem is when we want to use internally javax.xml.namespace.QName is thrown an exception. This exception is shown bellow:
java.lang.LinkageError: loader constraints violated when linking javax/xml/namespace/QName class
at wpt.ConventerStub.populateAxisService(ConventerStub.java:52)
at wpt.ConventerStub.<init>(ConventerStub.java:100)
at wpt.ConventerStub.<init>(ConventerStub.java:89)
at wpt.ConventerStub.<init>(ConventerStub.java:140)
at wpt.ConventerStub.<init>(ConventerStub.java:132)
at com.eadscasa.axis2.Axis2Converter.doContent(Axis2Converter.java:26)
In the guide is said that we have to deploy a library project to avoid this problem but we still are getting it. I have realized that Qname class is a basic class into the JDK 1.4 and in different projects as AXIS2 making revision about this class.
How can I deploy these libraries (jars) without dependencies with SAP Portal libraries?
Is there any way to setup the classloader to avoid this error?
In the documentation about this kind of project it is said that you cannot deploy libraries (*.jar) with the same name. I donu2019t know if it happens the same with the class.
We have to develop web Services with Soap 1.2 specification, SAML etc and we need to develop this class because sap portal doesnu2019t support this kind o features.
Regards,
Daniel UrbanoHi,
Firstly thanks for you reply. I generate the client with wsdl2java tool as it is mentioned in AXIS2 documentation and as you specified in your blog. After I follow the steps:
Step 1 - Generating the Axis2.war
Step 2 u2013 Modify the service *.aar file
Step 3 u2013 Create the J2EE library
Step 4 u2013 Create the J2EE application wrapping the web module axis2.war
We know how to make the step 1,2 and 3 but there is a little mess in the last step. Donu2019t worry about this because we got the general idea in this document. According to the guide the main problem is to solve a classloading conflict because it only can be loaded the libraries once and you need the AXIS2 libraries for *.arr and for the axis2 engine to be able to manage this module. This problem it is solved making a J2EE library Project and putting a reference to this library in the module, applications or project, which have to use AXIS2 libraries.
We have 3 different kind of projects that we can develop according to Sap Netweaver:
J2EE Project:
· Web Module Project: Resulting a war file.
· Enterprise Application Project: Resulting a ear file
· EJB Module Project: Resulting a war file.
Portal Application
· Portal Application Project: Resulting a par file.
In any project mentioned upper we know how to deploy these with a reference to this library project that previously we deployed successfully in the portal. But the problem is when we are going to check this module running it the server give us an exception.
java.lang.LinkageError: loader constraints violated when linking javax/xml/namespace/QName class
at wpt.ConventerStub.populateAxisService(ConventerStub.java:52)
at wpt.ConventerStub.(ConventerStub.java:132)
at com.eadscasa.axis2.Axis2Converter.doContent(Axis2Converter.java:26)
This exception is because exist classes into the axis2 libraries as javax.xml.namespace.Qname that are in SAP Portal libraries into the J2ee Server (JDK 1.4). This conflict is mentioned in the blog u201C360° View on enterprise SOAu201D where Michael Koegel, the author, says that if you want that AXIS2 libraries works you will have to work around with the dependencies of libraries.
The main problem in this point it is that we donu2019t know how to resolve this dependencies and if it is possible that other module of SAP Portal wonu2019t work fine if we change the base libraries. AXIS2 has newer classes than SAP Portal and it is possible that we can break other SAP Portal functions. In this case if we can not get that AXIS2 and SAP Portal co-exist in the same server we will probably have to change our way to get the enterprise objectives.
In order to resolve these dependencies we have found a SAP Note Number: 1138545. In this note it is said that we can setup the precedence class loader in the visual admin into the deploy service. If you add your AXIS2 library at the beginning of StandardAplicationReferences variable in the deploy service, it is loaded the axis2 libraries first and it works the services but other portal functionality fails. This variable it is used to load the libraries precedence for all applications in the Server. If we could setup the class load precedence in a web module project or the system doesnu2019t take into account the server libraries for this module it will work perfectly.
If you could specify more the last point of your manual, I will appreciate it.
Regards,
Daniel Urbano -
We deployed a war-file with a web service. The war file
includes the xbean.jar in the WEB-INF/lib directory. Within the
xbean.jar a version of class javax.xml.namespace.Qname exists with
the constructor
Qname(java.lang.String,java.lang.String,java.lang.String). Our web
service calls this a constructor and terminates with the exception:
java.lang.NoSuchMethodError:
javax.xml.namespace.QName.<init>(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String
I suppose that the QName class is taken from the Jrun's
webservices.jar file. This one includes the Qname class without the
needed constructor (3 string arguments).
How can I configure Jrun so that the xbean.jar's QName is
taken instead of the the webservices.jar's QName.
Regards AndreasYou can use the
<load-system-classes-first>false</load-system-classes-first>
attribute in jrun-web.xml to override the classes shipped
with JRun.
Thanks,
Gurdeep
"goebbi" <[email protected]> wrote in
message
news:e1lmrf$1ot$[email protected]..
> We deployed a war-file with a web service. The war file
includes the
> xbean.jar
> in the WEB-INF/lib directory. Within the xbean.jar a
version of class
> javax.xml.namespace.Qname exists with the constructor
>
Qname(java.lang.String,java.lang.String,java.lang.String). Our web
service
> calls this a constructor and terminates with the
exception:
> java.lang.NoSuchMethodError:
>
javax.xml.namespace.QName.<init>(Ljava/lang/String;Ljava/lang/String;Ljava/lang/
> String
>
> I suppose that the QName class is taken from the Jrun's
webservices.jar
> file.
> This one includes the Qname class without the needed
constructor (3 string
> arguments).
>
> How can I configure Jrun so that the xbean.jar's QName
is taken instead of
> the
> the webservices.jar's QName.
>
> Regards Andreas
> -
Class conflicts with third-party libraries on j2ee engine
Hi,
I am deploying a repository manager into EP. In my repository I referenced javax.xml.namespace.QName, which conflicts with the one declared in jaxrpc.jar in j2ee/cluster/server0/bin/ext/webservices_lib.
I am not very clear about how NW j2ee engine loads classes, but it seems that it loads classes in j2ee/cluster/server0/bin/ext/webservices_lib first. As a result, I got a class confliction error:
java.lang.NoSuchMethodError: javax.xml.namespace.QName.<init>(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V
If I remove QName.class from the jar in webservices_lib, it works fine, but this not the right way. I have read Note 990854, but not clear about how to do. Could anyone give any help?
Thanks,
RayClose this thread as it makes little sense.
-
Schemac error: doesn't support xsd:QName datatype
Hi all,
my problem is: I'm trying to create a facade of wsa:EndpointReferenceType in order to dynamically manipulate URIs through java snippets or standalone classes. So I used the command "schemac -d c:\classes ws-addressing.xsd" via the JDev Prompt. Where ws-addressing.xsd is the XSD Schema for WS-Addressing Specification 03/2003. But schemac prompts this warning: "The W3C datatype 'QName' is not currently supported by Collaxa schemac", even if schemac completes successfully. Because of this problem, I'm not able to create a facade of this kind: "EndpointReferenceType ep = EndpointReferenceTypeFactory.createFacade();" because when I compile my BPEL project it gives me the following error: "Error(18,71): cannot access class javax.xml.namespace.QName; file javax\xml\namespace\QName.class not found". What can I do in order to create a EndpointReference facade?
Thanks in advanceOk, I included in my project the library OraBPEL.
But it already throws a fault when I try to do this:
EndpointReferenceType ep=EndpointReferenceTypeFactory.createFacade()...
So I serched in orabpel.jar (C:\OraBPELPM_1\integration\bpelpm\designer\jdev\lib\ext\orabpel.jar) and found the package "org.xmlsoap.schemas.ws.addressing", where I found a readme file in which is written "These files are generated by schemac based on XML schema of WS-Addressing.
The schema is published at http://schemas.xmlsoap.org/ws/2003/03/addressing/", and I noticed that QName is supported in this release of facade!
So I tryed with the following code in a standalone java where the method "processRfQ" gets in input the Element quote corresponding to the bpel variable Quote, creates a facade and fill it:
package javaexec;
import it.polito.www.bProgress.sellingX.*;//my facades
import javax.xml.namespace.*;//for QName
import org.w3c.dom.Element;
import org.xmlsoap.schemas.ws.addressing.*;
public class SellingJ {
public SellingJ(){}
public void processRfQ(Element quote){
try{
QuoteMsgType quoteF=QuoteMsgTypeFactory.createFacade(quote);
EndpointReferenceType providerId = (EndpointReferenceType)EndpointReferenceTypeFactory.create();
AttributedURI aURI = (AttributedURI)AttributedURIFactory.create();
aURI.setContent("http://localhost:9700/orabpel/default/sellingP");//the endpoint address of the service I want to invoke
providerId.setAddress(aURI);
ServiceNameType sName = (ServiceNameType)ServiceNameTypeFactory.create();
QName qn=new QName("http://www.polito.it/bProgress/sellingP","sellingP","sellingP");//service namespace,name and prefix
sName.setContent(qn);
providerId.setServiceName(sName);
quoteF.setProviderId(providerId);
catch (Exception e){}
The result in bpel is the following:
<providerId>
<EndpointReferenceType xmlns:ns1="http://www.w3.org/1999/XMLSchema-instance" xmlns:ns2="http://schemas.xmlsoap.org/ws/2003/03/addressing" ns1:type="ns2:EndpointReferenceType">
<Address ns1:type="ns2:AttributedURI"> <content>http://localhost:9700/orabpel/default/sellingP</content></Address>
<ReferenceProperties null="true"/><PortType null="true"/>
<ServiceName ns1:type="ns2:ServiceNameType">
<content xmlns:ns3="http://www.w3.org/2001/XMLSchema" ns1:type="ns3:QName">
<namespaceURI>http://www.polito.it/bProgress/sellingP</namespaceURI><localpart>sellingP</localpart>
</content>
<PortName null="true"/>
</ServiceName>
</EndpointReferenceType>
</providerId>
and the element quote is declared as follow in the XSD file:
<element name="quote" type="tns:quoteMsgType"/>
<complexType name="quoteMsgType">
<sequence>
<element name="correlationId" type="string"/>
<element name="description" type="string"/>
<element name="providerId" type="wsa:EndpointReferenceType"/>
<element name="amount" type="double"/>
</sequence>
</complexType>
I'd like to have this kind of result:
<providerId>
<Address xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing">http://localhost:9700/orabpel/default/sellingP</Address>
<ServiceName xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing" xmlns:sellingP="http://www.polito.it/bProgress/sellingP">sellingP:sellingP</ServiceName>
</providerId>
in order to copy this endpoint reference into a partnerLink and then invoke it by another process...
What's wrong in my javacode? or, is ws-addressing facade completely supported?
Please help me...
Thanks in advance -
I am Using Ajax with DWR while running the application i am getting error?
Hi,
I am using DWR concept while running the program i am getting the following error:
uk.ltd.getahead.dwr.util.CommonsLoggingOutput info INFO: Exec[0]: Demo.sayHello()
and also all the methods that are there in that Java class. Plz anybody help me how to overcome this problemHi Rameshkumar,
The workaround mentioned by Chris will not be required in future versions of TopLink 10.1.3. We have removed our dependency on the 3-arg javax.xml.namespace.QName constructor that is not present in the WebLogic 8.1 distribution of the QName class.
-Blaise -
Weblogic 8.1 to 9.2 upgrade of web application Issues
Hi,
I am trying to migrate an Weblogic 8.1 web application project (based on netui/struts/pageflows) to 9.2 using the workshop upgrade utility. During the upgrade, i get the following errors(note, this is not after upgrade but during upgrade itself).
====================================================================================================
!SUBENTRY 1 com.bea.wlw.upgrade <ERROR> <RESOURCE: /RMSPortal/WebContent/visitorTools/skeletons/edittogglebutton.jsp> 2010-07-06 16:37:51.341
!MESSAGE Exception caught during upgrade of "edittogglebutton.jsp"
!STACK 0
java.lang.LinkageError: loader constraints violated when linking javax/xml/namespace/QName class
====================================================================================================
Please let me know if this is an issue or can be ignored ? or how can i get rid of this error ?
Regards,
RamHi,
I am trying to migrate an Weblogic 8.1 web application project (based on netui/struts/pageflows) to 9.2 using the workshop upgrade utility. During the upgrade, i get the following errors(note, this is not after upgrade but during upgrade itself).
====================================================================================================
!SUBENTRY 1 com.bea.wlw.upgrade <ERROR> <RESOURCE: /RMSPortal/WebContent/visitorTools/skeletons/edittogglebutton.jsp> 2010-07-06 16:37:51.341
!MESSAGE Exception caught during upgrade of "edittogglebutton.jsp"
!STACK 0
java.lang.LinkageError: loader constraints violated when linking javax/xml/namespace/QName class
====================================================================================================
Please let me know if this is an issue or can be ignored ? or how can i get rid of this error ?
Regards,
Ram -
Consuming dataservice as a stand alone java client, givng an exception com
when i am trying to access data service from a stand alone java application ,it giving an exception .
The dataservice is in remote machine.
Exception:
com.bea.dsp.dsmediator.client.exception.SDOMediatorException: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException
at com.bea.dsp.dsmediator.client.XmlDataServiceBase.invokeFunction(XmlDataServiceBase.java:322)
at empldetappdataservices.EmployeeDetails.getEmployeesByid(EmployeeDetails.java:84)
at com.patni.tsg.poc.DataServiceClient.DataServiceClient.main(DataServiceClient.java:42)
Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:290)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:248)
at com.bea.ld.Server_ydm4ie_EOImpl_815_WLStub.executeFunction(Unknown Source)
at com.bea.dsp.dsmediator.client.XmlDataServiceBase.invokeFunction(XmlDataServiceBase.java:312)
... 2 more
Caused by: java.io.EOFException
at weblogic.rjvm.t3.T3JVMConnection.endOfStream(T3JVMConnection.java:897)
at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:586)
at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:536)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:694)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:641)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:282)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
my class path i added all neccessary jars:
weblogic.jar,xbean.jar,DataServices.jar,ld-server-core.jar,ld-client.jar,wlsdo.jar
code sample:
public static InitialContext getInitialContext() throws NamingException {
Environment env = new Environment();
env.setProviderUrl("t3://pc-p40892:7001");
env.setInitialContextFactory("weblogic.jndi.WLInitialContextFactory");
env.setSecurityPrincipal("weblogic");
env.setSecurityCredentials("weblogic");
return new InitialContext(env.getInitialContext().getEnvironment());
public static void main (String args[]) {
try {
EmployeeDetailsDocument.EmployeeDetails edet=null;
EmployeeDetails ds=EmployeeDetails.getInstance(getInitialContext(),"EmplDetApp");
//The below statement generating the exception.
EmployeeDetailsDocument[]doc =ds.getEmployeesByid("1001");
} catch (Exception e) {
e.printStackTrace();
pls help me to solve this problem
Edited by sandeepc221 at 09/19/2007 2:50 AMYou didn't post the stack trace from the server, but I'm guessing it's complaining about the QName class. Sun changed the QName class in JDK 1.5 wreaking havoc on JDK 1.5 clients that use JDK 1.4 servers and attempt to pass a QName object from one to the other. If your client uses JDK 1.5, your sever will need to use a QName class which is compatible. The file liquiddata/lib/wls90interop.jar contains a QName class that is compatible with the one in JDK1.5. You can put it first in the classpath of your server.
If you already have wls90interop.jar first in the classpath of your server, then, for your client, you need to either (1) use the Sun JDK 1.5; or (2) put wls90interop.jar first in the classpath of your client (if you are running JDK 1.4).
http://e-docs.bea.com/aldsp/docs25/appdev/ejbclt.html#wp1090900
btw - BEA Customer Support is available 24/7 - they should be able to provide you quick answers to questions like this. -
Import Webservice mode error?
Hi All,
When I Import Webservice model it's rising the following errors.\
com.sap.engine cannot resolved.
Javax.xml.rpc cannot be resolved.
Regards,
PradeepHi Sumit,
Error messages are :
Error javax.xml.rpc cannot be resolved or is not a type Request_IciMessageViDocument_delete.java Webservice_proj/gen_wdp/packages/test line 67
Error javax.xml.rpc cannot be resolved or is not a type Request_IciMessageViDocument_delete.java Webservice_proj/gen_wdp/packages/test line 69
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_delete.java Webservice_proj/gen_wdp/packages/test line 69
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_delete.java Webservice_proj/gen_wdp/packages/test line 72
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_delete.java Webservice_proj/gen_wdp/packages/test line 75
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_delete.java Webservice_proj/gen_wdp/packages/test line 78
Error com.sap.engine cannot be resolved Request_IciMessageViDocument_delete.java Webservice_proj/gen_wdp/packages/test line 81
Error javax.xml.rpc cannot be resolved or is not a type Request_IciMessageViDocument_getAttributes.java Webservice_proj/gen_wdp/packages/test line 67
Error javax.xml.rpc cannot be resolved or is not a type Request_IciMessageViDocument_getAttributes.java Webservice_proj/gen_wdp/packages/test line 69
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_getAttributes.java Webservice_proj/gen_wdp/packages/test line 69
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_getAttributes.java Webservice_proj/gen_wdp/packages/test line 72
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_getAttributes.java Webservice_proj/gen_wdp/packages/test line 75
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_getAttributes.java Webservice_proj/gen_wdp/packages/test line 78
Error com.sap.engine cannot be resolved Request_IciMessageViDocument_getAttributes.java Webservice_proj/gen_wdp/packages/test line 81
Error javax.xml.rpc cannot be resolved or is not a type Request_IciMessageViDocument_getContent.java Webservice_proj/gen_wdp/packages/test line 67
Error javax.xml.rpc cannot be resolved or is not a type Request_IciMessageViDocument_getContent.java Webservice_proj/gen_wdp/packages/test line 69
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_getContent.java Webservice_proj/gen_wdp/packages/test line 69
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_getContent.java Webservice_proj/gen_wdp/packages/test line 72
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_getContent.java Webservice_proj/gen_wdp/packages/test line 75
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_getContent.java Webservice_proj/gen_wdp/packages/test line 78
Error com.sap.engine cannot be resolved Request_IciMessageViDocument_getContent.java Webservice_proj/gen_wdp/packages/test line 81
Error javax.xml.rpc cannot be resolved or is not a type Request_IciMessageViDocument_send.java Webservice_proj/gen_wdp/packages/test line 67
Error javax.xml.rpc cannot be resolved or is not a type Request_IciMessageViDocument_send.java Webservice_proj/gen_wdp/packages/test line 69
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_send.java Webservice_proj/gen_wdp/packages/test line 69
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_send.java Webservice_proj/gen_wdp/packages/test line 72
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_send.java Webservice_proj/gen_wdp/packages/test line 75
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_send.java Webservice_proj/gen_wdp/packages/test line 78
Error com.sap.engine cannot be resolved Request_IciMessageViDocument_send.java Webservice_proj/gen_wdp/packages/test line 81
Error javax.xml.rpc cannot be resolved or is not a type Request_IciMessageViDocument_setActionFlags.java Webservice_proj/gen_wdp/packages/test line 67
Error javax.xml.rpc cannot be resolved or is not a type Request_IciMessageViDocument_setActionFlags.java Webservice_proj/gen_wdp/packages/test line 69
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_setActionFlags.java Webservice_proj/gen_wdp/packages/test line 69
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_setActionFlags.java Webservice_proj/gen_wdp/packages/test line 72
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_setActionFlags.java Webservice_proj/gen_wdp/packages/test line 75
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_setActionFlags.java Webservice_proj/gen_wdp/packages/test line 78
Error com.sap.engine cannot be resolved Request_IciMessageViDocument_setActionFlags.java Webservice_proj/gen_wdp/packages/test line 81
Error javax.xml.rpc cannot be resolved or is not a type Request_IciMessageViDocument_setContent.java Webservice_proj/gen_wdp/packages/test line 67
Error javax.xml.rpc cannot be resolved or is not a type Request_IciMessageViDocument_setContent.java Webservice_proj/gen_wdp/packages/test line 69
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_setContent.java Webservice_proj/gen_wdp/packages/test line 69
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_setContent.java Webservice_proj/gen_wdp/packages/test line 72
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_setContent.java Webservice_proj/gen_wdp/packages/test line 75
Error javax.xml.rpc cannot be resolved Request_IciMessageViDocument_setContent.java Webservice_proj/gen_wdp/packages/test line 78
Error com.sap.engine cannot be resolved Request_IciMessageViDocument_setContent.java Webservice_proj/gen_wdp/packages/test line 81
Error The import javax.xml.rpc cannot be resolved IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 4
Error The import javax.xml.rpc cannot be resolved IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 6
Error The import com.sap.engine cannot be resolved IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 8
Error The import com.sap.engine cannot be resolved IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 9
Error The import com.sap.engine cannot be resolved IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 10
Error The import com.sap.engine cannot be resolved IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 11
Error com.sap.engine cannot be resolved or is not a valid superclass IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 14
Error com.sap.engine cannot be resolved or is not a valid superinterface IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 14
Error com.sap.engine cannot be resolved (or is not a valid type) for the field IciMessageConfBindingStub.typeRegistry IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 17
Error The method setEndpoint(String) is undefined for the type Object IciMessageConfBindingStub.java Webserviceproj/src/packages/test/proxies line 21
Error transportBinding cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 22
Error com.sap.engine cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 22
Error localProtocols cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 23
Error com.sap.engine cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 23
Error localFeatures cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 24
Error PropertyContext cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 24
Error localProtocols cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 25
Error com.sap.engine cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 25
Error localFeatures cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 26
Error PropertyContext cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 26
Error localProtocols cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 27
Error com.sap.engine cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 27
Error localFeatures cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 28
Error PropertyContext cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 28
Error localProtocols cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 29
Error com.sap.engine cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 29
Error localFeatures cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 30
Error PropertyContext cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 30
Error localProtocols cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 31
Error com.sap.engine cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 31
Error localFeatures cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 32
Error PropertyContext cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 32
Error localProtocols cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 33
Error com.sap.engine cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 33
Error localFeatures cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 34
Error PropertyContext cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 34
Error com.sap.engine cannot be resolved (or is not a valid type) for the argument binding of the method setTransportBinding IciMessageConfBindingStub.java Webserviceproj/src/packages/test/proxies line 37
Error transportBinding cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 39
Error typeRegistry cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 39
Error transportBinding cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 40
Error typeRegistry cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 40
Error typeRegistry cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 42
Error transportBinding cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 42
Error typeRegistry cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 43
Error com.sap.engine cannot be resolved IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 43
Error transportBinding cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 43
Error com.sap.engine cannot be resolved (or is not a valid type) for the argument _registry of the method setTypeRegistry IciMessageConfBindingStub.java Webserviceproj/src/packages/test/proxies line 47
Error typeRegistry cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 48
Error transportBinding cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 49
Error typeRegistry cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 49
Error transportBinding cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 50
Error typeRegistry cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 50
Error featureConfiguration cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 52
Error typeRegistry cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 52
Error Cannot throw the type SoapException IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 55
Error The method beginLogFrame() is undefined for the type Object IciMessageConfBindingStub.java Webserviceproj/src/packages/test/proxies line 57
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 59
Error ServiceParam cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 59
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 60
Error ServiceParam cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 60
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 61
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 62
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 63
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 64
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 65
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 66
Error ServiceParam cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 66
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 67
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 68
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 69
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 70
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 71
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 72
Error ServiceParam cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 72
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 73
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 74
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 75
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 76
Error inputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 77
Error outputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 79
Error ServiceParam cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 79
Error outputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 80
Error ServiceParam cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 80
Error outputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 81
Error outputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 82
Error outputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 83
Error outputParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 84
Error faultParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 86
Error ServiceParam cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 86
Error faultParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 87
Error ServiceParam cannot be resolved or is not a type IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 87
Error faultParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 88
Error faultParams cannot be resolved or is not a field IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 89
Error Cannot throw the type SoapException IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 132
Error Cannot throw the type SoapException IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 209
Error Cannot throw the type SoapException IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 286
Error Cannot throw the type SoapException IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 363
Error Cannot throw the type SoapException IciMessageConfBindingStub.java Webservice_proj/src/packages/test/proxies line 440
Error com.sap.engine cannot be resolved (or is not a valid return type) for the method getOpMetadata IciMessageConfBindingStub.java Webserviceproj/src/packages/test/proxies line 518
Error com.sap.engine cannot be resolved (or is not a valid type) for the argument opStruct of the method invoke IciMessageConfBindingStub.java Webserviceproj/src/packages/test/proxies line 869
Error javax.xml.rpc cannot be resolved or is not a valid superinterface IciMessageService.java Webservice_proj/src/packages/test/proxies line 7
Error javax.xml.rpc cannot be resolved (or is not an exception type) for the method getLogicalPort IciMessageService.java Webservice_proj/src/packages/test/proxies line 9
Error javax.xml.rpc cannot be resolved (or is not an exception type) for the method getLogicalPort IciMessageService.java Webservice_proj/src/packages/test/proxies line 10
Error javax.xml.rpc cannot be resolved (or is not an exception type) for the method getIciMessageConfPortDocument IciMessageService.java Webservice_proj/src/packages/test/proxies line 11
Error javax.xml.rpc cannot be resolved (or is not an exception type) for the method getLogicalPort IciMessageService.java Webservice_proj/src/packages/test/proxies line 12
Error javax.xml.rpc cannot be resolved (or is not an exception type) for the method getLogicalPort IciMessageService.java Webservice_proj/src/packages/test/proxies line 13
Error com.sap.engine cannot be resolved (or is not a valid return type) for the method getLogicalPortConfiguration IciMessageService.java Webservice_proj/src/packages/test/proxies line 15
Error Class must implement the inherited abstract method IciMessageService.getLogicalPortNames() IciMessageServiceImpl.java Webservice_proj/src/packages/test/proxies line 3
Error com.sap.engine cannot be resolved or is not a valid superclass IciMessageServiceImpl.java Webservice_proj/src/packages/test/proxies line 3
Error The method loadProtocolsFromPropertyFile(InputStream) is undefined for the type IciMessageServiceImpl IciMessageServiceImpl.java Webservice_proj/src/packages/test/proxies line 9
Error The method init(InputStream) is undefined for the type IciMessageServiceImpl IciMessageServiceImpl.java Webservice_proj/src/packages/test/proxies line 11
Error typeRegistry cannot be resolved or is not a field IciMessageServiceImpl.java Webserviceproj/src/packages/test/proxies line 12
Error com.sap.engine cannot be resolved or is not a type IciMessageServiceImpl.java Webservice_proj/src/packages/test/proxies line 12
Error typeRegistry cannot be resolved or is not a field IciMessageServiceImpl.java Webserviceproj/src/packages/test/proxies line 13
Error com.sap.engine cannot be resolved (or is not a valid type) for the argument componentFactory of the method IciMessageServiceImpl IciMessageServiceImpl.java Webservice_proj/src/packages/test/proxies line 16
Error componentFactory cannot be resolved or is not a field IciMessageServiceImpl.java Webservice_proj/src/packages/test/proxies line 18
Error The method init(InputStream) is undefined for the type IciMessageServiceImpl IciMessageServiceImpl.java Webservice_proj/src/packages/test/proxies line 19
Error typeRegistry cannot be resolved or is not a field IciMessageServiceImpl.java Webserviceproj/src/packages/test/proxies line 20
Error com.sap.engine cannot be resolved or is not a type IciMessageServiceImpl.java Webservice_proj/src/packages/test/proxies line 20
Error typeRegistry cannot be resolved or is not a field IciMessageServiceImpl.java Webserviceproj/src/packages/test/proxies line 21
Error javax.xml.rpc cannot be resolved (or is not an exception type) for the method getLogicalPort IciMessageServiceImpl.java Webservice_proj/src/packages/test/proxies line 24
Error The method getPort(QName, null) is undefined for the type IciMessageServiceImpl IciMessageServiceImpl.java Webservice_proj/src/packages/test/proxies line 25
Error javax.xml.rpc cannot be resolved (or is not an exception type) for the method getLogicalPort IciMessageServiceImpl.java Webservice_proj/src/packages/test/proxies line 27
Error javax.xml.rpc cannot be resolved (or is not an exception type) for the method getIciMessageConfPortDocument IciMessageServiceImpl.java Webservice_proj/src/packages/test/proxies line 30
Error The method getPort(QName, Class) is undefined for the type Object IciMessageServiceImpl.java Webservice_proj/src/packages/test/proxies line 31
Error javax.xml.rpc cannot be resolved (or is not an exception type) for the method getLogicalPort IciMessageServiceImpl.java Webservice_proj/src/packages/test/proxies line 35
Error The method getPort(QName, Class) is undefined for the type Object IciMessageServiceImpl.java Webservice_proj/src/packages/test/proxies line 36
Error javax.xml.rpc cannot be resolved (or is not an exception type) for the method getLogicalPort IciMessageServiceImpl.java Webservice_proj/src/packages/test/proxies line 39
Error The method getLogicalPort(Class) is undefined for the type Object IciMessageServiceImpl.java Webservice_proj/src/packages/test/proxies line 40
Error javax.xml.rpc cannot be resolved or is not a valid superinterface IciMessageViDocument.java Webservice_proj/src/packages/test/proxies line 7
Error Cannot throw the type SoapException IciMessageViDocument.java Webservice_proj/src/packages/test/proxies line 9
Error Cannot throw the type SoapException IciMessageViDocument.java Webservice_proj/src/packages/test/proxies line 10
Error Cannot throw the type SoapException IciMessageViDocument.java Webservice_proj/src/packages/test/proxies line 11
Error Cannot throw the type SoapException IciMessageViDocument.java Webservice_proj/src/packages/test/proxies line 12
Error Cannot throw the type SoapException IciMessageViDocument.java Webservice_proj/src/packages/test/proxies line 13
Error Cannot throw the type SoapException IciMessageViDocument.java Webservice_proj/src/packages/test/proxies line 14
Error com.sap.engine cannot be resolved or is not a valid superclass SoapException.java Webservice_proj/src/packages/test/proxies line 3
Error com.sap.engine cannot be resolved or is not a valid superclass Delete.java Webservice_proj/src/packages/test/proxies/types line 10
Error com.sap.engine[] cannot be resolved (or is not a valid type) for the field Delete.ATTRIBUTEINFO Delete.java Webservice_proj/src/packages/test/proxies/types line 21
Error ATTRIBUTEINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 25
Error ATTRIBUTEINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 26
Error com.sap.engine cannot be resolved or is not a type Delete.java Webservice_proj/src/packages/test/proxies/types line 26
Error com.sap.engine[] cannot be resolved (or is not a valid type) for the field Delete.FIELDINFO Delete.java Webservice_proj/src/packages/test/proxies/types line 30
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 34
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 35
Error com.sap.engine cannot be resolved or is not a type Delete.java Webservice_proj/src/packages/test/proxies/types line 35
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 36
Error com.sap.engine cannot be resolved or is not a type Delete.java Webservice_proj/src/packages/test/proxies/types line 36
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 38
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 39
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 40
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 41
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 42
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 43
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 44
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 45
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 46
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 47
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 48
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 49
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 50
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 51
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 52
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 53
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 54
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 55
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 56
Error com.sap.engine[] cannot be resolved (or is not a valid return type) for the method getFields Delete.java Webserviceproj/src/packages/test/proxies/types line 77
Error com.sap.engine[] cannot be resolved or is not a type Delete.java Webservice_proj/src/packages/test/proxies/types line 79
Error The method getFields() is undefined for the type Object Delete.java Webserviceproj/src/packages/test/proxies/types line 79
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 80
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 80
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 83
Error FIELDINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 87
Error The method getNumberOfFields() is undefined for the type Object Delete.java Webserviceproj/src/packages/test/proxies/types line 87
Error com.sap.engine[] cannot be resolved (or is not a valid return type) for the method getAttributes Delete.java Webserviceproj/src/packages/test/proxies/types line 90
Error ATTRIBUTEINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 91
Error ATTRIBUTEINFO cannot be resolved Delete.java Webservice_proj/src/packages/test/proxies/types line 95
Error com.sap.engine cannot be resolved or is not a valid superclass DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 10
Error com.sap.engine[] cannot be resolved (or is not a valid type) for the field DeleteResponse.ATTRIBUTEINFO DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 21
Error ATTRIBUTEINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 25
Error ATTRIBUTEINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 26
Error com.sap.engine cannot be resolved or is not a type DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 26
Error com.sap.engine[] cannot be resolved (or is not a valid type) for the field DeleteResponse.FIELDINFO DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 30
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 34
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 35
Error com.sap.engine cannot be resolved or is not a type DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 35
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 36
Error com.sap.engine cannot be resolved or is not a type DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 36
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 38
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 39
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 40
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 41
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 42
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 43
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 44
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 45
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 46
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 47
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 48
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 49
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 50
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 51
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 52
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 53
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 54
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 55
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 56
Error com.sap.engine[] cannot be resolved (or is not a valid return type) for the method getFields DeleteResponse.java Webserviceproj/src/packages/test/proxies/types line 84
Error com.sap.engine[] cannot be resolved or is not a type DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 86
Error The method getFields() is undefined for the type Object DeleteResponse.java Webserviceproj/src/packages/test/proxies/types line 86
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 87
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 87
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 90
Error FIELDINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 94
Error The method getNumberOfFields() is undefined for the type Object DeleteResponse.java Webserviceproj/src/packages/test/proxies/types line 94
Error com.sap.engine[] cannot be resolved (or is not a valid return type) for the method getAttributes DeleteResponse.java Webserviceproj/src/packages/test/proxies/types line 97
Error ATTRIBUTEINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 98
Error ATTRIBUTEINFO cannot be resolved DeleteResponse.java Webservice_proj/src/packages/test/proxies/types line 102
Error com.sap.engine cannot be resolved or is not a valid superclass GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 10
Error com.sap.engine[] cannot be resolved (or is not a valid type) for the field GetAttributes.ATTRIBUTEINFO GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 21
Error ATTRIBUTEINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 25
Error ATTRIBUTEINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 26
Error com.sap.engine cannot be resolved or is not a type GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 26
Error com.sap.engine[] cannot be resolved (or is not a valid type) for the field GetAttributes.FIELDINFO GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 30
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 34
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 35
Error com.sap.engine cannot be resolved or is not a type GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 35
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 36
Error com.sap.engine cannot be resolved or is not a type GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 36
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 38
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 39
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 40
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 41
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 42
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 43
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 44
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 45
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 46
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 47
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 48
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 49
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 50
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 51
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 52
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 53
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 54
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 55
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 56
Error com.sap.engine[] cannot be resolved (or is not a valid return type) for the method getFields GetAttributes.java Webserviceproj/src/packages/test/proxies/types line 77
Error com.sap.engine[] cannot be resolved or is not a type GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 79
Error The method getFields() is undefined for the type Object GetAttributes.java Webserviceproj/src/packages/test/proxies/types line 79
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 80
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 80
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 83
Error FIELDINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 87
Error The method getNumberOfFields() is undefined for the type Object GetAttributes.java Webserviceproj/src/packages/test/proxies/types line 87
Error com.sap.engine[] cannot be resolved (or is not a valid return type) for the method getAttributes GetAttributes.java Webserviceproj/src/packages/test/proxies/types line 90
Error ATTRIBUTEINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 91
Error ATTRIBUTEINFO cannot be resolved GetAttributes.java Webservice_proj/src/packages/test/proxies/types line 95
Error com.sap.engine cannot be resolved or is not a valid superclass GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 10
Error com.sap.engine[] cannot be resolved (or is not a valid type) for the field GetAttributesResponse.ATTRIBUTEINFO GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 21
Error ATTRIBUTEINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 25
Error ATTRIBUTEINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 26
Error com.sap.engine cannot be resolved or is not a type GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 26
Error com.sap.engine[] cannot be resolved (or is not a valid type) for the field GetAttributesResponse.FIELDINFO GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 30
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 34
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 35
Error com.sap.engine cannot be resolved or is not a type GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 35
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 36
Error com.sap.engine cannot be resolved or is not a type GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 36
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 38
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 39
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 40
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 41
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 42
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 43
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 44
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 45
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 46
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 47
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 48
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 49
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 50
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 51
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 52
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 53
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 54
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 55
Error FIELDINFO cannot be resolved GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 56
Error com.sap.engine[] cannot be resolved (or is not a valid return type) for the method getFields GetAttributesResponse.java Webserviceproj/src/packages/test/proxies/types line 77
Error com.sap.engine[] cannot be resolved or is not a type GetAttributesResponse.java Webservice_proj/src/packages/test/proxies/types line 79
Error -
Hi gyus
i have around 16000 line of code
which is already broke up in two mxml file and five class
file
still what ever i want to change in my application flex is
taking time
why so it is happening
i turn off my auto refresh option ,auto built option
Plz Help me out
ThanXAdobe Newsbot hopes that the following resources helps you.
NewsBot is experimental and any feedback (reply to this post) on
its utility will be appreciated:
XML (Flex 3):
The XML class contains methods and properties for working
with XML objects. The XML class (along with the XMLList, Namespace,
and QName classes) implements
Link:
http://livedocs.adobe.com/flex/3/langref/XML.html
Adobe - Flex Quick Starts: Using XML data:
The ECMAScript for XML specification in Adobe Flex defines a
set of classes and functionality for working with XML data. These
classes and functionality are
Link:
http://www.adobe.com/devnet/flex/quickstart/accessing_xml_data/
XML (Flex 2 Language Reference):
RSS feed | Send me an e-mail when comments are added to this
page | Comment Report. Current page:
http://livedocs.adobe.com/flex/2/langref/XML.html
Link:
http://livedocs.adobe.com/flex/2/langref/XML.html
Bruce Phillips' Blog: Using XML in Flex - Tutorial Part 4 -
WebService:
Bruce Phillips Flex and ColdFusion Tutorials: Using XML in
Flex - Tutorial Part 4 - WebService.
Link:
http://www.brucephillips.name/blog/index.cfm/2006/10/22/Using-XML-in-Flex--Tutorial-Part-4 --WebService
Working with XML -- Flex 2:
With ActionScript 3.0, there is a new group of classes based
on the ECMAScript for XML (E4X) specification (ECMA-357 edition 2).
Link:
http://livedocs.adobe.com/flex/2/docs/00001910.html
Disclaimer: This response is generated automatically by the
Adobe NewsBot based on Adobe
Community
Engine. -
WLP 9.2.3 integration problem with ALDSP 2.5
HI,
I am having the following issue when using WLP 9.2.3 and ALDSP 2.5 on WebLogic 8.1.
We have recently upgraded from WLP 9.2.1 to WLP 9.2.3,
We were initially getting this error,
following error observed if accessed via application or a standalone test case.
context :: javax.naming.InitialContext
com.bea.dsp.dsmediator.client.exception.SDOMediatorException: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException
at com.bea.dsp.dsmediator.client.XmlDataServiceBase.invokeFunction(XmlDataServiceBase.java:322)
at authenticationdataservices.logical.FirmUser.getFirmUserId(FirmUser.java:98)
at src.AuthenticationUtil.main(AuthenticationUtil.java:27)
Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:215)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
at com.bea.ld.Server_ydm4ie_EOImpl_816_WLStub.executeFunction(Unknown Source)
at com.bea.dsp.dsmediator.client.XmlDataServiceBase.invokeFunction(XmlDataServiceBase.java:312)
... 2 more
Caused by: java.io.EOFException
at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:383)
at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:737)
at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:684)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:845)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:792)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:283)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
To overcome this issue we have read this [ information |http://download.oracle.com/docs/cd/E13167_01/aldsp/docs25/appdev/intro.html] and have done the required.
Re: ALDSP 2.1 QName problem
To enable interop from 9.x client to DSP 2.1 server, follow the following steps.
1. Put ${WL_HOME}/liquiddata/lib/wls90interop.jar in PRE_CLASSPATH on
2.1 server by editing setDomainEnv.cmd
2. Put ${WL_HOME}/liquiddata/lib/wls90interop.jar in workshop's classpath
by modifying -cp key's value in Workshop.cfg
3. Build the application inside the workshop.
4. Build the client side jar using ${WL_HOME}/liquiddata/bin/ld_clientapi.xml
with following arguments on the command line:
-Dapproot=<application directory>
-Dxbeanjarpath=${WEBLOGIC9x}/server/lib/xbean.jar
5. Copy ${WL_HOME}/liquiddata/lib/wlsdo90interop.jar, ld-client.jar and
<appName>-ld-client.jar in WEB-INF/lib or classpath of the 9.x side.
Since network classloading is turned off in any WebLogic server, we need to copy wlsdo.jar and ld-client.jar on the client side.
Also added the flag -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 on the startup of the server (JDK 1.50_12 which is used WLP 9.2.3). We also downgraded the JVM version (JDK 1.5.0_06) for WLP server (as explained in the BUG to JDK 1.5.0_06.)
Now we are getting another issue:
Here is the exception observed:
com.bea.control.servicecontrol.util.memento.ServiceClassMementoUtil> <000000> <com.bea.control.servicecontrol.util.memento.ServiceClassMementoUtil: Cou
ld not load the ServiceClassMemento from the following resource file: uk/gov/fsa/mer/csadminservice/servicecontrol/AdministrationServiceControlServiceClassMemento.ser. This is probably due to a v
ersioning issue and if the developer was astute when they made the change then this should not be the reason. Another possibility is that this resource has become corrupt. The good news is a reb
uild of your app should fix it.
Throwable: java.io.InvalidClassException: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = -9120448754896609940, local class serialVersionUID = 4418622981026545151
Stack Trace:
java.io.InvalidClassException: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = -9120448754896609940, local class serialVersionUID = 4418622981026545151
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:519)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1546)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1460)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1693)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)
at java.util.HashMap.readObject(HashMap.java:1012)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:919)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1813)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1713)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
Please advice on how to overcome this issue.
Your attention to this issue will be highly appreciated.
Regards,
Edited by: user738507 on Jan 6, 2011 12:46 PMI don't know what the .ser file is that it is complaining about, but if it contains an (old) serialized QName object, you'll get that exception on an attempt to de-serialize it into a new QName object. Did you try rebuilding your app like the error message suggests?
You can also try :
@ Also, In 1.5 JDK, the javax.xml.namespace.QName class is bundled in
@ jre/lib/rt.jar. If you have to replace that in your classpath, you should be
@ pre-pending the wls90interop.jar to the bootClasspath.
@ For eg, in my wls9.2, i set the classpath as follows:
@ -Xbootclasspath/p:D:/releases/81sp5platform/weblogic81/liquiddata/lib/wls90int
@ erop.jar -
Error executing Webdynpro mail program
Hi,
I am using webdynpro code for implementing mail service.
I have imported jaxrpc.jar as external jar file.
I got this jar from axis.zip.
While implementing the code, I get following exception.
java.lang.Error: Unresolved compilation problems:
Class must implement the inherited abstract method Service.getWSDLDocumentLocation()
Class must implement the inherited abstract method Service.getPorts()
Class must implement the inherited abstract method IEmailServiceservice.getLogicalPortNames()
Class must implement the inherited abstract method Service.getPort(Class)
Class must implement the inherited abstract method Service.getTypeMappingRegistry()
Class must implement the inherited abstract method Service.getCalls(QName)
Class must implement the inherited abstract method Service.getPort(QName, Class)
Class must implement the inherited abstract method Service.createCall(QName, QName)
Class must implement the inherited abstract method Service.createCall(QName, String)
Class must implement the inherited abstract method Service.createCall()
Class must implement the inherited abstract method Service.getServiceName()
Class must implement the inherited abstract method Service.getHandlerRegistry()
Class must implement the inherited abstract method Service.createCall(QName)
com.sap.engine cannot be resolved or is not a valid superclass
The method loadProtocolsFromPropertyFile(InputStream) is undefined for the type IEmailServiceserviceImpl
The method init(InputStream) is undefined for the type IEmailServiceserviceImpl
The method getPort(QName, Class) is undefined for the type Object
The method getPort(QName, Class) is undefined for the type Object
The method getLogicalPort(Class) is undefined for the type Object
Whats wrong?
thanks,
AshutoshHello Anil,
I am not even able to compile my project.
I get compilation errors as
Class must implement the inherited abstract method SendEmailService.getLogicalPortNames()
Class must implement the inherited abstract method Service.createCall()
Class must implement the inherited abstract method Service.createCall(QName, QName)
Class must implement the inherited abstract method Service.createCall(QName, String)
Class must implement the inherited abstract method Service.createCall(QName)
Class must implement the inherited abstract method Service.getCalls(QName)
Class must implement the inherited abstract method Service.getHandlerRegistry()
Class must implement the inherited abstract method Service.getPort(Class)
Class must implement the inherited abstract method Service.getPort(QName, Class)
Class must implement the inherited abstract method Service.getPorts()
Class must implement the inherited abstract method Service.getServiceName()
Class must implement the inherited abstract method Service.getTypeMappingRegistry()
Class must implement the inherited abstract method Service.getWSDLDocumentLocation()
com.sap.engine cannot be resolved or is not a valid superclass
The method getLogicalPort(Class) is undefined for the type Object
The method getPort(QName, Class) in the type Service is not applicable for the arguments (QName, null)
The method getPort(QName, Class) is undefined for the type Object
The method getPort(QName, Class) is undefined for the type Object
The method init(InputStream) is undefined for the type SendEmailServiceImpl
The method loadProtocolsFromPropertyFile(InputStream) is undefined for the type SendEmailServiceImpl
Do you have any latest jaxrpc.jar download url?
thanks,
Ashutosh -
Hello
I was trying to do a JAX-RPC application, and I had some problems with type casting. My application worked fine with primitive types, vectors of primitive types, and beans with primitive type properties. But it didn't work with vectors of beans, or ArrayList's of beans... It couldn't deserialize the result on client side... Can anyone help?
The Java Web Services Tutorial says that JAX-RPC supports beans and vectors, but I had the impression that this is not a "recursive" support, like "beans with vectors" or "vectors of beans"... Does it make sense?
By the way, I was using a DII client...
Thanks,
Alexandre MurakamiHello!
Thanks for the reply! I can't put the code of my application here (because it's quite big and it's from work)... But I followed the dii client example from the Web Services Tutorial...
I'm trying to do a kind of a general client... The parameters are the URL of the service, the name of the operation, a list of parameters and the return type class.. And it takes the rest of the service information from the WSDL file... About the return type, I take the QName of the return type from the WSDL:
<message>
<part name="result" type="...">...
then I call the call.setReturnType(QName, Class) method. The return type was an array of a very simple bean, something like:
class Person {
String name;
int age;
public String getName() {...}
public void setName(...) {...}
public int getAge() {...}
public void setAge(...) {...}
I don't know if the information I put here is enough... but anyway, thanks for the reply!
Alexandre Murakami -
Java.lang.LinkageError Exception
Hi,
Here is an exception where i have got stuck up. I have been using weblogic9 with myeclipse. I have successfully deployed the application and when i was try to access a page in the application i have been end up with the following exception. Below is the exception message.
javax.faces.FacesException: #{FlightSearchBean.searchFlightOnly}: javax.faces.el.EvaluationException: java.lang.LinkageError: Class javax/xml/namespace/QName violates loader constraints
at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:78)
at javax.faces.component.UICommand.broadcast(UICommand.java:312)
I have searched for solution with the exception message on net, but none of the solutions could solve my problem. The problem seems to be with the Qname.class, i think due the duplicate existance of this class in different jar files is the reason for problem. I have followed different approach to load my application specific jar files but none worked. Can any one help me out in this regard where i was lacking. Any help rendered is greatly appreciated. Thanks in advance.
Thank You,
Tarun.I too have same error with WebLogic 9.2 and Java5. I tried to make sure that it wont load QName.class from app lib but only from container. Still it has issues. Could anybody suggest me the go?
-
Error retrieving JDBC connection from remote client (WLS 10.0)
Hallo,
I get an error when I try to retrieve a JDBC connection from a WLS datasource using a remote client. My Weblogic server version is: WebLogic Server 10.0 MP1 Thu Oct 18 20:17:44 EDT 2007 1005184
I use the following code to retrieve the JDBC connection:
Hashtable<String,String> ctxEnv = null;
InitialContext ctx = null;
DataSource dataSource = null;
Connection con = null;
ctxEnv = new Hashtable<String,String>();
ctxEnv.put(InitialContext.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
ctxEnv.put(InitialContext.PROVIDER_URL, "t3://localhost:7001");
ctx = new InitialContext(ctxEnv);
dataSource = (DataSource) ctx.lookup("datasources/XXX");
con = dataSource.getConnection();
When I execute this code with the weblogic.jar in the classpath everything works fine. However, when I put the wlfullclient.jar in the classpath which I created using the JAR Builder Tool I get the follwoing error:
weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception
at weblogic.jdbc.common.internal.RmiDataSource_1001_WLStub.getConnection(Unknown Source)
at net.schufa.enterprise.utilities.database.test.JDBCSupportTest.test_getConnection_manually(JDBCSupportTest.java:34)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
weblogic.utils.NestedException: java.lang.NoClassDefFoundError: weblogic/diagnostics/instrumentation/InstrumentationDebug
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:221)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
... 17 more
Caused by: weblogic.utils.NestedException: java.lang.NoClassDefFoundError: weblogic/diagnostics/instrumentation/InstrumentationDebug
at weblogic.rjvm.RJVMImpl.gotExceptionReceiving(RJVMImpl.java:938)
at weblogic.rjvm.ConnectionManager.gotExceptionReceiving(ConnectionManager.java:1009)
at weblogic.rjvm.MsgAbbrevJVMConnection.gotExceptionReceiving(MsgAbbrevJVMConnection.java:452)
at weblogic.rjvm.t3.MuxableSocketT3.hasException(MuxableSocketT3.java:373)
at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:755)
at weblogic.socket.SocketMuxer.deliverHasException(SocketMuxer.java:708)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:307)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
Caused by: java.lang.NoClassDefFoundError: weblogic/diagnostics/instrumentation/InstrumentationDebug
at weblogic.diagnostics.instrumentation.rtsupport.InstrumentationSupportImpl.getMonitor(InstrumentationSupportImpl.java:54)
at weblogic.diagnostics.instrumentation.InstrumentationSupport.getMonitor(InstrumentationSupport.java:201)
at weblogic.jdbc.rmi.SerialConnection.<clinit>(SerialConnection.java)
at sun.misc.Unsafe.ensureClassInitialized(Native Method)
at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:25)
at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:122)
at java.lang.reflect.Field.acquireFieldAccessor(Field.java:917)
at java.lang.reflect.Field.getFieldAccessor(Field.java:898)
at java.lang.reflect.Field.getLong(Field.java:527)
at java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1586)
at java.io.ObjectStreamClass.access$700(ObjectStreamClass.java:52)
at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:408)
at java.security.AccessController.doPrivileged(Native Method)
at java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:400)
at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:297)
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:531)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1552)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1292)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.rjvm.ClassTableEntry.readExternal(ClassTableEntry.java:36)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:65)
at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:37)
at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:223)
at weblogic.rjvm.MsgAbbrevInputStream.init(MsgAbbrevInputStream.java:174)
at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:435)
at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:368)
at weblogic.socket.AbstractMuxableSocket.dispatch(AbstractMuxableSocket.java:383)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:872)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:808)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:283)
... 4 more
Can please anyone tell me what's going on there? What really astonishes me is that the class mentioned in the stacktrace is neither present in the wlfullclient.jar nor in the weblogic.jar, but using the weblogic.jar everything works fine. Any hint would be appreciated so much ...
Here is the log written when is created the wlfullclient.jar:
C:\Programme\bea\weblogic10.0\server\lib>java -jar ../../../modules/com.bea.core.jarbuilder_1.0.1.0.jar
Setting Manifest:Class-Path = schema/weblogic-container-binding.jar schema/weblogic-domain-binding.jar schema/diagnostic
s-binding.jar schema/diagnostics-image-binding.jar schema/kodo-conf-binding.jar wlcipher.jar xmlx.jar ojdbc14.jar jconn2
.jar jConnect.jar EccpressoAsn1.jar EccpressoCore.jar EccpressoJcae.jar mysql-connector-java-commercial-5.0.3-bin.jar w
lbase.jar wlutil.jar wlsqlserver.jar wldb2.jar wlsybase.jar wloracle.jar wlinformix.jar wlw-langx.jar ../../common/lib/p
dev.jar debugging.jar wlw-system.jar ../../javelin/lib/javelinx.jar jcom.jar weblogic-L10N.jar
Setting Manifest:Implementation-Vendor = BEA Systems
Setting Manifest:Implementation-Title = Client jar for WebLogic Server 10.0 Thu Oct 18 20:17:44 EDT 2007 1005184
Setting Manifest:Implementation-Version = 10.0.1.0
Creating new jar file: wlfullclient.jar
Integrating jar -->(0)/(0)/C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(0)/(31337)/(31337)/C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar -->(0)/(31337)/C:\Programme\bea\modules\features\weblogic.client.modules_10.0.1.0.jar
Integrating jar <--(0)/(31337)/(0)/C:\Programme\bea\modules\features\weblogic.client.modules_10.0.1.0.jar
Integrating jar -->(1)/(31337)/C:\Programme\bea\modules\features\weblogic.client.modules.L10N_10.0.1.0.jar
Integrating jar <--(1)/(31337)/(0)/C:\Programme\bea\modules\features\weblogic.client.modules.L10N_10.0.1.0.jar
Ignoring unresolved jarC:\Programme\bea\modules\features\weblogic.client.modules.ja_10.0.1.0.jar
Ignoring unresolved jarC:\Programme\bea\modules\features\weblogic.client.modules.ko_10.0.1.0.jar
Ignoring unresolved jarC:\Programme\bea\modules\features\weblogic.client.modules.zh.CN_10.0.1.0.jar
Ignoring unresolved jarC:\Programme\bea\modules\features\weblogic.client.modules.zh.TW_10.0.1.0.jar
Integrating jar -->(1)/(31337)/C:\Programme\bea\modules\com.bea.core.antlr.runtime_2.7.5.jar
Integrating jar <--(1)/(31410)/(73)/C:\Programme\bea\modules\com.bea.core.antlr.runtime_2.7.5.jar
Integrating jar -->(1)/(31410)/C:\Programme\bea\modules\com.bea.core.logging_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(31487)/(77)/C:\Programme\bea\modules\com.bea.core.logging_1.0.1.0.jar
Integrating jar -->(1)/(31487)/C:\Programme\bea\modules\com.bea.core.xml.staxb.runtime_1.0.1.0.jar
Integrating jar <--(1)/(32047)/(560)/C:\Programme\bea\modules\com.bea.core.xml.staxb.runtime_1.0.1.0.jar
Integrating jar -->(1)/(32047)/C:\Programme\bea\modules\com.bea.core.annogen_1.0.1.0.jar
Integrating jar <--(1)/(32265)/(218)/C:\Programme\bea\modules\com.bea.core.annogen_1.0.1.0.jar
Integrating jar -->(1)/(32265)/C:\Programme\bea\modules\com.bea.core.process_5.3.0.0.jar
Integrating jar <--(1)/(32277)/(12)/C:\Programme\bea\modules\com.bea.core.process_5.3.0.0.jar
Integrating jar -->(1)/(32277)/C:\Programme\bea\modules\com.bea.core.common.engine.impl_2.0.1.0.jar
Integrating jar <--(1)/(32294)/(17)/C:\Programme\bea\modules\com.bea.core.common.engine.impl_2.0.1.0.jar
Integrating jar -->(1)/(32294)/C:\Programme\bea\modules\com.bea.core.common.engine.api_2.0.1.0.jar
Integrating jar <--(1)/(32321)/(27)/C:\Programme\bea\modules\com.bea.core.common.engine.api_2.0.1.0.jar
Integrating jar -->(1)/(32321)/C:\Programme\bea\modules\com.bea.core.common.security.api_2.0.1.0.jar
Integrating jar <--(1)/(32446)/(125)/C:\Programme\bea\modules\com.bea.core.common.security.api_2.0.1.0.jar
Integrating jar -->(1)/(32446)/C:\Programme\bea\modules\com.bea.core.common.security.impl_2.0.1.0.jar
Integrating jar <--(1)/(32895)/(449)/C:\Programme\bea\modules\com.bea.core.common.security.impl_2.0.1.0.jar
Integrating jar -->(1)/(32895)/C:\Programme\bea\modules\com.bea.core.common.security.jdkutils_2.0.1.0.jar
Integrating jar <--(1)/(32908)/(13)/C:\Programme\bea\modules\com.bea.core.common.security.jdkutils_2.0.1.0.jar
Integrating jar -->(1)/(32908)/C:\Programme\bea\modules\com.bea.core.common.security.utils_2.0.1.0.jar
Integrating jar <--(1)/(32963)/(55)/C:\Programme\bea\modules\com.bea.core.common.security.utils_2.0.1.0.jar
Integrating jar -->(1)/(32963)/C:\Programme\bea\modules\com.bea.core.common.security.providers.utils_2.0.1.0.jar
Ignoring Duplicate Entry com/bea/common/security/ProvidersLogger$LoggableMessageSpiImpl.class also in C:\Programme\bea\modules\com.bea.core.common.security.api_2.0.1.0.jar
Ignoring Duplicate Entry com/bea/common/security/ProvidersLogger.class also in C:\Programme\bea\modules\com.bea.core.common.security.api_2.0.1.0.jar
Integrating jar <--(1)/(33817)/(854)/C:\Programme\bea\modules\com.bea.core.common.security.providers.utils_2.0.1.0.jar
Integrating jar -->(1)/(33817)/C:\Programme\bea\modules\com.bea.core.common.security.providers.env_2.0.1.0.jar
Integrating jar <--(1)/(33901)/(84)/C:\Programme\bea\modules\com.bea.core.common.security.providers.env_2.0.1.0.jar
Integrating jar -->(1)/(33901)/C:\Programme\bea\modules\javax.activation_1.1.jar
Integrating jar <--(1)/(33945)/(44)/C:\Programme\bea\modules\javax.activation_1.1.jar
Integrating jar -->(1)/(33945)/C:\Programme\bea\modules\javax.annotation_1.0.jar
Integrating jar <--(1)/(33958)/(13)/C:\Programme\bea\modules\javax.annotation_1.0.jar
Integrating jar -->(1)/(33958)/C:\Programme\bea\modules\javax.interceptor_1.0.jar
Integrating jar <--(1)/(33964)/(6)/C:\Programme\bea\modules\javax.interceptor_1.0.jar
Integrating jar -->(1)/(33964)/C:\Programme\bea\modules\javax.ejb_3.0.jar
Integrating jar <--(1)/(34022)/(58)/C:\Programme\bea\modules\javax.ejb_3.0.jar
Integrating jar -->(1)/(34022)/C:\Programme\bea\modules\javax.jdo_2.0.jar
Integrating jar <--(1)/(34119)/(97)/C:\Programme\bea\modules\javax.jdo_2.0.jar
Integrating jar -->(1)/(34119)/C:\Programme\bea\modules\javax.enterprise.deploy_1.2.jar
Integrating jar <--(1)/(34162)/(43)/C:\Programme\bea\modules\javax.enterprise.deploy_1.2.jar
Integrating jar -->(1)/(34162)/C:\Programme\bea\modules\javax.jms_1.1.jar
Integrating jar <--(1)/(34221)/(59)/C:\Programme\bea\modules\javax.jms_1.1.jar
Integrating jar -->(1)/(34221)/C:\Programme\bea\modules\javax.jsp_1.0.1.0_2-1.jar
Integrating jar <--(1)/(34319)/(98)/C:\Programme\bea\modules\javax.jsp_1.0.1.0_2-1.jar
Integrating jar -->(1)/(34319)/C:\Programme\bea\modules\javax.jws_2.0.jar
Integrating jar <--(1)/(34335)/(16)/C:\Programme\bea\modules\javax.jws_2.0.jar
Integrating jar -->(1)/(34335)/C:\Programme\bea\modules\javax.mail_1.4.0.2.jar
Integrating jar <--(1)/(34602)/(267)/C:\Programme\bea\modules\javax.mail_1.4.0.2.jar
Integrating jar -->(1)/(34602)/C:\Programme\bea\modules\javax.management.j2ee_1.0.jar
Integrating jar <--(1)/(34637)/(35)/C:\Programme\bea\modules\javax.management.j2ee_1.0.jar
Integrating jar -->(1)/(34637)/C:\Programme\bea\modules\javax.persistence_1.0.1.0_1-0.jar
Integrating jar <--(1)/(34730)/(93)/C:\Programme\bea\modules\javax.persistence_1.0.1.0_1-0.jar
Integrating jar -->(1)/(34730)/C:\Programme\bea\modules\javax.resource_1.5.jar
Integrating jar <--(1)/(34799)/(69)/C:\Programme\bea\modules\javax.resource_1.5.jar
Integrating jar -->(1)/(34799)/C:\Programme\bea\modules\javax.servlet_1.0.1.0_2-5.jar
Integrating jar <--(1)/(34869)/(70)/C:\Programme\bea\modules\javax.servlet_1.0.1.0_2-5.jar
Integrating jar -->(1)/(34869)/C:\Programme\bea\modules\javax.transaction_1.1.jar
Integrating jar <--(1)/(34889)/(20)/C:\Programme\bea\modules\javax.transaction_1.1.jar
Integrating jar -->(1)/(34889)/C:\Programme\bea\modules\javax.xml.bind_2.0.jar
Integrating jar <--(1)/(34989)/(100)/C:\Programme\bea\modules\javax.xml.bind_2.0.jar
Integrating jar -->(1)/(34989)/C:\Programme\bea\modules\javax.xml.soap_1.3.0.0.jar
Integrating jar <--(1)/(35019)/(30)/C:\Programme\bea\modules\javax.xml.soap_1.3.0.0.jar
Ignoring unresolved jarC:\Programme\bea\modules\jaxp-api.jar
Ignoring unresolved jarC:\Programme\bea\modules\jax-qname.jar
Ignoring unresolved jarC:\Programme\bea\modules\activation.jar
Ignoring unresolved jarC:\Programme\bea\modules\servlet.jar
Integrating jar -->(1)/(35019)/C:\Programme\bea\modules\javax.xml.stream_1.0.1.0_1-0.jar
Integrating jar <--(1)/(35063)/(44)/C:\Programme\bea\modules\javax.xml.stream_1.0.1.0_1-0.jar
Integrating jar -->(1)/(35063)/C:\Programme\bea\modules\javax.xml.ws_2.0.jar
Integrating jar <--(1)/(35110)/(47)/C:\Programme\bea\modules\javax.xml.ws_2.0.jar
Integrating jar -->(1)/(35110)/C:\Programme\bea\modules\javax.xml.rpc_1.1.jar
Ignoring Duplicate Entry javax/xml/namespace/QName.class also in C:\Programme\bea\modules\javax.xml.stream_1.0.1.0_1-0.jar
Integrating jar <--(1)/(35167)/(57)/C:\Programme\bea\modules\javax.xml.rpc_1.1.jar
Integrating jar -->(1)/(35167)/C:\Programme\bea\modules\com.bea.core.jsafe_3.5.0.jar
Integrating jar <--(1)/(35423)/(256)/C:\Programme\bea\modules\com.bea.core.jsafe_3.5.0.jar
Integrating jar -->(1)/(35423)/C:\Programme\bea\modules\com.bea.core.apache_1.0.1.0.jar
Integrating jar <--(1)/(36825)/(1402)/C:\Programme\bea\modules\com.bea.core.apache_1.0.1.0.jar
Integrating jar -->(1)/(36825)/C:\Programme\bea\modules\com.bea.core.beangen_1.0.1.0.jar
Integrating jar <--(1)/(36964)/(139)/C:\Programme\bea\modules\com.bea.core.beangen_1.0.1.0.jar
Integrating jar -->(1)/(36964)/C:\Programme\bea\modules\com.bea.core.beaninfo_1.0.1.0.jar
Integrating jar <--(1)/(36976)/(12)/C:\Programme\bea\modules\com.bea.core.beaninfo_1.0.1.0.jar
Integrating jar -->(1)/(36976)/C:\Programme\bea\modules\com.bea.core.datasource_1.0.1.0.jar
Ignoring Duplicate Entry utils/Schema.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry utils/dbping.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCConnectionPoolParamsBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCDataSourceBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCDataSourceParamsBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCDriverParamsBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCPropertiesBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCPropertyBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry weblogic/j2ee/descriptor/wl/JDBCXAParamsBean.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(37133)/(157)/C:\Programme\bea\modules\com.bea.core.datasource_1.0.1.0.jar
Integrating jar -->(1)/(37133)/C:\Programme\bea\modules\com.bea.core.descriptor_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/descriptor/SettableBean.class also in C:\Programme\bea\modules\com.bea.core.datasource_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/descriptor/beangen/LegalChecks.class also in C:\Programme\bea\modules\com.bea.core.beangen_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/descriptor/beangen/StringHelper.class also in C:\Programme\bea\modules\com.bea.core.beangen_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/descriptor/beangen/XMLHelper.class also in C:\Programme\bea\modules\com.bea.core.beangen_1.0.1.0.jar
Integrating jar <--(1)/(37226)/(93)/C:\Programme\bea\modules\com.bea.core.descriptor_1.0.1.0.jar
Integrating jar -->(1)/(37226)/C:\Programme\bea\modules\com.bea.core.diagnostics.core_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/diagnostics/type/UnexpectedExceptionHandler.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(37264)/(38)/C:\Programme\bea\modules\com.bea.core.diagnostics.core_1.0.1.0.jar
Integrating jar -->(1)/(37264)/C:\Programme\bea\modules\com.bea.core.i18n_1.0.1.0.jar
Integrating jar <--(1)/(37289)/(25)/C:\Programme\bea\modules\com.bea.core.i18n_1.0.1.0.jar
Integrating jar -->(1)/(37289)/C:\Programme\bea\modules\com.bea.core.i18n.generator_1.0.1.0.jar
Integrating jar <--(1)/(37335)/(46)/C:\Programme\bea\modules\com.bea.core.i18n.generator_1.0.1.0.jar
Integrating jar -->(1)/(37335)/C:\Programme\bea\modules\com.bea.core.management.core_1.0.1.0.jar
Integrating jar <--(1)/(37343)/(8)/C:\Programme\bea\modules\com.bea.core.management.core_1.0.1.0.jar
Integrating jar -->(1)/(37343)/C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Integrating jar <--(1)/(37389)/(46)/C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Integrating jar -->(1)/(37389)/C:\Programme\bea\modules\com.bea.core.mbean.support_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/AbstractCommoConfigurationBean$Helper.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/AbstractCommoConfigurationBean.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/AbstractCommoConfigurationBeanBinder.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/AbstractCommoConfigurationBeanImplBeanInfo.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/BaseModelMBean.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/Commo$Pair.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/Commo.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/CommoMBean.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/CommoMBeanInstance.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/CommoModelMBeanAttributeInfo.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/CommoModelMBeanConstructorInfo.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/CommoModelMBeanInfoSupport.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/CommoModelMBeanNotificationInfo.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/CommoModelMBeanOperationInfo.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/CommoOperationsException.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/DescriptorSupport$1.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/DescriptorSupport$Pair.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/DescriptorSupport$VoidValue.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/DescriptorSupport.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/DescriptorSupportBase.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/RequiredModelMBeanWrapper.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/SecurityMBeanData.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/StandardInterface.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/TypedMBeanData.class also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/ant/taskdefs/management/commo/antlib.xml also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/CustomMBeanImpl.j also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/DiabloCustomMBeanIntf.j also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/commo/commo.dtd also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/management/internal/mbean/SecurityReadOnlyMBean.template also in C:\Programme\bea\modules\com.bea.core.mbean.maker_1.0.1.0.jar
Integrating jar <--(1)/(37389)/(0)/C:\Programme\bea\modules\com.bea.core.mbean.support_1.0.1.0.jar
Integrating jar -->(1)/(37389)/C:\Programme\bea\modules\com.bea.core.messaging.kernel_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(37548)/(159)/C:\Programme\bea\modules\com.bea.core.messaging.kernel_1.0.1.0.jar
Integrating jar -->(1)/(37548)/C:\Programme\bea\modules\com.bea.core.resourcepool_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(37583)/(35)/C:\Programme\bea\modules\com.bea.core.resourcepool_1.0.1.0.jar
Integrating jar -->(1)/(37583)/C:\Programme\bea\modules\com.bea.core.weblogic.rmi.client_1.0.1.0.jar
Ignoring Duplicate Entry weblogic/rmi/extensions/server/_HeartbeatHelper_Stub.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(37612)/(29)/C:\Programme\bea\modules\com.bea.core.weblogic.rmi.client_1.0.1.0.jar
Integrating jar -->(1)/(37612)/C:\Programme\bea\modules\com.bea.core.weblogic.security.wls_2.0.1.0.jar
Integrating jar <--(1)/(38016)/(404)/C:\Programme\bea\modules\com.bea.core.weblogic.security.wls_2.0.1.0.jar
Integrating jar -->(1)/(38016)/C:\Programme\bea\modules\com.bea.core.weblogic.saaj_1.0.1.0.jar
Integrating jar <--(1)/(38217)/(201)/C:\Programme\bea\modules\com.bea.core.weblogic.saaj_1.0.1.0.jar
Integrating jar -->(1)/(38217)/C:\Programme\bea\modules\com.bea.core.weblogic.stax_1.0.1.0.jar
Integrating jar <--(1)/(38543)/(326)/C:\Programme\bea\modules\com.bea.core.weblogic.stax_1.0.1.0.jar
Integrating jar -->(1)/(38543)/C:\Programme\bea\modules\com.bea.core.store_1.0.1.0.jar
Skipping native/aix/ppc64/libwlfileio2.so
Skipping native/aix/ppc/libwlfileio2.so
Skipping native/hpux11/IPF32/libwlfileio2.so
Skipping native/hpux11/IPF64/libwlfileio2.so
Skipping native/hpux11/PA_RISC64/libwlfileio2.sl
Skipping native/hpux11/PA_RISC/libwlfileio2.sl
Skipping native/linux/i686/libwlfileio2.so
Skipping native/linux/ia64/libwlfileio2.so
Skipping native/linux/x86_64/libwlfileio2.so
Skipping native/solaris/sparc64/libwlfileio2.so
Skipping native/solaris/sparc/libwlfileio2.so
Skipping native/solaris/x64/libwlfileio2.so
Skipping native/solaris/x86/libwlfileio2.so
Skipping native/win/32/wlfileio2.dll
Skipping native/win/64/wlfileio2.dll
Skipping native/win/x64/wlfileio2.dll
Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(38695)/(152)/C:\Programme\bea\modules\com.bea.core.store_1.0.1.0.jar
Integrating jar -->(1)/(38695)/C:\Programme\bea\modules\com.bea.core.store.gxa_1.0.1.0.jar
Integrating jar <--(1)/(38728)/(33)/C:\Programme\bea\modules\com.bea.core.store.gxa_1.0.1.0.jar
Integrating jar -->(1)/(38728)/C:\Programme\bea\modules\com.bea.core.transaction_2.0.1.0.jar
Ignoring Duplicate Entry weblogic/i18n/i18n.properties also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(38943)/(215)/C:\Programme\bea\modules\com.bea.core.transaction_2.0.1.0.jar
Integrating jar -->(1)/(38943)/C:\Programme\bea\modules\com.bea.core.utils.full_1.0.1.0.jar
Skipping native/aix/ppc64/libterminalio.so
Skipping native/aix/ppc/libterminalio.so
Skipping native/hpux11/IPF32/libterminalio.so
Skipping native/hpux11/IPF64/libterminalio.so
Skipping native/hpux11/PA_RISC64/libterminalio.sl
Skipping native/hpux11/PA_RISC/libterminalio.sl
Skipping native/linux/i686/libterminalio.so
Skipping native/linux/ia64/libterminalio.so
Skipping native/linux/s3990/libterminalio.so
Skipping native/linux/x86_64/libterminalio.so
Skipping native/macosx/pps/libterminalio.jnilib
Skipping native/solaris/sparc64/libterminalio.so
Skipping native/solaris/sparc/libterminalio.so
Skipping native/solaris/x64/libterminalio.so
Skipping native/solaris/x86/libterminalio.so
Skipping native/win/32/terminalio.dll
Skipping native/win/64/terminalio.dll
Skipping native/win/x64/terminalio.dll
Ignoring Duplicate Entry weblogic/utils/StackTraceUtilsClient.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(39367)/(424)/C:\Programme\bea\modules\com.bea.core.utils.full_1.0.1.0.jar
Integrating jar -->(1)/(39367)/C:\Programme\bea\modules\com.bea.core.utils.classloaders_1.0.1.0.jar
Integrating jar <--(1)/(39415)/(48)/C:\Programme\bea\modules\com.bea.core.utils.classloaders_1.0.1.0.jar
Integrating jar -->(1)/(39415)/C:\Programme\bea\modules\com.bea.core.utils.expressions_1.0.1.0.jar
Integrating jar <--(1)/(39429)/(14)/C:\Programme\bea\modules\com.bea.core.utils.expressions_1.0.1.0.jar
Integrating jar -->(1)/(39429)/C:\Programme\bea\modules\com.bea.core.utils.wrapper_1.0.1.0.jar
Integrating jar <--(1)/(39550)/(121)/C:\Programme\bea\modules\com.bea.core.utils.wrapper_1.0.1.0.jar
Integrating jar -->(1)/(39550)/C:\Programme\bea\modules\com.bea.core.timers_1.0.1.0.jar
Ignoring Duplicate Entry commonj/timers/CancelTimerListener.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry commonj/timers/StopTimerListener.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry commonj/timers/Timer.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry commonj/timers/TimerListener.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry commonj/timers/TimerManager.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Integrating jar <--(1)/(39581)/(31)/C:\Programme\bea\modules\com.bea.core.timers_1.0.1.0.jar
Integrating jar -->(1)/(39581)/C:\Programme\bea\modules\com.bea.core.weblogic.workmanager_1.0.1.0.jar
Ignoring Duplicate Entry commonj/work/RemoteWorkItem.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry commonj/work/Work.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry commonj/work/WorkCompletedException.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry commonj/work/WorkEvent.class also in C:\Programme\bea\weblogic10.0\server\lib\weblogic.jar
Ignoring Duplicate Entry commonj/work/WorkExcepDirk Ludwig wrote:
Joe Weinstein wrote:[...]
Hi. You should open an official support case,
but it may be that we do not support
external client JDBC with the client jar.Actually, I misspoke. I think we do supply a client
jar, and that may be true
what I said, but I see you're making your own. Can
you find out what jar you're
loading the InstrumentationSupport class from? That's
the original location of
the error, and that class doesn't exist in 10.0.Hi Joe, thanks for your reply.
First of all, let me clarify what we did and why we did it: We have a stand-alone client application that needs to communicate with a Weblogic server using the t3 protocol (we don't want IIOP or HTTP tunneling). According to the official BEA documentation (see http://e-docs.bea.com/wls/docs100/client/basics.html and http://e-docs.bea.com/wls/docs100/client/t3.html) we needed to create the wlfullclient.jar file. We did this using the Weblogic JAR Builder Tool (see http://e-docs.bea.com/wls/docs100/client/jarbuilder.html). Unfortunatley we discovered the problem mentioned in my original post when we tried to run the client with that wlfullclient.jar.
Regarding your classloading question: The InstrumentationSupportImpl class is located in the wlfullclient.jar, so it does exist in WLS 10.0 (it is also contained in the weblogic.jar). Unfortunately this JAR does not contain the required class "weblogic.diagnostics.instrumentation.InstrumentationDebug". I searched for this class and found it in the OSGI module "com.bea.core.diagnostics.instrumentor_1.0.1.0.jar" shipped with the Weblogic server. Obviously the JAR Builder Tool did not include the contents of this OSGI bundle into the wlfullclient.jar. I tried to include this OSGI bundle into the classpath of the client app manually (just for testing purposes), but this onyl resultet in another NoClassDefFoundError. This time the class "com.bea.objectweb.asm.Constants" could not be found.
What astonishes me is the fact that the connection retrieval works fine when we only have the weblogic.jar in the client applications classpath, but fails when we have the wlfullclient.jar in the classpaht. It seems that the t3 communication is handled completely different, depending on what JARs I have in the classpath. Also, JMS communication works fine in both cases (i.e. for the weblogic.jar and the wlfullclient.jar). The only thing that causes problems (at least as far as we have discovered) is getting a JDBC connection from a datasource. I simply fail to see why this is the case.
Best regards,
DirkInteresting. I hope the official support case solves your problem.
I would like to dig further, but it's too far afield for me with
the workload I have at the moment.
Joe
Maybe you are looking for
-
How can I have iPhone send data back to my Mac
I have an idea for a project. To make my idea possible, I plan to use the NSSpeechRecognizer, or speech recognition on my iPod (really any form of speech recognition). Then, I want my iPod to send what it heard back to my mac as a string. I would
-
Bank Account number duplication in IT0009
Dear Team, We want to stop the Bank Account number duplication in IT0009. This is regarding the updating the Infotype 0009 for a personnel number in PA30. While updating a bank account number for any employee, system has to check whether the same ban
-
Please Migrate to the java 2 Security Model.
HI, this is my first post BTW, I dont know much about Java its just that when i try to access my work from home(united Airlines). It was working fine until i had to format My hd and since u can no longer download java from the microsoft site i had to
-
Shift key appears to be stuck...
I just recently installed Snow Leopard on my MacBook Air, and I can no longer type numbers. It seems as if the Shift key is being pressed. Any advice?
-
Parse error does not return ORA error
I had a query for a chart that would not parse and did not return an ORA- error to help me find the problem. After some trial and error I was able to identify the source of the error. I was passing a string to the TRUNC function and not a date. I wou