Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » BPEL Designer » copy rule not checked for literals
copy rule not checked for literals [message #1424386] Mon, 15 September 2014 22:52
Sergei Karimov is currently offline Sergei KarimovFriend
Messages: 14
Registered: July 2009
Junior Member
Hi All!
I wonder when this will be resolved.
I have a following code
<bpel:assign validate="no" name="assignName">
  <bpel:copy>
    <bpel:from>
      <bpel:literal><ns0:createOrder>...</ns0:createOrder></bpel:literal>
    </bpel:from>
    <bpel:to variable="CreateOrderRequest" part="parameters" />
  </bpel:copy>
</bpel:assign>

This code generates warning of type info:
Copy rule not checked - from-spec type-of "unspecified", to-spec type-of "<xs:complexType>"

So basically there is no way to avoid warnings for the simplest hello world process.
Because you can't send any SOAP message without first initializing variable.
You are encouraging developer to just hide all warnings/infos and forget about such feature

    1. As it's not a CDATA section why compiler can't validate this piece of xml using wsdl? Can't you just wrap this xml with SOAP envelope and validate with wsdl?
    2. Is there no other way to construct SOAP message with strict validation? All tutorials suggest to use copy from xml literal (or initialize from xml literal which is the same basically). Maybe I can change wsdl/bpel somehow to enable strict validation?

[Updated on: Mon, 15 September 2014 22:55]

Report message to a moderator

Previous Topic:BPEL working from home, not working from office (same laptop, no changes)
Next Topic:Unknown Error
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Mon Nov 19 13:07:48 GMT 2018

Powered by FUDForum. Page generated in 0.01866 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly