Web service XML String

Hello,
I have javax.jws web service, I have method which return Document or String as well formed XML. And I need to my web service return this String as XML.
@WebMethod(operationName = "operation")
public String operation() {
XMLvystup pom = new XMLvystup();
pom.nulujHladane();
pom.setHladane(7, "Bc");
pom.setHladane(5, "MKP");
String vysledok = pom.getXml(pom.getHladane());
System.out.println(vysledok);
return vysledok;
Please help.

Similar Messages

Print label image in GIF format returned by Web Service XML string.

Hi All
I have extremely interesting situations and have been struggling with this for a past week. I have been looking everywhere but nobody seems to have an answer. This is my last resort.
Detail -
I am consuming UPS web service from my ABAP program. Everything works fine until I have to print UPS label. The label image is returned to my ABAP program via XML by the UPS reply transaction as a GIF image.
When I download this image to my PC I can see it and print it, but for the love of god I cannot print this image from my ABAP program. The GIF image is passed to me as a binary data string it looks like bunch on numbers - (2133FFDGFGFGFHHu2026..) very long string about 89800 bites. I cannot use smart forms since smart form requires to have graphic stored in SAP before smart form print, so this is not possible. I need help figuring out how print GIF image form ABAP or any other SAP method dynamically. Any ideas are extremely appreciated. I am just puzzled that I cannot find any info on something like this. I cannot be the first one who needs to print GIF image in SAP.

Hi all,
I understand this thread was started long back. But wanted to share this solution since I see the same question in many forums without any particular conclusive answer. So the steps I am explaining here, if it helps in some way, I will be really happy. I won't say this is the perfect solution. But it definitely helps us to print the images. This solution is infact implemented successfully in my client place & works fine.
And please note there may be better solutions definitely available in ECC6 or other higher releases. This solution is mainly for lesser versions, for people don't have ADOBE forms or other special classes.
Important thing here is binary string is converted to postscript here. So you need to make sure your printer supports postscripts. (Ofcourse, if anybody is interested, they can do their R&D on PCL conversion in the same way...and pls let me know). Once the binary data is converted to postscript, we are going to write it in the binary spool. so you will still see junk characters (or numberssss) in spool. But when you print it in postscript printer , it should work.
First step, assuming you have your binary data ready from tiff or pdf based on your requirement.
Basically below compress/decompress function modules convert the binary data from lt_bin (structure TBL1024) to target_tab (structure SOLIX). From Raw 1024 to Raw 255
DATA: aux_tab LIKE soli OCCURS 10. - temp table
Compress table
              CALL FUNCTION 'TABLE_COMPRESS'
                TABLES
                  in             = lt_bin
                  out            = aux_tab
                EXCEPTIONS
                  compress_error = 1
                  OTHERS         = 2.
Decompress table
              CALL FUNCTION 'TABLE_DECOMPRESS'
                TABLES
                  in                   = aux_tab
                  out                  = target_tab
                EXCEPTIONS
                  compress_error       = 1
                  table_not_compressed = 2
                  OTHERS               = 3.
In my case, since I have to get it from archived data using function module, ARCHIV_GET_TABLE which gives RAW 1024, above conversion was necessary.
Second step: Application server temporary files for tif/postscript files.
We need two file names here for tif file & for converted postscript file. Please keep in mind, if you are running it in background, user should have authorization to read/write/delete this file.
Logical file name just to make sure the file name is maintainable. Hard code the file name if you don't want to use logical file name.
              CALL FUNCTION 'FILE_GET_NAME'
                EXPORTING
                  logical_filename = 'ABCD'
                  parameter_1      = l_title
                  parameter_2      = sy-datum
                  parameter_3      = sy-uzeit
                IMPORTING
                  file_name        = lv_file_name_init
                EXCEPTIONS
                  file_not_found   = 1
                  OTHERS           = 2.
              IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
              ENDIF.
Now concatenate with the different extensions to get two different files.
              CONCATENATE lv_file_name_init '.tif' INTO lv_file_name_tif.
              CONCATENATE lv_file_name_init '.ps' INTO lv_file_name_ps.
Third step: Write the target_tab to tif file.
Open dataset for writing the tif file.
              OPEN DATASET lv_file_name_tif FOR OUTPUT IN BINARY MODE.
              IF NOT sy-subrc IS INITIAL.
                RAISE open_failed.
              ELSE.
                LOOP AT target_tab INTO w_target_tab.
                  CATCH SYSTEM-EXCEPTIONS dataset_write_error = 1
                                          OTHERS = 4.
                    TRANSFER w_target_tab TO lv_file_name_tif.
                  ENDCATCH.
                  IF NOT sy-subrc IS INITIAL.
                    RAISE write_failed.
                  ENDIF.
                ENDLOOP.
                CATCH SYSTEM-EXCEPTIONS dataset_cant_close = 1
                                        OTHERS = 4.
                  CLOSE DATASET lv_file_name_tif.
                ENDCATCH.
              ENDIF.
Fourth Step: Convert the tiff file to postscript file.
This is the critical step. Create an external command (SM49/SM69) for this conversion. In this example, Z_TIFF2PS is created. Infact, I did get help from our office basis gurus in this. so I don't have the exact code of this unix script. You can refer the below link or may get some help from unix gurus.
http://linux.about.com/library/cmd/blcmdl1_tiff2ps.htm
Since my external command needs .ps file name and .tif file name as input, concatenate it & pass it as additional parameter. Command will take care of the conversion & will generate the .ps file.
   CONCATENATE lv_file_name_ps lv_file_name_tif INTO lw_add SEPARATED BY space.
Call the external command with the file paths.
              CALL FUNCTION 'SXPG_COMMAND_EXECUTE'
                EXPORTING
                  commandname           = 'Command name'
                  additional_parameters = lw_add
                TABLES
                  exec_protocol         = t_comtab.
Fifth step: Read the converted ps file and convert it to RAW 255.
DATA:lw_content TYPE xstring.
Open dataset for reading the postscript (ps) file
              OPEN DATASET lv_file_name_ps FOR INPUT IN BINARY MODE.
Check whether the file is opened successfully
              IF NOT sy-subrc IS INITIAL.
                RAISE open_failed.
              ELSE.
                READ DATASET lv_file_name_ps INTO lw_content.
              ENDIF.
Close the dataset
              CATCH SYSTEM-EXCEPTIONS dataset_cant_close = 1
                                      OTHERS = 4.
                CLOSE DATASET lv_file_name_ps.
              ENDCATCH.
Make sure you delete the temporary files so that you can reuse the same names again & again for next conversions.
              DELETE DATASET lv_file_name_tif.
              DELETE DATASET lv_file_name_ps.
Convert the postscript file to RAW 255
              REFRESH target_tab.
              CALL FUNCTION 'SCMS_XSTRING_TO_BINARY'
                EXPORTING
                  buffer     = lw_content
                TABLES
                  binary_tab = target_tab.
Sixth step: Write the postscript data to binary spool by passing the correct print parameters.
              IF NOT target_tab[] IS INITIAL.
                PERFORM spo_job_open_cust USING l_device
                                                     l_title
                                                     l_handle
                                                     l_spoolid
                                                     lw_nast.
                LOOP AT target_tab INTO w_target_tab.
                  PERFORM spo_job_write(saplstxw) USING l_handle
                                                        w_target_tab
                                                      l_linewidth.
                ENDLOOP.
                PERFORM spo_job_close(saplstxw) USING l_handle
                                                      l_pages.
                IF sy-subrc EQ 0.
                  MESSAGE i014 WITH
                   'Spools for'(019) lw_final-vbeln
               'created successfully.Check transaction SP01'(020).
                ENDIF.
              ENDIF.
Please note the parameters when calling function module RSPO_SR_OPEN. Change the print parameters according to your requirement. This is very important.
FORM spo_job_open_cust USING value(device) LIKE tsp03-padest
                        value(title) LIKE tsp01-rqtitle
                        handle LIKE sy-tabix
                        spoolid LIKE tsp01-rqident
                        lw_nast TYPE nast.
DATA: layout LIKE tsp01-rqpaper,
        doctype LIKE tsp01-rqdoctype.
doctype = 'BIN'.
layout = 'G_RAW'.
CALL FUNCTION 'RSPO_SR_OPEN'
      EXPORTING
        dest                   = device "Printer name
    LDEST                  =
        layout                 = layout
    NAME                   =
        suffix1                = 'PDF'
    SUFFIX2                =
    COPIES                 =
     prio                   = '5'
       immediate_print        = 'X'
immediate_print        = lw_nast-dimme
        auto_delete            = ' '
        titleline              = title
    RECEIVER               =
    DIVISION               =
    AUTHORITY              =
    POSNAME                =
    ACTTIME                =
    LIFETIME               = '8'
        append                 = ' '
        coverpage              = ' '
    CODEPAGE               =
        doctype                = doctype
    ARCHMODE               =
    ARCHPARAMS             =
    TELELAND               =
    TELENUM                =
    TELENUME               =
      IMPORTING
        handle                 = handle
        spoolid                = spoolid
      EXCEPTIONS
        device_missing         = 1
        name_twice             = 2
        no_such_device         = 3
        operation_failed       = 4.
CASE sy-subrc.
    WHEN 0.
      PERFORM msg_v1(saplstxw) USING 'S'
                       'RSPO_SR_OPEN o.k., Spoolauftrag $'(128)
                       spoolid.
      sy-subrc = 0.
    WHEN 1.
      PERFORM msg_v1(saplstxw) USING 'E'
                           'RSPO_SR_OPEN Fehler: Gerät fehlt'(129)
                           space.
      sy-subrc = 1.
    WHEN 2.
      PERFORM msg_v1(saplstxw) USING 'E'
                         'RSPO_SR_OPEN Fehler: Ungültiges Gerät $'(130)
                         device.
      sy-subrc = 1.
    WHEN OTHERS.
      PERFORM msg_v1(saplstxw) USING 'E'
                           'RSPO_SR_OPEN Fehler: $'(131)
                           sy-subrc.
      sy-subrc = 1.
ENDCASE.
ENDFORM.                    "spo_job_open_cust
Thats it. We are done. If you open the spool, still you will see numbers/junk characters. if you print it in postscript printer, it will be printed correctly. If you try to print it PCL, you will get lot of pages wasted since it will print all junk characters. So please make sure you use postscript printer for this.
Extra step for mails (if interested):
Mails should work fine without any extra conversion/external command since it will be opened again using windows. So after the first step (compress & decompress)
Create attachment notification for each attachment
              objpack-transf_bin = 'X'.
              objpack-head_start = 1.
              objpack-head_num   = 1.
              objpack-body_start = lv_num + 1.
              DESCRIBE TABLE lt_target_tab LINES objpack-body_num.
              objpack-doc_size   = objpack-body_num * 255.
              objpack-body_num = lv_num + objpack-body_num.
              lv_num = objpack-body_num.
              objpack-doc_type   = 'TIF'.
              CONCATENATE 'Attachment_' l_object_id INTO objpack-obj_descr.
              reclist-receiver = l_email.
              reclist-rec_type = 'U'.
              reclist-express = 'X'.
              APPEND reclist.
              CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
                EXPORTING
                  document_data              = docdata
                  put_in_outbox              = 'X'
                  commit_work                = 'X'
                TABLES
                  packing_list               = objpack
                  contents_txt               = objtxt
                  contents_hex               = target_tab
                  receivers                  = reclist
                EXCEPTIONS
                  too_many_receivers         = 1
                  document_not_sent          = 2
                  document_type_not_exist    = 3
                  operation_no_authorization = 4
                  parameter_error            = 5
                  x_error                    = 6
                  enqueue_error              = 7
                  OTHERS                     = 8.
              IF sy-subrc <> 0.
                RAISE email_not_sent.
              ENDIF.
              COMMIT WORK.
Hope this helps. I am sure this (print/email both) can be improved further by removing some conversions/by using some other methods.Please check & let me know if you have any such suggestions or any other comments.
Regards,
Gokul
Edited by: Gokul R Nair on Nov 16, 2011 2:59 AM</pre>
Edited by: Gokul R Nair on Nov 16, 2011 3:01 AM
Edited by: Gokul R Nair on Nov 16, 2011 3:15 AM

Print label image in PDF format returned by Web Service XML string.

Hi Experts,
I have a scenario, where I am sending delivery details through IDOC and receives some labels to print in response from SAP PI. I am planning to print those labels from the inbound proxy.Is there any standard function module to print? I have gone through some function modules but no luck..could anybody help me on this? Give me some sample code..

Hi Experts,
I have a scenario, where I am sending delivery details through IDOC and receives some labels to print in response from SAP PI. I am planning to print those labels from the inbound proxy.Is there any standard function module to print? I have gone through some function modules but no luck..could anybody help me on this? Give me some sample code..

Fault elt in web-services.xml NOT WORKING

We are trying to capture an invalid message coming into our service before our
service actually processes it. Per WLS7 documentation, it provides the ability
to add a <fault> elt under the <params> elt in web-services.xml to perform that.
Here's how the operations portion of our web-services.xml looks like:
<operations>
<operation method="echo(java.lang.String)" component="jcComp0" name="echo"
handler-chain="diagnosticChain">
<params>
<param location="body" class-name="java.lang.String" style="in" name="echoString"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:string">
</param>
<return-param location="body" class-name="java.lang.String" name="Result"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:string">
</return-param>
<fault name="InvalidMessageException" class-name="com.gmacfs.routeone.diagnostic.InvalidMessageException"/>
</params>
</operation>
</operations>
However, when we tried doing that, we got a BIG set of exception while trying
to build our client. It looks as follows:
client:
[clientgen] Generating client jar for diagnostic.ear ...
[clientgen] Could not read Web Service deployment descriptor
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.java:112)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
[clientgen] --- Nested Exception ---
[clientgen] Could not read Web Service deployment descriptor
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EARClientGen.java:332)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.java:110)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
[clientgen] --- Nested Exception ---
[clientgen] weblogic.webservice.dd.DDProcessingException: Could not find required
attribute "type" for element <fault> (Line 28, Column 8)
[clientgen] at weblogic.webservice.dd.ParsingHelper.getRequiredAttribute(ParsingHelper.java:287)
[clientgen] at weblogic.webservice.dd.DDLoader.processFaultElement(DDLoader.java:1195)
[clientgen] at weblogic.webservice.dd.DDLoader.processFaultElements(DDLoader.java:1166)
[clientgen] at weblogic.webservice.dd.DDLoader.processParamsElement(DDLoader.java:1004)
[clientgen] at weblogic.webservice.dd.DDLoader.processOperationElement(DDLoader.java:977)
[clientgen] at weblogic.webservice.dd.DDLoader.processOperationElements(DDLoader.java:853)
[clientgen] at weblogic.webservice.dd.DDLoader.processOperationsElement(DDLoader.java:841)
[clientgen] at weblogic.webservice.dd.DDLoader.processWebServiceElement(DDLoader.java:378)
[clientgen] at weblogic.webservice.dd.DDLoader.processWebServiceElements(DDLoader.java:283)
[clientgen] at weblogic.webservice.dd.DDLoader.processWebServicesElement(DDLoader.java:271)
[clientgen] at weblogic.webservice.dd.DDLoader.load(DDLoader.java:249)
[clientgen] at weblogic.webservice.util.WebServiceWarFile.getWSDD(WebServiceWarFile.java:79)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EARClientGen.java:330)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.java:110)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
[clientgen] --------------- nested within: ------------------
[clientgen] weblogic.webservice.util.WebServiceJarException: Could not load deployment
descriptor - with nested exception:
[clientgen] [weblogic.webservice.dd.DDProcessingException: Could not find required
attribute "type" for element <fault> (Line 28, Column 8)]
[clientgen] at weblogic.webservice.util.WebServiceWarFile.getWSDD(WebServiceWarFile.java:81)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EARClientGen.java:330)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.java:110)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
BUILD FAILED
Anybody has any ideas?
Thanks much,
sami

