GSOAP invocation question

Hi,
We have created a custom service by merging two OOTB services GeneratePDF service and ApplyPolicy services.
Invoking this custom service via gSOAP web service fails with the following error.
SOAP 1.1 fault: SOAP-ENV:Server.userException [no subcode]
"ALC-DSC-003-000: com.adobe.idp.dsc.DSCInvocationException: Invocation error."
ALC-PDG-011-020-The source file you submitted is not supported by this version of PDF Generator.
Anyone has any examples of using gSOAP to invoke GeneratePDF service?
Can post a code snippet if required.
Thanks
Praveen Ramamurthy

looks like you did not specify the fileName parameter for the createPDFG operation, for example if you are converting a Word doc, specify the filename as abc.doc,if converting ppt filename would be abc.ppt(can be anyname as long as there is a the correct extension such as .doc extension)
If it still does not works after you provide the filename
mail me the process [email protected]

Similar Messages

Webservice invocation question ?

hi,
i had never create nor call a webservice... here the work i have to do :
my environnement is : weblogic 8.1, J2EE 1.3, eclipse.
i am developping a web application, this web applciation has a login form to enable user to connect to the application.
A web service already exits in another weblogicserver (i have the ip, port number, methode name....), this webservice and more specialy its methode checkAuthorization takes two parameters (username,password) and send back 3 result parameteers (res1, res2, res3).
what i have to do, is to create a helper class, let's say "webserviceClient" which invoke thsi webservice and depending on the result, authorize or not the connection.
i began to read the sun tutorial, i understand that there is two ways to do this job, using JAX-RPC or SOAP!!!!
my question is : are this componenet applicationserver dependent, in another way, does weblogic server 8.1 conatins the necessary package to do that ?
my second question is, what is the more easiest way to that ?
i have not a lot of time for doing that :-))),
thanks for your help

Hi Abhi,
Are your Web Service and Enterprise Application which call the web service both are running on the same server?
I think you should check web service processing time of the web service at server side(inside your web service/method) not at the client side. This way you will get better idea about how much time client takes to connect to web service and getting response back.
get elapsed time as Chicon specified at client side, and put similar at server side to get web method processing time like:
// This is you web method
public String webMethod() {
    long webServiceStart = System.currentTimeMillis();
    // Web Service Implementation
    // Web Service Implementation
    long webServiceEnd = System.currentTimeMillis();
    System.out.println("Web Service processing time : " + (webServiceEnd-webServiceStart) + " milliseconds");
}You should get above time almost same in both the case.
Because standalone application needs to connect to server explicitly where as an enterprise application running on same server as your web service is will get it invoked fast compared to standalone application.
Thanks,
Tejas

CacheLoader/Store invocation question

I believe the documentation is not very detailed when it comes to exactly how cache loader / store is invoked. I would like to see documentation explaining for instance:
1. Does the default backing-maps or some other component in the infrastructure keep track of concurrent calls to the cache store / loader for the same key or is it the job of the cache loader / store to detect and optimize this if so desired (in order to avoid that the same missing object is loaded from database multiple times in cases where each node has several service threads and/or database connections)?
2. Does the default backing-maps or some other component in the infrastructure keep track of updates that occur while a cache loader / store is requesting an object in order to prevent possible race-conditions (for instance if multiple service threads and connections are used or if updates are done using "write beside" (directly done to both cache and database using XA) and read using "read through")?
3. Can a cache store find out if object are locked or not using some node-local API? Using the normal Coherence API would result in dead-lock I assume...
I would appreciate if somebody could give a little info about these things!
/Magnus

Hi Magnus,
MagnusE wrote:
To me it seems like a specially designed CacheLoader (that in order to collect the needed information also implements the CacheStore interface but don't perform any updates to the underlying database) COULD do the trick to let me combine "read through" (that lazilly load objects from a database) and "write beside" (using XA on the cache and the database).
The special CacheLoader would keep track of any pending load (or loadAll) requests as well as the keys involved. By implementing also the CacheStore interface it would receive information about any updates performed
and if they involve any keys in the process of getting retrieved from the database it would keep the new value until the database request has terminated and in this case replace the retrieved value with the updated one (since the value from the database MAY in this case be stale since it may be based on the data before the XA transaction got committed).
I do not exactly follow this. Could you write a full transaction lifecycle example?
I am, since this may have an impact on if this is 100% race-free, trying to find out the details about what value an Oracle database return when if one tries to query an updated value when "prepare" but not "commit" (in the XA-protocol) has been called. AFAIK, you get the old value with Oracle database if you read a row for which an update is pending but not committed (doesn't matter if it is prepared). If you want to update a row for which an update is pending, then the transaction of the update invoked later blocks.
Ideal in this case would be that it block such a requests until either commit or rollback has been called but I am not sure this is the case? AFAIK, it is not.
The race condition would as I see it occur only under a very unlikely case - namely if an updated value has been evicted and is geting loaded in again by the case loader during the period between prepare and commit/rollback...
Do you see any problems with the proposed solution? It seems attractive compared to the entry processor based proposal since it would work together with transactional map (that will call normal get/getAll in order to read data) and be much simpler for the programmer that (once the special CacheLoader is developed and in place) can follow the standard Coherence model for accessing data (get, getAll)...
Please, an example (even in mail... to my new email address, not the old EPAM one). :-)
Best regards,
Robert

Question: is programmatic WL9.2 soap engine invocation possible?

Hi
Is it possible to run Weblogic9.2's SOAP engine programmatically - for instance, for axis1.2 it could be:
AxisEngine engine = getEngine();
MessageContext msgContext = new MessageContext(engine);
msgContext.setProperty(...,...);
InputStream is = HttpServletRequest.getInputStream();
Message requestMsg = new Message(is, ...);
engine.invoke(msgContext);
Message responseMsg = msgContext.getResponseMessage();
OutputStream os = HttpServletResponse.getOutputStream();
responseMsg.writeTo(os);
Why one should do it? Say, the request XML arrives not through WL's soap dedicated servlet or MDB - for example, the SOAP mdb must work in mode of Unit-of-Order or some other incoming messages treatment required before message processing?
The same question is about the client side: is it possible to obtain the SOAP request without sending [of course it is possible to specify the endpoint's URL as the myprotocol://any:any/ by extending standard java.net.URLStreamHandler - but it's ugly and brutal way:o)] to real destination? Possible reason - for instance, in case of mentioned jms binding - in case some special jms.Message proeprties must be set (say, Unit-of-Order flags)
Sincerely,
Alex
Edited by JabberW at 12/14/2006 8:28 AM
Edited by JabberW at 12/14/2006 8:30 AM

