AXIS - deploying services implemented as dynamic proxy.

I have web services defined in interfaces Service1, Service2, Service3 deployed using a deploy.wsdd that contains the class names Impl1, Impl2, Impl3 that implements their respective interfaces.
What I want to do now is to replace Impl1, Impl2, Impl3 with instances of dynamic proxy classes that I will create using my factory.
I just want to tell Axis something like:
Implement each service by calling
Class MyFactory.getImpl(Class serviceInterface).
How can I tell Axis to do that?

Similar Messages

Dynamic proxy (clientside) for EJBObject

I ran into some ClassNotFoundException when using dynamic proxy.
Can anyone shed some light? I am running weblogic workshop 8.1 beta.
Here is the code and exception stack trace:
session bean code:
public VPNIf makeProxy(){
ClassLoader ejbcl =
ctx.getEJBObject().getClass().getClassLoader();
     try {
Class cs = Class.forName(VPNIf.class.getName(), true,
ejbcl);
     VPNIf obj = (VPNIf)VProxy.createProxy(ejbcl, new Class[]{cs});
obj.setBandwidth(15);
return obj;
} catch (Exception ex){
ex.printStackTrace();
return null;
VProxy class packaged with the bean:
public class VProxy implements InvocationHandler, Serializable {
private Map m_map;
public static Object createProxy(ClassLoader cl, Class[] interfaces)
try {
     Class proxyedClass = Class.forName(VProxy.class.getName(), true, cl);
InvocationHandler ih =
(InvocationHandler)proxyedClass.newInstance();
     return Proxy.newProxyInstance(cl, interfaces, ih);
} catch (Exception ex){
ex.printStackTrace();
return null;
VPNIf with the bean:
public interface VPNIf extends Serializable {
public void setBandwidth(int x);
public int getBandwidth();
Client code:
Method method =
sessionObject.getClass().getMethod("makeProxy", null);
Class proxyedIf = method.getReturnType();
Class x = Class.forName("org.openuri.VPNIf", true,
proxyedIf.getClassLoader()); // this line works fine
Method method1 = proxyedIf.getMethod("getBandwidth", null);
Object proxy = method.invoke(sessionObject, null); //
Exception here
method = proxyedIf.getMethod("getBandwidth", null);
Integer bw = (Integer)method.invoke(proxy, null);
System.out.println("bandwidth: " + bw);
Here is the exception on client side:
Caused by: java.rmi.UnmarshalException: failed to unmarshal interface
org.openuri.VPNIf; nested exception is:
     java.lang.ClassNotFoundException: org.openuri.VPNIf
     at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:163)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:285)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
     at org.openuri.VPNServiceBean_9khl0e_EOImpl_WLStub.makeProxy(Unknown
Source)
     ... 21 more
Caused by: java.lang.ClassNotFoundException: org.openuri.VPNIf
     at java.net.URLClassLoader$1.run(URLClassLoader.java:198)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:186)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:265)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:217)
     at java.io.ObjectInputStream.resolveProxyClass(ObjectInputStream.java:630)
     at java.io.ObjectInputStream.readProxyDesc(ObjectInputStream.java:1469)
     at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1432)
     at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1626)
     at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
     at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
     at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:111)
     at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:95)
     at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:56)
     at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:159)

Greetings,
Say i have a servlet named "DispatcherServlet",
let", how should i go about to implement a
dynamic proxy class for the same? Depends on your application requirements and what you want to proxy to and where. Can you be more specific?
Thanks
SamRegards,
Tony "Vee Schade" Cook

OAAM web services implementation class for WebSphere 6.1

Hi All,
My client is running OAAM 10.1.4.5 and looking to migrate to WebSphere 6.1. I'd like to replace the (default) Apache Axis web services implementation class with a custom-built WebSphere 6.1 implementation class. Does anyone have any code they'd been willing to share?
Regards,
Steven

It is may be because BO is not ready for Java 2 and you can find more info about readyness of applications at
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/csec_rsecmgr2.html
I am not sure if BO is prepared for the very fine-grain access control programming model that Java 2 security is capable of enforcing.
May be some one from PG should be able to answer readyness of BO with Java2.
-Gokul.

Dynamic proxy invokes basic auth web service