Manoj,
Thanks a lot, THAT DID IT... two very helpful hints from you in a row.
By the way, one thing worth mentioning is that the Weblogic documentation that
we explored did not have enough information about that issue.
Thanks again.
sami
"manoj cheenath" <[email protected]> wrote:
Buried deep in the stack trace, is this little
detail:
Could not find required
attribute "type" for element <fault> (Line 28, Column 8)
So the correct DD should look something like:
<fault type="typeNS:string"
xmlns:typeNS="http://www.w3.org/2001/XMLSchema"
class-name="tutorial.sample9.HelloWorldException"
name="HelloWorldException">
</fault>
Also, check out this example:
http://manojc.com/?sample9
There is a know problem: WLS can not handle
exceptions that contain complex data types.
This will be fixed in SP1.
Regards,
-manoj
http://manojc.com
"sami titi" <[email protected]> wrote in message
news:[email protected]...
We are trying to capture an invalid message coming into our servicebefore
our
service actually processes it. Per WLS7 documentation, it providesthe
ability
to add a <fault> elt under the <params> elt in web-services.xml toperform
that.
Here's how the operations portion of our web-services.xml looks like:
<operations>
<operation method="echo(java.lang.String)" component="jcComp0"name="echo"
handler-chain="diagnosticChain">
<params>
<param location="body" class-name="java.lang.String" style="in"name="echoString"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:string">
</param>
<return-param location="body" class-name="java.lang.String"name="Result"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:string">
</return-param>
<fault name="InvalidMessageException"class-name="com.gmacfs.routeone.diagnostic.InvalidMessageException"/>
</params>
</operation>
</operations>
However, when we tried doing that, we got a BIG set of exception whiletrying
to build our client. It looks as follows:
client:
[clientgen] Generating client jar for diagnostic.ear ...
[clientgen] Could not read Web Service deployment descriptor
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.ja
va:112)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenT
ask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
[clientgen] --- Nested Exception ---
[clientgen] Could not read Web Service deployment descriptor
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EAR
ClientGen.java:332)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.ja
va:110)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenT
ask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
[clientgen] --- Nested Exception ---
[clientgen] weblogic.webservice.dd.DDProcessingException: Could notfind
required
attribute "type" for element <fault> (Line 28, Column 8)
[clientgen] atweblogic.webservice.dd.ParsingHelper.getRequiredAttribute(ParsingHelper.java
:287)
[clientgen] atweblogic.webservice.dd.DDLoader.processFaultElement(DDLoader.java:1195)
[clientgen] atweblogic.webservice.dd.DDLoader.processFaultElements(DDLoader.java:1166)
[clientgen] atweblogic.webservice.dd.DDLoader.processParamsElement(DDLoader.java:1004)
[clientgen] atweblogic.webservice.dd.DDLoader.processOperationElement(DDLoader.java:977)
[clientgen] atweblogic.webservice.dd.DDLoader.processOperationElements(DDLoader.java:853)
[clientgen] atweblogic.webservice.dd.DDLoader.processOperationsElement(DDLoader.java:841)
[clientgen] atweblogic.webservice.dd.DDLoader.processWebServiceElement(DDLoader.java:378)
[clientgen] atweblogic.webservice.dd.DDLoader.processWebServiceElements(DDLoader.java:283)
[clientgen] atweblogic.webservice.dd.DDLoader.processWebServicesElement(DDLoader.java:271)
[clientgen] at weblogic.webservice.dd.DDLoader.load(DDLoader.java:249)
[clientgen] atweblogic.webservice.util.WebServiceWarFile.getWSDD(WebServiceWarFile.java:79
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EAR
ClientGen.java:330)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.ja
va:110)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenT
ask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
[clientgen] --------------- nested within: ------------------
[clientgen] weblogic.webservice.util.WebServiceJarException: Couldnot
load deployment
descriptor - with nested exception:
[clientgen] [weblogic.webservice.dd.DDProcessingException: Could not
find>required>> attribute "type" for element <fault> (Line 28, Column 8)
[clientgen] atweblogic.webservice.util.WebServiceWarFile.getWSDD(WebServiceWarFile.java:81
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EAR
ClientGen.java:330)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.ja
va:110)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenT
ask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
BUILD FAILED
Anybody has any ideas?
Thanks much,
sami