Hi rskhanuja,
Have you fix your problem? cause i have the same case.
I'm using Axis 2 right now, and i assume it uses the SOAP 1.2 namespace in defualt. My concern is i want to set my defulat namespace to SOAP 1.1.
How will go through about it? Any help will be very much appreciated. Thanks.

Dynamic client invocation (6.1) question

Hi
I am invoking an external webservice using a WL6.1 based client.
Since I have the WSDL, I use WebSeviceProxy.getServiceAt(wsdl)
to get the proxy based on the given wsdl URL. The external
webservice has the following signature :
void notification(Measurement[])
Measurement { long timestamp; double value }
In my client code, I have my own test.telemetry.Measurement
class. In the WSDL, the Measurement datastructure's QName is
http://www.6d.com/Measurement.
I am thinking that the WL webservices machinery will be able
to serialize my test.telemetry.Measurement object into the WSDL
specificed format for the Measurement datastructure. But that
doesn't seem to be happening - the QName in the serialization
is java:test.telemetry.Measurement; and hence the external
endpoint doesn't recogonize it.
I guess my above assumption is wrong ? (WHY ?)
Any workarounds ? Note that I have to use the dynamic client
mode, not the static mode.
thanx
-john

Hi John,
I'm don't think that you will be able to get WLS 6.1's Web Services Platform (i.e.
SOAP processor, WSDL processor, etc), to use your Measurement Java Bean in its
serialization/deserialization, unless the namespace prefix for it (the Measurement
complex type in the WSDL) is "java:" in the WSDL :-)
WLS 6.1 assumes that namespace URIs that start with "java:" are Java package names,
and that the corresponding elements are Java classes (i.e. <xsd:element name="Measurement">)
in that Java package. You might be able to get WLS 6.1 to use your Measurement
Java Bean using public methods on the SoapEncodingCodec class, but not if you
use the WSDL. It will still be a dynamic client. It just won't start with using
the WSDL to define stuff for you.
Regards,
Mike Wooten
"john" <[email protected]> wrote:
>
Hi
I am invoking an external webservice using a WL6.1 based client.
Since I have the WSDL, I use WebSeviceProxy.getServiceAt(wsdl)
to get the proxy based on the given wsdl URL. The external
webservice has the following signature :
void notification(Measurement[])
Measurement { long timestamp; double value }
In my client code, I have my own test.telemetry.Measurement
class. In the WSDL, the Measurement datastructure's QName is
http://www.6d.com/Measurement.
I am thinking that the WL webservices machinery will be able
to serialize my test.telemetry.Measurement object into the WSDL
specificed format for the Measurement datastructure. But that
doesn't seem to be happening - the QName in the serialization
is java:test.telemetry.Measurement; and hence the external
endpoint doesn't recogonize it.
I guess my above assumption is wrong ? (WHY ?)
Any workarounds ? Note that I have to use the dynamic client
mode, not the static mode.
thanx
-john

A question about a method with generic bounded type parameter

Hello everybody,
Sorry, if I ask a question which seems basic, but
I'm new to generic types. My problem is about a method
with a bounded type parameter. Consider the following
situation:
abstract class A{     }
class B extends A{     }
abstract class C
     public abstract <T extends A> T someMethod();
public class Test extends C
     public <T extends A> T someMethod()
          return new B();
}What I want to do inside the method someMethod in the class Test, is to
return an instance of the class B.
Normally, I'm supposed to be able to do that, because an instance of
B is also an instance of A (because B extends A).
However I cannot compile this program, and here is the error message:
Test.java:16: incompatible types
found   : B
required: T
                return new B();
                       ^
1 errorany idea?
many thanks,

Hello again,
First of all, thank you very much for all the answers. After I posted the comment, I worked on the program
and I understood that in fact, as spoon_ says the only returned value can be null.
I'm agree that I asked you a very strange (and a bit stupid) question. Actually, during recent months,
I have been working with cryptography API Core in Java. I understood that there are classes and
interfaces for defining keys and key factories specification, such as KeySpec (interface) and
KeyFactorySpi (abstract class). I wanted to have some experience with these classes in order to
understand them better. So I created a class implementing the interface KeySpec, following by a
corresponding Key subclass (with some XOR algorithm that I defined myself) and everything was
compiled (JDK 1.6) and worked perfectly. Except that, when I wanted to implement a factory spi
for my classes, I saw for the first time this strange method header:
protected abstract <T extends KeySpec> T engineGetKeySpec
(Key key, Class<T> keySpec) throws InvalidKeySpecExceptionThat's why yesterday, I gave you a similar example with the classes A, B, ...
in order to not to open a complicated security discussion but just to explain the ambiguous
part for me, that is, the use of T generic parameter.
The abstract class KeyFactorySpi was defined by Sun Microsystem, in order to give to security
providers, the possibility to implement cryptography services and algorithms according to a given
RFC (or whatever technical document). The methods in this class are invoked inside the
KeyFactory class (If you have installed the JDK sources provided by Sun, You can
verify this, by looking the source code of the KeyFactory class.) So here the T parameter is a
key specification, that is, a class that implements the interface KeySpec and this class is often
defined by the provider and not Sun.
stefan.schulz wrote:
>
If you define the method to return some bound T that extends A, you cannot
return a B, because T would be declared externally at invocation time.
The definition of T as is does not make sense at all.>
He is absolutely right about that, but the problem is, as I said, here we are
talking about the implementation and not the invocation. The implementation is done
by the provider whereas the invocation is done by Sun in the class KeyFactory.
So there are completely separated.
Therefore I wonder, how a provider can finally impelment this method??
Besides, dannyyates wrote
>
Find whoever wrote the signature and shoot them. Then rewrite their code.
Actually, before you shoot them, ask them what they were trying to achieve that
is different from my first suggestion!
>
As I said, I didn't choose this method header and I'm completely agree
with your suggestion, the following method header will do the job very well
protected abstract KeySpec engineGetKeySpec (Key key, KeySpec key_spec)
throws InvalidKeySpecException and personally I don't see any interest in using a generic bounded parameter T
in this method header definition.
Once agin, thanks a lot for the answers.

Questions on JMX and management-config

I was wondering if anyone can clarify the usage of management-config.
We've got a setup with managed-nodes=all and allow-remote-management=true (other params defaulted). We've got processes that occasionally ping the cluster (via a single node) to log performance statistics and to look for problems that might require intervention (across all nodes via remote management).
I'm trying to determine if the JMX subsystem is completely isolated from runtime cache performance.
1) Does the setting for the read-only flag impact performance in any way? If set to false, is there any sort of locking or synchronization that takes place when querying cluster nodes?
2) Do calls to JMX (and presumably the Invocation Service) share any resources with a Distributed Cache Service?
3) the Default management-config settings in Tangosol-coherence.xml point to the "Management" service - which is not actually defined elsewhere in the configuration file. Is this actually an implicit link to the Invocation Service?
4) Is there a single "Service Thread"? or does each distinct service have its own service thread?
Thanks in advance,
Dave