My dynamic proxy client works fine with any web service except the basic auth secured one.
I know how to use stub client to work around this issue. But I haven't found a way to get around when dynamic proxy clients are used.
Any idea is appricated. Thanks

Paula-
Given that you can work around this issue with the stub client,
you should be able to work around the issue in the dynamic proxy client
in the same way-
I am interested that you say workaround the issue with the stub client.
Is there a problem that you have noted?
If you can let me know how you worked this issue with the stub,
and what problems you have specifically had with the dynamic proxy client
I will look at the issue to see if it a bug.
Please let me know what environment you are working in, the version of jaxrpc 1.x,
what container, jdk or jre and a sample client program that would help me understand
the problem.
Thanks,
Kathy

Using Dynamic Proxy in AppServer 7 during EJB deploy

Hello Guys.
I know Dynamic Proxy is the default when deploying EJBs starting from AS 8.1. If I want to use Dynamic Proxy in AS before 8.1, how can I do that?
Thanks.
Rye

Just to clarify, I assume you're referring to the Remote EJB dynamic RMI-IIOP feature in 8.x and later.
Java SE has a generic dynamic proxy facility in the java.lang.reflect package. That can of course
be used by any JDK 1.4 program and has no relationship to Java EE.
There is no support for the Remote EJB dynamic RMI-IIOP feature prior to AS 8.x / J2EE SDK 1.4.
In those releases, e.g. S1AS 7.x / J2EE 1.3 SDK , static RMI-IIOP stubs are generated during
deployment and must be present for any client access to Remote EJBs.
--ken

How to get original message in web service implementation and proxy

Hi,
We have a java web service and its client (proxy) generated from WSDL by JDev wizards. All the parameters are mapped to classes, but we need a way to get the original message we send and receive in order to log it.
Is there any way to get the SOAP message that is being sent/received?
Thank you

If you are using 10.1.3 or later releases, you can use the JAX-RPC handler to gain access to the message. Your SOAP payload can then been manipulated using the SAAJ APIs. You have also the option to log messages directly from OWSM.
Best,
-Eric

JAX-RPC Dynamic Proxy Client Question

I have a very simple web service successfully deployed using Tomcat 5 and Apache Axis. It simply takes a string and returns a String. Regardless, it's working.
Now I'm wanting to create a JAX-RPC dynamic proxy client as described on the following page:
http://java.sun.com/webservices/docs/1.3/tutorial/doc/JAXRPC5.html
There are numerous other articles out there describing the same method.
My problem is that I'm getting a ServiceException on the following line every time I try to run my client:
ServiceFactory factory = ServiceFactory.newInstance();
Would anyone have any ideas why this might be or what I might be missing? All the articles make it seem like this is just a trivial line and never mention much about it.
Any help would be appreciated. Thanks.

Hello,
You are getting a service Exception on ServiceFactory.newInstance() method?
Actually, I have never seen this problem before. Is it possible that there are
classpath issues? That is, are you using just the jars from the jwsdp?
Regards,
Kathy

Dynamic proxy not working