Error while inluding xsd:whiteSpace in web-services.xml

Hi,
i am trying to allow the xml attribute values to preserve the whiteSpace characters(tabs, line feeds, carriage returns etc...)
In web-services.xml i am adding
<xsd:complexContent>
<xsd:restriction base="xsd:string">
<xsd:attribute name="address">
<xsd:whiteSpace value="preserve"/>
</xsd:attribute>
</xsd:restriction>
</xsd:complexContent>
But i am getting a run time exception as
[weblogic.xml.schema.model.parser.XSDParseException: invalid element "xsd:whiteSpace" AT line 0, column 0: <['http://www.w3.org/2001/XMLSchema']:xsd:whiteSpace value="preserve">]
am i doing in a correct way?
Please suggest me.
Thanks
subba.

weblogic server doesn't support some of the xsd features.
WebLogic Server does not support the following XML Schema features:
?     Complex data type inheritance by restriction
?     Union simple data types
?     References to named model groups
?     Nested content models in a single complex type
?     Redefinition of declarations
?     Identity constraints (key, keyref, unique)
?     Nested XSD model groups with other content models at the same level.
There cannot be a modelgroup (say sequence) that contains another nested modelgroup (say choice), and a content element (say element). So, if a nested modelgroup is required, make sure that it contains only another model group and no other content element.
?     Wildcards
but i didn't understand why its giving error for whiteSpace.
Can someone reply to this please,, its urgent for me.
thanks
subba.