The performance impact of management is relatively small. The consumption is based on the information "read" (getAttribute/getAttribute) and the frequency of the poll. Polls of the same data element within 1 second will receive the same result for remote nodes.
The formula to determine the network consumption estimation formula for Coherence 3.3 on a single poll of the information is:
Estimated network bytes per poll =
Number of remote Node MBeans retrieved * 725
+ Number of remote Cache MBeans retrieved * 225
+ Number of remote Storage Manager MBeans Retrieved * 720
+ Number of remote Service MBeans Retrieved * 144
+ Number of remote Point to Point MBeans * (Number of Nodes in Grid -1 * 250)
Given the order N size of the Point-to-Point MBeans, It is not recommended to put that information in a loop for a large cluster.
1) Does the setting for the read-only flag impact performance in any way? If set to false, is there any sort of locking or synchronization that takes place when querying cluster nodes?
EW: The Read-only flag does not impact performance. There is no synchronization on read of the objects. Synchronization on update is on an attribute by attribute basis.
2) Do calls to JMX (and presumably the Invocation Service) share any resources with a Distributed Cache Service?
EW: The JMX calls are processed through the Management (Invocation) Service. This shares system (memory, CPU, network) resources with other services. The management information is not processed out-of-band and under extreme load performance will be impacted.
3) the Default management-config settings in Tangosol-coherence.xml point to the "Management" service - which is not actually defined elsewhere in the configuration file. Is this actually an implicit link to the Invocation Service?
EW: The Management service is a non-configurable Invocation service.
4) Is there a single "Service Thread"? or does each distinct service have its own service thread?
EW : Not exactly sure I understand the question. Each service has its' own "Service" thread and thread pool. However, there are some shared components at the TCMP (network) layer.
Hope this helps,
Everett Williams
Message was edited by:
user631017
Message was edited by:
user631017

Problem to generate classes from a gsoap server's wsdl with wsimport

Hello,
I trie for a long time to generate my client classes from a wsdl file with wsimport. The wsdl file was generated by gsoap.
Here, the wsdl file :
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="form"
targetNamespace="https://enterprise-name-masked.com/form.wsdl"
xmlns:tns="https://enterprise-name-masked.com/form.wsdl"
xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:generic="generic"
xmlns:xop="http://www.w3.org/2004/08/xop/include"
xmlns:xmime4="http://www.w3.org/2004/11/xmlmime"
xmlns:form="form"
xmlns:SOAP="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:MIME="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:DIME="http://schemas.xmlsoap.org/ws/2002/04/dime/wsdl/"
xmlns:WSDL="http://schemas.xmlsoap.org/wsdl/"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
<schema targetNamespace="generic"
xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:generic="generic"
xmlns:xop="http://www.w3.org/2004/08/xop/include"
xmlns:xmime4="http://www.w3.org/2004/11/xmlmime"
xmlns:form="form"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="unqualified"
attributeFormDefault="unqualified">
<import namespace="http://www.w3.org/2004/08/xop/include"/>
<import namespace="http://www.w3.org/2004/11/xmlmime"/>
<import namespace="http://www.w3.org/2003/05/soap-encoding"/>
<simpleType name="service">
   <restriction base="xsd:string">
    <enumeration value="service-none"/>
    <enumeration value="service-ident"/>
    <enumeration value="service-pool"/>
    <enumeration value="service-hwr"/>
    <enumeration value="service-form"/>
    <enumeration value="service-document"/>
   </restriction>
</simpleType>
<simpleType name="result-code">
   <restriction base="xsd:string">
    <enumeration value="ok"/>
    <enumeration value="already-exists"/>
    <enumeration value="not-found"/>
    <enumeration value="cant-connect"/>
    <enumeration value="exception"/>
    <enumeration value="bad-conversion"/>
    <enumeration value="bad-values"/>
    <enumeration value="session-not-found"/>
    <enumeration value="initialization-failed"/>
   </restriction>
</simpleType>
<complexType name="result">
   <sequence>
     <element name="code" type="generic:result-code" minOccurs="1" maxOccurs="1"/>
     <element name="details" type="xsd:string" minOccurs="1" maxOccurs="1"/>
   </sequence>
</complexType>
</schema>
<schema targetNamespace="form"
xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:generic="generic"
xmlns:xop="http://www.w3.org/2004/08/xop/include"
xmlns:xmime4="http://www.w3.org/2004/11/xmlmime"
xmlns:form="form"
xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="unqualified"
attributeFormDefault="unqualified">
<import namespace="http://www.w3.org/2004/08/xop/include"/>
<import namespace="http://www.w3.org/2004/11/xmlmime"/>
<import namespace="http://www.w3.org/2003/05/soap-encoding"/>
<simpleType name="area-type">
   <restriction base="xsd:string">
    <enumeration value="area-type-text"/>
    <enumeration value="area-type-numeric"/>
    <enumeration value="area-type-date"/>
    <enumeration value="area-type-checkbox"/>
    <enumeration value="area-type-slider"/>
    <enumeration value="area-type-draw"/>
    <enumeration value="area-type-identifier"/>
   </restriction>
</simpleType>
<simpleType name="format">
   <restriction base="xsd:string">
    <enumeration value="A5"/>
    <enumeration value="A4"/>
    <enumeration value="A3"/>
    <enumeration value="A2"/>
    <enumeration value="A1"/>
    <enumeration value="A0"/>
   </restriction>
</simpleType>
<complexType name="area">
   <sequence>
     <element name="name" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="x" type="xsd:double" minOccurs="1" maxOccurs="1"/>
     <element name="y" type="xsd:double" minOccurs="1" maxOccurs="1"/>
     <element name="width" type="xsd:double" minOccurs="1" maxOccurs="1"/>
     <element name="height" type="xsd:double" minOccurs="1" maxOccurs="1"/>
     <element name="comments" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="area-type" type="form:area-type" minOccurs="1" maxOccurs="1"/>
   </sequence>
</complexType>
<complexType name="area-with-string">
   <sequence>
     <element name="area" type="form:area" minOccurs="1" maxOccurs="1"/>
     <element name="string" type="xsd:string" minOccurs="1" maxOccurs="1"/>
   </sequence>