Folks,
I deployed a EJB Webservice(Document Literal) in Sun App Server. I am able to access the method through Static Stub but Dynamic proxy says the below error:
port: {http://com.venkat.webservice/AllInOne/targ}AllInOneIntfPort does not contain operation: justConcat
     at com.sun.xml.rpc.client.dii.ConfiguredCall.configureCall(ConfiguredCall.java:98)
     at com.sun.xml.rpc.client.dii.ConfiguredCall.configureCall(ConfiguredCall.java:69)
     at com.sun.xml.rpc.client.dii.ConfiguredCall.setMethodName(ConfiguredCall.java:50)
     at com.sun.xml.rpc.client.dii.DynamicProxyBuilder.buildDynamicProxyFor(DynamicProxyBuilder.java:66)
     at com.sun.xml.rpc.client.dii.ConfiguredService.getPort(ConfiguredService.java:250)
     at wsclient.DynProxy.main(DynProxy.java:50)
The Code i used to access is as below:
String UrlString = "http://venkat:8080/AllInOneServiceBean" + "?WSDL";
            String nameSpaceUri = "http://com.venkat.webservice/AllInOne/targ";
            String serviceName = "AllInOneService";
            String portName = "AllInOneIntfPort";
Service helloService =
                serviceFactory.createService(helloWsdlUrl,
                    new QName(nameSpaceUri, serviceName));
AllInOneIntf myProxy = (AllInOneIntf) helloService.getPort(new QName(
                    nameSpaceUri,
                    portName), AllInOneIntf.class);
            System.out.println(myProxy.justConcat("aasds","as"));The WSDL File is:
<?xml version="1.0" encoding="UTF-8"?><definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://com.venkat.webservice/AllInOne/targ" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:ns2="http://com.venkat.webservice/AllInOne/type" name="AllInOneService" targetNamespace="http://com.venkat.webservice/AllInOne/targ">
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://com.venkat.webservice/AllInOne/type" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://com.venkat.webservice/AllInOne/type">
<complexType name="justConcat">
<sequence>
<element name="String_1" type="string" nillable="true"/>
<element name="String_2" type="string" nillable="true"/></sequence></complexType>
<complexType name="justConcatResponse">
<sequence>
<element name="result" type="string" nillable="true"/></sequence></complexType>
<complexType name="takeCustomObject">
<sequence>
<element name="ValueObject_1" type="tns:ValueObject" nillable="true"/></sequence></complexType>
<complexType name="ValueObject">
<sequence>
<element name="comp" type="string" nillable="true"/>
<element name="name" type="string" nillable="true"/></sequence></complexType>
<complexType name="takeCustomObjectResponse">
<sequence>
<element name="result" type="string" nillable="true"/></sequence></complexType>
<element name="justConcat" type="tns:justConcat"/>
<element name="justConcatResponse" type="tns:justConcatResponse"/>
<element name="takeCustomObject" type="tns:takeCustomObject"/>
<element name="takeCustomObjectResponse" type="tns:takeCustomObjectResponse"/></schema></types>
<message name="AllInOneIntf_justConcat">
<part name="parameters" element="ns2:justConcat"/></message>
<message name="AllInOneIntf_justConcatResponse">
<part name="result" element="ns2:justConcatResponse"/></message>
<message name="AllInOneIntf_takeCustomObject">
<part name="parameters" element="ns2:takeCustomObject"/></message>
<message name="AllInOneIntf_takeCustomObjectResponse">
<part name="result" element="ns2:takeCustomObjectResponse"/></message>
<portType name="AllInOneIntf">
<operation name="justConcat">
<input message="tns:AllInOneIntf_justConcat"/>
<output message="tns:AllInOneIntf_justConcatResponse"/></operation>
<operation name="takeCustomObject">
<input message="tns:AllInOneIntf_takeCustomObject"/>
<output message="tns:AllInOneIntf_takeCustomObjectResponse"/></operation></portType>
<binding name="AllInOneIntfBinding" type="tns:AllInOneIntf">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<operation name="justConcat">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/></input>
<output>
<soap:body use="literal"/></output></operation>
<operation name="takeCustomObject">
<soap:operation soapAction=""/>
<input>
<soap:body use="literal"/></input>
<output>
<soap:body use="literal"/></output></operation></binding>
<service name="AllInOneService">
<port name="AllInOneIntfPort" binding="tns:AllInOneIntfBinding">
<soap:address location="http://venkat:8080/AllInOneServiceBean" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"/></port></service></definitions>
Please let me what mistake i am doing if any? or is this a bug
Thanks
Venkat

If you are using document/literal, which this WSDL is, you would be much better off using Metro (JAX-WS) as it has a much better dynamic interface in the Dispatch APIs. Metro: http://metro.dev.java.net, JAX-WS: http://jax-ws.dev.java.net.

Dynamic Proxy API does not support WSRM.

Hi ,
I am recieving "Dynamic Proxy API does not support WSRM. See operation Outbound_Service_Interface" when i am testing the scenario in WSNavigator where in i am using WS adapter at the sender side.
Can anyone tell what might be the problem.
Thanks & Regards,
Hamsa Shree

Hello Hamsa,
This was known error still SDN buddies are looking for research:
May these links will help:
http://help.sap.com/saphelp_nwpi71/helpdata/en/46/741a3dfcfa0eede10000000a155369/content.htm
You can try with this blog also:
/people/michael.hill/blog/2007/12/13/service-implementation-in-java
Even previous threads are shown the proofs as still looking for clues:
web service scenario with PI 7.1 as mediator does not work
error with WS navigator , 'Dynamic Proxy API does not support WSRM'

Dynamic Proxy API does not support WSRM. See operation: si employee

Hi,
I have followed all the steps required in SOAMANAGER on application system and have successfully published a service. However while testing the service from service regisrty I encountered this error Dynamic Proxy API does not support WSRM. See operation: si employee
Kindly help to resolve the issue
Regards,
Milan Thaker

Please refer
/people/michael.hill/blog/2007/12/13/service-implementation-in-java
http://help.sap.com/saphelp_nwpi71/helpdata/en/46/741a3dfcfa0eede10000000a155369/content.htm

JBI: problem with deploy-service-assembly

I've developed a service component following the instructions in :
http://java.sun.com/integration/reference/techart/DevelopingAServiceEngineComponent-1-2.pdf
The Componet has been installed and started succesfully:
With jbiadmin command "list-service-engines" the result is:
================================
List of Service Engines
================================
Name : MyServiceEngine
State: Started
Name : SunSequencingEngine
State: Started
Name : SunTransformationEngine
State: Started
When I try to deploy the Service Assembly deploy-service-assembly C:\mine\MyServiceAssembly.zip I got the following error:
deploy-service-assembly C:\mine\MyServiceAssembly.zipThe deploy-service-assembly Command Failed Component : MyServiceEngine
MESSAGE:()RuntimeException thrown by the invoke method of the Dynamic MBean
Root Cause:
MESSAGE:(UNKNOWN)<?xml version="1.0" encoding="UTF-8" standalone="yes"?><component-task-result><component-name>MyServiceEngine</componen
t-name><component-task-result-details><task-result-details><task-id>deploy</task-id><task-result>FAILED</task-result><message-type>ERROR</message-type
<task-status-msg><msg-loc-info><loc-token> </loc-token><loc-message>JBIFW0063: Internal error: Null argument received for serviceUnitRootPath.</loc-message></msg-loc-info></task-status-msg></task-result-details></component-task-result-details></component-task-result>
>
In the Application server log (server.log) there's the following message:
[#|2005-10-07T02:33:58.268+0200|SEVERE|sun-appserver-pe8.1_02|com.sun.jbi.framework|_ThreadID=40;|JBIFW0063: Internal error: Null argument received for serviceUnitRootPath.|#]
Any ideas'information on how to get past this situation?
Thx
Adrian

Adrian,
I'll pass this along to the RI team, to see if they have any ideas.
In the meantime, I'll take a guess: have you implemented the ServiceUnitManager interface, and have you implemented the Component.getServiceUnitManager() method such that it returns an instance (preferably a singleton) of your SUM class?
Also, if you look in the appserver's server.log file, are there any errors or warnings logged concerning the installation or startup of your custom component that occured before the JBIFW0063 error you reported?

Error while invoking a webservice using Axis deployed in tomacat from Bpel

Hi,
I am trying to invoke a Axis webservice(from Java class to WSDL- bottom up java bean webservice approach) developed in Exclipse IDE, deployed in Tomcat.
When i am trying to invoke the service, from Bpel from Jdeveloper it is throwing error as such :
Invoke_1 (faulted)
[2009/05/22 14:32:18] Faulted while invoking operation "storeLoanData" on provider "LoanDataPersist".less
-<messages>
-<input>
-<Invoke_1_storeLoanData_InputVariable>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="p_request">
-<p_request xmlns="" xmlns:def="http://dtos.demo.com" xsi:type="def:LoanDataPersistRequest" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<customerName>wew
</customerName>
<netIncome>12
</netIncome>
<loanAmount>12
</loanAmount>
<realEstateAddress>wew
</realEstateAddress>
<customerID/>
</p_request>
</part>
</Invoke_1_storeLoanData_InputVariable>
</input>
-<fault>
-<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
-<part name="summary">
<summary>exception on JaxRpc invoke: trailing block elements must have an id attribute
</summary>
</part>
</remoteFault>
</fault>
</messages>
I may add that, the WSDL generated is using "soap:enc:array ", rpc style.
Can anyone tell me the reason and suggest .

Hi Marc,
Thanks for the guidancer. But sir, i am unable to detect at which place i have to do the required changes.I found p_request as a parameter in the method only in the interface only.
As bcos ultimately , i am generating the tomcat /axis web service (WSDL) from the java class, which is using 2 Request and response java bean, in which they are doing someing like this:
private static org.apache.axis.description.TypeDesc typeDesc =
new org.apache.axis.description.TypeDesc(LoanDataPersistRequest.class, true);
static {
typeDesc.setXmlType(new javax.xml.namespace.QName("http://dtos.demo.com", "LoanDataPersistRequest"));
org.apache.axis.description.ElementDesc elemField = new org.apache.axis.description.ElementDesc();
elemField.setFieldName("customerName");
elemField.setXmlName(new javax.xml.namespace.QName("", "customerName"));
elemField.setXmlType(new javax.xml.namespace.QName("", "string"));
elemField.setNillable(true);
etc etc...................}
And second thing is when the WSDL is generated, from that the stubs and skeletons is generated to test the service.
There in the Stub i found out "p_request" in this place:
private static void _initOperationDesc1(){
org.apache.axis.description.OperationDesc oper;
org.apache.axis.description.ParameterDesc param;
oper = new org.apache.axis.description.OperationDesc();
oper.setName("storeLoanData");
param = new org.apache.axis.description.ParameterDesc(*new javax.xml.namespace.QName("", "p_request")*, org.apache.axis.description.ParameterDesc.IN, new javax.xml.namespace.QName("http://dtos.demo.com", "LoanDataPersistRequest"), com.demo.dtos.LoanDataPersistRequest.class, false, false);
oper.addParameter(param);
oper.setReturnType(new javax.xml.namespace.QName("http://dtos.demo.com", "LoanDataPersistResponse"));
oper.setReturnClass(com.demo.dtos.LoanDataPersistResponse.class);
oper.setReturnQName(new javax.xml.namespace.QName("", "storeLoanDataReturn"));
oper.setStyle(org.apache.axis.constants.Style.RPC);
oper.setUse(org.apache.axis.constants.Use.ENCODED);
_operations[0] = oper;
And in skeleton :
static {
org.apache.axis.description.OperationDesc _oper;
org.apache.axis.description.FaultDesc _fault;
org.apache.axis.description.ParameterDesc [] _params;
_params = new org.apache.axis.description.ParameterDesc [] {
new org.apache.axis.description.ParameterDesc(*new javax.xml.namespace.QName("", "p_request")*, org.apache.axis.description.ParameterDesc.IN, new javax.xml.namespace.QName("http://dtos.demo.com", "LoanDataPersistRequest"), com.demo.dtos.LoanDataPersistRequest.class, false, false),
oper = new org.apache.axis.description.OperationDesc("storeLoanData", params, new javax.xml.namespace.QName("", "storeLoanDataReturn"));
_oper.setReturnType(new javax.xml.namespace.QName("http://dtos.demo.com", "LoanDataPersistResponse"));
_oper.setElementQName(new javax.xml.namespace.QName("urn:com.demo.service", "storeLoanData"));
_oper.setSoapAction("");
myOperationsList.add(oper);
if (_myOperations.get("storeLoanData") == null) {
_myOperations.put("storeLoanData", new java.util.ArrayList());
((java.util.List)_myOperations.get("storeLoanData")).add(_oper);
PLease suggest if i make some changes in stub and skeleton how it would reflect the WSDL... or else please suggest where shud i do the required changes.

Issue in deploying Service Bus projects using maven

Hi,
I am following the following documentation for deploying service bus projects to my OSB server.
http://docs.oracle.com/middleware/1213/core/MAVEN/osb_maven_project.htm#MAVEN8973
I was able to issue mvn package as described in documentation and also able to see sbar files in .data/Maven directory of each project.
But i am seeing following error when i issue mvn pre-integration-test. Am i missing any steps.
[INFO] --- oracle-servicebus-plugin:12.1.3-0-0:deploy (default-deploy) @ System ---
[INFO] Service Bus Archive deployed using session Service_Bus_Maven-System-1424718369010.
java.io.IOException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'w
eblogic.management.mbeanservers'
        at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.ja
va:237)
        at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.j
ava:120)
        at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:369)
        at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:267)
        at oracle.sb.maven.plugin.deploy.MBeanHelper$MBeanInvocationHandler.getJMXConnector(MBeanHel
per.java:228)
        at oracle.sb.maven.plugin.deploy.MBeanHelper$MBeanInvocationHandler.invoke(MBeanHelper.java:
131)
        at com.sun.proxy.$Proxy16.createSession(Unknown Source)
        at oracle.sb.maven.plugin.DeployMojo.createSession(DeployMojo.java:141)
        at oracle.sb.maven.plugin.DeployMojo.execute(DeployMojo.java:89)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.j
ava:101)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBu
ilder.java:84)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBu
ilder.java:59)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter
.java:183)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.management.mbeanservers.d
omainruntime'. Resolved 'weblogic.management.mbeanservers' [Root exception is javax.naming.NameNotFo
undException: Unable to resolve 'weblogic.management.mbeanservers.domainruntime'. Resolved 'weblogic
.management.mbeanservers']; remaining name 'domainruntime'
        at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1180
        at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:270)
        at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:187)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:210)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:224)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:224)
        at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:224)
        at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
        at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:701)
        at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:231)
        at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:527)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
        at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:523)

Hi Siva,
I am facing same issue I am bale to create package but while deployment goal I am facing problem.I am following same document as you do.
I can see my mvn-pre-integration ..show me sucees in result
[DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:3.0.3
[DEBUG] Configuring mojo com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:package from plugin realm ClassRealm[plugin>com.oracle.servicebus.plugin:oracl
-servicebus-plugin:12.1.3-0-0, parent: sun.misc.Launcher$AppClassLoader@65450f1f]
[DEBUG] Configuring mojo 'com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:package' with basic configurator -->
[DEBUG]   (f) oracleHome = C:\Oracle\Middleware\Oracle_Home
[DEBUG]   (f) project = MavenProject: LinuxMachine:TestOSBLinux:1.0-SNAPSHOT @ C:\JDeveloper\mywork\OSB-DEPLOY\LinuxMachine\TestOSBLinux\pom.xml
[DEBUG]   (f) system = false
[DEBUG] -- end configuration --
[INFO]
[INFO] --- oracle-servicebus-plugin:12.1.3-0-0:deploy (default-deploy) @ TestOSBLinux ---
[DEBUG] Configuring mojo com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy from plugin realm ClassRealm[plugin>com.oracle.servicebus.plugin:oracle
servicebus-plugin:12.1.3-0-0, parent: sun.misc.Launcher$AppClassLoader@65450f1f]
[DEBUG] Configuring mojo 'com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy' with basic configurator -->
[DEBUG]   (f) oraclePassword = Oracle123
[DEBUG]   (f) oracleServerUrl = http://192.168.137.150:7001
[DEBUG]   (f) oracleUsername = weblogic
[DEBUG]   (f) project = MavenProject: LinuxMachine:TestOSBLinux:1.0-SNAPSHOT @ C:\JDeveloper\mywork\OSB-DEPLOY\LinuxMachine\TestOSBLinux\pom.xml
[DEBUG] -- end configuration --
[INFO] Service Bus Archive deployed using session Service_Bus_Maven-TestOSBLinux-1429888616161.
[INFO]
[INFO] --- oracle-servicebus-plugin:12.1.3-0-0:deploy (deploy) @ TestOSBLinux ---
[DEBUG] Configuring mojo com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy from plugin realm ClassRealm[plugin>com.oracle.servicebus.plugin:oracle
servicebus-plugin:12.1.3-0-0, parent: sun.misc.Launcher$AppClassLoader@65450f1f]
[DEBUG] Configuring mojo 'com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0:deploy' with basic configurator -->
[DEBUG]   (f) oraclePassword = Oracle123
[DEBUG]   (f) oracleServerUrl = http://192.168.137.150:7001
[DEBUG]   (f) oracleUsername = weblogic
[DEBUG]   (f) project = MavenProject: LinuxMachine:TestOSBLinux:1.0-SNAPSHOT @ C:\JDeveloper\mywork\OSB-DEPLOY\LinuxMachine\TestOSBLinux\pom.xml
[DEBUG] -- end configuration --
[INFO] Service Bus Archive deployed using session Service_Bus_Maven-TestOSBLinux-1429888623126.
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building LinuxMachine 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-so
rces, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, i
tegration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy]
[DEBUG] === PROJECT BUILD PLAN ================================================
[DEBUG] Project:       LinuxMachine:LinuxMachine:1.0-SNAPSHOT
[DEBUG] Dependencies (collect): []
[DEBUG] Dependencies (resolve): []
[DEBUG] Repositories (dependencies): [central (https://repo.maven.apache.org/maven2, default, releases)]
[DEBUG] Repositories (plugins)     : [central (https://repo.maven.apache.org/maven2, default, releases)]
[DEBUG] =======================================================================
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] TestOSBLinux ....................................... SUCCESS [ 20.752 s]
[INFO] LinuxMachine ....................................... SUCCESS [ 0.009 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
But not get deployed .....
When i run mvn com.oracle.servicebus.plugin:oracle-servicebus-plugin:deploy** to invoke deployment goal it fails which below logs
org.apache.maven.plugin.MojoNotFoundException: Could not find goal 'deploy*.*' in plugin com.oracle.servicebus.plugin:oracle-servicebus-plugin:12.1.3-0-0 amon
goals deploy, package
        at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:275)
        at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:239)
        at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:233)
        at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:103)
        at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:83)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:85)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[ERROR]