Nice parameter names generation in web-services.xml

Hi
My session bean has explicit parameter names such as:
public void createCustomer(String name, String address, String telephoneNumber);
But inside web-services.xml for his operation, 'servicegen' generates parameters
name 'string, string0, string1'. Composing the xml becomes a tedious job!
Is there a way to have this file generated automatically but with the original
parameter names?
Thanks for the help,
guy

Can source2wsdd be applied to an EJB implementation - the doc mentions only Java class-implemented web service - has this been
fixed or being fixed in the next wls 7 service pack.
http://edocs.bea.com/wls/docs70/webserv/assemble.html#1056639
Thanks.
Darma
Shridhar Mysore wrote:
In WLS 7.0.1 onwards, using "source2wsdd" ant task (quo vide http://e-docs.bea.com/wls/docs70/webserv/anttasks.html#1080421)
you would be able to preserve the parameter names.
For instance, if you do :
<source2wsdd
javaSource="MyService.java"
ddFile="web-services.xml"
typesInfo="temp_dir/WEB-INF/classes/types.xml"
serviceURI="/MyService" >
<classpath>
<pathelement path="temp_dir/WEB-INF/classes"/>
<pathelement path="${java.class.path}"/>
</classpath>
</source2wsdd>
Then, the signature of a method in the backend component,
public void testMethod( int a, float fval, String name ){
would get translated mapped inside web-services.xml as :
- <operation component="MyService" name="testMethod" method="testMethod">
- <params>
<param name="a" class-name="int" type="parms:int" style="in" xmlns:parms="http://www.w3.org/2001/XMLSchema"
location="body" />
<param name="fval" class-name="float" type="parms:float" style="in" xmlns:parms="http://www.w3.org/2001/XMLSchema"
location="body" />
<param name="name" class-name="java.lang.String" type="parms:string" style="in"
xmlns:parms="http://www.w3.org/2001/XMLSchema" location="body" />
</params>
</operation>
where you would see that the parameter names are being preserved.
Regards
Shridhar
"Guy Deffaux" <[email protected]> wrote:
Hi
My session bean has explicit parameter names such as:
public void createCustomer(String name, String address, String telephoneNumber);
But inside web-services.xml for his operation, 'servicegen' generates
parameters
name 'string, string0, string1'. Composing the xml becomes a tedious
job!
Is there a way to have this file generated automatically but with the
original
parameter names?
Thanks for the help,
guy

Web-services.xml, why is security not enforced (format improved)

<pre>
Hi,
Sorry about the lack of formatting in previous post.
Running weblogic 8.1SP5.
Im having problems with the message style security, it doesn't seem to be enforced by weblogic.
The intention of web-services.xml (below) is that weblogic should authenticate the user according to credential info in the request header.
The console webservice testpage seem OK, it has user and password input boxes. But invocations fail with an obscure message involving
AssertionError: Bad password type: wsse:PasswordText
A simple Axis based client (see below) with no security tags in the header can invoke the service with no problems, would expect it to fail on athentication.
Did I miss something in web-services.xml or does something general need to be set up in the server for this to work as intended?
I am pulling my hair out on this one so any help will be greatly appreciated.
Rgds.
web-services.xml looks like this:
<security>
<user>
<name>test_user</name>
<password>test_password</password>
</user>
<spec:SecuritySpec xmlns:spec="http://www.openuri.org/2002/11/wsse/spec"
Namespace="http://schemas.xmlsoap.org/ws/2002/07/secext"
Id="_mySpec">
<spec:UsernameTokenSpec xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext"
PasswordType="wsse:PasswordText">
</spec:UsernameTokenSpec>
</spec:SecuritySpec>
</security>
<components>
<stateless-ejb name="CaseConverter">
<jndi-name path="CaseConverter"></jndi-name>
</stateless-ejb>
</components>
<operations xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<operation
component="CaseConverter"
name="convertToUpper"
method="convertToUpper"
in-security-spec="_mySpec"
>
The client looks like this (Axis based):
URL endpoint = new URL("http://127.0.0.1:7001/WebModule/CaseConverter");
Service service = new Service();
Call call = (Call)service.createCall();
call.setTargetEndpointAddress(endpoint);
call.setOperationName("convertToUpper");
call.addParameter("inputString",XMLType.XSD_STRING,ParameterMode.IN);
call.setReturnType(XMLType.XSD_STRING);
String result = (String) call.invoke(new Object[] { "hello!" });
System.out.println("Result: " + result);
</pre>

Hi
I am also getting the same error. if anybody has some solution, pl. tell us

Web-services.xml, why is security not enforced

Hi,
Running weblogic 8.1SP5.
Im having problems with the message style security, it doesn't seem to be enforced by weblogic.
The intention of web-services.xml (below) is that weblogic should authenticate the user according to credential info in the request header.
The console webservice testpage seem OK, it has user and password input boxes. But invocations fail with an obscure message involving
<b>AssertionError: Bad password type: wsse:PasswordText</b>
A simple Axis based client (see below) with no security tags in the header can invoke the service with no problems, would expect it to fail on athentication.
Did I miss something in web-services.xml or does something general need to be set up in the server for this to work as intended?
I am pulling my hair out on this one so any help will be greatly appreciated.
Rgds.
web-services.xml looks like this:
<security>
<user>
<name>test_user</name>
<password>test_password</password>
</user>
<spec:SecuritySpec xmlns:spec="http://www.openuri.org/2002/11/wsse/spec"
Namespace="http://schemas.xmlsoap.org/ws/2002/07/secext"
Id="_mySpec">
<spec:UsernameTokenSpec xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/07/secext"
PasswordType="wsse:PasswordText">
</spec:UsernameTokenSpec>
</spec:SecuritySpec>
</security>
<components>
<stateless-ejb name="CaseConverter">
<jndi-name path="CaseConverter"></jndi-name>
</stateless-ejb>
</components>
<operations xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<operation
component="CaseConverter"
name="convertToUpper"
method="convertToUpper"
in-security-spec="_mySpec"
>
The client looks like this (Axis based):
URL endpoint = new URL("http://127.0.0.1:7001/WebModule/CaseConverter");
Service service = new Service();
Call call = (Call)service.createCall();
call.setTargetEndpointAddress(endpoint);
call.setOperationName("convertToUpper");
call.addParameter("inputString",XMLType.XSD_STRING,ParameterMode.IN);
call.setReturnType(XMLType.XSD_STRING);
String result = (String) call.invoke(new Object[] { "hello!" });
System.out.println("Result: " + result);
.......

Hi
I am also getting the same error. if anybody has some solution, pl. tell us

Web-services.xml: cannot set "charset" attribute for alternative encoding

Hi,
the definition of the charset attribute in tag web-service in a web-services.xml
descriptor gets lost, when deploying a web-service.
Sample:
Before deployment I defined:
<web-service charset="ISO-8859-1" useSOAP12="false" targetNamespace="http://www.itpearls.com/unity/SubscriberData"
name="WebSubscriberDataCollector" style="rpc" uri="/WebSubscriberDataCollector">
After deployment the console states:
<web-service jmsUri="ISO-8859-1" useSOAP12="false" exposeWSDL="true" targetNamespace="http://www.itpearls.com/unity/SubscriberData"
name="WebSubscriberDataCollector" style="rpc" uri="/WebSubscriberDataCollector">
So the value "ISO-8859-1" changed his master :-(
I consider this a bug. Is there a workaround for the charset definition of an
individual web-service?
Thanks for an comments
Manfred

Hi Neal
my server's locale is not en_US. The locale command delivers:
$ locale
LANG=de_CH.ISO8859-1
LC_CTYPE="de_CH.ISO8859-1"
LC_NUMERIC="de_CH.ISO8859-1"
LC_TIME="de_CH.ISO8859-1"
LC_COLLATE="de_CH.ISO8859-1"
LC_MONETARY="de_CH.ISO8859-1"
LC_MESSAGES="de_CH.ISO8859-1"
LC_ALL=de_CH.ISO8859-1
but the Weblogic Server remains stubborn on all possibilities according to http://e-docs.bea.com/wls/docs81/webserv/i18n.html#1069538
and keeps complaining:
java.io.CharConversionException: Malformed UTF-8 char -- is an XML encoding declaration
missing?
My analysis: The Weblogic server seems to expect a UTF-8 compliant stream (due
to the current user.language property set to "de") regardless of the chosen configuration
possibilities proposed on the above mentioned link page.
Q: is this bug related to CR105388 on http://e-docs.bea.com/wls/docs81/notes/issues.html
Now I urgently need a workaround to make Umlaute contained in a web service request
working.
Thanks for any help
Manfred
"Manfred Sturm" <[email protected]> wrote:
>
Hi Neal
OK, typo. But it doesn't work. I get the console output:
java.io.CharConversionException: Malformed UTF-8 char -- is an XML encoding
declaration
missing?
plus I get following stack trace from the web-service client:
javax.xml.soap.SOAPException: Failed to read a xml element from
Vorname_aou_AOU091 Name_aou_AOU091 Ort_äou_AOU091 091A 1091 Strasse_aou_AOU091
bbcs adsl sample string
at weblogic.webservice.tools.pagegen.SampleInstance.getJavaObject(SampleInstance.java:139)
at weblogic.webservice.server.servlet.ServletBase.getJavaParams(ServletBase.java:378)
at weblogic.webservice.server.servlet.ServletBase.invokeMultiOutput(ServletBase.java:347)
at weblogic.webservice.server.servlet.ServletBase.invokeOperation(ServletBase.java:306)
at weblogic.webservice.server.servlet.WebServiceServlet.invokeOperation(WebServiceServlet.java:312)
at weblogic.webservice.server.servlet.ServletBase.handleGet(ServletBase.java:272)
at weblogic.webservice.server.servlet.ServletBase.doGet(ServletBase.java:154)
at weblogic.webservice.server.servlet.WebServiceServlet.doGet(WebServiceServlet.java:232)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6310)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
(server's locale is en_US)
Alternatively, when using "-Dweblogic.webservice.i18n.charset=ISO-8859-1"
in
I get the console output:
<Oct 7, 2003 11:46:05 AM MEST> <Warning> <Management> <BEA-141087> <Unrecognized
property: webservice.i18n.charset.>
which results in the above stack trace when invoking on the web service.
I still need a workaround within weblogic server. I cannot change the
Solaris
server's locale settings.
Thanks for an comments
Manfred
"Neal Yin" <[email protected]> wrote:
Hi Manfred,
There is a typo in code. But this should NOT affect any functionality
(charset attribute is working). Please contact support for a patch.
Thanks,
-Neal
"Manfred Sturm" <[email protected]> wrote in message
news:[email protected]...
Hi,
the definition of the charset attribute in tag web-service in aweb-services.xml
descriptor gets lost, when deploying a web-service.
Sample:
Before deployment I defined:
<web-service charset="ISO-8859-1" useSOAP12="false"
targetNamespace="http://www.itpearls.com/unity/SubscriberData"
name="WebSubscriberDataCollector" style="rpc"uri="/WebSubscriberDataCollector">
After deployment the console states:
<web-service jmsUri="ISO-8859-1" useSOAP12="false" exposeWSDL="true"
targetNamespace="http://www.itpearls.com/unity/SubscriberData"
name="WebSubscriberDataCollector" style="rpc"uri="/WebSubscriberDataCollector">
So the value "ISO-8859-1" changed his master :-(
I consider this a bug. Is there a workaround for the charset definitionof
an
individual web-service?
Thanks for an comments
Manfred

How to generate param-prefix in web-services.xml

Hello I am using source2wsdd to generate my WSDL and my web-services.xml. For sake
of interoperability I would like to have the type param-prefix in the web-services.xml
file. From my Bean class what kind of javadoc comments would help me generate
the type param-prefix ?
I also would like the location="header" in the param list.
Thanks,
Aswin.
<param xmlns:param-prefix="http://tempuri.org/"
type="param-prefix:SOAPCredentials"
location="header"
class-name="com.xyz.webservices.SOAPCredentials"
name="SOAPCredentials"
style="in">
</param>
<return-param xmlns:param-prefix="http://tempuri.org/"
type="param-prefix:GetFileProfileInformationResponse"
class-name="com.xyz.webservices.GetFileProfileInformationResponse"
name="parameters">
</return-param>
</params>

Please try this:
* @wlws:part p_SOAPAuthToken location="header"
* type="typeNS:p_SOAPAuthToken"
* class-name="com.xyz.webservices.SOAPAuthToken"
* style="inout"
* xmlns:typeNS=http://namespace/of/the/type
* @wlws:part p_SOAPCredentials location="header"
* type="typeNS:p_SOAPCredentials"
* class-name="com.xyz.webservices.SOAPCredentials"
* style="in"
* xmlns:typeNS=http://namespace/of/the/type
* @ejbgen:remote-method
public void login(SOAPAuthToken p_SOAPAuthToken,
SOAPCredentials p_SOAPCredentials)
I did not try this one out. So i can only hope that it works.
Regards,
-manoj
http://manojc.com
"Aswin Dinakar" <[email protected]> wrote in message
news:40aeeb5d$1@mktnews1...
>
I tried this
* @wlws:part p_SOAPAuthToken location="header"
* @wlws:part p_SOAPAuthToken type="param-prefix:p_SOAPAuthToken"
* @wlws:part p_SOAPAuthTokenclass-name="com.xyz.webservices.SOAPAuthToken"
* @wlws:part p_SOAPAuthToken style="inout"
* @wlws:part p_SOAPCredentials location="header"
* @wlws:part p_SOAPCredentials type="param-prefix:p_SOAPCredentials"
* @wlws:part p_SOAPCredentialsclass-name="com.xyz.webservices.SOAPCredentials"
* @wlws:part p_SOAPCredentials style="in"
* @ejbgen:remote-method
public void login(SOAPAuthToken p_SOAPAuthToken,
SOAPCredentials p_SOAPCredentials)
and I got the following error -
[source2wsdd] source2wsdd: In doclet classweblogic.webservice.tools.ddgen.Servi
ceGen, method start has thrown an exceptionjava.lang.reflect.InvocationTargetE
xception
[source2wsdd] weblogic.xml.stream.XMLStreamException: Attribute QNamevalue "par
am-prefix:p_SOAPAuthToken" does not map to a prefix that is in scope
[source2wsdd] atweblogic.webservice.dd.NSAttribute.getValueAsXMLName(NSAttrib
ute.java:45)
[source2wsdd] atweblogic.webservice.dd.DDLoader.processParamElement(DDLoader.
java:1252)
"manoj cheenath" <[email protected]> wrote:
Check out this example:
http://manojc.com/?sample3
You can find more details regarding the tags here:
http://manojc.com/tutorial/sample3/source2wsdd.html
Regards,
-manoj
http://manojc.com
"Aswin D" <[email protected]> wrote in message
news:[email protected]...
Hello I am using source2wsdd to generate my WSDL and my
web-services.xml.
For sake
of interoperability I would like to have the type param-prefix inthe
web-services.xml
file. From my Bean class what kind of javadoc comments would help megenerate
the type param-prefix ?
I also would like the location="header" in the param list.
Thanks,
Aswin.
<param xmlns:param-prefix="http://tempuri.org/"
type="param-prefix:SOAPCredentials"
location="header"
class-name="com.xyz.webservices.SOAPCredentials"
name="SOAPCredentials"
style="in">
</param>
<return-param xmlns:param-prefix="http://tempuri.org/"
type="param-prefix:GetFileProfileInformationResponse"
class-name="com.xyz.webservices.GetFileProfileInformationResponse"
name="parameters">
</return-param>
</params>

Generate web-service.xml

I need to configure the deployment descriptor web-services.xml, but I don't know where or how to generate it. I use version 8.1 of weblogic. Someone can help me? thanks!

I have an XML input in my transaction. I was able to generate the WSDL without problems. But need to know how to test it by sendig in some XML data. Probably, we could both be helping each other in the process.
Regards,
Chanti.

What web service & xml will be used for deleting the packged epub/pdf file from Admin Console

What web service & xml will be used for deleting the packged epub/pdf file from Admin Console?
I am able to delete the files from Admin console directy but not able to get which web service is calling on deleting the file from admin console:
Mangal

Hi Jim,
I tired following web service and xml to delete the packaged ebook but it is giving me error instead of response:
Web Service & XML
http://myserver_url/admin/ManageResourceKey
<request action="delete" auth="builtin" xmlns="http://ns.adobe.com/adept">
<nonce>" . $nonce . "</nonce>
<expiration>'. $expiration .'</expiration>
<resourceKey>
<resource>resource_id</resource>
<resourceItem>1</resourceItem>
</resourceKey>
</request>
Error Message
<error xmlns="http://ns.adobe.com/adept"
data="E_ADEPT_DATABASE http://myserver_url/admin/ManageResourceKey
Cannot%20delete%20or%20update%20a%20parent%20row:%20a%20foreign%20key%20constraint%20fails %20(`adept`.`distributionrights`,%20CONSTRAINT%20`distributionrights_ibfk_2`%20FOREIGN%20K EY%20(`resourceid`)%20REFERENCES%20`resourcekey`%20(`resourceid`))"/>
Magal Varshney

Web-services.xml for EJB component and SOAP Message Handler Chain

I have used the following example for my own web service with EJB component and SOAP
Message Handler Chain:
http://e-docs.bea.com/wls/docs70/webServices/dd.html#1058208
I have a deployment error:
javax.naming.NameNotFoundException: Unable to resolve 'app/ejb/DocumentService.j
ar#DocumentService/home' Resolved: 'app/ejb' Unresolved:'DocumentService.jar#Doc
umentService' ; remaining name 'DocumentService.jar#DocumentService/home'
In attachement is the ear file.
Is there a problem in web-services.xml?
Thanks
[ws_dox_sdi.ear]

It works. Thanks,
Ioana
"Neal Yin" <[email protected]> wrote:
The error means your EJB is not deployed.
Adding a EJB module to your application.xml file of the ear should fixe
it.
<application>
<display-name />
<module>
<web>
<web-uri>dox_sdi.war</web-uri>
</web>
</module>
<module>
<ejb>DocumentService.jar</ejb>
</module>
</application>
"Ioana Meissner" <[email protected]> wrote in message
news:3cf640cc$[email protected]..
I have used the following example for my own web service with EJBcomponent and SOAP
Message Handler Chain:
http://e-docs.bea.com/wls/docs70/webServices/dd.html#1058208
I have a deployment error:
javax.naming.NameNotFoundException: Unable to resolve'app/ejb/DocumentService.j
ar#DocumentService/home' Resolved: 'app/ejb'Unresolved:'DocumentService.jar#Doc
umentService' ; remaining name 'DocumentService.jar#DocumentService/home'
In attachement is the ear file.
Is there a problem in web-services.xml?
Thanks

Web-services.xml, dtd or xml schema?

Hi there!
I'm just curious to know whether there exists any dtd or schema
for wls 7.x web-services.xml file?
The diagram in
http://e-docs.bea.com/wls/docs70/webserv/wsp.html#1001373
shows one order for the contents of the web-service element,
whereas the examples reflect another (being types,
type-mapping, components, operations).
Why are the example web-services.xml not tagged with the
information of the location of the schema?
Of course building web-services.xml manually is not the first
thing to try, but since the contents are documented and since
it gives the best control over the process, it makes sense.

Hello,
There's not one. The primary vision for the web-services.xml file
was/is to be a linkage between wsdl/soap and the j2ee environment. It
was not intended to be a starting point for building an application, but
a semi-private intermediary.
HTHs,
Bruce
Toni Nykanen wrote:
>
Hi there!
I'm just curious to know whether there exists any dtd or schema
for wls 7.x web-services.xml file?
The diagram in
http://e-docs.bea.com/wls/docs70/webserv/wsp.html#1001373
shows one order for the contents of the web-service element,
whereas the examples reflect another (being types,
type-mapping, components, operations).
Why are the example web-services.xml not tagged with the
information of the location of the schema?
Of course building web-services.xml manually is not the first
thing to try, but since the contents are documented and since
it gives the best control over the process, it makes sense.

Web-services.xml

I'm implementing WS-SECURITY for my web service. The only service that I am enabling is the soap encryption. Furthermore, I only want to encrypt the request. I in the web-services.xml the operations specify the security spec to use for both the request and the response...
in-security-spec
out-security-spec
The docs say "If you do not specify this attribute, the default security specification, if it exists, is applied to the SOAP response. If there is no default security specification, then no message-level security is applied to the SOAP response."
My question is how do you disable the response if there is a default security spec.
thx

xmllint is correct. Here's what the 1.1.3 XSD says (I put in the leading periods to fool the discussion board into preserving structure ):
. <xsd:element name="ITunesUDocument">
. . <xsd:complexType>
. . . <xsd:sequence>
. . . . <xsd:element ref="Version" minOccurs="1" maxOccurs="1"/>
. . . . <xsd:element ref="AddCourse" minOccurs="0"/>
. . . </xsd:sequence>
. . </xsd:complexType>
. </xsd:element>
If "minOccurs" or "maxOccurs" aren't specified in sequence elements, then they both default to "1". So the "minOccurs" and "maxOccurs" specifiers are redundant in the "Version" element specification…they'd be "1" anyway. Setting "minOccurs" to "0" means that you can omit the element in XML…but unless "maxOccurs" is set, than the most any element can appear in the sequence is once to be valid. "unbounded" can be used in "maxOccurs" to set no limit on the number of times it can appear in the sequence.
Recall that XML doesn't necessarily have to validate to "work". An XML validation is a contract between us and Apple…Apple promises that we can put at least one "AddCourse" in an "ITunesUDocument" and that is going to work, or our money back. But if we don't submit valid XML, it might still work…but there is no promise there either. It might work today, it might fail tomorrow. The iTunes U people have said, in various venues, that we should expect Apple to validate our XML…but nobody's perfect. It could be that Apple just missed this one…but we should still write code under the assumption that the XSD is being correctly applied and that our XML is being validated on Apple's end. That way, our code can never be "wrong".

Web service XML String

Similar Messages

Maybe you are looking for