</complexType>
<complexType name="area-with-integer">
   <sequence>
     <element name="area" type="form:area" minOccurs="1" maxOccurs="1"/>
     <element name="integer" type="xsd:int" minOccurs="1" maxOccurs="1"/>
   </sequence>
</complexType>
<complexType name="area-with-range">
   <sequence>
     <element name="area" type="form:area" minOccurs="1" maxOccurs="1"/>
     <element name="lower" type="xsd:double" minOccurs="1" maxOccurs="1"/>
     <element name="upper" type="xsd:double" minOccurs="1" maxOccurs="1"/>
   </sequence>
</complexType>
<complexType name="areas">
   <sequence>
     <element name="areas" type="form:area" minOccurs="0" maxOccurs="unbounded"/>
     <element name="string-areas" type="form:area-with-string" minOccurs="0" maxOccurs="unbounded"/>
     <element name="integer-areas" type="form:area-with-integer" minOccurs="0" maxOccurs="unbounded"/>
     <element name="range-areas" type="form:area-with-range" minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
</complexType>
<complexType name="group">
   <sequence>
     <element name="name" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="areas" type="form:areas" minOccurs="1" maxOccurs="1"/>
     <element name="groups" type="form:group" minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
</complexType>
<complexType name="background">
   <sequence>
     <element name="name" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="md5" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="mime" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="num-page" type="xsd:int" minOccurs="1" maxOccurs="1"/>
   </sequence>
</complexType>
<complexType name="pattern-type">
   <sequence>
     <element name="print-once" type="xsd:boolean" minOccurs="1" maxOccurs="1"/>
     <element name="has-identifier" type="xsd:boolean" minOccurs="1" maxOccurs="1"/>
   </sequence>
</complexType>
<complexType name="page">
   <sequence>
     <element name="num-page" type="xsd:int" minOccurs="1" maxOccurs="1"/>
     <element name="format" type="form:format" minOccurs="1" maxOccurs="1"/>
     <element name="is-portrait" type="xsd:boolean" minOccurs="1" maxOccurs="1"/>
     <element name="background" type="form:background" minOccurs="1" maxOccurs="1"/>
     <element name="areas" type="form:areas" minOccurs="1" maxOccurs="1"/>
     <element name="groups" type="form:group" minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
</complexType>
<complexType name="document-new">
   <sequence>
     <element name="name" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="pattern-type" type="form:pattern-type" minOccurs="1" maxOccurs="1"/>
     <element name="form-pages" type="form:page" minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
</complexType>
<complexType name="document">
   <sequence>
     <element name="uuid" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="name" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="pattern-type" type="form:pattern-type" minOccurs="1" maxOccurs="1"/>
     <element name="form-pages" type="form:page" minOccurs="0" maxOccurs="unbounded"/>
   </sequence>
</complexType>
<complexType name="document-info">
   <sequence>
     <element name="uuid" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="name" type="xsd:string" minOccurs="1" maxOccurs="1"/>
     <element name="page-count" type="xsd:int" minOccurs="1" maxOccurs="1"/>
   </sequence>
</complexType>
<complexType name="Data">
   <sequence>
     <element ref="xop:Include" minOccurs="1" maxOccurs="1"/>
   </sequence>
     <attribute ref="xmime4:contentType" use="optional"/>
</complexType>
<complexType name="login-response">
   <sequence>
     <element name="result" type="generic:result" minOccurs="1" maxOccurs="1"/>
     <element name="session" type="xsd:string" minOccurs="1" maxOccurs="1"/>
   </sequence>
</complexType>

<element name="login" type="xsd:string"/>

<element name="password" type="xsd:string"/>

<element name="result" type="generic:result"/>

<element name="uuid" type="xsd:string"/>

<element name="session" type="xsd:string"/>

<element name="aform" type="form:document-new"/>

<element name="form" type="form:document"/>

<element name="md5" type="xsd:string"/>

<element name="data" type="form:Data"/>

<element name="exists" type="xsd:boolean"/>

<element name="backgrounds" type="form:background"/>

<element name="forms" type="form:document"/>

<element name="forms-info" type="form:document-info"/>
</schema>
</types>
<message name="login">
<part name="login" element="form:login"/>
<part name="password" element="form:password"/>
</message>
<message name="uuid-response">
<part name="result" element="form:result"/>
<part name="uuid" element="form:uuid"/>
</message>
<message name="quit">
<part name="session" element="form:session"/>
</message>
<message name="response">
<part name="result" element="form:result"/>
</message>
<message name="new-form">
<part name="session" element="form:session"/>
<part name="aform" element="form:aform"/>
</message>
<message name="free-form">
<part name="session" element="form:session"/>
<part name="uuid" element="form:uuid"/>
</message>
<message name="get-form">
<part name="session" element="form:session"/>
<part name="uuid" element="form:uuid"/>
</message>
<message name="document-response">
<part name="result" element="form:result"/>
<part name="form" element="form:form"/>
</message>
<message name="get-file">
<part name="session" element="form:session"/>
<part name="md5" element="form:md5"/>
</message>
<message name="data-response">
<part name="result" element="form:result"/>
<part name="data" element="form:data"/>
</message>
<message name="set-file">
<part name="session" element="form:session"/>
<part name="md5" element="form:md5"/>
<part name="data" element="form:data"/>
</message>
<message name="file-exists">
<part name="session" element="form:session"/>
<part name="md5" element="form:md5"/>
</message>
<message name="exists-response">
<part name="result" element="form:result"/>
<part name="exists" element="form:exists"/>
</message>
<message name="list-form-backgrounds">
<part name="session" element="form:session"/>
<part name="uuid" element="form:uuid"/>
</message>
<message name="list-backgrounds-response">
<part name="result" element="form:result"/>
<part name="backgrounds" element="form:backgrounds"/>
</message>
<message name="list-forms">
<part name="session" element="form:session"/>
</message>
<message name="list-forms-response">
<part name="result" element="form:result"/>
<part name="forms" element="form:forms"/>
</message>
<message name="list-forms-info">
<part name="session" element="form:session"/>
</message>
<message name="list-forms-info-response">
<part name="result" element="form:result"/>
<part name="forms-info" element="form:forms-info"/>
</message>
<portType name="formPortType">
<operation name="login">
<documentation>Service definition of function form__login</documentation>
<input message="tns:login"/>
<output message="tns:uuid-response"/>
</operation>
<operation name="quit">
<documentation>Service definition of function form__quit</documentation>
<input message="tns:quit"/>
<output message="tns:response"/>
</operation>
<operation name="new-form">
<documentation>Service definition of function form__new_form</documentation>
<input message="tns:new-form"/>
<output message="tns:uuid-response"/>
</operation>
<operation name="free-form">
<documentation>Service definition of function form__free_form</documentation>
<input message="tns:free-form"/>
<output message="tns:response"/>
</operation>
<operation name="get-form">
<documentation>Service definition of function form__get_form</documentation>
<input message="tns:get-form"/>
<output message="tns:document-response"/>
</operation>
<operation name="get-file">
<documentation>Service definition of function form__get_file</documentation>
<input message="tns:get-file"/>
<output message="tns:data-response"/>
</operation>
<operation name="set-file">
<documentation>Service definition of function form__set_file</documentation>
<input message="tns:set-file"/>
<output message="tns:response"/>
</operation>
<operation name="file-exists">
<documentation>Service definition of function form__file_exists</documentation>
<input message="tns:file-exists"/>
<output message="tns:exists-response"/>
</operation>
<operation name="list-form-backgrounds">
<documentation>Service definition of function form__list_form_backgrounds</documentation>
<input message="tns:list-form-backgrounds"/>
<output message="tns:list-backgrounds-response"/>
</operation>
<operation name="list-forms">
<documentation>Service definition of function form__list_forms</documentation>
<input message="tns:list-forms"/>
<output message="tns:list-forms-response"/>
</operation>
<operation name="list-forms-info">
<documentation>Service definition of function form__list_forms_info</documentation>
<input message="tns:list-forms-info"/>
<output message="tns:list-forms-info-response"/>
</operation>
</portType>
<binding name="form" type="tns:formPortType">
<SOAP:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="login">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="quit">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="new-form">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="free-form">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="get-form">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="get-file">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="set-file">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="file-exists">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="list-form-backgrounds">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="list-forms">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
<operation name="list-forms-info">
<SOAP:operation style="rpc"/>
<input>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</input>
<output>
     <SOAP:body parts="parameters" use="literal" namespace="form"/>
</output>
</operation>
</binding>
<service name="form">
<documentation>gSOAP 2.7.10 generated service definition</documentation>
<port name="form" binding="tns:form">
<SOAP:address location="https://enterprise-name-masked.com/cgi-bin/form.fcgi"/>
</port>
</service>
</definitions>And here, you can find the generated errors :
wsimport -s Sources -b http://www.w3.org/2004/08/xop/includ
e -b http://www.w3.org/2004/11/xmlmime form.wsdl
parsing WSDL...
[WARNING] src-resolve: Cannot resolve the name 'xmime4:contentType' to a(n) 'attribute declaration' component.
line 215 of file:/C:/Documents%20and%20Settings/Hopi_1/Mes%20documents/Alexandre/Recherche%20SOAP/WSImport/Test/Form/form.wsdl#types?schema2
[WARNING] s4s-elt-invalid-content.1: The content of 'Data' is invalid. Element 'attribute' is invalid, misplaced, or occurs too often.
line 215 of file:/C:/Documents%20and%20Settings/Hopi_1/Mes%20documents/Alexandre/Recherche%20SOAP/WSImport/Test/Form/form.wsdl#types?schema2
[WARNING] src-resolve.4.2: Error resolving component 'generic:result'. It was detected that 'generic:result' is in namespace 'generic', but components
from this namespace are not referenceable from schema document 'file:/C:/Documents%20and%20Settings/Hopi_1/Mes%20documents/Alexandre/Recherche%20SOAP
/WSImport/Test/Form/form.wsdl#types?schema2'. If this is the incorrect namespace, perhaps the prefix of 'generic:result' needs to be changed. If this
is the correct namespace, then an appropriate 'import' tag should be added to 'file:/C:/Documents%20and%20Settings/Hopi_1/Mes%20documents/Alexandre/Re
cherche%20SOAP/WSImport/Test/Form/form.wsdl#types?schema2'.
line 230 of file:/C:/Documents%20and%20Settings/Hopi_1/Mes%20documents/Alexandre/Recherche%20SOAP/WSImport/Test/Form/form.wsdl#types?schema2
[WARNING] src-resolve: Cannot resolve the name 'xop:Include' to a(n) 'element declaration' component.
line 213 of file:/C:/Documents%20and%20Settings/Hopi_1/Mes%20documents/Alexandre/Recherche%20SOAP/WSImport/Test/Form/form.wsdl#types?schema2
[WARNING] Ignoring SOAP port "form": it uses non-standard SOAP 1.2 binding.
You must specify the "-extension" option to use this binding.
line 533 of file:/C:/Documents%20and%20Settings/Hopi_1/Mes%20documents/Alexandre/Recherche%20SOAP/WSImport/Test/Form/form.wsdl
[WARNING] Service "form" does not contain any usable ports. try running wsimport with -extension switch.
line 531 of file:/C:/Documents%20and%20Settings/Hopi_1/Mes%20documents/Alexandre/Recherche%20SOAP/WSImport/Test/Form/form.wsdl
generating code...
compiling code...Could you tell me how to correctly generate my classes in this case ?
Thank you.
Edited by: morphet on May 30, 2008 6:12 AM

Alchemista,
Not sure if you were able to solve your problem..but I was trying to do exactly what you were trying to do.. access a datasource from a simple Java client. However, you cannot do so by simply writing the Java class and running it. The simple Java client has to be deployed as a J2EE Application Client. The following tutorial shows how to create a J2EE Application Client using the non-J2EE Java class you have written.
http://developer.java.sun.com/developer/technicalArticles/J2EE/appclient
The article talks about accessing EJBs from a J2EE App. Client.. but since you only want to access the DataSource, just skip all the screens until it asks you to register the JNDI DataSource resources...
Let me know if you have any questions. You can email me at [email protected]
I hope this helps.

EJB 3.1new instance of stateless session bean not created on new invocation