[ERROR]
Thanks&Regards
Prabhat

Invoking a AXIS Web Service with a Java object as input argument

Hi
I've been trying to execute a bpel process that invokes a web service deployed through axis.
This web service takes a java object as input argument as opposed to data types that are directly mapped to java types through the SOAP engine.
I deployed and tested the service outside of BPEL using a test client class. Everything works well.
When I try to configure the "Assign" and "Invoke" activities so that service can be invoked, I cannot see the data structure through the variable picker and I see the following message:
"The element {urn:ComplexTypeWebService}TimeSheetBean is not know to the schema container. Perhaps a schema file that uses it needs to include or import its definition.There mat also be an XML schema issue (non resolvable schema) which prevents {urn:ComplexTypeWebService}TimeSheetBean from being seen by the schema processor."
Is there any example that demonstrates how to invoke an axis web service in such scenario? What am I doing wrong?
Please, let me know.

The passing of Java objects in and out of a web service is NOT supported. variables must be xml documents defined by a XML schema. In my opinion, missing Java object and WSDL is not a good idea. -Edwin

Windows Deployment Services Unable to PXE boot clients PXE-E53: No Boot Filename Received

Hi
I'm trying to configure WDS/MDT to deploy Windows 8.1. I've captured an image and I'm ready to deploy the image to a workstation, as per the above title when I attempt to PXE boot a test workstation it just times out with the following error message PXE-E52:No
Boot Filename Recieved. I've tried a few tweaks to get it working however no such luck.
The setup is as follows it's a virtual Windows 2012 R2 machine, just a fresh member server with microsoft deployment toolkit installed and WDS role installed with the nesscary framework features installed.
I've tried tweaking the properties of most of the settings within the server settings in WDS with no such luck.
I'm a novice at WDS but from what I've read I shouldn't need configure that much in the first place to get it working.
I'm willing to bet it will be something I've overlooked so I need a 2nd opinon, could anyone provide any troubleshooting tips. If you require anymore information please let me know.
Cheers

Hi Joel,
This error may caused by the WDS server is not pushing the images because PXE Clients are not able to download or communicate with the TFTP server.
The image can’t be download generally caused by the the Vlan is not enabled IP helper/DHCP relay agent configured on it, all DHCP broadcasts on UDP port 67 by client computers
should be forwarded directly to both the DHCP server and the Windows Deployment Services PXE server.
The related KB:
PXE clients computers do not start when you configure the Dynamic Host Configuration Protocol server to use options 60, 66, 67
http://support.microsoft.com/kb/259670
The similar thread:
PXE-E53: No boot filename received
http://social.technet.microsoft.com/Forums/systemcenter/en-US/8de3bd6a-f8ec-41d9-ae0f-5b2fdb9e5831/pxee53-no-boot-filename-recieved?forum=configmgrosd
WDSServer (Windows Deployment Server) Fails to Start
http://social.microsoft.com/Forums/en-US/d96b0b86-f2b0-49a5-8946-19ab515f23e6/wdsserver-windows-deployment-server-fails-to-start?forum=windowshpcitpros
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

AXIS - deploying services implemented as dynamic proxy.

Similar Messages

Maybe you are looking for