Adding White Space

I am trying an example form "Professional Java XML" book about creating a simple DOM tree. The problem is that the Output XML is without new line (i.e. the all tags are one the same line)
does any body know how to toggle this problem, please your help?
I am using the following code:
import org.w3c.dom.*;
// We are going to use JAXP's classes for DOM I/O
import javax.xml.parsers.*;
import javax.xml.transform.*;
import javax.xml.transform.stream.*;
import javax.xml.transform.dom.*;
// Import other Java classes
import java.io.PrintWriter;
import java.io.IOException;
public class CreatePresident {
public static void main(String[] args) {
Document doc;
Element president;
Element person;
Element firstName;
Element surname;
try
// This is JAXP's way to create a new empty Document
// The lines within the {} braces are NOT DOM level 1
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
dbf.setValidating(true);
dbf.setIgnoringElementContentWhitespace(true);
DocumentBuilder db = dbf.newDocumentBuilder();
doc = db.newDocument();
// We'll start by creating a "<Person>"
person = doc.createElement("Person");
// No create the "<FirstName>" element
firstName = doc.createElement("FirstName");
// Create a Text node "George" and add it to the "FirstName" tag
firstName.appendChild( doc.createTextNode("George") );
// Add the "<FirstName>" tag to "<Person>"
person.appendChild(firstName);
// Same as above
surname = doc.createElement("Surname");
surname.appendChild( doc.createTextNode("Bush") );
person.appendChild(surname);
president = doc.createElement("President");
// Set the "Country" attribute in "<Presedent>"
president.setAttribute("Country","US");
president.appendChild( person );
// Add everything to the XmlDocument (doc)
doc.appendChild( president );
// This is JAXP's way to output a DOM to a OutputStream
// The lines within the {} braces are NOT DOM level 1
TransformerFactory tFactory = TransformerFactory.newInstance();
Transformer transformer = tFactory.newTransformer();
transformer.transform(new DOMSource(doc), new StreamResult(System.out));
catch( ParserConfigurationException pcEx )
System.out.println("ParserConfigurationException: "+pcEx.getMessage());
pcEx.printStackTrace();
catch( TransformerConfigurationException tcEx )
System.out.println("TransformerConfigurationException: "+tcEx.getMessage());
tcEx.printStackTrace();
catch( TransformerException tEx )
System.out.println("TransformerException: "+tEx.getMessage());
tEx.printStackTrace();
Regards

Transformer transformer = TransformerFactory.newInstance().newTransformer();
transformer.setOutputProperty(OutputKeys.INDENT, "yes");
transformer.setOutputProperty("{http://xml.apache.org/xslt}indent-amount", "2");
transformer.transform(new DOMSource(doc), new StreamResult(out));

Similar Messages

  • PDF Report adding white spaces

    NEVER MIND.... Why is their no DEL option... Added fm in front of MONTH ('DD fmMONTH YY') and its fixed.
    I have a report that goes to a PDF based on a RTF template. On the Dates, the XML Feed looks fine, but when it generates the PDF it is adding random white spaces in the date.
    XML Feed:
    <REPORT_DATE>31 AUGUST 09</REPORT_DATE>
    <ORDER_DATE>19 AUGUST 09</ORDER_DATE>
    PDF Returns:
    Dated 19 AUGUST 09
    31 AUGUST 10
    so the year is seperated from the month. The SQL is a TO_CHAR(ORDER_DATE, 'DD MONTH YY') and so on...
    Any thoughts from anyone??? Please.....
    Edited by: Matt.Smith on Aug 26, 2009 7:56 AM

    Because instead of editing your previous message, it is a better practice to add a new message and CLOSE the thread there. Allows people to see the thread properly..
    Thank you,
    Tony Miller
    Webster, TX

  • Adding white spaces between strings during concatenation in JSTL

    Please provide a way to add white space between strings during concatenation in JSTL.
    I tried the following.
    eg:
    <c:set var="even_odd" value="odd">
    <c:out value="first ${even_odd}"/>
    I want the output string as "first odd ".
    Moreover i am using the above value for generating the class attribute of a row of a table like
    <tr class=<c:out value="first ${even_odd}"/>>
    while printing the value of <c:out value="first ${even_odd}"/> in the page,i am getting correctly as i needed as "first odd".
    But while taking the code of the page while rendering by the browser, it is showing like
    <tr class="first" odd="">
    I think the white space is the problem.
    Please provide any solution or hint.

    <tr class=<c:out value="first ${even_odd}"/>><tr class="first ${even_odd}">

  • XSL processor adding white space

    Hi,
    Is it possible to prevent the XSL processor from inserting
    white space as this can affect HTML table layout & other
    things.
    For example.
    XSL contains the following: (On one line)
    <td colspan="2" bgcolor="#000066"><img
    src="/images/global_spacer01.gif"/ width="1" height="1"/></td>
    is converted to (Three lines)
    <td colspan="2" bgcolor="#000066">
    <img rc="/images/global_spacer01.gif"/ width="1" height="1">
    </td>
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    null

    Dougall Squair (guest) wrote:
    : Hi,
    : Is it possible to prevent the XSL processor from inserting
    : white space as this can affect HTML table layout & other
    : things.
    : For example.
    : XSL contains the following: (On one line)
    : <td colspan="2" bgcolor="#000066"><img
    : src="/images/global_spacer01.gif"/ width="1" height="1"/></td>
    : is converted to (Three lines)
    : <td colspan="2" bgcolor="#000066">
    : <img rc="/images/global_spacer01.gif"/ width="1"
    height="1">
    : </td>
    : ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    null

  • Adding white spaces

    Hi everyone;
    How would I add a certain number of white [blank]spaces to the end of a string? I know how to add a space, but don't know how to add more than one. Thanks in advance.

    there are several ways. Here is one:
    for (int x = 0; x < spaces; x++) {
    stringBuffer.append(" ");
    return string.toString();

  • Adding white space in a form field

    Hello all,
    anyone know if it is possible to add whitespace in a form field.
    I have an IF like this ....
    <?if:WORKSITE_ADDRESS2=''?>
    <?WORKSITE_ADDRESS3?> <?WORKSITE_ADDRESS4?> <?end if?>
    I need a space to appear in between WORKSITE_ADDRESS3 and WORKSITE_ADDRESS4.
    I can not figure out how to do that ? is it possible ? the results I get are that
    the two values are shown with no space in between. Do I have to use separate form fields?
    Thanks

    Hi,
    I hit the same issue a while back, the workaround is to use the CDATA tag. See the below post:
    Form fields stripping SPACE characters from IF statement
    Thanks
    Paul

  • White space added to end of slideshow

    I've created a slideshow in 5.5 and at the end of my slideshow when it's played (either in project preview or exported to YouTube) there is about :40sec of white space added in.
    What could I have done to create this? The last slide is an image slide, there is nothing beyond that.
    Also, is there a way to instruct the slideshow to repeat at the end or is there a player besides a YouTube player that will repeat once it reaches the end?
    Many thanks for the help!

    Thanks, Andy!  That was helpful.
    Here is a screen shot of the last slide: 
    In the Project Preview within Captivate, there is no white addition.  It is when I upload it to YouTube is when the additional white space is added on - it adds about :40sec or so of white before it fades out.
    Thanks so much for your help - I've been trying to figure this out for awhile!

  • Why is there unwanted white space added to all .jpg/.png when "inserted" into Dreamweaver CS4?

    I have two seperate sites/seperate root folders that I am building right now and every image that I insert into Dreamweaver has an extra white space added to the left of every image. Please help, I must have checked/unchecked something in my preferences. Thank you!
    Its not in my CSS or in the HTML coding...from my site:
    <a href="optomized-large/Havana-Night-(66-of-312).jpg" title=""> <img src="optomized-thumb/Havana-Night-(66-of-312).jpg" width="100" height="150" alt="" /> </a>

    You do know how wrong it is to make a web page that is nothing but images, right? It's on the list of the 10 worst mistakes you can make for sure.
    Anyhow, look at this page -
    http://www.murraytestsite.com/denver.html
    I have outlined every image on that page with a 1px red border.  There is no unwanted white space being added to those images.  If there were you would never see the menu button images that close together.  I have also put a 1px green border on the left of the container div.  Note that the images are snug against that green border.

  • Adding custom stamps to many pages in white space.

    Is there any way to add a custom stamp to every page of a PDF book and having it placed into the white space on the document? I have found a script that will do every thing except for the 'white space' part of my query, so I don't think I will have much luck.
    Watermarks will probably not work in this instance, the stamp needs to be noticible but not in the way, and the watermark will encouter the same placement problem (as it is preferable if the stamp/watermark is not getting the in way of the drawing pdf's content).
    Any help will be appreciated, just let me know if you need more clarification.

    The question is what do you mean by "white space"? Is it always the same area on the page (like a 2" margin), or is it a different location for each page, where there happens to be no text or images? The former is possible, the latter only partially, and is very difficult to implement with a script.

  • IE 11 white space problem

    I created  a page with dreamweaver. It renders as intended in firefox but shows unwanted white space in ie 11.
    How do I fix this?
    Here is the page in firefox:
    Here is ie 11 page:
    Please respond to [email protected]
    Here is my code:
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <title>Untitled Document</title>
    <style type="text/css">
    <!--
    body {
    font: 100%/1.4 Verdana, Arial, Helvetica, sans-serif;
    background: #4E5869;
    margin: 0;
    padding: 0;
    color: #000;
    /* ~~ Element/tag selectors ~~ */
    ul, ol, dl { /* Due to variations between browsers, it's best practices to zero padding and margin on lists. For consistency, you can either specify the amounts you want here, or on the list items (LI, DT, DD) they contain. Remember that what you do here will cascade to the .nav list unless you write a more specific selector. */
    padding: 0;
    margin: 0;
    h1, h2, h3, h4, h5, h6, p {
    margin-top: 0;  /* removing the top margin gets around an issue where margins can escape from their containing div. The remaining bottom margin will hold it away from any elements that follow. */
    padding-right: 15px;
    padding-left: 15px; /* adding the padding to the sides of the elements within the divs, instead of the divs themselves, gets rid of any box model math. A nested div with side padding can also be used as an alternate method. */
    font-size: x-small;
    color: #FFF;
    a img { /* this selector removes the default blue border displayed in some browsers around an image when it is surrounded by a link */
    border: none;
    /* ~~ Styling for your site's links must remain in this order - including the group of selectors that create the hover effect. ~~ */
    a:link {
    color:#414958;
    text-decoration: underline; /* unless you style your links to look extremely unique, it's best to provide underlines for quick visual identification */
    a:visited {
    color: #4E5869;
    text-decoration: underline;
    a:hover, a:active, a:focus { /* this group of selectors will give a keyboard navigator the same hover experience as the person using a mouse. */
    text-decoration: none;
    color: #FFFFFF;
    /* ~~ this container surrounds all other divs giving them their percentage-based width ~~ */
    .container {
    width: 80%;
    max-width: 1260px;/* a max-width may be desirable to keep this layout from getting too wide on a large monitor. This keeps line length more readable. IE6 does not respect this declaration. */
    min-width: 780px;/* a min-width may be desirable to keep this layout from getting too narrow. This keeps line length more readable in the side columns. IE6 does not respect this declaration. */
    background: #FFF; /* the auto value on the sides, coupled with the width, centers the layout. It is not needed if you set the .container's width to 100%. */
    height: 80%;
    margin-top: 0;
    margin-right: auto;
    margin-bottom: 0;
    margin-left: auto;
    .container .footer #fMisc div p {
    font-family: Verdana, Geneva, sans-serif;
    font-size: x-small;
    color: #FFF;
    /* ~~ the header is not given a width. It will extend the full width of your layout. It contains an image placeholder that should be replaced with your own linked logo ~~ */
    .header {
    background: #6F7D94;
    /* ~~ These are the columns for the layout. ~~
    1) Padding is only placed on the top and/or bottom of the divs. The elements within these divs have padding on their sides. This saves you from any "box model math". Keep in mind, if you add any side padding or border to the div itself, it will be added to the width you define to create the *total* width. You may also choose to remove the padding on the element in the div and place a second div within it with no width and the padding necessary for your design.
    2) No margin has been given to the columns since they are all floated. If you must add margin, avoid placing it on the side you're floating toward (for example: a right margin on a div set to float right). Many times, padding can be used instead. For divs where this rule must be broken, you should add a "display:inline" declaration to the div's rule to tame a bug where some versions of Internet Explorer double the margin.
    3) Since classes can be used multiple times in a document (and an element can also have multiple classes applied), the columns have been assigned class names instead of IDs. For example, two sidebar divs could be stacked if necessary. These can very easily be changed to IDs if that's your preference, as long as you'll only be using them once per document.
    4) If you prefer your nav on the left instead of the right, simply float these columns the opposite direction (all left instead of all right) and they'll render in reverse order. There's no need to move the divs around in the HTML source.
    .sidebar1 {
    float: right;
    width: 20%;
    padding-bottom: 64px;
    height: 100%;
    font-family: "Comic Sans MS", cursive;
    font-weight: bolder;
    font-size: x-large;
    border-top-width: 0%;
    border-right-width: 0%;
    border-bottom-width: 0%;
    border-left-width: 0%;
    background-color: #93A5C4;
    background-repeat: repeat;
    margin: 0px;
    overflow: hidden;
    .content {
    width: 80%;
    float: right;
    background-image: url(back1.gif);
    background-repeat: repeat;
    background-color: #CCC;
    padding-top: 0px;
    padding-right: 0px;
    padding-bottom: 10px;
    padding-left: 0px;
    height: 100%;
    overflow: hidden;
    /* ~~ This grouped selector gives the lists in the .content area space ~~ */
    .content ul, .content ol {
    padding: 0 15px 15px 40px; /* this padding mirrors the right padding in the headings and paragraph rule above. Padding was placed on the bottom for space between other elements on the lists and on the left to create the indention. These may be adjusted as you wish. */
    /* ~~ The navigation list styles (can be removed if you choose to use a premade flyout menu like Spry) ~~ */
    ul.nav {
    list-style: none; /* this removes the list marker */
    border-top: 1px solid #666; /* this creates the top border for the links - all others are placed using a bottom border on the LI */
    margin-bottom: 15px; /* this creates the space between the navigation on the content below */
    ul.nav li {
    border-bottom: 1px solid #666; /* this creates the button separation */
    ul.nav a, ul.nav a:visited { /* grouping these selectors makes sure that your links retain their button look even after being visited */
    padding: 5px 5px 5px 15px;
    display: block; /* this gives the link block properties causing it to fill the whole LI containing it. This causes the entire area to react to a mouse click. */
    text-decoration: none;
    background: #8090AB;
    color: #000;
    ul.nav a:hover, ul.nav a:active, ul.nav a:focus { /* this changes the background and text color for both mouse and keyboard navigators */
    background: #6F7D94;
    color: #FFF;
    /* ~~ The footer ~~ */
    .footer {
    background: #6F7D94;
    position: relative;/* this gives IE6 hasLayout to properly clear */
    clear: both; /* this clear property forces the .container to understand where the columns end and contain them */
    font-size: xx-small;
    color: #000;
    margin: 0px;
    padding-top: 10px;
    padding-right: 0;
    padding-bottom: 10px;
    padding-left: 0;
    /* ~~ miscellaneous float/clear classes ~~ */
    .fltrt {  /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
    float: right;
    margin-left: 8px;
    .fltlft { /* this class can be used to float an element left in your page. The floated element must precede the element it should be next to on the page. */
    float: left;
    margin-right: 8px;
    .clearfloat { /* this class can be placed on a <br /> or empty div as the final element following the last floated div (within the #container) if the #footer is removed or taken out of the #container */
    clear:both;
    height:0;
    font-size: 1px;
    line-height: 0px;
    a {
    color: #FFF;
    .container .footer #fMisc div p a {
    color: #FFF;
    .container .footer div p {
    font-family: Verdana, Geneva, sans-serif;
    font-size: x-small;
    color: #FFF;
    .container .footer div p a {
    color: #FFF;
    p {
    font-size: xx-large;
    p {
    color: #000;
    font-size: x-large;
    .container .footer #fMisc div {
    font-size: x-small;
    .container .footer #fMisc div {
    color: #FFF;
    .container .content h1 {
    font-family: Verdana, Geneva, sans-serif;
    font-size: x-large;
    font-weight: bold;
    color: #000;
    -->
    </style><!--[if lte IE 7]>
    <style>
    .content { margin-right: -1px; } /* this 1px negative margin can be placed on any of the columns in this layout with the same corrective effect. */
    ul.nav a { zoom: 1; }  /* the zoom property gives IE the hasLayout trigger it needs to correct extra whiltespace between the links */
    </style>
    <![endif]-->
    <script src="SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
    <link href="SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css" />
    </head>
    <body>
    <div class="container">
      <div class="header">
      <img src="Pictures/logo.gif" alt="Logo" name="Insert_logo" width="81" height="63" id="Insert_logo" style="background: #8090AB; display:block;" />
    <!-- end .header --></div>
      <div class="sidebar1">
       <img src="Pictures/back1.jpg" width="72" height="72" /><p> Cliff is an all breed AKC Registered Professional Dog Handler</p>
    <p><img src="Pictures/back1.jpg" width="72" height="72" /></p>
    <p><img src="Pictures/back1.jpg" width="72" height="72" /></p>
    <!-- end .sidebar --></div>
      <div class="content">
       <ul id="MenuBar1" class="MenuBarHorizontal">
         <li><a href="#">Home</a>      </li>
         <li><a href="#" class="MenuBarItemSubmenu">Kennel</a>
           <ul>
             <li><a href="#">Our Facility</a></li>
             <li><a href="#">Rates</a></li>
             <li><a href="#">Pictures</a></li>
           </ul>
         </li>
         <li><a class="MenuBarItemSubmenu" href="#">Show Handling</a>
           <ul>
             <li><a href="#">Info</a></li>
             <li><a href="#">Rates</a></li>
             <li><a href="Schedulefile:///S:/Homepage/calendar.html">Schedule</a></li>
    </ul>
         </li>
         <li><a href="#">Photo Gallery</a></li>
         <li><a href="#">About Me</a></li>
         <li><a href="#">Contact Me</a></li>
       </ul>
       <br />
        <h1 style="margin: 10px; clear: both; text-align:center; font-size: xx-large; font-family: Georgia, 'Times New Roman', Times, serif;">Clifford W. Steele </h1>
       <div style="text-align:center; font-size: xx-large;"> <img src="Pictures/Harley Champion001.jpg" alt="Harley Champion" width="530" height="423" border="0" /></div>
      <!-- end .content --></div>
      <div class="footer">
          <div style="float:right">
            <p> <a href="MAILTO:[email protected]" >Site Designed by Fredric M. Zipser</a><br />
           </p>
        </div>
        <div>
            <p>Clifford W. Steele  Professional Handler <br />
              1395 Rt. 6<br />
              Carmel, NY  10512-1627<br />
              United States<br />
              ph:(845) 225-2463<br />
              Cell:(845) 661-0010<br />
            <a href="MAILTO:[email protected]" >[email protected]</a></p>
        </div>
      <!-- end .footer --></div>
    <!-- end .container --></div>
    </script>
    <script type="text/javascript">
    var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgDown:"SpryAssets/SpryMenuBarDownHover.gif", imgRight:"SpryAssets/SpryMenuBarRightHover.gif"});
    </script>
    </body>
    </html>

    Give <div class="container"> the same blue background color as your right side bar.
    You'll notice in IE some of the spacing for the rest of your page is slightly larger than in Firefox (browsers do that a lot if you aren't very, very specific about sizes). Because of that, your side bar isn't long enough to fill in the space on that side and the background color of the "container" <div> shows through.

  • Bottom White Space

    On my website you can see that there is white space at the bottom but it ends just short of the true bottom, is there anyway I can make this so white continues down all the way?
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <link rel="stylesheet" href="layout.css" ... />
    <meta name="google-site-verification" content="_Plh0Sn97-RFeQaAZFoZgv8tZ9Ap9FhMbNGy3eq3CeM" />
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <title>Home</title>
    <style type="text/css">
    <!--
    body {
        font: 100%/1.4 Verdana, Arial, Helvetica, sans-serif;
        background: #4E5869;
        margin: 0;
        padding: 0;
        color: #000;
        background-image: url(Pictures/1276207208635.jpg);
    /* ~~ Element/tag selectors ~~ */
    ul, ol, dl { /* Due to variations between browsers, it's best practices to zero padding and margin on lists. For consistency, you can either specify the amounts you want here, or on the list items (LI, DT, DD) they contain. Remember that what you do here will cascade to the .nav list unless you write a more specific selector. */
        padding: 0;
        margin: 0;
    h1, h2, h3, h4, h5, h6, p {
        margin-top: 0;     /* removing the top margin gets around an issue where margins can escape from their containing div. The remaining bottom margin will hold it away from any elements that follow. */
        padding-right: 15px;
        padding-left: 15px; /* adding the padding to the sides of the elements within the divs, instead of the divs themselves, gets rid of any box model math. A nested div with side padding can also be used as an alternate method. */
        font-size: xx-large;
    a img { /* this selector removes the default blue border displayed in some browsers around an image when it is surrounded by a link */
        border: none;
    /* ~~ Styling for your site's links must remain in this order - including the group of selectors that create the hover effect. ~~ */
    a:link {
        color:#09F;
        text-decoration: none; /* unless you style your links to look extremely unique, it's best to provide underlines for quick visual identification */
    a:visited {
        color: #06F;
        text-decoration: none;
    a:hover, a:active, a:focus { /* this group of selectors will give a keyboard navigator the same hover experience as the person using a mouse. */
        text-decoration: none;
    /* ~~ this container surrounds all other divs giving them their percentage-based width ~~ */
    .container {
        width: 80%;
        max-width: 1260px;/* a max-width may be desirable to keep this layout from getting too wide on a large monitor. This keeps line length more readable. IE6 does not respect this declaration. */
        min-width: 780px;/* a min-width may be desirable to keep this layout from getting too narrow. This keeps line length more readable in the side columns. IE6 does not respect this declaration. */
        background: #FFF;
        margin: 0 auto; /* the auto value on the sides, coupled with the width, centers the layout. It is not needed if you set the .container's width to 100%. */
        overflow: hidden; /* this declaration makes the .container clear all floated columns within it. */
    /* ~~ These are the columns for the layout. ~~
    1) Padding is only placed on the top and/or bottom of the divs. The elements within these divs have padding on their sides. This saves you from any "box model math". Keep in mind, if you add any side padding or border to the div itself, it will be added to the width you define to create the *total* width. You may also choose to remove the padding on the element in the div and place a second div within it with no width and the padding necessary for your design.
    2) No margin has been given to the columns since they are all floated. If you must add margin, avoid placing it on the side you're floating toward (for example: a right margin on a div set to float right). Many times, padding can be used instead. For divs where this rule must be broken, you should add a "display:inline" declaration to the div's rule to tame a bug where some versions of Internet Explorer double the margin.
    3) Since classes can be used multiple times in a document (and an element can also have multiple classes applied), the columns have been assigned class names instead of IDs. For example, two sidebar divs could be stacked if necessary. These can very easily be changed to IDs if that's your preference, as long as you'll only be using them once per document.
    4) If you prefer your nav on the right instead of the left, simply float these columns the opposite direction (all right instead of all left) and they'll render in reverse order. There's no need to move the divs around in the HTML source.
    .sidebar1 {
        float: left;
        width: 20%;
        background: #93A5C4;
        padding-bottom: 10px;
    .content {
        padding: 10px 0;
        width: 60%;
        float: left;
    .sidebar2 {
        float: left;
        width: 20%;
        background: #93A5C4;
        padding: 10px 0;
    /* ~~ This grouped selector gives the lists in the .content area space ~~ */
    .content ul, .content ol {
        padding: 0 15px 15px 40px; /* this padding mirrors the right padding in the headings and paragraph rule above. Padding was placed on the bottom for space between other elements on the lists and on the left to create the indention. These may be adjusted as you wish. */
    /* ~~ The navigation list styles (can be removed if you choose to use a premade flyout menu like Spry) ~~ */
    ul.nav {
        list-style: none; /* this removes the list marker */
        border-top: 1px solid #666; /* this creates the top border for the links - all others are placed using a bottom border on the LI */
        margin-bottom: 15px; /* this creates the space between the navigation on the content below */
        color: #FFF;
    ul.nav li {
        border-bottom: 1px solid #666; /* this creates the button separation */
    ul.nav a, ul.nav a:visited { /* grouping these selectors makes sure that your links retain their button look even after being visited */
        padding: 5px 5px 5px 15px;
        display: block; /* this gives the link block properties causing it to fill the whole LI containing it. This causes the entire area to react to a mouse click. */
        text-decoration: none;
        background: #8090AB;
        color: #000;
    ul.nav a:hover, ul.nav a:active, ul.nav a:focus { /* this changes the background and text color for both mouse and keyboard navigators */
        background: #6F7D94;
        color: #FFF;
    /* ~~ miscellaneous float/clear classes ~~ */
    .fltrt {  /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
        float: right;
        margin-left: 8px;
    .fltlft { /* this class can be used to float an element left in your page. The floated element must precede the element it should be next to on the page. */
        float: left;
        margin-right: 8px;
    .clearfloat { /* this class can be placed on a <br /> or empty div as the final element following the last floated div (within the #container) if the overflow:hidden on the .container is removed */
        clear:both;
        height:0;
        font-size: 1px;
        line-height: 0px;
    .container .content h1 {
        font-family: OCR A Extended;
    body,td,th {
        color: #000;
    -->
    </style><!--[if lte IE 7]>
    <style>
    .content { margin-right: -1px; } /* this 1px negative margin can be placed on any of the columns in this layout with the same corrective effect. */
    ul.nav a { zoom: 1; }  /* the zoom property gives IE the hasLayout trigger it needs to correct extra whiltespace between the links */
    </style>
    <![endif]-->
    <!--Analystics-->
    <script type="text/javascript">
      var _gaq = _gaq || [];
      _gaq.push(['_setAccount', 'UA-19878287-1']);
      _gaq.push(['_trackPageview']);
      (function() {
        var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
        ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
        var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
    </script>
    <!--Iphone Redirect-->
    <script type="text/javascript" src="http://widgets.amung.us/tab.js"></script><script type="text/javascript">WAU_tab('tnvkzuebf877', 'right-upper')</script>
    <script type="text/javascript" src="http://hunterthornsberry.com/mobilejs.js"> if((navigator.userAgent.match(/iPhone/i)) || (navigator.userAgent.match(/iPod/i))) {
         if (document.cookie.indexOf("iphone_redirect=false") == -1) window.location = "http://hunterthornsberry.com/mobile.html";
    </script>
    </head>
    <body>
    <div class="wrapper">
    <div class="container" align="left">
      <div class="sidebar1">
        <ul class="nav">
          <li><img src="../../Pictures/TDLLOGO.png" width="172" height="129" /></li>     
          <li><a href="index.html">Home</a></li>      <li><a href="About.html">About Me</a></li>
          <li><a href="Blog.html">Personal Blog</a></li>
          <li><a href="tech.html">Tech Stuff</a></li>
          <li><a href="Projects.html">Projects</a></li>
          <li><a href="design.html">Design/Art</a></li>
          <li><a href="Contact.html">Contact</a></li>
        </ul>
        <p> <center><script type="text/javascript"><!--
    google_ad_client = "pub-9636713487359174";
    /* HunterThornsberry */
    google_ad_slot = "9954026781";
    google_ad_width = 160;
    google_ad_height = 600;
    //-->
    </script>
    <script type="text/javascript"
    src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
    </script></center></p>
      <!-- end .sidebar1 --></div>
      <div class="content">
        <center><h1>Home</h1>
          <p><strong><em>UNDER CONSTRUCTION</em></strong></p>
          <p>
            <object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="550" height="400" id="FlashID" title="This is my life">
              <param name="movie" value="../../Intro.swf" />
              <param name="quality" value="high" />
              <param name="wmode" value="opaque" />
              <param name="swfversion" value="6.0.65.0" />
              <!-- This param tag prompts users with Flash Player 6.0 r65 and higher to download the latest version of Flash Player. Delete it if you don’t want users to see the prompt. -->
              <param name="expressinstall" value="../../Scripts/expressInstall.swf" />
              <param name="LOOP" value="false" />
              <!-- Next object tag is for non-IE browsers. So hide it from IE using IECC. -->
              <!--[if !IE]>-->
              <object type="application/x-shockwave-flash" data="../../Intro.swf" width="550" height="400">
                <!--<![endif]-->
                <param name="quality" value="high" />
                <param name="wmode" value="opaque" />
                <param name="swfversion" value="6.0.65.0" />
                <param name="expressinstall" value="../../Scripts/expressInstall.swf" />
                <param name="LOOP" value="false" />
                <!-- The browser displays the following alternative content for users with Flash Player 6.0 and older. -->
                <div>
                  <h4>Content on this page requires a newer version of Adobe Flash Player.</h4>
                  <p><a href="http://www.adobe.com/go/getflashplayer"><img src="http://www.adobe.com/images/shared/download_buttons/get_flash_player.gif" alt="Get Adobe Flash player" width="112" height="33" /></a></p>
                </div>
                <!--[if !IE]>-->
              </object>
              <!--<![endif]-->
            </object>
          </p>
          <p> </p>
        </center>
      </div>
      <div class="sidebar2" align="right">
    <script type="text/javascript"><!--
    google_ad_client = "pub-9636713487359174";
    /* Sky */
    google_ad_slot = "5228573680";
    google_ad_width = 120;
    google_ad_height = 600;
    //-->
    </script>
    <script type="text/javascript"
    src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
    </script>
      <!-- end .container --></div>
    <script type="text/javascript">
    <!--
    swfobject.registerObject("FlashID");
    //-->
    </script>
    </div>
    <!--Footer-->
    <div class="push"></div>
    <div class="footer">
    <p><center>Copyright (c) 2008</p>
    </div>
    </body>
    </html>

    Well its the 'footer' <div> and the <div> before that which need some attention.
    Add the below to your css styles:
    .footer {
    width: 80%;
    margin: 0 auto;
    background-color: #fff;
    .footer p {
    margin: 0;
    padding: 0;
    Then remove the "push" <div> completely:
    <div class="push"></div>
    <div class="footer">
    <p><center>Copyright (c) 2008</p>
    </div>
    To just leave:
    <div class="footer">
    <p><center>Copyright (c) 2008</p>
    </div>

  • XSL mapping of ARTMAS IDoc - carriage returns and white space

    Hi all. I have tried all sorts here and am completely stuck. I am mapping an article master ARTMAS IDoc using XSL mapping and an extra carriage return and white space characters are being added to the FIELD1 and FIELD2 fields of the E1BPE1MARAEXTRT segment and I don't know why! These fields contain all our bespoke field values joined together so they are 229 and 250 characters long respectively, which I think is related to the problem. The mapping program looks like this:
    <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
    <xsl:output method="xml" encoding="UTF-8" omit-xml-declaration="no" indent="yes"/>
    <xsl:template match="/">
    <ARTMAS04>
    <IDOC>
      <xsl:copy-of select="//ARTMAS04/IDOC/EDI_DC40"/>
      <xsl:copy-of select="//ARTMAS04/IDOC/E1BPE1MATHEAD"/>
      <xsl:copy-of select="//ARTMAS04/IDOC/E1BPE1MARART"/>
      <xsl:copy-of select="//ARTMAS04/IDOC/E1BPE1MARAEXTRT"/>
      <xsl:copy-of select="//ARTMAS04/IDOC/E1BPE1MAKTRT"/>
      <xsl:for-each select="//ARTMAS04/IDOC/E1BPE1MARCRT">
        <xsl:if test="(PLANT='D100') or (PLANT='D200') or (PLANT='D300')">
          <xsl:copy-of select="."/>
        </xsl:if>
      </xsl:for-each>
      <xsl:copy-of select="//ARTMAS04/IDOC/E1BPE1MARMRT"/>
      <xsl:copy-of select="//ARTMAS04/IDOC/E1BPE1MEANRT"/>
    </IDOC>
    </ARTMAS04>
    </xsl:template>
    </xsl:stylesheet>
    I have a test IDoc going through this and the first 3 characters of the FIELD1 are "BIK". If I look at the source of the XML file, the problem area looks like this:
    <E1BPE1MARAEXTRT SEGMENT="1">
          <FUNCTION>004</FUNCTION>
          <MATERIAL>000000000000895649</MATERIAL>
          <b><FIELD1>
            BIK</b>      0  0.00 T                                    000000001CARRERA FURY 04 20"     CARRERA FURY 04 20" 2005092420040622    X                    00000000   20031104 00200406140000000000                    0.00 0000000
          </FIELD1>
    You can't really see it above, but there is a carriage return and 8 white spaces before the BIK. Where does this carriage return and white space come from?! Any help would be really appreciated - this is driving me crazy!
    Many thanks,
    Stuart Richards

    Stuart,
    I think I know the cause to your problem. I am not an XSLT programmer but based on searching this forum I found how I can acheive the carriage return at the end of my document. Your xsl statement is as follows:
    <xsl:output method="xml" encoding="UTF-8" omit-xml-declaration="no" indent="yes"/>
    Change the indent value from yes to no. This should remove the carraige return. Hope this works for you.
    I actually need a carriage return and line feed on my document so I am still stuck. All I have acheived is the carraige return.
    Thanks,
    Jim

  • I can't get rid of white space between images (even when margins are 0)

    I'd like the user to be able to add two images that actually touch. I've set up 2 image fields that are touching, and set the margins to 0, but there is still white space in between the user added pictures.
    I thought maybe the problem had something to do with borders, but when i click the borders palette, it tells me "these properties are not available for forms that contain background artwork".
    Any help is appreciated.

    The behavior only appears if you create a static form.
    I saw an old thread about it here in the forums, you have commented too.
    It probably will never get changed or nobody have ever send a bug report about this to Adobe.
    http://forums.adobe.com/message/4927663#4927663
    I never had such problem with image fields in dynamic forms.
    And I almost never build static forms from existing PDF files, as those forms are too limited in — ahem — everything.

  • White space not preserved with XSL Mapping

    Hello
    Is there a problem with preserving white space when using a XSL mapping? My schema has the following included:
                  <xs:element name="FileVersion" minOccurs="1" maxOccurs="1">
                    <xs:simpleType>
                      <xs:restriction base="xs:string">
                        <xs:length value="5"/>
                        <xs:whiteSpace value="preserve"/>
                      </xs:restriction>
                    </xs:simpleType>
                  </xs:element>             
    The whiteSpace attribute alone didn't do it, so I've added length as well which didn't help either.
    My imported XSL mapping writes a fix value of " 6.00" (having a leading space) into the field:
         <FileVersion>
              <xsl:value-of select="' 6.00'"/>
         </FileVersion>
    Processing the mapping with an external tool provides the correct output with a leading space.
    The leading space is missing in the output file or when I do testing in the integration builder. Looking at the target payload in sxmb_moni also shows me the value without leading space:
      <FileVersion>6.00</FileVersion>
    What do I miss? I haven't really found a posting regarding the issue, hence I assume it isn't really one!? Any feedback is appreciated.
    Thanks,
    Daniel

    My XSLT mapping does not have a preserve-space declaration. I am using Altova MapForce, and apparently preserve-space is not a declaration that is supported by MapForce. I would need to manually add it to the mapping after generating it in the tool. Nevertheless, isn't preserve-space the default anyway if nothing is declared, and therefore not necessary?.

  • JDeveloper Error: White spaces are required between publicId and systemId.

    I'm using JDeveloper 10.1.3.1.0.
    This error is occurring in a BPEL process project.
    With one particular web service I have, adding a Partner Link to the BPEL generates the following compile error:
    Error: White spaces are required between publicId and systemId.
    I can add Partner links from other web services and the BPEL will compile fine. The main difference I can see is that this web service supports WS-Addressing.
    I have found one other reference to a similar (but not exactly the same) problem elsewhere in these forums but the fix is not really applicable. All of the wsdl files pass the "Validate WSDL" operation, and I don't see anything wrong with them.
    When the error occurs and I select "Go To Source" it points back to the first line of the bpel file.
    Can anyone help me out on this?
    This is the wsdl for the web service, wsademo.wsdl:
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions name="wsademo"
    targetNamespace="http://localhost:11001/wsademo.wsdl"
    xmlns:tns="http://localhost:11001/wsademo.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:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
    xmlns:ns="http://localhost:11001/wsademo.wsdl"
    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="http://localhost:11001/wsademo.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:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
    xmlns:ns="http://localhost:11001/wsademo.wsdl"
    xmlns="http://www.w3.org/2001/XMLSchema"
    elementFormDefault="unqualified"
    attributeFormDefault="unqualified">
    <import namespace="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
    <import namespace="http://www.w3.org/2003/05/soap-encoding"/>
    <!-- operation request element -->
    <element name="wsademoResult">
    <complexType>
    <sequence>
    <element name="out" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true"/>
    </sequence>
    </complexType>
    </element>
    <!-- operation request element -->
    <element name="wsademo">
    <complexType>
    <sequence>
    <element name="in" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true"/>
    </sequence>
    </complexType>
    </element>
    <!-- operation response element -->
    <element name="wsademoResult">
    <complexType>
    <sequence>
    <element name="out" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true"/>
    </sequence>
    </complexType>
    </element>
    </schema>
    </types>
    <message name="wsademoResult">
    <part name="parameters" element="ns:wsademoResult"/>
    </message>
    <message name="wsademo">
    <part name="parameters" element="ns:wsademo"/>
    </message>
    <message name="wsademoResult">
    <part name="parameters" element="ns:wsademoResult"/>
    </message>
    <message name="wsademoHeader">
    <part name="MessageID" element="wsa:MessageID"/>
    <part name="RelatesTo" element="wsa:RelatesTo"/>
    <part name="From" element="wsa:From"/>
    <part name="ReplyTo" element="wsa:ReplyTo"/>
    <part name="FaultTo" element="wsa:FaultTo"/>
    <part name="To" element="wsa:To"/>
    <part name="Action" element="wsa:Action"/>
    </message>
    <portType name="wsademoPort">
    <operation name="wsademoResult">
    <documentation>accepts a string value from a relayed response</documentation>
    <input message="tns:wsademoResult"/>
    </operation>
    <operation name="wsademo">
    <documentation>echos a string value and relays the response to the wsa replyTo address (if present)</documentation>
    <input message="tns:wsademo"/>
    <output message="tns:wsademoResult"/>
    </operation>
    </portType>
    <binding name="wsademo" type="tns:wsademoPort">
    <SOAP:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="wsademoResult">
    <SOAP:operation soapAction="urn:wsademo/wsademoPort/wsademoResult"/>
    <input>
    <SOAP:body parts="parameters" use="literal"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="Action"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="To"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="FaultTo"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="ReplyTo"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="From"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="RelatesTo"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="MessageID"/>
    </input>
    </operation>
    <operation name="wsademo">
    <SOAP:operation soapAction="urn:wsademo/wsademoPort/wsademo"/>
    <input>
    <SOAP:body parts="parameters" use="literal"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="Action"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="To"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="FaultTo"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="ReplyTo"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="From"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="RelatesTo"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="MessageID"/>
    </input>
    <output>
    <SOAP:body parts="parameters" use="literal"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="Action"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="To"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="FaultTo"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="ReplyTo"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="From"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="RelatesTo"/>
    <SOAP:header use="literal" message="tns:wsademoHeader" part="MessageID"/>
    </output>
    </operation>
    </binding>
    <service name="wsademo">
    <documentation>demonstrates WS-Addressing capabilities</documentation>
    <port name="wsademo" binding="tns:wsademo">
    <SOAP:address location="http://localhost:11001"/>
    </port>
    </service>
    </definitions>
    This is the wsdl that is generated by JDeveloper that contains the PartnerLinks and refernce back to the original wsdl file, wsademoRef.wsdl:
    <definitions
    name="wsademo"
    targetNamespace="http://localhost:11001/wsademo.wsdl"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:tns="http://localhost:11001/wsademo.wsdl"
    xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    >
    <import namespace="http://localhost:11001/wsademo.wsdl" location="wsademo.wsdl"/>
    <plnk:partnerLinkType name="wsademoPort_PL">
    <plnk:role name="wsademoPort_Role">
    <plnk:portType name="tns:wsademoPort"/>
    </plnk:role>
    </plnk:partnerLinkType>
    </definitions>
    And finally the is the BPEL, WSAtest3.bpel:
    <?xml version="1.0" encoding="UTF-8"?>
    <!--
    Oracle JDeveloper BPEL Designer
    Created: Thu Oct 05 15:27:12 GMT-08:00 2006
    Author: wstielau
    Purpose: Synchronous BPEL Process
    -->
    <process name="WsaTest3" targetNamespace="http://xmlns.oracle.com/WsaTest3"
    xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
    xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
    xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
    xmlns:ns1="http://localhost:11001/wsademo.wsdl"
    xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:ns2="http://localhost:80/Service.wsdl"
    xmlns:client="http://xmlns.oracle.com/WsaTest3"
    xmlns:bpelx="http://schemas.oracle.com/bpel/extension/"
    xmlns:ora="http://schemas.oracle.com/xpath/extension"
    xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc">
    <!--
    PARTNERLINKS
    List of services participating in this BPEL process
    -->
    <partnerLinks>
    <!--
    The 'client' role represents the requester of this service. It is
    used for callback. The location and correlation information associated
    with the client role are automatically set using WS-Addressing.
    -->
    <partnerLink name="client" partnerLinkType="client:WsaTest3"
    myRole="WsaTest3Provider"/>
    <partnerLink name="wsademo" partnerLinkType="ns1:wsademoPort_PL"
    myRole="wsademoPort_Role" partnerRole="wsademoPort_Role"/>
    </partnerLinks>
    <!--
    VARIABLES
    List of messages and XML documents used within this BPEL process
    -->
    <variables>
    <!-- Reference to the message passed as input during initiation -->
    <variable name="inputVariable" messageType="client:WsaTest3RequestMessage"/>
    <!-- Reference to the message that will be returned to the requester-->
    <variable name="outputVariable"
    messageType="client:WsaTest3ResponseMessage"/>
    <variable name="Invoke_1_wsademo_InputVariable" messageType="ns1:wsademo"/>
    <variable name="Invoke_1_wsademo_OutputVariable"
    messageType="ns1:wsademoResult"/>
    </variables>
    <!--
    ORCHESTRATION LOGIC
    Set of activities coordinating the flow of messages across the
    services integrated within this business process
    -->
    <sequence name="main">
    <!-- Receive input from requestor. (Note: This maps to operation defined in WsaTest3.wsdl) -->
    <receive name="receiveInput" partnerLink="client" portType="client:WsaTest3"
    operation="process" variable="inputVariable" createInstance="yes"/>
    <!-- Generate reply to synchronous request -->
    <assign name="Assign_1">
    <copy>
    <from variable="inputVariable" part="payload"
    query="/client:WsaTest3ProcessRequest/client:input"/>
    <to variable="Invoke_1_wsademo_InputVariable" part="parameters"/>
    </copy>
    </assign>
    <invoke name="Invoke_1" partnerLink="wsademo" portType="ns1:wsademoPort"
    operation="wsademo" inputVariable="Invoke_1_wsademo_InputVariable"
    outputVariable="Invoke_1_wsademo_OutputVariable"/>
    <assign name="Assign_2">
    <copy>
    <from variable="Invoke_1_wsademo_OutputVariable" part="parameters"/>
    <to variable="outputVariable" part="payload"
    query="/client:WsaTest3ProcessResponse/client:result"/>
    </copy>
    </assign>
    <reply name="replyOutput" partnerLink="client" portType="client:WsaTest3"
    operation="process" variable="outputVariable"/>
    </sequence>
    </process>
    -Wayne Stielau
    Open Text Corporation
    Irvine, CA

    I have discovered two issues.
    1. JDeveloper does not seem to like the SOAP 1.2 envelope and encoding namespaces. Is this a known limitation? Changed them to 1.1.
    2. JDeveloper does not like the double definition of wsaDemoResult.
    When these two items are changed, the bpel compiles clean. Now I've got to get the message header to populate correctly. There are no values assigned, only namespace definitions. This is the SOAP packet that is received at the web service.
    <?xml version="1.0" encoding="UTF-8"?>
    <env:Envelope
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <env:Header>
    <MessageID xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
    <From xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
    <RelatesTo xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
    <Action xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
    <ReplyTo xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
    <To xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
    <FaultTo xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing"/>
    </env:Header>
    <env:Body>
    <wsademo xmlns="http://localhost:11001/wsademo.wsdl">
    <in xmlns="">hello</in>
    </wsademo>
    </env:Body>
    </env:Envelope>

Maybe you are looking for

  • How to print a report directly on printer

    Hi, anyone, plz help me in finding out, why my report i.e. i m sending directly to printer is getting printed like html codes? Plz help asap. Br, Divya Alok

  • I pad not recognized by pc ....... Help.... Please.

    Hi to all my I pad 3 will not be recognized by my pc I have temporarily disabled my anti virus , and re booted both & made sure all drivers are up to date . I have made sure iTunes is the latest version & changed USB ports ...... Man I'm getting frus

  • GR is not posible in an inbound delivery that contains nested HU

    Hi!!! I need your halep!!! I have the next problem in a cross company process:. When the outbound delivery ( that contains nested HU), the good issue is posted, an inbound delivery is created (using a standard workfolw that is used to transfer the ou

  • CSS layout problems in IE

    DW8 In IE, this web page looks "squished." In FF and NS, it looks wonderful. This is the work of a student of mine and I would like to give a semi-intelligent answer as to why it's behaving as it does in IE. I am teaching a beginner's level of DW and

  • Speakerphone dynamics.....Just a thought.

    I wonder - is the volume problem with the speaker phone Apples way of handling feedback? With my limited experience with sound reinforcement depending on where you set a mic and a speaker and what they are facing could change their characteristics. W