I am using Netbeans 6.8 bundle that comes with JAVA EE 6. I have created a web application then created restful web services and then created few stateless session beans (with local interfaces) that are invoked from restful web services. From the browser, when I call the url with get method, restful web services are being invoked and they in turn calls stateless session beans and does the appropriate business logic. While testing, I observed that for every new url call from the browser, the same bean is being invoked. I tested this by adding a instance variable vector and adding one item ('test") to the vector in bean's method. My understanding is that on every bean's method invocation the vector should have only one item. However, the vector is growing with many "test" items. I am literally confused, not sure this is the way it is supposed to work. I tried to invoke bean's method from restful web service by using both dependency injection and jndi look up, both instances the vector is growing with many "test" items.
I would really appreciate if some body gives me more insight.

I appreciate your answers. There is a strong reason for posting this question. Basically, I am using JPA and using stateless session beans to invoke database calls. In the bean I am using the following code for entity manager.
@PersistenceContext(unitName = "AsgProtocolServerPU")
private EntityManager em;
I have noticed very strange scenario while getting records. From the application, I have obtained few records of a table. Then, I manually deleted few records from the table. Very strangely, I have obtained the deleted records during my next call to bean. After 2 hours, I tested the same and did not get those records. This is not consistent.
I am totally confused. I am just wondering this is happening because I made beans local (not remote) and placed them in the web application (Java EE6 allows this). I am not sure whether this is JPA related issue or beans issue.

Efficiency Question: Simple Java DC vs Used WD Component

Hello guys,
The scenario is - I want to call a function that returns a FileInputStream object so I can process it on my WD view. I can think of two approaches - one is to simply write a simple Java DC that does so and just use it as a used DC so I can call the functionality from there. Or create another WD DC that exposes the value (as binary) via component interface.
I'm leaning on the simple Java DC approach - its easier to create. But I'm just curious on what would be the Pro-side (if there's any) if I use the WD Component interface approach? Is there a plus for the efficiency? (Though I doubt) Or is it just a 'best/recommended practice' approach?
Thanks!
Regards,
Jan

Hi Jan
>one is to simply write a simple Java DC that does so and just use it as a used DC so I can call the functionality from there
Implemented Java API for the purpose mentioned in your question is the right way, I think. The Java API can be even located in the same WebDynpro DC as your WebDynpro components. There is not strongly necessity to put it into separate Java DC.
>Or create another WD DC that exposes the value (as binary) via component interface
You should not do this because in general WD components' purpose is UI, not API. Implementing WD component without any UI, but with some component interface has very-very restricted use cases. Such WD component shall only be a choice in the cases when the API is WebDynpro based and if you have to strongly use WebDynpro Runtime API in order to implement your own API.
If your API does not require WebDynpro Runtime API invocations or anything else related to WebDynpro then your choice is simple Java API.
>But I'm just curious on what would be the Pro-side (if there's any) if I use the WD Component interface approach? Is there a plus for the efficiency?
No. Performance will be better in simple Java API then in WebDynpro component interface. The reason is the API will not pass thought heavy WebDynpro engine.
BR, Siarhei

A question about concurrency and static getter methods

Hello
I have a class with some static methods. they just return a reference and doesnt apply any changes.
something like this:
public class FieldMapper {
        private static Map<Class,Map<String,String>> fieldMap = new HashMap<Class,Map<String,String>>();
        public static getFields(Class clazz){
              return fieldMap.get(clazz);
}my question is, let's consider many users connect to my server and each has its own session, now assume one user want to use FieldMapper.getFields(User.class) and another is going to call FieldMapper.getFields(Employee.class) at same time or a bit milli seconds after, and this method is not synchronized, is there any conflict in calling the method? would this method return wrong reference to the first invocation?
in genereal, may the concurrency make problem on reading resources? or just on changing resources?
Thank you very much in advance.

To publish an object safely, both the reference to the object and the object's state must be made visible to other threads at the same time. A properly constructed object can be safely published by:
Initializing an object reference from a static initializer;
Storing a reference to it into a volatile field or AtomicReference;
Storing a reference to it into a final field of a properly constructed object; or
Storing a reference to it into a field that is properly guarded by a lock. The internal synchronization in thread-safe collections means that placing an object in a thread-safe collection, such as a Vector or synchronizedList, fulfills the last of these requirements. If thread A places object X in a thread-safe collection and thread B subsequently retrieves it, B is guaranteed to see the state of X as A left it, even though the application code that hands X off in this manner has no explicit synchronization.
Now in the case you have specified you are using HashMap. Which is not designed to be threadsafe as opposed to HashTable or concurrentHashMap. In such a case I would advise against using this. The concurrency problem is caused by race conditions on mutable objects, whether it is reading or writing. If it is mutable, it is susceptible to race conditions. IMHO
&spades;

Oracle to File, filename and order by question

Hello
I am writing a simple interface, source is an oracle table and destination is a flat file.
I have two questions:
1) the file name should be in the form allocation_ddmmyyyy.txt, where ddmmyyyy is the current date. which is the best way to accomplish this?
2) the file should be sorted with some criteria, which could be easily achieved with an order by clause in the source datastore, but looks this is not possible. How could I do this?

Hello.
My Idea follows
(1) You create ODI Variables,then you may set ODI Variables to resource Name of data-store.
detail Example (i) you create the ODI-Variable "FILENAME" to GLOBAL
detail Example (ii) you set #FILENAME to resource name of data-store.
detail Example (iii) startscen.sh SCENARIONAME VERSION CONTEXT GLOBAL.FILENAME=allocation_ddmmyyyy.txt
(in other method, invocation API, ODI Public Web Services via Oracle WebServiceProxy API/BPEL PartnerLink invoke)
(2) you customise IKM. you add "order by criteria" to the command "Insert new rows" 's SQL.
If criteria is not const, you should use ODI Variables or Java Variables.
othewise,you may use harcord literal.
Please challenge my idea.
Message was edited by:
futokiyo

Best practice question for implementing a custom component

I'm implementing a custom component which renders multiple <input type="text" .../> controls as part of it. The examples I've seen that do something similar use the ResponseWriter to generate the markup "by hand" like:
     writer.startElement("input", component);
     writer.writeAttribute("type", "text", null);
     writer.writeAttribute("id", "foo", null);
     writer.writeAttribute("name", "foo", null);
     writer.writeAttribute("value", "hello", null);
     writer.writeAttribute("size", "20", null);
     writer.endElement("input");
I don't know about anyone else, but I HATE having to write code that manufactures this stuff - seems to me that there are already classes that do this, so why not just use those? For example, the above could be replaced with:
     HtmlInputText textField = new HtmlInputText();
     textField.setId("foo");
     textField.setValue("hello");
     textField.setSize(20);
     // just to be safe, invoke both encodeBegin() and encodeEnd(),
     // though it seems like encodeEnd() actually does the work in this case,
     // but who knows if they might change it at some point
     textField.encodeBegin(context);
     textField.encodeEnd(context);
So my question is, why does everyone seem to favor the former over the latter? Why not leverage objects that already do the (encoding) work for you?

Got it!
You JSP should have this:
<h:panelGroup styleClass="jspPanel" id="jspPanel1"></h:panelGroup>
And your code page ValueChangeListener/ActionListner should have this:
          if (findComponent(getForm1(),"myOutputText") == null)
               FacesContext facesCtx = FacesContext.getCurrentInstance();
               System.out.println("Adding component");
               HtmlOutputText output =
                    (HtmlOutputText) facesCtx.getApplication().createComponent(
                         HtmlOutputText.COMPONENT_TYPE);
               output.setId("myOutputText");
               output.setValue("It works");
               getJspPanel1().getChildren().add(output);
               System.out.println("Done");
               DebugUtil.printTree(FacesContext.getCurrentInstance().getViewRoot(),System.out);
          else
               System.out.println("component already added");
