Babel Pseudo Translations Index for technology.bpel

Version: 3.7.0.v20110723043401

technology.bpel602164 www.example.org
technology.bpel602171 Apache ODE Runtime Adapter
technology.bpel602173 ODE's home directory:
technology.bpel602174 Tomcat's home directory:
technology.bpel602175 Port:
technology.bpel680804 Server address:
technology.bpel680805 VM Arguments:
technology.bpel680830 File Deleted
technology.bpel680831 Could not find editor\: {0}
technology.bpel680832 Multiple content providers for marker type {0}
technology.bpel680833 Marker not subtype of graphicalMarker
technology.bpel680834 Could not instantiate marker content provider from the extension {0}
technology.bpel680835 Marker content provider with null markerType from the extension {0}
technology.bpel680836 There are {0} issues here:
technology.bpel680837 The file has been deleted from the file system. Do you want to save your changes or close the editor ...
technology.bpel680838 &Today
technology.bpel680839 The files {0} can not be changed. {1}
technology.bpel680840 The file {0} can not be changed. {1}
technology.bpel680841 The editor is not connected to this composite editor.
technology.bpel680842 Saving...
technology.bpel680843 ...
technology.bpel680844 The active editor cannot be removed
technology.bpel680845 Can not change files.
technology.bpel680846 &No Date
technology.bpel680847 {0} {1}
technology.bpel680848 File Changed
technology.bpel680849 Cannot disconnect active editor\: {0}
technology.bpel680850 The file {0} \n\ has been changed on the file system.\n\ Do you want to load the changes?
technology.bpel680851 Save
technology.bpel680852 Embedded editors must provide an id. Ignoring editor.
technology.bpel680853 None
technology.bpel680854 BPEL Graphical Markers
technology.bpel680855 BPEL Model Markers
technology.bpel680856 BPEL Text Markers
technology.bpel602187 BPEL Model
technology.bpel680883 Empty
technology.bpel680884 Switch
technology.bpel680885 Flow
technology.bpel680886 Pick
technology.bpel680887 OnMessage
technology.bpel680888 OnAlarm
technology.bpel680889 Partner Link
technology.bpel680890 While
technology.bpel680891 Variable
technology.bpel680892 Event Handler
technology.bpel680893 OnEvent
technology.bpel680894 Fault Handler
technology.bpel680895 Compensation Handler
technology.bpel680896 Catch
technology.bpel680897 Catch All
technology.bpel680898 Invoke
technology.bpel680899 Receive
technology.bpel680900 Reply
technology.bpel680901 Wait
technology.bpel680902 Sequence
technology.bpel680903 Scope
technology.bpel680904 Terminate
technology.bpel680905 Throw
technology.bpel680906 Rethrow
technology.bpel680907 Compensate
technology.bpel680908 Assign
technology.bpel602192 BPEL module file resource must end with bpel file extension.
technology.bpel602193 New BPEL Project
technology.bpel602194 Create a new BPEL 2.0 project.
technology.bpel602195 Eclipse BPEL Designer Runtimes
technology.bpel602197 BPEL 2.0 Process
technology.bpel602198 Module representing a BPEL process
technology.bpel602199 BPEL 2.0 Facet
technology.bpel602200 Enables modelling and deployment of BPEL processes.
technology.bpel602201 BPEL 2.0
technology.bpel602202 BPEL 2.0 Project
technology.bpel602203 BPEL 2.0
technology.bpel602204 BPEL Project
technology.bpel602205 Create a new BPEL project.
technology.bpel602218 Default Text
technology.bpel602233 Start counter value
technology.bpel602234 Final counter value
technology.bpel602235 Counter variable name
technology.bpel602236 Condition
technology.bpel602237 Language
technology.bpel602238 Partner Link
technology.bpel602239 Operation
technology.bpel602240 Input
technology.bpel602241 Output
technology.bpel602242 My Role
technology.bpel602243 Partner Role
technology.bpel602244 None
technology.bpel602245 Error
technology.bpel602246 Press 'Ctrl+Space' to show Function Proposals
technology.bpel602247 Press 'Ctrl+Space' to show Operator Proposals
technology.bpel602248 Press 'Ctrl+Space' to show Template Proposals
technology.bpel602249 Press 'Ctrl+Space' to show Link Proposals
technology.bpel602250 Press 'Ctrl+Space' to show Variable Proposals
technology.bpel602251 No proposals
technology.bpel602252 Drop Problem
technology.bpel602253 {0} drop(s) could not be processed:\n\n\ {1}\n\n\ Hint: You can drop XSD and WSDL resources (files ...
technology.bpel602254 &Variable Picker ...
technology.bpel602255 BPEL Variable Picker
technology.bpel602256
technology.bpel602257 Pick a variable from variable picker.
technology.bpel602258 Choose a variable from tree
technology.bpel602259 Action Category\:
technology.bpel602260 Choose one of these actions\:
technology.bpel602261 &Description\:
technology.bpel602262 <HTML>Hover the mouse over the action buttons<br>to see the description.</HTML>
technology.bpel602263 Hover the mouse over the action buttons to see the description.
technology.bpel602264 Add a {0}
technology.bpel602265 <H3>Assign</H3><DIV><P>Use this activity to copy some form of information fr ...
technology.bpel602266 &Delete
technology.bpel602267 Fr&om\:
technology.bpel602268 &New
technology.bpel602269 &To\:
technology.bpel602270 &Keep Source Element Name
technology.bpel602271 &Ignore Missing Source Data
technology.bpel602272 &Validate
technology.bpel602273 E&xpression language\:
technology.bpel602274 &Query language\:
technology.bpel602275 Arrange Flow Contents
technology.bpel602276 Auto-arrange Flow Contents
technology.bpel602277 Switch to horizontal layout
technology.bpel602278 Switch to vertical layout
technology.bpel602279 Copy
technology.bpel602280 Copy
technology.bpel602281 Copy
technology.bpel602282 Duplicate
technology.bpel602283 Duplicate
technology.bpel602284 Cut
technology.bpel602285 Cut
technology.bpel602286 Cut
technology.bpel602287 Drag
technology.bpel602288 Rename error
technology.bpel602289 {0}\: {1} Please enter a different name.
technology.bpel602290 Enter a new name.
technology.bpel602291 Rename
technology.bpel602292 Could not create an edit part for {0}.
technology.bpel602293 Opaque Activity
technology.bpel602294 Opaque Activity
technology.bpel602295 Assign
technology.bpel602296 Assign
technology.bpel602297 Validate
technology.bpel602298 Validate
technology.bpel602299 Bottom Control Group
technology.bpel602300 Error opening editor. Can't read input file.
technology.bpel602301 Compensate
technology.bpel602302 Compensate
technology.bpel602303 CompensateScope
technology.bpel602304 CompensateScope
technology.bpel602305 Flow
technology.bpel602306 Flow
technology.bpel602307 Invoke
technology.bpel602308 Invoke
technology.bpel602309 Marquee Tool
technology.bpel602310 Pick
technology.bpel602311 Pick
technology.bpel602312 Rethrow
technology.bpel602313 Rethrow
technology.bpel602314 Receive
technology.bpel602315 Receive
technology.bpel602316 Reply
technology.bpel602317 Reply
technology.bpel602318 Scope
technology.bpel602319 Scope
technology.bpel602320 Selection Tool
technology.bpel602321 Sequence
technology.bpel602322 Sequence
technology.bpel602323 If
technology.bpel602324 If
technology.bpel602325 Exit
technology.bpel602326 Exit
technology.bpel602327 Throw
technology.bpel602328 Throw
technology.bpel602329 Top Control Group
technology.bpel602330 Wait
technology.bpel602331 Wait
technology.bpel602332 While
technology.bpel602333 While
technology.bpel602334 For Each
technology.bpel602335 For Each
technology.bpel602336 Zoom In
technology.bpel602337 Zoom Out
technology.bpel602338 Repeat Until
technology.bpel602339 Repeat Until
technology.bpel602340 Add Correlation Set
technology.bpel602341 Add Partner Link
technology.bpel602342 Add Variable
technology.bpel602343 Add Message Exchange
technology.bpel602344 link1
technology.bpel602345 Paste
technology.bpel602346 Paste from Transfer Buffer
technology.bpel602347 Paste
technology.bpel602348 Expand the tree to edit preferences for the BPEL feature.
technology.bpel602349 Expand the tree to edit preferences for the Expression Editor.
technology.bpel602350 Use animation when laying out activities
technology.bpel602351 When Flows automatically lay out their child activities, animation will be used to bring about a smo ...
technology.bpel602352 Manual place activities in the Flow node
technology.bpel602353 Placement of elements within a Flow will be done manually.
technology.bpel602354 Warn on links
technology.bpel602355 Warn when links are being used in the process
technology.bpel602356 Layout Flow children automatically
technology.bpel602357 The editor will layout the children of the Flow activity automatically.
technology.bpel602358 Create Spec compliant process
technology.bpel602359 Do not allow non-spec compliant constructs in the process, warn during validation.
technology.bpel602360 Document URL:
technology.bpel602361 Browse ...
technology.bpel602362 Abstract
technology.bpel602363 Ref Namespace
technology.bpel602364 Location
technology.bpel602365 Add
technology.bpel602366 Remove
technology.bpel602367 #
technology.bpel602368 WSIL Document not loaded.
technology.bpel602369 WSIL Document's name should be ended with .wsil
technology.bpel602370 Move Down
technology.bpel602371 Move Up
technology.bpel602372 Open in Browser
technology.bpel602373 <enter description>
technology.bpel602374 <enter location>
technology.bpel602375 \ The document above contains links to other WSIL documents shown below.\n\ You can add or remove WS ...
technology.bpel602376 Expression language editors must provide expressionLanguage and class.
technology.bpel602377 <unknown URI>
technology.bpel602378 HiddenSequence
technology.bpel602379 Sequence
technology.bpel602380 Not a valid NCName
technology.bpel602381 Variable
technology.bpel602382 Add Part
technology.bpel602383 Move Part
technology.bpel602384 Else If
technology.bpel602385 Create a New Condition
technology.bpel602386 To create a valid BPEL process you should specify a condition.\nChoose the type of condition from th ...
technology.bpel602387 This ElseIf currently does not have a condition specified.
technology.bpel602388 Catch
technology.bpel602389 Catch All
technology.bpel602390 The Catch All will be executed if the Fault is not caught by an existing Catch.
technology.bpel602391 Change type to {0}
technology.bpel602392 &Target Activity\:
technology.bpel602393 Compensation Handlers
technology.bpel602394 &Add...
technology.bpel602395 E&dit...
technology.bpel602396 Proper&ties\:
technology.bpel602397 Property
technology.bpel602398 &Remove
technology.bpel602399 &Add
technology.bpel602400 Both
technology.bpel602401 Correlation Set
technology.bpel602402 Correlat&ion Sets\:
technology.bpel602403 Direction
technology.bpel602404 Initiation
technology.bpel602405 Join
technology.bpel602406 No
technology.bpel602407 Receive
technology.bpel602408 Receive
technology.bpel602409 &Remove
technology.bpel602410 Send
technology.bpel602411 Yes
technology.bpel602412 Correlation Set
technology.bpel602413 Correlation Sets
technology.bpel602414 Add Correlation Set
technology.bpel602415 Correlation Sets
technology.bpel602416 Remove Correlation Set
technology.bpel602417 Add ElseIf
technology.bpel602418 Add Catch
technology.bpel602419 Add Catch All
technology.bpel602420 Add Compensation Handler
technology.bpel602421 Add Event Handler
technology.bpel602422 Add Fault Handler
technology.bpel602423 Add Link
technology.bpel602424 Create a ne&w Process instance if one does not already exist
technology.bpel602425 Add OnAlarm
technology.bpel602426 Add OnEvent
technology.bpel602427 Add OnMessage
technology.bpel602428 Add Else
technology.bpel602429 Delete {0}
technology.bpel602430 Item
technology.bpel602431 Delete
technology.bpel602432 Delete
technology.bpel602433 Delete
technology.bpel602434 Delete {0} items
technology.bpel602435 &Source URI:
technology.bpel602436 &Language:
technology.bpel602437 &Description:
technology.bpel602438 Da&ys
technology.bpel602439 H&ours
technology.bpel602440 Minu&tes
technology.bpel602441 Mont&hs
technology.bpel602442 Se&conds
technology.bpel602443 Ye&ars
technology.bpel602444 Create Property
technology.bpel602445 Defined As
technology.bpel602446 Na&me\:
technology.bpel602447 Bro&wse...
technology.bpel602448 Message Type && Part
technology.bpel602449 Aliases
technology.bpel602450 N&ew...
technology.bpel602451 E&dit...
technology.bpel602452 &Remove
technology.bpel602453 Create Message Property
technology.bpel602454 Edit Message Property
technology.bpel602455 Part
technology.bpel602456 <none>
technology.bpel602457 \: {0}
technology.bpel602458 Simple Type
technology.bpel602459 Element
technology.bpel602460 Message Type
technology.bpel602461 Element
technology.bpel602462 Simple Type
technology.bpel602463 Type\:
technology.bpel602464 Element\:
technology.bpel602465 Message\:
technology.bpel602466 Edit Property Alias
technology.bpel602467 Create Property Alias
technology.bpel602468 Edit Property Alias
technology.bpel602469 &Part\:
technology.bpel602470 Create Property Alias
technology.bpel602471 End
technology.bpel602472 Endpoint Reference
technology.bpel602473 Event Handlers
technology.bpel602474 Exit on Standard Fault:
technology.bpel602475 &Yes
technology.bpel602476 &No
technology.bpel602477 Expression
technology.bpel602478 E&xpression language\:
technology.bpel602479 No Expression
technology.bpel602480 Same as Process ({0})
technology.bpel602481 Fault
technology.bpel602482 &Built-in
technology.bpel602483 Faul&t Name\:
technology.bpel602484 Faul&t Name\:
technology.bpel602485 Fault Type\:
technology.bpel602486 Na&mespace\:
technology.bpel602487 &User-defined
technology.bpel602488 Variable Name\:
technology.bpel602489 (none)
technology.bpel602490 Fault Handlers
technology.bpel602491 &Built-in
technology.bpel602492 Faul&t Name\:
technology.bpel602493 Faul&t Name\:
technology.bpel602494 Fault Type\:
technology.bpel602495 Fault &Variable\:
technology.bpel602496 Na&mespace\:
technology.bpel602497 &User-defined
technology.bpel602498 Br&owse...
technology.bpel602499 (none)
technology.bpel602500 Select Fault Variable
technology.bpel602501 Browse
technology.bpel602502 Create
technology.bpel602503 Activity Change
technology.bpel602504 Add Compensation Handler
technology.bpel602505 Add Termination Handler
technology.bpel602506 Add Copy
technology.bpel602507 Add Correlation
technology.bpel602508 Add Custom Property
technology.bpel602509 Add Custom Setting
technology.bpel602510 Add Event Handler
technology.bpel602511 Add Fault Handler
technology.bpel602512 Add Import
technology.bpel602513 Add Link
technology.bpel602514 Add Partner Link
technology.bpel602515 Add Property
technology.bpel602516 Add Property Alias
technology.bpel602517 Add Role
technology.bpel602518 Add Variable
technology.bpel602519 Add Message Exchange
technology.bpel602520 Add Variable to Validate
technology.bpel602521 Assign/Copy Change
technology.bpel602522 Assign/ValidateXML Change
technology.bpel602523 Auto Arrange
technology.bpel602524 {0} Change
technology.bpel602525 {0} Change
technology.bpel602526 Change BPEL File
technology.bpel602527 Compensate Link Change
technology.bpel602528 Correlation Change
technology.bpel602529 Create Instance Change
technology.bpel602530 Delete Copy
technology.bpel602531 Delete Correlation
technology.bpel602532 Delete Link
technology.bpel602533 Delete Property
technology.bpel602534 Delete Property Alias
technology.bpel602535 Delete Role
technology.bpel602536 Remove Validate Variable
technology.bpel602537 Exit on Standard Fault Change
technology.bpel602538 Expression Body Change
technology.bpel602539 Expression Change
technology.bpel602540 Expression Language Change
technology.bpel602541 Fault Name Change
technology.bpel602542 Fault Namespace Change
technology.bpel602543 Fault Variable Name Change
technology.bpel602544 Interface Change
technology.bpel602545 Join Failure Change
technology.bpel602546 Message Type Change
technology.bpel602547 Method Change
technology.bpel602548 Process Role Change
technology.bpel602549 Name Change
technology.bpel602550 Name Change
technology.bpel602551 Message Exchange Change
technology.bpel602552 Operation Change
technology.bpel602553 Partner Link Change
technology.bpel602554 Partner Link Change
technology.bpel602555 Partner Link Role Change
technology.bpel602556 Interface Change
technology.bpel602557 Process Type Change
technology.bpel602558 Property Change
technology.bpel602559 Query Language Change
technology.bpel602560 Remove Client Settings
technology.bpel602561 Remove Custom Property
technology.bpel602562 Remove Custom Settings
technology.bpel602563 Remove Import
technology.bpel602564 Remove Property
technology.bpel602565 Reposition
technology.bpel602566 Resize
technology.bpel602567 Scope Compensable Change
technology.bpel602568 Scope Serialization Change
technology.bpel602569 Specification Compliance Change
technology.bpel602570 Target namespace Change
technology.bpel602571 Variable Change
technology.bpel602572 Variable Type Change
technology.bpel602573 Variable Type Change
technology.bpel602574 Parallel Execution Change
technology.bpel602575 Counter Variable Name Change
technology.bpel602576 Count Successful Branches Only Change
technology.bpel602577 Insert Copy
technology.bpel602578 Swap Copy
technology.bpel602579 Location
technology.bpel602580 Namespace
technology.bpel602581 &Imports\:
technology.bpel602582 Add {0}
technology.bpel602583 Add Node
technology.bpel602584 Node
technology.bpel602585 Insert a {0}
technology.bpel602586 <H3>Invoke</H3><DIV><P>Use this activity to perform an operation.</DIV> ...
technology.bpel602587 Fault Name\:
technology.bpel602588 &Operation\:
technology.bpel602589 Par&tner Link\:
technology.bpel602590 Request
technology.bpel602591 Response
technology.bpel602592 (none)
technology.bpel602593 Create Global Partner Link.
technology.bpel602594 Create Local Partner Link.
technology.bpel602595 Clear Partner Link.
technology.bpel602596 Effective Port Type:
technology.bpel602597 Click to edit Port Type.
technology.bpel602598 &Input Variable:
technology.bpel602599 Create Global Input Variable.
technology.bpel602600 Create Local Input Variable.
technology.bpel602601 Clear Input Variable
technology.bpel602602 &Output Variable:
technology.bpel602603 Create Global Output Variable
technology.bpel602604 &Input Variable:
technology.bpel602605 &Variable:
technology.bpel602606 Edit WSDL.
technology.bpel602607 Clear Fault Name
technology.bpel602608 &Create a New Condition
technology.bpel602609 This activity currently does not have a join condition specified.
technology.bpel602610 Join conditions are optional. If you don't specify this\njoin condition, it will evaluate to the lo ...
technology.bpel602611 &No
technology.bpel602612 Suppress Join Failure\:
technology.bpel602613 Use Same Value as P&arent (No)
technology.bpel602614 Use Same Value as &Parent (Yes)
technology.bpel602615 &Use Same Value as Parent
technology.bpel602616 &Yes
technology.bpel602617 Link
technology.bpel602618 Fixed Value
technology.bpel602619 The fixed value you entered does not appear to be valid XML (which is required for some types of fix ...
technology.bpel602620 Warning
technology.bpel602621 Make Partner Link two-way
technology.bpel602622 Message
technology.bpel602623 Message Exchanges
technology.bpel602624 messageExchanges
technology.bpel602625 messageExchange
technology.bpel602626 Add Message Exchange
technology.bpel602627 Remove Message Exchange
technology.bpel602628 Message Exchange:
technology.bpel602629 Create Global Message Exchange
technology.bpel602630 Create Local Message Exchange
technology.bpel602631 Clear Message Exchange
technology.bpel602632 Create Message Exchange
technology.bpel602633 Message Exchange Name
technology.bpel602634 -- None --
technology.bpel602635 {0} \: {1}
technology.bpel602636 N&ame\:
technology.bpel602637 Set Namespace Prefix
technology.bpel602638 BPEL Namespace Mappings
technology.bpel602639 Target Namespace:
technology.bpel602640 Prefix Name:
technology.bpel602641 Prefix name is not valid.
technology.bpel602642 This prefix is already used.
technology.bpel602643 Element "{0}" already exists.
technology.bpel602644 Tar&get namespace\:
technology.bpel602645 -- None --
technology.bpel602646 -- None --
technology.bpel602647 OnAlarm
technology.bpel602648 OnEvent
technology.bpel602649 OnMessage
technology.bpel602650 An opaque value is used in abstract processes.
technology.bpel602651 Opaque
technology.bpel602652 Operation
technology.bpel602653 {0} - {1}
technology.bpel602654 Else
technology.bpel602655 The Else will be executed if all If and ElseIf conditions are false.
technology.bpel602656 Part
technology.bpel602657 <none>
technology.bpel602658 {0} \: {1}
technology.bpel602659 Partner Link
technology.bpel602660 {0} - {1}
technology.bpel602661 Browse...
technology.bpel602662 Partner Link Type:
technology.bpel602663 Click to edit this partnerLinkType.
technology.bpel602664 My Role
technology.bpel602665 None
technology.bpel602666 Initialize Role
technology.bpel602667 Partner Role
technology.bpel602668 None
technology.bpel602669 My Operations:
technology.bpel602670 Partner Operations:
technology.bpel602671 (None)
technology.bpel602672 Unspecified
technology.bpel602673 <none>
technology.bpel602674 Select a Partner Link
technology.bpel602675 Partner Link Name (? \= any character, * \= any String)\:
technology.bpel602676 Matches\:
technology.bpel602677 Interface\:
technology.bpel602678 New Partner Link
technology.bpel602679 Partner Link Name
technology.bpel602680 Choose Partner Role
technology.bpel602681 Choose My Role
technology.bpel602682 Partner Link Type
technology.bpel602683 Partner Links
technology.bpel602684 Add Partner Link
technology.bpel602685 Remove Partner Link
technology.bpel602686 {0} - {1}
technology.bpel602687 Partner Links
technology.bpel602688 ShowPortTypes
technology.bpel602689 Choose Partner Link Type
technology.bpel602690 Partner Link Type Structure:
technology.bpel602691 Show Partner Link Types
technology.bpel602692 Object selected must be either a partnerLinkType or portType
technology.bpel602693 Show Port Types
technology.bpel602694 Add WSDL
technology.bpel602695 Partner Link Change
technology.bpel602696 Partner Link Reference
technology.bpel602697 Role Change
technology.bpel602698 Role\:
technology.bpel602699 Interface
technology.bpel602700 Process
technology.bpel602701 Add
technology.bpel602702 Change Type
technology.bpel602703 Insert Before
technology.bpel602704 Property
technology.bpel602705 Matches\:
technology.bpel602706 (none)
technology.bpel602707 Property Name (? \= any character, * \= any String)\:
technology.bpel602708 Property Type\:
technology.bpel602709 Select a Property
technology.bpel602710 <H3>Receive</H3><DIV><P>The first activity in any process, the receive activ ...
technology.bpel602711 Reference Partners
technology.bpel602712 Add Reference Partner Link
technology.bpel602713 Remove Reference Partner Link
technology.bpel602714 Rename
technology.bpel602715 Rename
technology.bpel602716 Reorder
technology.bpel602717 Choose the type of Repeat condition from the Combo Box above, or click\nthe button below to create a ...
technology.bpel602718 &Create a New Repeat Condition
technology.bpel602719 This OnAlarm currently does not have a Repeat condition specified.
technology.bpel602720 Repeat conditions are only supported for an OnAlarm in an Event Handler.
technology.bpel602721 Replace
technology.bpel602722 <H3>Reply</H3><DIV><P>Use this activity to return a message to the partner t ...
technology.bpel602723 Revert
technology.bpel602724 Rever&t
technology.bpel602725 Role
technology.bpel602726 Interface
technology.bpel602727 Error
technology.bpel602728 New...
technology.bpel602729 No elements were selected. Please select one or press the Cancel button.
technology.bpel602730 Change
technology.bpel602731 Change to "{0}"
technology.bpel602732 Set Compensate Link
technology.bpel602733 Change
technology.bpel602734 Set Partner Link
technology.bpel602735 Set Request Variable
technology.bpel602736 Set Response Variable
technology.bpel602737 Select Request Variable
technology.bpel602738 Select Response Variable
technology.bpel602739 Simple Action
technology.bpel602740 Start
technology.bpel602741 Edit field
technology.bpel602742 Align Flow Contents Automatically
technology.bpel602743 Align activities in Flows automatically
technology.bpel602744 Show Compensation Handler
technology.bpel602745 Shows termination handler activities
technology.bpel602746 Show Termination Handler
technology.bpel602747 Shows compensation handler activities
technology.bpel602748 Show Event Handler
technology.bpel602749 Shows event handler activities
technology.bpel602750 Show Fault Handler
technology.bpel602751 Shows fault handler activities
technology.bpel602752 &Create a New Condition
technology.bpel602753 This Link currently does not have a transition condition specified.
technology.bpel602754 Transition conditions are optional. A Link with no transition\ncondition specified will always eval ...
technology.bpel602755 I&solated
technology.bpel602756 &Query\:
technology.bpel602757 Variable
technology.bpel602758 Property of a Variable
technology.bpel602759 Matches\:
technology.bpel602760 New Variable
technology.bpel602761 (none)
technology.bpel602762 Variable Name
technology.bpel602763 Variable Name (? \= any character, * \= any String)\:
technology.bpel602764 Variable Type\:
technology.bpel602765 Browse...
technology.bpel602766 Browse...
technology.bpel602767 &Data Type
technology.bpel602768 Data Type\:
technology.bpel602769 Direction\:
technology.bpel602770 Fault
technology.bpel602771 Fault\:
technology.bpel602772 Input
technology.bpel602773 &Interface
technology.bpel602774 Interface\:
technology.bpel602775 (None)
technology.bpel602776 Element Type:
technology.bpel602777 Message Type:
technology.bpel602778 Structure:
technology.bpel602779 Click to edit this variable type.
technology.bpel602780 {0} - {1}
technology.bpel602781 Operation\:
technology.bpel602782 Output
technology.bpel602783 Variables
technology.bpel602784 Add Variable
technology.bpel602785 Remove Variable
technology.bpel602786 Variables
technology.bpel602787 &Create a New Condition
technology.bpel602788 To create a valid BPEL process you should specify a condition.\nChoose the type of condition from th ...
technology.bpel602789 &Date
technology.bpel602790 D&uration
technology.bpel602791 This object currently does not have a duration or deadline specified.
technology.bpel602792 &Create a New Condition
technology.bpel602793 To create a valid BPEL process you should specify a condition.\nChoose the type of condition from th ...
technology.bpel602794 This While currently does not have a condition specified.
technology.bpel602795 Counter &variable name\:
technology.bpel602796 &Parallel execution
technology.bpel602797 This ForEach currently does not have a completion condition specified.
technology.bpel602798 You may specify a completion condition to prevent some of the\nchildren from executing (in the seria ...
technology.bpel602799 &Create a New Condition
technology.bpel602800 Count &successful branches only
technology.bpel602801 This ForEach currently does not have a start counter value specified.
technology.bpel602802 This ForEach currently does not have a final counter value specified.
technology.bpel602803 Start Counter Value
technology.bpel602804 Final Counter Value
technology.bpel602805 To create a valid BPEL process you should specify an expression.\nChoose the type of expression from ...
technology.bpel602806 Create a New Expression
technology.bpel602807 Browse
technology.bpel602808 Select a WSDL File
technology.bpel602809 Date/Time (UTC)\:
technology.bpel602810 Duration\:
technology.bpel602811 Expression &Type\:
technology.bpel602812 Literal
technology.bpel602813 Text
technology.bpel602814 XSD Attribute
technology.bpel602815 XSD Element
technology.bpel602816 XSD Type
technology.bpel602817 Zoom in
technology.bpel602818 Zoom out
technology.bpel602819 Termination Handlers
technology.bpel602820 Add Termination Handler
technology.bpel602821 &Add
technology.bpel602822 &Remove
technology.bpel602823 Variables to validate:
technology.bpel602824 Select Variable
technology.bpel602825 Jan
technology.bpel602826 Feb
technology.bpel602827 Mar
technology.bpel602828 Apr
technology.bpel602829 May
technology.bpel602830 Jun
technology.bpel602831 Jul
technology.bpel602832 Aug
technology.bpel602833 Sep
technology.bpel602834 Oct
technology.bpel602835 Nov
technology.bpel602836 Dec
technology.bpel602837 Show in Properties
technology.bpel602838 Show Palette in Palette View
technology.bpel602839 Simple Type Definition
technology.bpel602840 Complex Type Definition
technology.bpel602841 Schema
technology.bpel602842 Schema targetNamespace={0}
technology.bpel602843 Schema
technology.bpel602844 Schema targetNamespace={0}
technology.bpel602845 Browse for an XML Schema to Import
technology.bpel602846 Import Source
technology.bpel602847 Resource
technology.bpel602848 File
technology.bpel602849 URL
technology.bpel602850 Location:
technology.bpel602851 Browse ...
technology.bpel602852 Browse for a WSDL to Import
technology.bpel602853 Select Resource to Import
technology.bpel602854 Available Types:
technology.bpel602855 Invalid location syntax.
technology.bpel602856 Ports and Partner Links:
technology.bpel602857 WSIL
technology.bpel602858 Filter by name
technology.bpel602859 Loading {0} ...
technology.bpel602860 Loaded {0} [{1}ms]
technology.bpel602861 Failed to load {0} [{1}ms]
technology.bpel602862 Choose type of variable
technology.bpel602863 Type Name (* or ? are wildcards):
technology.bpel602864 Type Structure:
technology.bpel602865 Show XSD Types
technology.bpel602866 Add Schema
technology.bpel602867 From Imports
technology.bpel602868 From Project
technology.bpel602869 From Workspace
technology.bpel602870 Primitives
technology.bpel602871 Simple Types
technology.bpel602872 Complex Types
technology.bpel602873 Element Declarations
technology.bpel602874 Messages
technology.bpel602875 Show Duplicates
technology.bpel602876 Import a &WSDL ...
technology.bpel602877 Import an &XSD ...
technology.bpel602878 &Remove
technology.bpel602879 Import Type
technology.bpel602880 Namespace Prefixes
technology.bpel602881 Prefix
technology.bpel602882 Namespace
technology.bpel602883 Scope
technology.bpel602884 Location
technology.bpel602885 Assign Prefix
technology.bpel602886 Name (* and ? are wildcards):
technology.bpel602887 Matches:
technology.bpel602888 Browse Source
technology.bpel602889 Filter
technology.bpel602890 Output Message
technology.bpel602891 Input Message
technology.bpel602892 Overview
technology.bpel602893 Outline
technology.bpel602894 Question
technology.bpel602895 Overwrite {0}?
technology.bpel602896 Error
technology.bpel602897 Can't save image to the file {0}
technology.bpel602898 Warning
technology.bpel602899 When you delete the PartnerLink -- ''{0}'', you may delete its reference PartnerLinkType -- ''{1}'' ...
technology.bpel602900 Error creating the editor Design Page.
technology.bpel602901 File Open Error
technology.bpel602902 Unable to open the input file.
technology.bpel602903 File Load Error
technology.bpel602904 Unable to load the BPEL file {0}\n It may be corrupt, do you want to continue?
technology.bpel602905 Unable to load the BPEL extensions file {0}\n It may be corrupt, do you want to continue?
technology.bpel602906 Unable to load the WSDL file {0}\n It may be corrupt, do you want to continue?
technology.bpel602907 File Delete Error
technology.bpel602908 Unable to delete the file. See Error Log for more information.
technology.bpel681683 Error
technology.bpel681684 Cannot open editor for null object
technology.bpel681685 Cannot open editor for object of type {0}
technology.bpel681686 Data caught by a Fault Handler must be a Message Type or an XSD Element
technology.bpel681687 Message Type\:
technology.bpel681688 Element\:
technology.bpel681689 Message/Element\:
technology.bpel681690 Warning
technology.bpel681691 Opaque activities are only used in Abstract Processes\n\ Would you like to convert this process ...
technology.bpel602909 New BPEL Process
technology.bpel602911 Create a BPEL Process File
technology.bpel602912 Create a 2.0 BPEL file.
technology.bpel602913 Process Details
technology.bpel602914 BPEL Process Name:
technology.bpel602915 Namespace:
technology.bpel602916 Template:
technology.bpel602917 Specify the name of this BPEL file.
technology.bpel602918 Abstract Process
technology.bpel602920 Select location for the BPEL source files.
technology.bpel602921 Select Project or Folder for the BPEL files.
technology.bpel602923 Select Files Location
technology.bpel602924 Name must not include a space.
technology.bpel602925 Namespace of the process cannot be empty.
technology.bpel602926 A BPEL file with this name already exists in the directory.
technology.bpel602928 Create a WSDL File
technology.bpel602929 Create a WSDL File for the BPEL Process
technology.bpel602930 WSDL Details
technology.bpel602931 Service Name
technology.bpel602932 Port Name
technology.bpel602933 Service Address
technology.bpel602934 Binding Protocol
technology.bpel602935 Specify a {0} for the BPEL process in the WSDL file.
technology.bpel602936 {0} must not include a space.
technology.bpel602937 The Binding Protocol must be 'SOAP' or 'HTTP'.
technology.bpel602938 Creating process from template ...
technology.bpel602939 Create Partner Link Type
technology.bpel602940 Create new Partner Link Type
technology.bpel602941 Type in the name of the partner link type.
technology.bpel602942 Create new Partner Link Type
technology.bpel602943 Define the 1st Role of this Partner Link Type.
technology.bpel602944 Create new Partner Link Type
technology.bpel602945 Define the 2nd Role of this Partner Link Type (Optional)
technology.bpel602946 Role Name:
technology.bpel602947 Port Type:
technology.bpel602948 This role will be undefined.
technology.bpel602949 Port type must be selected.
technology.bpel602950 The role names must have different names.
technology.bpel602951 Create new Partner Link Type
technology.bpel602952 Type in the name of the partner link type.
technology.bpel602953 Partner Link Type Name:
technology.bpel602954 Hint: The name of the partner link must be a valid NCName (Non-Qualified Name).
technology.bpel602955 Partner Link Type name is already used.
technology.bpel681692 The selected location is not a faceted project.
technology.bpel602956 BPEL Editor
technology.bpel602957 Business Process Editor
technology.bpel602958 Hoverhelp Helper
technology.bpel602959 Expression Language Editors
technology.bpel602960 Business Process
technology.bpel602961 Description
technology.bpel602962 Details
technology.bpel602963 Compensation
technology.bpel602964 Repeat
technology.bpel602965 Expiration
technology.bpel602966 Join Behavior
technology.bpel602967 Correlation
technology.bpel602968 Expressions
technology.bpel602969 Imports
technology.bpel602970 Counter Values
technology.bpel602971 Completion
technology.bpel602972 Initialization
technology.bpel602973 Documentation
technology.bpel602974 Message Exchange
technology.bpel602975 Namespaces
technology.bpel602976 XPath 1.0
technology.bpel602977 XPath 1.0 in BPEL 2.0
technology.bpel602978 UI Marker
technology.bpel602979 BPEL
technology.bpel602980 Editor
technology.bpel602981 WSIL Browser
technology.bpel602982 Expression Editors
technology.bpel602983 Templates
technology.bpel602984 Create a new Business Process
technology.bpel602985 Basic Actions
technology.bpel602986 Process
technology.bpel602987 Business Process
technology.bpel602989 New BPEL Process File
technology.bpel602990 Export BPEL as image...
technology.bpel602991 Export as Image...
technology.bpel602992 BPEL Editor (Incubation)
technology.bpel603004 Asynchronous BPEL Process
technology.bpel603011 Generates an empty BPEL process. Only receive and reply activities are \ placed in the process body ...
technology.bpel603012 empty
technology.bpel603013 Empty BPEL Process
technology.bpel603018 Generates a completely empty BPEL process. No partner links are generated. \ Only the basic skeleto ...
technology.bpel603022 Synchronous BPEL Process
technology.bpel603027 Generates an empty BPEL process. Only receive and reply activities are \ placed in the process body ...
technology.bpel681678 Drop File/URL Popup Template
technology.bpel681679 dropPopupTemplate
technology.bpel681680 drop.html
technology.bpel681681 ../popup.css
technology.bpel681682 This template is used to display a drop file/text confirmation \ when the user drops a file into th ...
technology.bpel603033 "BPEL activities" (assign,while,if,flow,...)
technology.bpel603034 Internal validator error has occurred.
technology.bpel603035 Internal validator error on <{0}> while running rule "{1}" - exception "{4}&quo ...
technology.bpel603036 You have found a bug. Send it in !
technology.bpel603037 org.eclipse.bpel.validator.rules.Factory, \ org.eclipse.bpel.validator.wsdl.Factory, \ org.eclip ...
technology.bpel603038 property
technology.bpel603039 variable
technology.bpel603040 message part
technology.bpel603041 from-spec
technology.bpel603042 to-spec
technology.bpel603043 unspecified
technology.bpel603044 The "{0}" attribute of this <{1}> is set to "{2}" - it is not a valid NCNa ...
technology.bpel603045 Set the "{0}" attribute to a valid NCName.
technology.bpel603046 No validator for <{0}>
technology.bpel603047 Unable to find validator for element <{0}> - it will not be checked.
technology.bpel603048 No fix for that.
technology.bpel603049 No activity in this <{0}>.
technology.bpel603050 There is no activity inside this <{0}> activity.
technology.bpel603051 Place an activity inside this <{0}> or remove it.
technology.bpel603052 Too many activity in this <{0}>.
technology.bpel603053 There are too many activities inside this <{0}> activity.
technology.bpel603054 Remove the activities inside this <{0}> or use a compound activity (sequence).
technology.bpel603055 <{0}> "{1}" is hiding a {0} by the same name
technology.bpel603056 <{0}> "{1}" is hiding a {0} by the same name in a higher scope/process.
technology.bpel603057 There is nothing to fix.
technology.bpel603058 No expression validator present.
technology.bpel603059 The expression in <{0}> cannot be checked - \ no expression validator has been registered for ...
technology.bpel603060 Register the validator for this expression \ language and try again.
technology.bpel603061 Missing required children nodes.
technology.bpel603062 The node <{0}> requires at least {3,choice,1\#one {1}|1<children nodes from {1}}
technology.bpel603063 You must add any of the following child nodes {1}
technology.bpel603064 Too many occurrences of node
technology.bpel603065 <{3}> can only occur at most {5,choice,1\#one time|1<{5} times} in parent {1,choice,0\#node ...
technology.bpel603066 Remove from {1,choice,0#node|1#activity} <{0}> the node <{3}>
technology.bpel603067 {1,choice,0\#Node|1\#Activity} <{0}> must contain at least {5,choice,1\#one node|1<{5} node ...
technology.bpel603068 Add <{3}> to {1,choice,0\#node|1\#activity} <{0}> to satisfy the constraint.
technology.bpel603069 Missing {3,choice,0\#node|1\#activity|2\#attribute} {2} in <{0}> {1,choice,0\#node|1\#activity ...
technology.bpel603070 {1,choice,0\#Node|1\#Activity} <{0}> must have {2} {3,choice,0\#node|1\#activity|2\#attribute} ...
technology.bpel603071 You need to add {3,choice,0\#node|1\#activity|2\#attribute} {2} to {1,choice,0\#node|1\#activity} &l ...
technology.bpel603072 {1,choice,0\#Node|1\#Activity} <{0}> must specify one {3,choice,0\#node|1\#activity|2\#attribu ...
technology.bpel603073 {1,choice,0\#Node|1\#Activity} <{0}> must specify one {3,choice,0\#node|1\#activity|2\#attribu ...
technology.bpel603074 You need to remove {3,choice,0\#node|1\#activity|2\#attribute} {2} from {1,choice,0\#node|1\#activit ...
technology.bpel603075 {3,choice,0\#Node|1\#Activity|2\#Attribute} {2} must not be specified on {1,choice,0\#node|1\#activi ...
technology.bpel603076 {3,choice,0\#Node|1\#Activity|2\#Attribute} {2} must not be specified on {1,choice,0\#node|1\#activ ...
technology.bpel603077 Remove {3,choice,0\#node|1\#activity|2\#attribute} {2} from {1,choice,0\#node|1\#activity} <{0}&g ...
technology.bpel603078 The starting <{0}> is placed incorrectly
technology.bpel603079 The start activity <{0}> must be the first \ activity in the process.
technology.bpel603080 Make <{0}> the first activity in the process.
technology.bpel603081 10117
technology.bpel603082 Unsupported expression/query language"
technology.bpel603083 {0} attribute refers to an unsupported language URI {1}
technology.bpel603084 Please use an {1} \ supported by this BPEL processor.
technology.bpel603085 {1} has an invalid value "{2}" on {4,choice,0\#node|1\#activity} <{0}>
technology.bpel603086 "{1}" is set to "{2}" on this <{0}> {4,choice,0\#node|1\#activity} but it ...
technology.bpel603087 Make sure that "{1}" is set \ to one of the values from {3}
technology.bpel603088 {1} cannot be resolved on <{0}> {2,choice,0\#|1\#activity}.
technology.bpel603089 "{1}" is set to "{3}" on this <{0}> {2,choice,0\#|1\#activity} but it cann ...
technology.bpel603090 Make sure that value "{3}" is resolvable \ (check imports, value of "{1}").
technology.bpel603091 {0} cannot be a child of {1}
technology.bpel603092 <{0}> cannot be a child of <{1}>; it can only be a child of {2}
technology.bpel603093 Seems like a syntax issue. <{0}> cannot exist as a child of <{2}>
technology.bpel603094 Attribute "{1}" is not set on <{0}>
technology.bpel603095 Attribute "{1}" is not set on this <{0}> {2,choice,0#node|1#activity}.
technology.bpel603096 Make sure that the attribute "{1}" is specified.
technology.bpel603097 Attribute "{0}" must not be set on <{1}>
technology.bpel603098 Attribute "{0}" must not be set on this <{1}> {2,choice,0#node|1#activity}.
technology.bpel603099 Make sure that the attribute "{0}" is defined.
technology.bpel603100 The {3,choice,0#node|1#activity} <{0}> refers to a {1} which has problems.
technology.bpel603101 The {3,choice,0\#node|1\#activity} <{0}> refers to a {1} (via the attribute "{2}") - ...
technology.bpel603102 Check the {1} specified on this {3,choice,0\#node|1\#activity} via attribute "{2}" and mak ...
technology.bpel603103 missing {3} in {2} in activity <{0}>
technology.bpel603104 <{0}> activity "{1}" is trying to use partnerLink "{2}" which does not hav ...
technology.bpel603105 make sure there is a "{3}" defined for for partnerLink "{2}"
technology.bpel603106 10006
technology.bpel603107 role not found
technology.bpel603108 invoke "{3}" references a role "{0}", yet this role does not exist in the partne ...
technology.bpel603109 make sure the role "{0}" is defined correctly in partnerLink "{1}"
technology.bpel603110 10005
technology.bpel603111 mismatch role portType
technology.bpel603112 <{0}> activity "{1}" specifies a \ portType "{2}", yet this portType does ...
technology.bpel603113 make sure the {4} is \ defined correctly in partnerLink "{3}" in WSDL {5}
technology.bpel603114 10016
technology.bpel603115 unresolved portType "{0}"
technology.bpel603116 portType "{0}" of <{1}> is not defined (or is defined \ but does not resolve to a v ...
technology.bpel603117 Make sure the portType "{0}" is defined in one of \ the referenced WSDLs
technology.bpel603118 empty {0}
technology.bpel603119 This <{0}> has no activities.
technology.bpel603120 You can safely remove it.
technology.bpel603121 <{1}> name "{2}" is already used.
technology.bpel603122 <{1}> name "{2}" is already defined in this scope/process.
technology.bpel603123 You must change the name of {1} "{2}" to something else.
technology.bpel603124 Missing IModelQuery adapter
technology.bpel603125 The adapter for IModelQuery is missing and prevents rule "{0}" from running.
technology.bpel603126 Contact vendor or check configuration.
technology.bpel603127 10020
technology.bpel603128 empty expiration setting
technology.bpel603129 Neither "for" nor "until" expressions are \ set for activity <{0}>
technology.bpel603130 Make sure either "for" or "until" expression is set for activity <{0}>
technology.bpel603131 10077
technology.bpel603132 Multiple expiration setting
technology.bpel603133 Both "for" and "until" expressions are \ set for activity <{0}>.
technology.bpel603134 Make sure only one of "for" and "until" \ expression is set for activity <{0 ...
technology.bpel603135 no expression in "{0}" on <{1}>
technology.bpel603136 There is no expression for "{0}" in activity <{1}>
technology.bpel603137 Set the expression for "{0}" in activity <{1}>
technology.bpel603138 {1} of {1} is not understood.
technology.bpel603139 The {1} of {0} is not defined in BPEL 2.0 and is not understood by this implementation.
technology.bpel603140 WSDL and XSD imports are allowed in BPEL 2.0, others are implementation dependent.
technology.bpel603141 The import {1} of {1} is not supported.
technology.bpel603142 The import {1} of {0} is not supported by this implementation. Import artifacts must be contained wi ...
technology.bpel603143 Move the imported artifacts into the supported folder hierarchy and change the import location.
technology.bpel603144 Namespaces do not match.
technology.bpel603145 The import namespace {1} and the imported document target namespace {2} do not match.
technology.bpel603146 Change the import statement namespace.
technology.bpel603147 Namespace is not the default namespace.
technology.bpel603148 The targetNamespace {2} of the imported document is not the default namespace.
technology.bpel603149 Remove the namespace attribute from the import statement.
technology.bpel603150 Cannot import from "{2}"
technology.bpel603151 Cannot import type "{1}" from location "{2}"
technology.bpel603152 Check location "{2}" and import type "{1}"
technology.bpel603153 Variable name must not contain a "."
technology.bpel603154 The variable name "{0}" contains an illegal period (.) character.
technology.bpel603155 Remove the period (.) character from variable name.
technology.bpel603156 variable "{0}" has no type
technology.bpel603157 Variable "{0}" must be have either messageType,element, or type defined.
technology.bpel603158 Define the type of the variable "{0}"
technology.bpel603159 <{0}> name "{1}" is already used
technology.bpel603160 <{0}> name "{1}" is already used
technology.bpel603161 You must change the name of <{0}> "{1}" to something else.
technology.bpel603162 {0} must have "{2}" and/or "{3}" set.
technology.bpel603163 {0} "{1}" must have "{2}" and/or "{3}" set.
technology.bpel603164 You must specify either "{2}" or "{3}" for the <{0}> "{1}"
technology.bpel603165 "{1}" must not be used on this <{0}>.
technology.bpel603166 The "{1}" cannot be used on <{0}> that does not have {2} defined.
technology.bpel603167 You must remove "{1}" from this <{0}>.
technology.bpel603168 Overloaded operation "{4}" in portType "{3}".
technology.bpel603169 partnerLink "{1}" uses portType "{3}" \ (via partnerLinkType "{2}") w ...
technology.bpel603170 Remove the overloaded operation "{4}" in portType "{3}".
technology.bpel603171 Notification operation "{4}" in portType "{3}"
technology.bpel603172 Notification operation "{4}" in portType "{3}" \ (via partnerLinkType "{2} ...
technology.bpel603173 Notification operations cannot be used in BPEL partnerLinkTypes.
technology.bpel603174 Solicit-response operation "{4}" in portType "{3}"
technology.bpel603175 Solicit-response operation "{4}" in portType "{3}" \ cannot be used in a BPEL ...
technology.bpel603176 Solicit-response operations cannot be used in \ BPEL partnerLinkTypes.
technology.bpel603177 No roles defined for this <{0}>
technology.bpel603178 There are no roles defined in the "{0}" used by this <{1}>
technology.bpel603179 You must define at least one role in this {0}
technology.bpel603180 Too many roles defined for this <{0}>
technology.bpel603181 There are more then 2 roles defined in the <{0}> used by this <{1}>
technology.bpel603182 At least 1 but at most 2 roles can be defined for this <{1}>
technology.bpel603183 <{0}> does not have a role "{1}" defined.
technology.bpel603184 <{0}> does not have a role "{1}" defined.
technology.bpel603185 The <{0}> must define a role "{1}".
technology.bpel603186 No such fault variable "{0}".
technology.bpel603187 The variable "{0}" used in this throw activity, does not exist.
technology.bpel603188 You must define this fault variable "{0}" or \ remove the reference from the throw activi ...
technology.bpel603189 No such variable "{0}".
technology.bpel603190 The variable "{0}" used in this <{1}> activity, does not exist.
technology.bpel603191 You must define this variable "{0}" or \ remove the reference from the <{1}> activi ...
technology.bpel603192 No variables to validate.
technology.bpel603193 The list of variables to validate is empty or is not specified.
technology.bpel603194 You must specify at least 1 variable to validate.
technology.bpel603195 <{1}> named "{0}" cannot be placed here.
technology.bpel603196 The <{1}> activity named {0} must be in a fault handler.
technology.bpel603197 You need to move this <{1}> activity to a fault \ handler.
technology.bpel603198 <{0}> named "{1}" cannot be placed here.
technology.bpel603199 The <{0}> activity named "{1}" must be in a fault, compensate, \ or termination han ...
technology.bpel603200 You need to move this <{0}> activity to fault, compensate, \ or termination handlers.
technology.bpel603201 <{1}> named "{0}" cannot be placed here.
technology.bpel603202 The <{1}> activity named {0} must be in a fault, compensate, \ or termination handlers.
technology.bpel603203 You need to move this <{1}> activity to fault, compensate, \ or termination handlers.
technology.bpel603204 Target scope "{2}" does not exist.
technology.bpel603205 Target scope "{2}" does not exist.
technology.bpel603206 Change target scope name "{2}" or create a new target scope.
technology.bpel603207 Target {3} "{2}" must have
technology.bpel603208 Target {3} "{2}" must have a \ compensationHandler or a faultHandler.
technology.bpel603209 Add a compensationHandler \ or a faultHandler to the target {3}.
technology.bpel603210 Invalid <{0}> variant.
technology.bpel603211 The form of <{0}> is not valid (too many variants detected).
technology.bpel603212 You must change the <{0}> to be one of the allowed variants.
technology.bpel603213 Variable part is missing.
technology.bpel603214 The {1} "{2}" is of messageType and needs \ to have a "part" name specified in ...
technology.bpel603215 You need to specify the variable part or chose \ a different variable.
technology.bpel603216 Variable part must not be specified.
technology.bpel603217 The {1} "{2}" is not of messageType and a "part" is specified in this <{0}> ...
technology.bpel603218 Remove the "part" attribute or choose a \ messageType variable.
technology.bpel603219 Partner Link "{1}" must have "{2}" defined.
technology.bpel603220 The partner link "{1}" referenced from this <{0}> must have "{2}" defined. ...
technology.bpel603221 Define a "{2}" in parterLink "{1}" or use a different \ partnerLink.
technology.bpel603222 The <{1}> node must be EII or TII
technology.bpel603223 The <{1}> node present in this <{0}> has {2,choice,0\# unspecified text value (is empty) ...
technology.bpel603224 Change the <{1}> to have only 1 element or a text value.
technology.bpel603225 ${BPELC_FROM__VARIANT}
technology.bpel603226 ${BPELC_FROM__VARIABLE_PART_MISSING}
technology.bpel603227 ${BPELC_FROM__VARIABLE_PART}
technology.bpel603228 ${BPELC_FROM__PARTNER_LINK}
technology.bpel603229 The <{0}> part has no activity.
technology.bpel603230 The <{0}> part has no activity.
technology.bpel603231 You can safely remove this <{0}>
technology.bpel603232 This <{0}> is a start activity - \ it cannot have onAlarm
technology.bpel603233 This <{0}> activity is a start activity and cannot \ have an onAlarm component.
technology.bpel603234 Remove the onAlarm component.
technology.bpel603235
technology.bpel603236 The role named "{0}" on this {2} uses {3} "{1}" \ which is not defined anywhere ...
technology.bpel603237 The {3} must be defined or the value of this {3} must be \ changed.
technology.bpel603238 Standard fault "{1}" cannot be \ handled in <{0}> when exitOnStandardFaults is set ...
technology.bpel603239 Standard fault "{1}" cannot be \ handled in <{0}> when exitOnStandardFaults is set ...
technology.bpel603240 Remove the handler or set "Exit On Standard Faults" to "No" for this process.
technology.bpel603241 A catch for fault "{1}" already exist.
technology.bpel603242 A catch for fault "{1}" already exist.
technology.bpel603243 Remove the duplicate catch for fault "{1}".
technology.bpel603244 No start activity in process.
technology.bpel603245 There is no start activity in process "{1}"
technology.bpel603246 A <receive> or <pick> with createInstance set \ to "true" must be present.
technology.bpel603247 The link "{1}" is not defined.
technology.bpel603248 The link "{1}" used as a {0} is not defined in the enclosing flow.
technology.bpel603249 Define the link "{1}".
technology.bpel603250 The link "{1}" does not have a source.
technology.bpel603251 The link "{1}" does not have a source.
technology.bpel603252 Make the link "{1}" a source of an activity within this flow.
technology.bpel603253 The link "{1}" does not have a target.
technology.bpel603254 The link "{1}" does not have a target.
technology.bpel603255 Make the link "{1}" a target of an activity within this flow.
technology.bpel603256 The link "{1}" is already used as a {0}
technology.bpel603257 The link "{1}" is already used as a {0}.
technology.bpel603258 Use a different link then "{1}" as a {0}.
technology.bpel603259 The link "{1}" crosses a repeatable boundary.
technology.bpel603260 The link "{1}" crosses repeatable boundary on <{2}>.
technology.bpel603261 Links cannot cross repeatable boundaries.
technology.bpel603262 The link "{1}" is not unique.
technology.bpel603263 The link "{1}" is not unique - the link "{2}" also makes \ an identical connect ...
technology.bpel603264 Link in BPEL must be unique - remove either "{1}" or "{2}".
technology.bpel603265 Link "{1}" must be outbound only (target outside of <{2}>)
technology.bpel603266 Link "{1}" must be outbound only; target activity must be \ outside of the enclosing < ...
technology.bpel603267 Change the linkage expressed by the link "{1}"
technology.bpel603268 The variable "{1}" is used as <{2}> counter name.
technology.bpel603269 The variable name "{1}" is used as a counter name in <{2}>.
technology.bpel603270 Change the name of this variable.
technology.bpel603271 Immediately enclosed {0} "{1}" must have unique name.
technology.bpel603272 Immediately enclosed {0} "{1}" must have a unique \ name within the outer scope "{3} ...
technology.bpel603273 Choose unique name for {0} "{1}"
technology.bpel603274 Isolated scope "{1}" cannot exist within another isolated scope.
technology.bpel603275 Isolated scope "{1}" cannot exist within another isolated scope (scope "{3}").
technology.bpel603276 Remove this isolated scope "{1}".
technology.bpel603277 Scope "{1}" cannot have a <{2}>.
technology.bpel603278 Scope "{1}" cannot have a <{2}> because because \ it is itself inside an FCT-hander ...
technology.bpel603279 Remove <{2}> from the scope "{1}".
technology.bpel603280 Incompatible {1}/message types on <{0}> activity.
technology.bpel603281 {1} "{2}" of type "{4}" is not compatible with \ WSDL message "{3}".
technology.bpel603282 Check {1} "{2}" declaration, check WSDL message "{3}" declaration.
technology.bpel603283 {3,choice,0#Node <{4}>|2#Attribute "{4}"} must be omitted from this <{0}>.
technology.bpel603284 There is no "{2}" message that is used by this <{0}> - {3,choice,0\#node <{4}> ...
technology.bpel603285 {3,choice,0#Node <{4}> |2#Attribute "{4}"} must be omitted from this <{0}>.
technology.bpel603286 Either <{1}> *or* attribute "{2}" must be specified on <{0}>
technology.bpel603287 Either <{1}> *or* attribute "{2}" must be specified on <{0}>.
technology.bpel603288 Specify either <{1}> *or* attribute "{2}" on <{0}>.
technology.bpel603289 Message part "{1}" does not exist in message "{2}"
technology.bpel603290 Message part "{1}" does not exist in message "{2}"
technology.bpel603291 Pick a valid message type.
technology.bpel603292 No "{3}" message exist on portType "{1}" with operation "{2}".
technology.bpel603293 No "{3}" message exist on portType "{1}" with operation "{2}".
technology.bpel603294 Check value of operation ("{2}") and portType "{1}".
technology.bpel603295 Part "{3}" must be specified on this <{2}>
technology.bpel603296 Part "{3}" must be specified on this <{2}> - activity <{1}> requires it.
technology.bpel603297 You must specify part "{3}" on this <{2}>
technology.bpel603298 The part "{1}" is already specified in another <{0}>.
technology.bpel603299 The part "{1}" is already specified in another <{0}>.
technology.bpel603300 Remove the duplicate <{0}> "{1}"
technology.bpel603301 The attribute {1} must be set to "{2}" on this <{0}>
technology.bpel603302 The attribute {1} must be set to "{2}" on this <{0}>
technology.bpel603303 Set the value of {1} to "{2}" on this <{0}>
technology.bpel603304 Start activities specify but do not share a single correlation.
technology.bpel603305 The {1} start activities must share at least one correlation.
technology.bpel603306 Remove the correlation from the start {1} activities or \ have them share at least one correlation.
technology.bpel603307 The type "{1}" of {2} "{3}" is not a XSD simple type.
technology.bpel603308 The XSD type "{1}" of {2} "{3}" in this <{0}> is not a simple XSD type.
technology.bpel603309 The {2} "{3}" must of be simple XSD type.
technology.bpel603310 Incompatible types of {1} "{2}" and {4} "{5}".
technology.bpel603311 The {1} "{2}" of type "{3}" is not \ compatible with {4} "{5}" of typ ...
technology.bpel603312 Type must be compatible.
technology.bpel603313 Incompatible types of {1} and {3}.
technology.bpel603314 The {1} of "{2}" is not \ compatible with {3} of "{4}" - {5}
technology.bpel603315 Types must be compatible.
technology.bpel603316 Incompatible simple types of {1} and {3}.
technology.bpel603317 The {1} of simple type "{2}" is not \ compatible with {3} of simple type "{4}" ...
technology.bpel603318 Simple types ought to be compatible.
technology.bpel603319 Copy rule not checked.
technology.bpel603320 Copy rule not checked - {1} type-of "{2}", {3} type-of "{4}".
technology.bpel603321 Nothing.
technology.bpel603322 Attribute "{1}" cannot be set on this <{0}>.
technology.bpel603323 Attribute "{1}" cannot be set because {2} "{3}" is not an element.
technology.bpel603324 Remove the attribute "{1}" from this <{0}>
technology.bpel603325 Extension "{1}" is not supported.
technology.bpel603326 Extension "{1}" is not supported by this implementation.
technology.bpel603327 Remove the dependency on extension "{1}"
technology.bpel603328 Extension Activity element <{0}> is not supported.
technology.bpel603329 Extension Activity element <{0} name="{1}"> is not supported by this implementation.
technology.bpel603330 Remove the Extension Activity <{0}> or contact the vendor to obtain the necessary plug-in(s)
technology.bpel603331 Extension Activity element <{0}> must have exactly one child element.
technology.bpel603332 Extension Activity element <{0} name="{1}"> must have exactly one child element.
technology.bpel603333 Make sure the Extension Activity element <{0}> has exactly one child element that is supported ...
technology.bpel603334 BPEL element <{0}> is not supported.
technology.bpel603335 BPEL element <{0}> in namespace "{1}" is not supported by this implementation.
technology.bpel603336 Remove the element <{0}> or contact the vendor to obtain the necessary plug-in(s)
technology.bpel682196 Conflicting XSD element <{0}> definitions.
technology.bpel682197 XSD element <{0}> in import {1} conflicts with element of the same name in {2}.
technology.bpel682198 Resolve the conflict by removing the conflicting definitions, or ensuring that all definitions are i ...
technology.bpel682199 Link cycle on "{1}": target "{3}" precedes source "{2}".
technology.bpel682200 The <link> "{1}" has a control cycle where the source "{2}" has the target ...
technology.bpel682201 Rearrange the source and target activities so that the source "{2}" does not have the targ ...
technology.bpel603337 Validation is not supported for <{0}> "{1}" in namespace "{2}"
technology.bpel603338 Validation is not supported for <{0}> "{1}" in namespace "{2}"
technology.bpel603339 You cannot validate a BPEL process in namespace "{2}"
technology.bpel603340 Missing "{1}" or "{2}" attribute for this <{0}>
technology.bpel603341 Either "{1}" or "{2}" attribute is required on this <{0}>
technology.bpel603342 Provide a valid "{1}" or "{2}" attribute for this <{0}>
technology.bpel603343 Duplicate <{0} name="{1}">
technology.bpel603344 This <{0}> with name="{1}" was already defined previously
technology.bpel603345 Change the "name" attribute of this <{0}> to something other than "{1}"
technology.bpel603346 Undefined message "{2}/{1}" for <{0}>
technology.bpel603347 This <{0}> uses undefined message part "{1}" in message type "{2}"
technology.bpel603348 Provide a valid message type and part attribute for this <{0}>
technology.bpel603349 Cannot import "{1}"
technology.bpel603350 The "{1}" document could not be imported while parsing "{2}"
technology.bpel603351 Check that the document exists and that the location is correct
technology.bpel603352 unsigned integer expression
technology.bpel603353 boolean expression
technology.bpel603354 unsigned integer expression
technology.bpel603355 duration expression
technology.bpel603356 expression
technology.bpel603357 boolean expression
technology.bpel603358 duration expression
technology.bpel603359 unsigned integer expression
technology.bpel603360 variable reference expression
technology.bpel603361 boolean expression
technology.bpel603362 deadline expression
technology.bpel603363 path expression
technology.bpel603364 unspecified
technology.bpel603365 No {1} specified on <{0}>.
technology.bpel603366 The {1} is not specified on <{0}>.
technology.bpel603367 You must specify a valid {1} expression in <{0}>.
technology.bpel603368 Invalid {2} "{1}" on <{0}> - check syntax.
technology.bpel603369 The {2} "{1}" has invalid syntax - {3}
technology.bpel603370 Check {2} syntax on <{0}>.
technology.bpel603371 Expression in <{0}> must be a {2}.
technology.bpel603372 The expression in <{0}> is not a {2}.
technology.bpel603373 Make sure that the expression in <{0}> is a {2}.
technology.bpel603374 BPEL function {1} cannot be used in node <{0}>.
technology.bpel603375 BPEL function "{1}" cannot be used in node <{0}>.
technology.bpel603376 You cannot use BPEL functions in nodes like <{0}>.
technology.bpel603377 Variable "{0}" is not defined.
technology.bpel603378 The variable "{0}" is not defined in scope or process.
technology.bpel603379 You must defined the variable to use it in the XPath expression.
technology.bpel603380 Variable "{0}" \ {3,choice,0#must not|1#must} specify a part name.
technology.bpel603381 Variable "{0}" \ {3,choice,0# must not specify part "{1}"|1#needs to specify a ...
technology.bpel603382 Variable "{0}" \ {3,choice,0#must not|1#must} specify a part name.
technology.bpel603383 10078
technology.bpel603384 return value of this expression may not be a boolean
technology.bpel603385 xpath expression "{0}" used in <{1}> may not return \ boolean type value, the xpath ...
technology.bpel603386 Please use one of the built-in boolean \ functions from xpath http://www.w3.org/TR/xpath#section-Bo ...
technology.bpel603387 unresolved namespace prefix
technology.bpel603388 Namespace prefix "{0}" qualifying "{1}" cannot be resolved.
technology.bpel603389 Please define this prefix in the BPEL source file.
technology.bpel603390 unresolved xpath function {0}
technology.bpel603391 Could not resolve xpath function \"{0}\", because {1},
technology.bpel603392 Please make sure to register this function in xpath-functions.xml file located under domain config d ...
technology.bpel603393 Invalid expression
technology.bpel603394 XPath expression "{0}" in <{0}> relies on the presence of a context node \ which is ...
technology.bpel603395 You must remove the Location Path fragment in the XPath expression.
technology.bpel603396 Invalid expression
technology.bpel603397 XPath expression "{0}" in <{0}> is not a LocationPath expression.
technology.bpel603398 The expression in <{1}> must be a LocationPath expression.
technology.bpel603399 99999
technology.bpel603400 Wrong link name syntax.
technology.bpel603401 Wrong link name syntax in expression in "{0}"
technology.bpel603402 Remove the part name from the overloaded link reference \ expression and try again.
technology.bpel603403 99999
technology.bpel603404 Link does not exist.
technology.bpel603405 The link "{0}" does not exist and cannot be used in the expression.
technology.bpel603406 Check to make sure that the link "{0}" is defined.
technology.bpel603407 No location path expression allowed.
technology.bpel603408 The LocationPath expression "{0}" is not allowed in \ expressions as there is no implicit ...
technology.bpel603409 Change the part name used in this expression or define \ this part name in the message type definit ...
technology.bpel603410 SA00027
technology.bpel603411 When XPath 1.0 is used as an expression language \ in WS-BPEL there is no context node available. T ...
technology.bpel603412 Variable part "{1}" does not exist in variable "{0}"
technology.bpel603413 Variable "{0}" does not have a part named "{1}" - \ check expression segment &q ...
technology.bpel603414 The XPath segment {0} cannot be resolved - check definition.
technology.bpel603415 The XPath segment "{0}" cannot be resolved.
technology.bpel603416 Check the type definition associated with the BPEL variable.
technology.bpel603417 The axis of XPath segment "{0}" cannot be followed.
technology.bpel603418 The axis of XPath segment "{0}" cannot be followed.
technology.bpel603419 Static XPath checking is not possible here.
technology.bpel603420 {3,choice,0#Not enough|1#Too many} arguments in {2}
technology.bpel603421 {3,choice,0#Not enough|1#Too many} arguments to function {1} in "{2}" \ (requires {4} {4, ...
technology.bpel603422 {3,choice,0#Not enough|1#Too many} arguments and modify "{2}"
technology.bpel603423 The {3,choice,1#first|2#second|3#third|4<{3}th} argument to \ function {1} in "{2}" mu ...
technology.bpel603424 The {3,choice,1#first|2#second|3#third|4<{3}th} argument ({4}) to \ function {1} in "{2}&qu ...
technology.bpel603425 Change the {3,choice,1#first|2#second|3#third|4<{3}th} argument to \ function {1} in "{2}&q ...
technology.bpel603426 Bad URI syntax in "{1}"
technology.bpel603427 The URI in "{1}" has bad syntax because {3}
technology.bpel603428 Correct the syntax of URI "{1}" present in "{2}" and try again
technology.bpel603429 Prefix "{2}" is not allowed in expression "{1}"
technology.bpel603430 Prefix "{2}" is not allowed in expression "{1}"
technology.bpel603431 Remove the prefix "{1}"
technology.bpel603432 The function "{1}" is not unknown
technology.bpel603433 Unknown function "{1}" used in <{0}>
technology.bpel603434 Add function definition for this function "{1}" to the validator
technology.bpel603435 The function call "{1}" has too many arguments.
technology.bpel603436 Too many arguments to function "{1}" in <{0}>; no more than {2} arguments are needed ...
technology.bpel603437 Remove arguments from the call to function "{1}".
technology.bpel603438 The function call "{1}" has too few arguments.
technology.bpel603439 Too few arguments to function "{1}" in <{0}>; at least {2} arguments are needed.
technology.bpel603440 Remove arguments from the call to function "{1}".
technology.bpel603441 unsigned integer expression
technology.bpel603442 boolean expression
technology.bpel603443 unsigned integer expression
technology.bpel603444 duration expression
technology.bpel603445 expression
technology.bpel603446 boolean expression
technology.bpel603447 duration expression
technology.bpel603448 unsigned integer expression
technology.bpel603449 variable reference expression
technology.bpel603450 boolean expression
technology.bpel603451 deadline expression
technology.bpel603452 path expression
technology.bpel603453 unspecified
technology.bpel603454 No {1} specified on <{0}>.
technology.bpel603455 The {1} is not specified on <{0}>.
technology.bpel603456 You must specify a valid {1} expression in <{0}>.
technology.bpel603457 Invalid {2} "{1}" on <{0}> - check syntax.
technology.bpel603458 The {2} "{1}" has invalid syntax - {3}
technology.bpel603459 Check {2} syntax on <{0}>.
technology.bpel603460 Expression in <{0}> must be a {2}.
technology.bpel603461 The expression in <{0}> is not a {2}.
technology.bpel603462 Make sure that the expression in <{0}> is a {2}.
technology.bpel603463 BPEL function {1} cannot be used in node <{0}>.
technology.bpel603464 BPEL function "{1}" cannot be used in node <{0}>.
technology.bpel603465 You cannot use BPEL functions in nodes like <{0}>.
technology.bpel603466 Variable "{0}" is not defined.
technology.bpel603467 The variable "{0}" is not defined in scope or process.
technology.bpel603468 You must defined the variable to use it in the XPath expression.
technology.bpel603469 Variable "{0}" \ {3,choice,0#must not|1#must} specify a part name.
technology.bpel603470 Variable "{0}" \ {3,choice,0# must not specify part "{1}"|1#needs to specify a ...
technology.bpel603471 Variable "{0}" \ {3,choice,0#must not|1#must} specify a part name.
technology.bpel603472 10078
technology.bpel603473 return value of this expression may not be a boolean
technology.bpel603474 xpath expression "{0}" used in <{1}> may not return \ boolean type value, the xpath ...
technology.bpel603475 Please use one of the built-in boolean \ functions from xpath http://www.w3.org/TR/xpath#section-Bo ...
technology.bpel603476 unresolved namespace prefix
technology.bpel603477 Namespace prefix "{0}" qualifying "{1}" cannot be resolved.
technology.bpel603478 Please define this prefix in the BPEL source file.
technology.bpel603479 unresolved xpath function {0}
technology.bpel603480 Could not resolve xpath function \"{0}\", because {1},
technology.bpel603481 Please make sure to register this function in xpath-functions.xml file located under domain config d ...
technology.bpel603482 Invalid expression
technology.bpel603483 XPath expression "{0}" in <{0}> relies on the presence of a context node \ which is ...
technology.bpel603484 You must remove the Location Path fragment in the XPath expression.
technology.bpel603485 Invalid expression
technology.bpel603486 XPath expression "{0}" in <{0}> is not a LocationPath expression.
technology.bpel603487 The expression in <{1}> must be a LocationPath expression.
technology.bpel603488 99999
technology.bpel603489 Wrong link name syntax.
technology.bpel603490 Wrong link name syntax in expression in "{0}"
technology.bpel603491 Remove the part name from the overloaded link reference \ expression and try again.
technology.bpel603492 99999
technology.bpel603493 Link does not exist.
technology.bpel603494 The link "{0}" does not exist and cannot be used in the expression.
technology.bpel603495 Check to make sure that the link "{0}" is defined.
technology.bpel603496 No location path expression allowed.
technology.bpel603497 The LocationPath expression "{0}" is not allowed in \ expressions as there is no implicit ...
technology.bpel603498 Change the part name used in this expression or define \ this part name in the message type definit ...
technology.bpel603499 SA00027
technology.bpel603500 When XPath 1.0 is used as an expression language \ in WS-BPEL there is no context node available. T ...
technology.bpel603501 Variable part "{1}" does not exist in variable "{0}"
technology.bpel603502 Variable "{0}" does not have a part named "{1}" - \ check expression segment &q ...
technology.bpel603503 The XPath segment {0} cannot be resolved - check definition.
technology.bpel603504 The XPath segment "{0}" cannot be resolved.
technology.bpel603505 Check the type definition associated with the BPEL variable.
technology.bpel603506 The axis of XPath segment "{0}" cannot be followed.
technology.bpel603507 The axis of XPath segment "{0}" cannot be followed.
technology.bpel603508 Static XPath checking is not possible here.
technology.bpel603509 {3,choice,0#Not enough|1#Too many} arguments in {2}
technology.bpel603510 {3,choice,0#Not enough|1#Too many} arguments to function {1} in "{2}" \ (requires {4} {4, ...
technology.bpel603511 {3,choice,0#Not enough|1#Too many} arguments and modify "{2}"
technology.bpel603512 The {3,choice,1#first|2#second|3#third|4<{3}th} argument to \ function {1} in "{2}" mu ...
technology.bpel603513 The {3,choice,1#first|2#second|3#third|4<{3}th} argument ({4}) to \ function {1} in "{2}&qu ...
technology.bpel603514 Change the {3,choice,1#first|2#second|3#third|4<{3}th} argument to \ function {1} in "{2}&q ...
technology.bpel603515 Bad URI syntax in "{1}"
technology.bpel603516 The URI in "{1}" has bad syntax because {3}
technology.bpel603517 Correct the syntax of URI "{1}" present in "{2}" and try again
technology.bpel603518 Prefix "{2}" is not allowed in expression "{1}"
technology.bpel603519 Prefix "{2}" is not allowed in expression "{1}"
technology.bpel603520 Remove the prefix "{1}"
technology.bpel603521 The function "{1}" is not unknown
technology.bpel603522 Unknown function "{1}" used in <{0}>
technology.bpel603523 Add function definition for this function "{1}" to the validator
technology.bpel603524 The function call "{1}" has too many arguments.
technology.bpel603525 Too many arguments to function "{1}" in <{0}>; no more than {2} arguments are needed ...
technology.bpel603526 Remove arguments from the call to function "{1}".
technology.bpel603527 The function call "{1}" has too few arguments.
technology.bpel603528 Too few arguments to function "{1}" in <{0}>; at least {2} arguments are needed.
technology.bpel603529 Remove arguments from the call to function "{1}".