I just have to figure out this IOException on the closed stream - probably has to do with [immidiate="true"].
Thanks.
[9/15/04 13:05:53:505 EDT] 6e436e43 SystemErr R java.io.IOException: Stream closed
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at java.lang.Throwable.<init>(Throwable.java)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at java.lang.Throwable.<init>(Throwable.java)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at org.apache.jasper.runtime.JspWriterImpl.ensureOpen(JspWriterImpl.java:294)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:424)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:452)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at com.ibm.faces.component.UIJspPanel$ChildrenListEx.add(UIJspPanel.java:114)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at pagecode.admin.Test.handleListbox1ValueChange(Test.java)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at java.lang.reflect.AccessibleObject.invokeImpl(Native Method)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at java.lang.reflect.AccessibleObject.invokeV(AccessibleObject.java:199)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at java.lang.reflect.Method.invoke(Method.java:252)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at com.sun.faces.el.MethodBindingImpl.invoke(MethodBindingImpl.java:126)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at javax.faces.component.UIInput.broadcast(UIInput.java:492)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:284)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at javax.faces.component.UIViewRoot.processDecodes(UIViewRoot.java:342)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at com.sun.faces.lifecycle.ApplyRequestValuesPhase.execute(ApplyRequestValuesPhase.java:79)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:90)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at javax.faces.webapp.FacesServlet.service(FacesServlet.java:197)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
[9/15/04 13:05:53:536 EDT] 6e436e43 SystemErr R      at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
[9/15/04 13:05:53:552 EDT] 6e436e43 SystemErr R      at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:201)
[9/15/04 13:05:53:552 EDT] 6e436e43 SystemErr R      at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
[9/15/04 13:05:53:552 EDT] 6e436e43 SystemErr R      at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
[9/15/04 13:05:53:567 EDT] 6e436e43 SystemErr R      at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
[9/15/04 13:05:53:567 EDT] 6e436e43 SystemErr R      at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
[9/15/04 13:05:53:567 EDT] 6e436e43 SystemErr R      at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
[9/15/04 13:05:53:567 EDT] 6e436e43 SystemErr R      at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:435)
[9/15/04 13:05:53:567 EDT] 6e436e43 SystemErr R      at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
[9/15/04 13:05:56:146 EDT] 6e436e43 SystemOut O Done

Error in invocating the service

I have a problem in writing a Java program and calling the service using invocation API. The service is a very simple one, which has one input parameter (String) and one output parameter (XML). When I ran the Java program, I got the following error:
ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error.
at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapAxisDispatcher.doSend(SoapAxisDispatche r.java:102)
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:57)
at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
at adobe.lc.sdk.UploadForm.invokeMyService(UploadForm.java:75)
at adobe.lc.sdk.UploadForm.main(UploadForm.java:55)
Caused by: rO0ABXNyAB1vcmcuYXBhY2hlLnNvYXAuU09BUEV4Y2VwdGlvbh5POjjsHQpiAgACTAAJZmF1bHRDb2RldAASTGphd mEvbGFuZy9TdHJpbmc7TAAPdGFyZ2V0RXhjZXB0aW9udAAVTGphdmEvbGFuZy9UaHJvd2FibGU7eHIAE2phdmEubGF uZy5FeGNlcHRpb27Q/R8+GjscxAIAAHhyABNqYXZhLmxhbmcuVGhyb3dhYmxl1cY1Jzl3uMsDAANMAAVjYXVzZXEAf gACTAANZGV0YWlsTWVzc2FnZXEAfgABWwAKc3RhY2tUcmFjZXQAHltMamF2YS9sYW5nL1N0YWNrVHJhY2VFbGVtZW5 0O3hwcQB+AAZ0AEdBRE1DMDAxMUU6IFRoZSBTT0FQIHJlbW90ZSBwcm9jZWR1cmUgY2FsbCAoUlBDKSBjYW5ub3QgY mUgdW5tYXJzaGFsbGVkLnVyAB5bTGphdmEubGFuZy5TdGFja1RyYWNlRWxlbWVudDsCRio8PP0iOQIAAHhwAAAABnN yABtqYXZhLmxhbmcuU3RhY2tUcmFjZUVsZW1lbnRhCcWaJjbdhQIABEkACmxpbmVOdW1iZXJMAA5kZWNsYXJpbmdDb GFzc3EAfgABTAAIZmlsZU5hbWVxAH4AAUwACm1ldGhvZE5hbWVxAH4AAXhwAAAAsnQALmNvbS5pYm0ud3MubWFuYWd lbWVudC5jb25uZWN0b3Iuc29hcC5TT0FQVXRpbHN0AA5TT0FQVXRpbHMuamF2YXQAD2V4dHJhY3RTb2FwQ2FsbHNxA H4ACgAAAHB0ADJjb20uaWJtLndzLm1hbmFnZW1lbnQuY29ubmVjdG9yLnNvYXAuU09BUENvbm5lY3RvcnQAElNPQVB Db25uZWN0b3IuamF2YXQAB3NlcnZpY2VzcQB+AAoAAAA3dAAzY29tLmlibS53cy5tYW5hZ2VtZW50LmNvbm5lY3Rvc i5zb2FwLlNPQVBDb25uZWN0aW9udAATU09BUENvbm5lY3Rpb24uamF2YXQADWhhbmRsZVJlcXVlc3RzcQB+AAoAAAK odAAeY29tLmlibS53cy5odHRwLkh0dHBDb25uZWN0aW9udAATSHR0cENvbm5lY3Rpb24uamF2YXQAFHJlYWRBbmRIY W5kbGVSZXF1ZXN0c3EAfgAKAAAB5HQAHmNvbS5pYm0ud3MuaHR0cC5IdHRwQ29ubmVjdGlvbnQAE0h0dHBDb25uZWN 0aW9uLmphdmF0AANydW5zcQB+AAoAAAW9dAAhY29tLmlibS53cy51dGlsLlRocmVhZFBvb2wkV29ya2VydAAPVGhyZ WFkUG9vbC5qYXZhdAADcnVueHQAGVNPQVAtRU5WOlNlcnZlci5FeGNlcHRpb25zcgAiamF2YS5sYW5nLklsbGVnYWx Bcmd1bWVudEV4Y2VwdGlvbrWJc9N9Zo+8AgAAeHIAGmphdmEubGFuZy5SdW50aW1lRXhjZXB0aW9unl8GRwo0g+UCA AB4cQB+AANxAH4AJnQIrGNvbS5hZG9iZS5pZHAuZHNjLnByb3ZpZGVyLmltcGwuZWpiLkVqYlJlcXVlc3RIb2xkZXI KU2VydmVyIHN0YWNrIHRyYWNlCkpNWFRyYW5zZm9ybUV4Y2VwdGlvbiBqYXZhLmxhbmcuQ2xhc3NOb3RGb3VuZEV4Y 2VwdGlvbjogY29tLmFkb2JlLmlkcC5kc2MucHJvdmlkZXIuaW1wbC5lamIuRWpiUmVxdWVzdEhvbGRlcgoJYXQgamF 2YS5uZXQuVVJMQ2xhc3NMb2FkZXIuZmluZENsYXNzKFVSTENsYXNzTG9hZGVyLmphdmE6NDkyKQoJYXQgY29tLmlib S53cy5ib290c3RyYXAuRXh0Q2xhc3NMb2FkZXIuZmluZENsYXNzKEV4dENsYXNzTG9hZGVyLmphdmE6MTMyKQoJYXQ gamF2YS5sYW5nLkNsYXNzTG9hZGVyLmxvYWRDbGFzcyhDbGFzc0xvYWRlci5qYXZhOjYwMykKCWF0IGNvbS5pYm0ud 3MuYm9vdHN0cmFwLkV4dENsYXNzTG9hZGVyLmxvYWRDbGFzcyhFeHRDbGFzc0xvYWRlci5qYXZhOjg3KQoJYXQgamF 2YS5sYW5nLkNsYXNzTG9hZGVyLmxvYWRDbGFzcyhDbGFzc0xvYWRlci5qYXZhOjU2OSkKCWF0IGNvbS5pYm0ud3Mub WFuYWdlbWVudC5jb25uZWN0b3IuaW50ZXJvcC5KTVhDbGFzc0xvYWRlci5sb2FkSk1YQ2xhc3MoSk1YQ2xhc3NMb2F kZXIuamF2YToyMTEpCglhdCBjb20uaWJtLndzLm1hbmFnZW1lbnQuY29ubmVjdG9yLmludGVyb3AuSk1YQ2xhc3NMb 2FkZXIubG9hZE9sZEpNWENsYXNzKEpNWENsYXNzTG9hZGVyLmphdmE6MTY1KQoJYXQgY29tLmlibS53cy5tYW5hZ2V tZW50LmNvbm5lY3Rvci5pbnRlcm9wLkpNWENsYXNzTG9hZGVyLmxvYWRDbGFzcyhKTVhDbGFzc0xvYWRlci5qYXZhO jEwMikKCWF0IGNvbS5pYm0ud3MubWFuYWdlbWVudC5jb25uZWN0b3IuaW50ZXJvcC5KTVhPYmplY3RJbnB1dFN0cmV hbS5yZXNvbHZlQ2xhc3MoSk1YT2JqZWN0SW5wdXRTdHJlYW0uamF2YTo5NSkKCWF0IGphdmEuaW8uT2JqZWN0SW5wd XRTdHJlYW0ucmVhZE5vblByb3h5RGVzYyhPYmplY3RJbnB1dFN0cmVhbS5qYXZhOjE1NjMpCglhdCBqYXZhLmlvLk9 iamVjdElucHV0U3RyZWFtLnJlYWRDbGFzc0Rlc2MoT2JqZWN0SW5wdXRTdHJlYW0uamF2YToxNDg1KQoJYXQgamF2Y S5pby5PYmplY3RJbnB1dFN0cmVhbS5yZWFkT3JkaW5hcnlPYmplY3QoT2JqZWN0SW5wdXRTdHJlYW0uamF2YToxNzE 4KQoJYXQgamF2YS5pby5PYmplY3RJbnB1dFN0cmVhbS5yZWFkT2JqZWN0MChPYmplY3RJbnB1dFN0cmVhbS5qYXZhO jEzMjQpCglhdCBqYXZhLmlvLk9iamVjdElucHV0U3RyZWFtLnJlYWRPYmplY3QoT2JqZWN0SW5wdXRTdHJlYW0uamF 2YTozNjIpCglh

at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:10 87)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch( Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapAxisDispatcher.doSend(SoapAxisDispatche r.java:100)
... 4 more
The source code is:
public class UploadForm
public static void main(String[] args)
try
Properties connectionProps = new Properties();
connectionProps.setProperty("DSC_DEFAULT_SOAP_ENDPOINT", "http://myserver:40005");
connectionProps.setProperty("DSC_TRANSPORT_PROTOCOL", ServiceClientFactoryProperties.DSC_SOAP_PROTOCOL);
connectionProps.setProperty("DSC_SERVER_TYPE", ServiceClientFactoryProperties.DSC_WEBSPHERE_SERVER_TYPE);
connectionProps.setProperty("DSC_CREDENTIAL_USERNAME", "administrator");
connectionProps.setProperty("DSC_CREDENTIAL_PASSWORD", "password");
ServiceClientFactory myFactory = ServiceClientFactory.createInstance(connectionProps);
invokeMyService ( myFactory );
catch (Exception e)
e.printStackTrace();
private static void invokeMyService ( ServiceClientFactory myFactory ) throws Exception
ServiceClient serviceClient = myFactory.getServiceClient();
HashMap parameters = new HashMap ( );
parameters.put ( "confirmationNumber", "000000000012" );
InvocationRequest request = myFactory.createInvocationRequest( "QueryForm", "invoke", parameters, true );
InvocationResponse response = serviceClient.invoke( request );
Document xmlDocument = (Document) response.getOutputParameter ( "xmlDocument" );
The question is, I don't know if this is a client problem or on the server side. If it's the process problem, how can I tell if my process is working?

Question about SOAPBody # extractContentAsDocument()

Hi java experts,
I have a question about a method SOAPBody # extractContentAsDocument().
According to its javadoc,
http://docs.oracle.com/javase/6/docs/api/javax/xml/soap/SOAPBody.html#extractContentAsDocument%28%29
when you use this method, "The child SOAPElement is removed as part of the process",
but when I use this method to get a SOAPBody's full content as XML, with several kind of JVM,
it seems like I can perfectly retrieve its all children elements without any loss.
So I can't get what the javadoc is meaning by "The child SOAPElement is removed".
Does anyone know anything about this?
Thanks and regards

It seems that original SOAPBody element is erased after the method invocation. To restore it, you need to call the .addDocument(Document doc) method passing the original or changed body as Document.

GSOAP invocation question

Similar Messages

Maybe you are looking for