Re: [Dev] [BPS] [Cluster] Error while deploying BPEL & HT packages

[Chamila Wijayarathna]

Hi Hasitha,

I added the suggested solution to prevent above error message at [1].
But I am still getting following error message which seems to be a part of
previous error message.

TID: [-1234] [] [2015-12-02 11:01:04,552] ERROR
{org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
 
null:file:///home/chamila/IS/packs/4114/2/wso2is-5.1.0-SNAPSHOT/repository/bpel/-1234/wf1-1/wf1.bpel:51:17:cvc-complex-type.2.4.a:
Invalid content was found starting with element 'extensions'. One of '{"
http://docs.oasis-open.org/wsbpel/2.0/process/executable":import, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":partnerLinks, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":messageExchanges,
"http://docs.oasis-open.org/wsbpel/2.0/process/executable":variables, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":correlationSets, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":faultHandlers, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":eventHandlers, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":assign, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensate, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensateScope, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":empty, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":exit, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":extensionActivity,
"http://docs.oasis-open.org/wsbpel/2.0/process/executable":flow, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":forEach, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":if, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":invoke, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":pick, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":receive, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":repeatUntil, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":reply, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":rethrow, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":scope, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":sequence, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":throw, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":validate, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":wait, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":while}' is
expected.
TID: [-1234] [] [2015-12-02 11:01:04,560] ERROR
{org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
 
null:file:///home/chamila/IS/packs/4114/2/wso2is-5.1.0-SNAPSHOT/repository/bpel/-1234/wf1-1/wf1.bpel:304:84:cvc-elt.4.2:
Cannot resolve 'p:tExpression' to a type definition for element
'p:searchBy'.

Thank You!

1.
https://github.com/cdwijayarathna/carbon-identity/commit/b3d0b2b45b3d9f9f878af38dcc9650893c23632e

On Tue, Nov 3, 2015 at 8:56 AM, Harsha Thirimanna  wrote:

> On Tue, Nov 3, 2015 at 8:38 AM, Hasitha Aravinda  wrote:
>
>> Hi Harsha,
>>
>>
>>
>> On Mon, Nov 2, 2015 at 11:46 PM, Harsha Thirimanna 
>> wrote:
>>
>>> Hi Vinod/Nandika,
>>> Can you please help to get resolve this BPEL package ? You guys always
>>> helped us to fix these kind of things :)
>>>
>>
>> ​Sure, We can guide you on this. It is a simple fix. Remove all xml:space
>> in BPEL file. If you know xml, you can fix it in no time.
>>
> ​Thanks​
>
> ​Hasitha​
>
>>
>> Btw
>>
>> ​w​
>> e need some one from IS team to maintain these process ? (like what we do
>> in APIM
>> ​​
>> ) Not knowing
>> ​ BPEL or xml is not an excuse and
>>  It is time to learn BPEL
>> ​/BPMN​
>> ​;​
>> )
>> ​
>>
>>
> ​Sorry for make misunderstand because we didn't tell we don't know. We
> will try to fix these our self and if there any issues, will ask from BPS
> team.
>
>>
>>> @Hasitha
>>> If these elements and attributes adding by Dev Studio and those are not
>>> expected by the BPEL compiler, IMO , we should eliminate it by the editor.
>>> So it is not an issue in IS side. Better to discuss with the relevant party
>>> and avoid this happen in future also.  Didn't you get this complain before
>>> when these BPEL created using dev studio and deploy it to the BPS ?
>>>
>>
>> ​As I mentioned earlier, that is not a bug in ether BPS or DevS.
>>
> ​If this is not a bug, then no issue :)​
>
>
>> Those are added as place holders preserve white spaces temporally,
>> because IDEs are not intelligent enough to predict what developers want to
>> do next and
>> It is a xml standard. (Read http://www.xmlplease.com/xml/xmlspace/,
>> http://www.w3.org/TR/xml/#sec-white-space ).
>>
>> But this attribute is not define in BPEL schema and BPEL compiler
>> strictly validating bpel files against BPEL schema. But In BPS we continue
>> BPEL compilation even on those validation
>> errors(-Dorg.apache.ode.compiler.failOnValidationErrors=false) because m
>> ost of
>> ​times, 

Re: [Dev] [BPS] [Cluster] Error while deploying BPEL & HT packages

[Harsha Thirimanna]

Hi Vinod/Nandika,
Can you please help to get resolve this BPEL package ? You guys always
helped us to fix these kind of things :)

@Hasitha
If these elements and attributes adding by Dev Studio and those are not
expected by the BPEL compiler, IMO , we should eliminate it by the editor.
So it is not an issue in IS side. Better to discuss with the relevant party
and avoid this happen in future also.  Didn't you get this complain before
when these BPEL created using dev studio and deploy it to the BPS ?


*Harsha Thirimanna*
Senior Software Engineer; WSO2, Inc.; http://wso2.com
* *
*email: **hars...@wso2.com* * cell: +94 71 5186770 *
*twitter: **http://twitter.com/ *
*harshathirimannlinked-in: **http:
**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
*

*Lean . Enterprise . Middleware*


On Mon, Nov 2, 2015 at 11:33 PM, Hasitha Aravinda  wrote:

> Hi Aparna,
>
> When you develop a BPEL process, eclipse editor adds xml:space attribute
> temporally to handle white space [1]. Developer has to remove those
> temporary attributes and initialize variable properly.
>
> xml:space attribute is not a part of the BPEL spec, hence BPEL compiler
> report those as errors. It is not a bug, that is expected behavior. But
> having those in BPEL make no harm.
>
> ​I went though attached BPEL. You can eliminate xml:space and other xml
> elements related errors by modifying BPEL process. Those are not bugs of
> ODE compiler, but problem of BPEL archive. Since IS is shipping this BPEL
> archive, IMO we have to move this jira to IS space and track there. WDYT ?
>
> [1] - http://www.xmlplease.com/xml/xmlspace/
>
> Thanks
> Hasitha.
>
> On Mon, Nov 2, 2015 at 7:48 PM, Nandika Jayawardana 
> wrote:
>
>> Hi Aparana,
>>
>> This extension is b4p extension. We have not modified ode compiler when
>> introducing the b4p extension, hence the warning. However, it does not have
>> any impact on the runtime.
>>
>> Regards
>> Nandika
>>
>> On Mon, Nov 2, 2015 at 1:54 AM, Aparna Karunarathna 
>> wrote:
>>
>>> Hi Nandika/ Chathura/ Hasitha,
>>>
>>> Shouldn't we fix this issue? Vinod has clearly mentioned in the jira[1]
>>> that this was getting from extension that introduced in BPS/Dev Studio
>>> which is not compliance with ODE.
>>>
>>> *"Those errors can be seen in both standalone and cluster mode. These
>>> are bpel compilation errors logged by ODE server due to the extensions we
>>> have introduced in BPS/Dev Studio, which are not compliance with ODE (They
>>> are not errors actually).*
>>> *If the package get deployed successfully, please ignore those error
>>> logs."*
>>>
>>> [1] https://wso2.org/jira/browse/BPS-915
>>>
>>> Regards,
>>> Aparna
>>>
>>> On Thu, Oct 29, 2015 at 2:39 PM, Vinod Kavinda  wrote:
>>>
 HI,
 Adding to above, some of those tags such as 'xml:space'  are not
 required that are added by dev studio. They can be removed from the model
 without affecting any functionality.

 Regards,
 Vinod Kavinda

 On Thu, Oct 29, 2015 at 2:36 PM, Vinod Kavinda  wrote:

> Hi all,
> Those errors can be seen in standalone mode also, they can be seen in
> carbon logs. These are bpel compilation errors logged by ODE server due to
> the extensions we have introduced in  BPS, which are not compliance with
> ODE (They are not errors actually).
> If the package get deployed successfully, please ignore those error
> logs.
>
> Regards,
> Vinod
>
> On Thu, Oct 29, 2015 at 9:46 AM, Aparna Karunarathna 
> wrote:
>
>> Hi all,
>>
>> I have attached the bpel package to the jira[1]
>>
>> [1] https://wso2.org/jira/browse/IDENTITY-3950
>>
>> Regards,
>> Aparna
>>
>> On Wed, Oct 28, 2015 at 10:29 PM, Nandika Jayawardana <
>> nand...@wso2.com> wrote:
>>
>>> Hi,
>>> Can you attach the actual bpel package generated. It looks like some
>>> invalid content is generated into the bpel file.
>>>
>>> Regards
>>> Nandika
>>>
>>> On Wed, Oct 28, 2015 at 10:20 PM, Harsha Thirimanna <
>>> hars...@wso2.com> wrote:
>>>
 Is this intermittent ? Because I also reported this once earlier
 in dev mail. This was happened intermittently earlier in standalone 
 pack as
 well.
 On Oct 28, 2015 10:15 PM, "Chamila Wijayarathna" 
 wrote:

> Hi all,
>
> Currently we are testing IS workflow feature with a BPS cluster.
> When creating a new workflow, we have observed following error at BPS
> terminal.
>
> ERROR
> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler}
>  -

Re: [Dev] [BPS] [Cluster] Error while deploying BPEL & HT packages

[Harsha Thirimanna]

adding Jasintha and Viraj ...


*Harsha Thirimanna*
Senior Software Engineer; WSO2, Inc.; http://wso2.com
* *
*email: **hars...@wso2.com* * cell: +94 71 5186770 *
*twitter: **http://twitter.com/ *
*harshathirimannlinked-in: **http:
**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
*

*Lean . Enterprise . Middleware*


On Mon, Nov 2, 2015 at 11:46 PM, Harsha Thirimanna  wrote:

> Hi Vinod/Nandika,
> Can you please help to get resolve this BPEL package ? You guys always
> helped us to fix these kind of things :)
>
> @Hasitha
> If these elements and attributes adding by Dev Studio and those are not
> expected by the BPEL compiler, IMO , we should eliminate it by the editor.
> So it is not an issue in IS side. Better to discuss with the relevant party
> and avoid this happen in future also.  Didn't you get this complain before
> when these BPEL created using dev studio and deploy it to the BPS ?
>
>
> *Harsha Thirimanna*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com
> * *
> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
> *twitter: **http://twitter.com/ *
> *harshathirimannlinked-in: **http:
> **//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
> *
>
> *Lean . Enterprise . Middleware*
>
>
> On Mon, Nov 2, 2015 at 11:33 PM, Hasitha Aravinda 
> wrote:
>
>> Hi Aparna,
>>
>> When you develop a BPEL process, eclipse editor adds xml:space attribute
>> temporally to handle white space [1]. Developer has to remove those
>> temporary attributes and initialize variable properly.
>>
>> xml:space attribute is not a part of the BPEL spec, hence BPEL compiler
>> report those as errors. It is not a bug, that is expected behavior. But
>> having those in BPEL make no harm.
>>
>> ​I went though attached BPEL. You can eliminate xml:space and other xml
>> elements related errors by modifying BPEL process. Those are not bugs of
>> ODE compiler, but problem of BPEL archive. Since IS is shipping this
>> BPEL archive, IMO we have to move this jira to IS space and track there.
>> WDYT ?
>>
>> [1] - http://www.xmlplease.com/xml/xmlspace/
>>
>> Thanks
>> Hasitha.
>>
>> On Mon, Nov 2, 2015 at 7:48 PM, Nandika Jayawardana 
>> wrote:
>>
>>> Hi Aparana,
>>>
>>> This extension is b4p extension. We have not modified ode compiler when
>>> introducing the b4p extension, hence the warning. However, it does not have
>>> any impact on the runtime.
>>>
>>> Regards
>>> Nandika
>>>
>>> On Mon, Nov 2, 2015 at 1:54 AM, Aparna Karunarathna 
>>> wrote:
>>>
 Hi Nandika/ Chathura/ Hasitha,

 Shouldn't we fix this issue? Vinod has clearly mentioned in the jira[1]
 that this was getting from extension that introduced in BPS/Dev Studio
 which is not compliance with ODE.

 *"Those errors can be seen in both standalone and cluster mode. These
 are bpel compilation errors logged by ODE server due to the extensions we
 have introduced in BPS/Dev Studio, which are not compliance with ODE (They
 are not errors actually).*
 *If the package get deployed successfully, please ignore those error
 logs."*

 [1] https://wso2.org/jira/browse/BPS-915

 Regards,
 Aparna

 On Thu, Oct 29, 2015 at 2:39 PM, Vinod Kavinda  wrote:

> HI,
> Adding to above, some of those tags such as 'xml:space'  are not
> required that are added by dev studio. They can be removed from the model
> without affecting any functionality.
>
> Regards,
> Vinod Kavinda
>
> On Thu, Oct 29, 2015 at 2:36 PM, Vinod Kavinda  wrote:
>
>> Hi all,
>> Those errors can be seen in standalone mode also, they can be seen in
>> carbon logs. These are bpel compilation errors logged by ODE server due 
>> to
>> the extensions we have introduced in  BPS, which are not compliance with
>> ODE (They are not errors actually).
>> If the package get deployed successfully, please ignore those error
>> logs.
>>
>> Regards,
>> Vinod
>>
>> On Thu, Oct 29, 2015 at 9:46 AM, Aparna Karunarathna > > wrote:
>>
>>> Hi all,
>>>
>>> I have attached the bpel package to the jira[1]
>>>
>>> [1] https://wso2.org/jira/browse/IDENTITY-3950
>>>
>>> Regards,
>>> Aparna
>>>
>>> On Wed, Oct 28, 2015 at 10:29 PM, Nandika Jayawardana <
>>> nand...@wso2.com> wrote:
>>>
 Hi,
 Can you attach the actual bpel package generated. It looks like
 some invalid content is generated into the bpel file.

 Regards
 

Re: [Dev] [BPS] [Cluster] Error while deploying BPEL & HT packages

[Hasitha Aravinda]

Hi Aparna,

When you develop a BPEL process, eclipse editor adds xml:space attribute
temporally to handle white space [1]. Developer has to remove those
temporary attributes and initialize variable properly.

xml:space attribute is not a part of the BPEL spec, hence BPEL compiler
report those as errors. It is not a bug, that is expected behavior. But
having those in BPEL make no harm.

​I went though attached BPEL. You can eliminate xml:space and other xml
elements related errors by modifying BPEL process. Those are not bugs of
ODE compiler, but problem of BPEL archive. Since IS is shipping this BPEL
archive, IMO we have to move this jira to IS space and track there. WDYT ?

[1] - http://www.xmlplease.com/xml/xmlspace/

Thanks
Hasitha.

On Mon, Nov 2, 2015 at 7:48 PM, Nandika Jayawardana 
wrote:

> Hi Aparana,
>
> This extension is b4p extension. We have not modified ode compiler when
> introducing the b4p extension, hence the warning. However, it does not have
> any impact on the runtime.
>
> Regards
> Nandika
>
> On Mon, Nov 2, 2015 at 1:54 AM, Aparna Karunarathna 
> wrote:
>
>> Hi Nandika/ Chathura/ Hasitha,
>>
>> Shouldn't we fix this issue? Vinod has clearly mentioned in the jira[1]
>> that this was getting from extension that introduced in BPS/Dev Studio
>> which is not compliance with ODE.
>>
>> *"Those errors can be seen in both standalone and cluster mode. These are
>> bpel compilation errors logged by ODE server due to the extensions we have
>> introduced in BPS/Dev Studio, which are not compliance with ODE (They are
>> not errors actually).*
>> *If the package get deployed successfully, please ignore those error
>> logs."*
>>
>> [1] https://wso2.org/jira/browse/BPS-915
>>
>> Regards,
>> Aparna
>>
>> On Thu, Oct 29, 2015 at 2:39 PM, Vinod Kavinda  wrote:
>>
>>> HI,
>>> Adding to above, some of those tags such as 'xml:space'  are not
>>> required that are added by dev studio. They can be removed from the model
>>> without affecting any functionality.
>>>
>>> Regards,
>>> Vinod Kavinda
>>>
>>> On Thu, Oct 29, 2015 at 2:36 PM, Vinod Kavinda  wrote:
>>>
 Hi all,
 Those errors can be seen in standalone mode also, they can be seen in
 carbon logs. These are bpel compilation errors logged by ODE server due to
 the extensions we have introduced in  BPS, which are not compliance with
 ODE (They are not errors actually).
 If the package get deployed successfully, please ignore those error
 logs.

 Regards,
 Vinod

 On Thu, Oct 29, 2015 at 9:46 AM, Aparna Karunarathna 
 wrote:

> Hi all,
>
> I have attached the bpel package to the jira[1]
>
> [1] https://wso2.org/jira/browse/IDENTITY-3950
>
> Regards,
> Aparna
>
> On Wed, Oct 28, 2015 at 10:29 PM, Nandika Jayawardana <
> nand...@wso2.com> wrote:
>
>> Hi,
>> Can you attach the actual bpel package generated. It looks like some
>> invalid content is generated into the bpel file.
>>
>> Regards
>> Nandika
>>
>> On Wed, Oct 28, 2015 at 10:20 PM, Harsha Thirimanna > > wrote:
>>
>>> Is this intermittent ? Because I also reported this once earlier  in
>>> dev mail. This was happened intermittently earlier in standalone pack as
>>> well.
>>> On Oct 28, 2015 10:15 PM, "Chamila Wijayarathna" 
>>> wrote:
>>>
 Hi all,

 Currently we are testing IS workflow feature with a BPS cluster.
 When creating a new workflow, we have observed following error at BPS
 terminal.

 ERROR
 {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler}
  -
  
 null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:51:17:cvc-complex-type.2.4.a:
 Invalid content was found starting with element 'extensions'. One of 
 '{"
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":import, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":partnerLinks,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":messageExchanges,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":variables,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":correlationSets,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":faultHandlers,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":eventHandlers,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":assign,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensate,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensateScope,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":empty, "
 

Re: [Dev] [BPS] [Cluster] Error while deploying BPEL & HT packages

[Aparna Karunarathna]

Hi Nandika/ Chathura/ Hasitha,

Shouldn't we fix this issue? Vinod has clearly mentioned in the jira[1]
that this was getting from extension that introduced in BPS/Dev Studio
which is not compliance with ODE.

*"Those errors can be seen in both standalone and cluster mode. These are
bpel compilation errors logged by ODE server due to the extensions we have
introduced in BPS/Dev Studio, which are not compliance with ODE (They are
not errors actually).*
*If the package get deployed successfully, please ignore those error logs."*

[1] https://wso2.org/jira/browse/BPS-915

Regards,
Aparna

On Thu, Oct 29, 2015 at 2:39 PM, Vinod Kavinda  wrote:

> HI,
> Adding to above, some of those tags such as 'xml:space'  are not required
> that are added by dev studio. They can be removed from the model without
> affecting any functionality.
>
> Regards,
> Vinod Kavinda
>
> On Thu, Oct 29, 2015 at 2:36 PM, Vinod Kavinda  wrote:
>
>> Hi all,
>> Those errors can be seen in standalone mode also, they can be seen in
>> carbon logs. These are bpel compilation errors logged by ODE server due to
>> the extensions we have introduced in  BPS, which are not compliance with
>> ODE (They are not errors actually).
>> If the package get deployed successfully, please ignore those error logs.
>>
>> Regards,
>> Vinod
>>
>> On Thu, Oct 29, 2015 at 9:46 AM, Aparna Karunarathna 
>> wrote:
>>
>>> Hi all,
>>>
>>> I have attached the bpel package to the jira[1]
>>>
>>> [1] https://wso2.org/jira/browse/IDENTITY-3950
>>>
>>> Regards,
>>> Aparna
>>>
>>> On Wed, Oct 28, 2015 at 10:29 PM, Nandika Jayawardana 
>>> wrote:
>>>
 Hi,
 Can you attach the actual bpel package generated. It looks like some
 invalid content is generated into the bpel file.

 Regards
 Nandika

 On Wed, Oct 28, 2015 at 10:20 PM, Harsha Thirimanna 
 wrote:

> Is this intermittent ? Because I also reported this once earlier  in
> dev mail. This was happened intermittently earlier in standalone pack as
> well.
> On Oct 28, 2015 10:15 PM, "Chamila Wijayarathna" 
> wrote:
>
>> Hi all,
>>
>> Currently we are testing IS workflow feature with a BPS cluster. When
>> creating a new workflow, we have observed following error at BPS 
>> terminal.
>>
>> ERROR
>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
>>  
>> null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:51:17:cvc-complex-type.2.4.a:
>> Invalid content was found starting with element 'extensions'. One of '{"
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":import, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":partnerLinks,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":messageExchanges,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":variables,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":correlationSets,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":faultHandlers,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":eventHandlers,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":assign, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensate,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensateScope,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":empty, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":exit, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":extensionActivity,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":flow, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":forEach, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":if, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":invoke, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":pick, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":receive, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":repeatUntil,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":reply, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":rethrow, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":scope, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":sequence, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":throw, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":validate, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":wait, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":while}' is
>> expected.
>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler}
>> TID: [-1234] [] [2015-10-28 

Re: [Dev] [BPS] [Cluster] Error while deploying BPEL & HT packages

[Nandika Jayawardana]

Hi Aparana,

This extension is b4p extension. We have not modified ode compiler when
introducing the b4p extension, hence the warning. However, it does not have
any impact on the runtime.

Regards
Nandika

On Mon, Nov 2, 2015 at 1:54 AM, Aparna Karunarathna  wrote:

> Hi Nandika/ Chathura/ Hasitha,
>
> Shouldn't we fix this issue? Vinod has clearly mentioned in the jira[1]
> that this was getting from extension that introduced in BPS/Dev Studio
> which is not compliance with ODE.
>
> *"Those errors can be seen in both standalone and cluster mode. These are
> bpel compilation errors logged by ODE server due to the extensions we have
> introduced in BPS/Dev Studio, which are not compliance with ODE (They are
> not errors actually).*
> *If the package get deployed successfully, please ignore those error
> logs."*
>
> [1] https://wso2.org/jira/browse/BPS-915
>
> Regards,
> Aparna
>
> On Thu, Oct 29, 2015 at 2:39 PM, Vinod Kavinda  wrote:
>
>> HI,
>> Adding to above, some of those tags such as 'xml:space'  are not required
>> that are added by dev studio. They can be removed from the model without
>> affecting any functionality.
>>
>> Regards,
>> Vinod Kavinda
>>
>> On Thu, Oct 29, 2015 at 2:36 PM, Vinod Kavinda  wrote:
>>
>>> Hi all,
>>> Those errors can be seen in standalone mode also, they can be seen in
>>> carbon logs. These are bpel compilation errors logged by ODE server due to
>>> the extensions we have introduced in  BPS, which are not compliance with
>>> ODE (They are not errors actually).
>>> If the package get deployed successfully, please ignore those error logs.
>>>
>>> Regards,
>>> Vinod
>>>
>>> On Thu, Oct 29, 2015 at 9:46 AM, Aparna Karunarathna 
>>> wrote:
>>>
 Hi all,

 I have attached the bpel package to the jira[1]

 [1] https://wso2.org/jira/browse/IDENTITY-3950

 Regards,
 Aparna

 On Wed, Oct 28, 2015 at 10:29 PM, Nandika Jayawardana  wrote:

> Hi,
> Can you attach the actual bpel package generated. It looks like some
> invalid content is generated into the bpel file.
>
> Regards
> Nandika
>
> On Wed, Oct 28, 2015 at 10:20 PM, Harsha Thirimanna 
> wrote:
>
>> Is this intermittent ? Because I also reported this once earlier  in
>> dev mail. This was happened intermittently earlier in standalone pack as
>> well.
>> On Oct 28, 2015 10:15 PM, "Chamila Wijayarathna" 
>> wrote:
>>
>>> Hi all,
>>>
>>> Currently we are testing IS workflow feature with a BPS cluster.
>>> When creating a new workflow, we have observed following error at BPS
>>> terminal.
>>>
>>> ERROR
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} 
>>> -
>>>  
>>> null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:51:17:cvc-complex-type.2.4.a:
>>> Invalid content was found starting with element 'extensions'. One of '{"
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":import, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":partnerLinks,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":messageExchanges,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":variables,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":correlationSets,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":faultHandlers,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":eventHandlers,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":assign, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensate,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensateScope,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":empty, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":exit, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":extensionActivity,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":flow, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":forEach, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":if, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":invoke, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":pick, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":receive, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":repeatUntil,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":reply, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":rethrow, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":scope, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":sequence,
>>> 

Re: [Dev] [BPS] [Cluster] Error while deploying BPEL & HT packages

[Hasitha Aravinda]

Hi Harsha,



On Mon, Nov 2, 2015 at 11:46 PM, Harsha Thirimanna  wrote:

> Hi Vinod/Nandika,
> Can you please help to get resolve this BPEL package ? You guys always
> helped us to fix these kind of things :)
>

​Sure, We can guide you on this. It is a simple fix. Remove all xml:space
in BPEL file. If you know xml, you can fix it in no time.

Btw

​w​
e need some one from IS team to maintain these process ? (like what we do
in APIM
​​
) Not knowing
​ BPEL or xml is not an excuse and
 It is time to learn BPEL
​/BPMN​
​;​
)
​


>
> @Hasitha
> If these elements and attributes adding by Dev Studio and those are not
> expected by the BPEL compiler, IMO , we should eliminate it by the editor.
> So it is not an issue in IS side. Better to discuss with the relevant party
> and avoid this happen in future also.  Didn't you get this complain before
> when these BPEL created using dev studio and deploy it to the BPS ?
>

​As I mentioned earlier, that is not a bug in ether BPS or DevS. Those are
added as place holders preserve white spaces temporally, because IDEs are
not intelligent enough to predict what developers want to do next and
It is a xml standard. (Read http://www.xmlplease.com/xml/xmlspace/,
http://www.w3.org/TR/xml/#sec-white-space ).

But this attribute is not define in BPEL schema and BPEL compiler strictly
validating bpel files against BPEL schema. But In BPS we continue BPEL
compilation even on those validation
errors(-Dorg.apache.ode.compiler.failOnValidationErrors=false) because m
ost of
​times, ​
users don't care
​ and waste time​
​in​

​fixing

​these ​
kind of xml related issue
​s​
as long as BPEL structure is correct.
​Also it will make BPEL development
harder
​.​


If you don't like those
​ validation
errors, take
​a little time
 and remove those tags. But having it in BPEL
​ will not break BPEL execution.

Thanks,
Hasitha.
​



>
> *Harsha Thirimanna*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com
> * *
> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
> *twitter: **http://twitter.com/ *
> *harshathirimannlinked-in: **http:
> **//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
> *
>
> *Lean . Enterprise . Middleware*
>
>
> On Mon, Nov 2, 2015 at 11:33 PM, Hasitha Aravinda 
> wrote:
>
>> Hi Aparna,
>>
>> When you develop a BPEL process, eclipse editor adds xml:space attribute
>> temporally to handle white space [1]. Developer has to remove those
>> temporary attributes and initialize variable properly.
>>
>> xml:space attribute is not a part of the BPEL spec, hence BPEL compiler
>> report those as errors. It is not a bug, that is expected behavior. But
>> having those in BPEL make no harm.
>>
>> ​I went though attached BPEL. You can eliminate xml:space and other xml
>> elements related errors by modifying BPEL process. Those are not bugs of
>> ODE compiler, but problem of BPEL archive. Since IS is shipping this
>> BPEL archive, IMO we have to move this jira to IS space and track there.
>> WDYT ?
>>
>> [1] - http://www.xmlplease.com/xml/xmlspace/
>>
>> Thanks
>> Hasitha.
>>
>> On Mon, Nov 2, 2015 at 7:48 PM, Nandika Jayawardana 
>> wrote:
>>
>>> Hi Aparana,
>>>
>>> This extension is b4p extension. We have not modified ode compiler when
>>> introducing the b4p extension, hence the warning. However, it does not have
>>> any impact on the runtime.
>>>
>>> Regards
>>> Nandika
>>>
>>> On Mon, Nov 2, 2015 at 1:54 AM, Aparna Karunarathna 
>>> wrote:
>>>
 Hi Nandika/ Chathura/ Hasitha,

 Shouldn't we fix this issue? Vinod has clearly mentioned in the jira[1]
 that this was getting from extension that introduced in BPS/Dev Studio
 which is not compliance with ODE.

 *"Those errors can be seen in both standalone and cluster mode. These
 are bpel compilation errors logged by ODE server due to the extensions we
 have introduced in BPS/Dev Studio, which are not compliance with ODE (They
 are not errors actually).*
 *If the package get deployed successfully, please ignore those error
 logs."*

 [1] https://wso2.org/jira/browse/BPS-915

 Regards,
 Aparna

 On Thu, Oct 29, 2015 at 2:39 PM, Vinod Kavinda  wrote:

> HI,
> Adding to above, some of those tags such as 'xml:space'  are not
> required that are added by dev studio. They can be removed from the model
> without affecting any functionality.
>
> Regards,
> Vinod Kavinda
>
> On Thu, Oct 29, 2015 at 2:36 PM, Vinod Kavinda  wrote:
>
>> Hi all,
>> Those errors can be seen in standalone mode also, they can be seen in
>> carbon logs. These are bpel compilation errors logged by ODE server due 
>> to
>> the extensions we have introduced in  

Re: [Dev] [BPS] [Cluster] Error while deploying BPEL & HT packages

[Chamila Wijayarathna]

Hi Hasitha,

I our current BPEL definition, we have places which use xml:space like
following example.

**
*NULL*
**

So will replacing it with following code fix it?

**
*NULL*

**

Thanks!


On Tue, Nov 3, 2015 at 8:38 AM, Hasitha Aravinda  wrote:

> Hi Harsha,
>
>
>
> On Mon, Nov 2, 2015 at 11:46 PM, Harsha Thirimanna 
> wrote:
>
>> Hi Vinod/Nandika,
>> Can you please help to get resolve this BPEL package ? You guys always
>> helped us to fix these kind of things :)
>>
>
> ​Sure, We can guide you on this. It is a simple fix. Remove all xml:space
> in BPEL file. If you know xml, you can fix it in no time.
>
> Btw
>
> ​w​
> e need some one from IS team to maintain these process ? (like what we do
> in APIM
> ​​
> ) Not knowing
> ​ BPEL or xml is not an excuse and
>  It is time to learn BPEL
> ​/BPMN​
> ​;​
> )
> ​
>
>
>>
>> @Hasitha
>> If these elements and attributes adding by Dev Studio and those are not
>> expected by the BPEL compiler, IMO , we should eliminate it by the editor.
>> So it is not an issue in IS side. Better to discuss with the relevant party
>> and avoid this happen in future also.  Didn't you get this complain before
>> when these BPEL created using dev studio and deploy it to the BPS ?
>>
>
> ​As I mentioned earlier, that is not a bug in ether BPS or DevS. Those are
> added as place holders preserve white spaces temporally, because IDEs are
> not intelligent enough to predict what developers want to do next and
> It is a xml standard. (Read http://www.xmlplease.com/xml/xmlspace/,
> http://www.w3.org/TR/xml/#sec-white-space ).
>
> But this attribute is not define in BPEL schema and BPEL compiler strictly
> validating bpel files against BPEL schema. But In BPS we continue BPEL
> compilation even on those validation
> errors(-Dorg.apache.ode.compiler.failOnValidationErrors=false) because m
> ost of
> ​times, ​
> users don't care
> ​ and waste time​
> ​in​
>
> ​fixing
>
> ​these ​
> kind of xml related issue
> ​s​
> as long as BPEL structure is correct.
> ​Also it will make BPEL development
> harder
> ​.​
>
>
> If you don't like those
> ​ validation
> errors, take
> ​a little time
>  and remove those tags. But having it in BPEL
> ​ will not break BPEL execution.
>
> Thanks,
> Hasitha.
> ​
>
>
>
>>
>> *Harsha Thirimanna*
>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>> * *
>> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
>> *twitter: **http://twitter.com/ *
>> *harshathirimannlinked-in: **http:
>> **//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>>
>> On Mon, Nov 2, 2015 at 11:33 PM, Hasitha Aravinda 
>> wrote:
>>
>>> Hi Aparna,
>>>
>>> When you develop a BPEL process, eclipse editor adds xml:space attribute
>>> temporally to handle white space [1]. Developer has to remove those
>>> temporary attributes and initialize variable properly.
>>>
>>> xml:space attribute is not a part of the BPEL spec, hence BPEL compiler
>>> report those as errors. It is not a bug, that is expected behavior. But
>>> having those in BPEL make no harm.
>>>
>>> ​I went though attached BPEL. You can eliminate xml:space and other xml
>>> elements related errors by modifying BPEL process. Those are not bugs of
>>> ODE compiler, but problem of BPEL archive. Since IS is shipping this
>>> BPEL archive, IMO we have to move this jira to IS space and track there.
>>> WDYT ?
>>>
>>> [1] - http://www.xmlplease.com/xml/xmlspace/
>>>
>>> Thanks
>>> Hasitha.
>>>
>>> On Mon, Nov 2, 2015 at 7:48 PM, Nandika Jayawardana 
>>> wrote:
>>>
 Hi Aparana,

 This extension is b4p extension. We have not modified ode compiler when
 introducing the b4p extension, hence the warning. However, it does not have
 any impact on the runtime.

 Regards
 Nandika

 On Mon, Nov 2, 2015 at 1:54 AM, Aparna Karunarathna 
 wrote:

> Hi Nandika/ Chathura/ Hasitha,
>
> Shouldn't we fix this issue? Vinod has clearly mentioned in the
> jira[1] that this was getting from extension that introduced in BPS/Dev
> Studio which is not compliance with ODE.
>
> *"Those errors can be seen in both standalone and cluster mode. These
> are bpel compilation errors logged by ODE server due to the extensions we
> have introduced in BPS/Dev Studio, which are not compliance with ODE (They
> are not errors actually).*
> *If the package get deployed successfully, please ignore those error
> logs."*
>
> [1] https://wso2.org/jira/browse/BPS-915
>
> Regards,
> Aparna
>
> On Thu, Oct 29, 2015 at 2:39 PM, Vinod Kavinda  wrote:
>
>> HI,
>> Adding to above, some of those tags such as 'xml:space'  are not

Re: [Dev] [BPS] [Cluster] Error while deploying BPEL & HT packages

[Harsha Thirimanna]

On Tue, Nov 3, 2015 at 8:38 AM, Hasitha Aravinda  wrote:

> Hi Harsha,
>
>
>
> On Mon, Nov 2, 2015 at 11:46 PM, Harsha Thirimanna 
> wrote:
>
>> Hi Vinod/Nandika,
>> Can you please help to get resolve this BPEL package ? You guys always
>> helped us to fix these kind of things :)
>>
>
> ​Sure, We can guide you on this. It is a simple fix. Remove all xml:space
> in BPEL file. If you know xml, you can fix it in no time.
>
​Thanks​

​Hasitha​

>
> Btw
>
> ​w​
> e need some one from IS team to maintain these process ? (like what we do
> in APIM
> ​​
> ) Not knowing
> ​ BPEL or xml is not an excuse and
>  It is time to learn BPEL
> ​/BPMN​
> ​;​
> )
> ​
>
>
​Sorry for make misunderstand because we didn't tell we don't know. We will
try to fix these our self and if there any issues, will ask from BPS team.

>
>> @Hasitha
>> If these elements and attributes adding by Dev Studio and those are not
>> expected by the BPEL compiler, IMO , we should eliminate it by the editor.
>> So it is not an issue in IS side. Better to discuss with the relevant party
>> and avoid this happen in future also.  Didn't you get this complain before
>> when these BPEL created using dev studio and deploy it to the BPS ?
>>
>
> ​As I mentioned earlier, that is not a bug in ether BPS or DevS.
>
​If this is not a bug, then no issue :)​


> Those are added as place holders preserve white spaces temporally, because
> IDEs are not intelligent enough to predict what developers want to do next
> and
> It is a xml standard. (Read http://www.xmlplease.com/xml/xmlspace/,
> http://www.w3.org/TR/xml/#sec-white-space ).
>
> But this attribute is not define in BPEL schema and BPEL compiler strictly
> validating bpel files against BPEL schema. But In BPS we continue BPEL
> compilation even on those validation
> errors(-Dorg.apache.ode.compiler.failOnValidationErrors=false) because m
> ost of
> ​times, ​
> users don't care
> ​ and waste time​
> ​in​
>
> ​fixing
>
> ​these ​
> kind of xml related issue
> ​s​
> as long as BPEL structure is correct.
> ​Also it will make BPEL development
> harder
> ​.​
>
>
> If you don't like those
> ​ validation
> errors, take
> ​a little time
>  and remove those tags. But having it in BPEL
> ​ will not break BPEL execution.
>
​This is not a like or not like issue, but for complaining by the QA team.
Anyway are we going to same explanation to the customers also ?

>
> Thanks,
> Hasitha.
> ​
>
>
>
>>
>> *Harsha Thirimanna*
>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>> * *
>> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
>> *twitter: **http://twitter.com/ *
>> *harshathirimannlinked-in: **http:
>> **//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>>
>> On Mon, Nov 2, 2015 at 11:33 PM, Hasitha Aravinda 
>> wrote:
>>
>>> Hi Aparna,
>>>
>>> When you develop a BPEL process, eclipse editor adds xml:space attribute
>>> temporally to handle white space [1]. Developer has to remove those
>>> temporary attributes and initialize variable properly.
>>>
>>> xml:space attribute is not a part of the BPEL spec, hence BPEL compiler
>>> report those as errors. It is not a bug, that is expected behavior. But
>>> having those in BPEL make no harm.
>>>
>>> ​I went though attached BPEL. You can eliminate xml:space and other xml
>>> elements related errors by modifying BPEL process. Those are not bugs of
>>> ODE compiler, but problem of BPEL archive. Since IS is shipping this
>>> BPEL archive, IMO we have to move this jira to IS space and track there.
>>> WDYT ?
>>>
>>> [1] - http://www.xmlplease.com/xml/xmlspace/
>>>
>>> Thanks
>>> Hasitha.
>>>
>>> On Mon, Nov 2, 2015 at 7:48 PM, Nandika Jayawardana 
>>> wrote:
>>>
 Hi Aparana,

 This extension is b4p extension. We have not modified ode compiler when
 introducing the b4p extension, hence the warning. However, it does not have
 any impact on the runtime.

 Regards
 Nandika

 On Mon, Nov 2, 2015 at 1:54 AM, Aparna Karunarathna 
 wrote:

> Hi Nandika/ Chathura/ Hasitha,
>
> Shouldn't we fix this issue? Vinod has clearly mentioned in the
> jira[1] that this was getting from extension that introduced in BPS/Dev
> Studio which is not compliance with ODE.
>
> *"Those errors can be seen in both standalone and cluster mode. These
> are bpel compilation errors logged by ODE server due to the extensions we
> have introduced in BPS/Dev Studio, which are not compliance with ODE (They
> are not errors actually).*
> *If the package get deployed successfully, please ignore those error
> logs."*
>
> [1] https://wso2.org/jira/browse/BPS-915
>
> Regards,
> Aparna
>
> 

Re: [Dev] [BPS] [Cluster] Error while deploying BPEL & HT packages

[Vinod Kavinda]

Hi all,
Those errors can be seen in standalone mode also, they can be seen in
carbon logs. These are bpel compilation errors logged by ODE server due to
the extensions we have introduced in  BPS, which are not compliance with
ODE (They are not errors actually).
If the package get deployed successfully, please ignore those error logs.

Regards,
Vinod

On Thu, Oct 29, 2015 at 9:46 AM, Aparna Karunarathna 
wrote:

> Hi all,
>
> I have attached the bpel package to the jira[1]
>
> [1] https://wso2.org/jira/browse/IDENTITY-3950
>
> Regards,
> Aparna
>
> On Wed, Oct 28, 2015 at 10:29 PM, Nandika Jayawardana 
> wrote:
>
>> Hi,
>> Can you attach the actual bpel package generated. It looks like some
>> invalid content is generated into the bpel file.
>>
>> Regards
>> Nandika
>>
>> On Wed, Oct 28, 2015 at 10:20 PM, Harsha Thirimanna 
>> wrote:
>>
>>> Is this intermittent ? Because I also reported this once earlier  in dev
>>> mail. This was happened intermittently earlier in standalone pack as well.
>>> On Oct 28, 2015 10:15 PM, "Chamila Wijayarathna" 
>>> wrote:
>>>
 Hi all,

 Currently we are testing IS workflow feature with a BPS cluster. When
 creating a new workflow, we have observed following error at BPS terminal.

 ERROR
 {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
  
 null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:51:17:cvc-complex-type.2.4.a:
 Invalid content was found starting with element 'extensions'. One of '{"
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":import, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":partnerLinks,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":messageExchanges,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":variables, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":correlationSets,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":faultHandlers,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":eventHandlers,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":assign, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensate, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensateScope,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":empty, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":exit, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":extensionActivity,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":flow, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":forEach, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":if, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":invoke, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":pick, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":receive, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":repeatUntil,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":reply, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":rethrow, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":scope, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":sequence, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":throw, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":validate, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":wait, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":while}' is
 expected.
 {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler}
 TID: [-1234] [] [2015-10-28 03:30:39,230] ERROR
 {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
  
 null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:51:17:cvc-complex-type.2.4.a:
 Invalid content was found starting with element 'extensions'. One of '{"
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":import, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":partnerLinks,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":messageExchanges,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":variables, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":correlationSets,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":faultHandlers,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":eventHandlers,
 "http://docs.oasis-open.org/wsbpel/2.0/process/executable":assign, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensate, "
 http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensateScope,
 

Re: [Dev] [BPS] [Cluster] Error while deploying BPEL & HT packages

[Vinod Kavinda]

HI,
Adding to above, some of those tags such as 'xml:space'  are not required
that are added by dev studio. They can be removed from the model without
affecting any functionality.

Regards,
Vinod Kavinda

On Thu, Oct 29, 2015 at 2:36 PM, Vinod Kavinda  wrote:

> Hi all,
> Those errors can be seen in standalone mode also, they can be seen in
> carbon logs. These are bpel compilation errors logged by ODE server due to
> the extensions we have introduced in  BPS, which are not compliance with
> ODE (They are not errors actually).
> If the package get deployed successfully, please ignore those error logs.
>
> Regards,
> Vinod
>
> On Thu, Oct 29, 2015 at 9:46 AM, Aparna Karunarathna 
> wrote:
>
>> Hi all,
>>
>> I have attached the bpel package to the jira[1]
>>
>> [1] https://wso2.org/jira/browse/IDENTITY-3950
>>
>> Regards,
>> Aparna
>>
>> On Wed, Oct 28, 2015 at 10:29 PM, Nandika Jayawardana 
>> wrote:
>>
>>> Hi,
>>> Can you attach the actual bpel package generated. It looks like some
>>> invalid content is generated into the bpel file.
>>>
>>> Regards
>>> Nandika
>>>
>>> On Wed, Oct 28, 2015 at 10:20 PM, Harsha Thirimanna 
>>> wrote:
>>>
 Is this intermittent ? Because I also reported this once earlier  in
 dev mail. This was happened intermittently earlier in standalone pack as
 well.
 On Oct 28, 2015 10:15 PM, "Chamila Wijayarathna" 
 wrote:

> Hi all,
>
> Currently we are testing IS workflow feature with a BPS cluster. When
> creating a new workflow, we have observed following error at BPS terminal.
>
> ERROR
> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
>  
> null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:51:17:cvc-complex-type.2.4.a:
> Invalid content was found starting with element 'extensions'. One of '{"
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":import, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":partnerLinks,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":messageExchanges,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":variables,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":correlationSets,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":faultHandlers,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":eventHandlers,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":assign, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensate,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensateScope,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":empty, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":exit, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":extensionActivity,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":flow, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":forEach, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":if, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":invoke, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":pick, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":receive, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":repeatUntil,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":reply, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":rethrow, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":scope, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":sequence, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":throw, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":validate, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":wait, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":while}' is
> expected.
> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler}
> TID: [-1234] [] [2015-10-28 03:30:39,230] ERROR
> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
>  
> null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:51:17:cvc-complex-type.2.4.a:
> Invalid content was found starting with element 'extensions'. One of '{"
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":import, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":partnerLinks,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":messageExchanges,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":variables,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":correlationSets,
> 

[Dev] [BPS] [Cluster] Error while deploying BPEL & HT packages

[Chamila Wijayarathna]

Hi all,

Currently we are testing IS workflow feature with a BPS cluster. When
creating a new workflow, we have observed following error at BPS terminal.

ERROR
{org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
 
null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:51:17:cvc-complex-type.2.4.a:
Invalid content was found starting with element 'extensions'. One of '{"
http://docs.oasis-open.org/wsbpel/2.0/process/executable":import, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":partnerLinks, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":messageExchanges,
"http://docs.oasis-open.org/wsbpel/2.0/process/executable":variables, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":correlationSets, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":faultHandlers, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":eventHandlers, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":assign, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensate, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensateScope, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":empty, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":exit, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":extensionActivity,
"http://docs.oasis-open.org/wsbpel/2.0/process/executable":flow, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":forEach, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":if, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":invoke, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":pick, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":receive, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":repeatUntil, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":reply, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":rethrow, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":scope, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":sequence, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":throw, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":validate, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":wait, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":while}' is
expected.
{org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler}
TID: [-1234] [] [2015-10-28 03:30:39,230] ERROR
{org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
 
null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:51:17:cvc-complex-type.2.4.a:
Invalid content was found starting with element 'extensions'. One of '{"
http://docs.oasis-open.org/wsbpel/2.0/process/executable":import, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":partnerLinks, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":messageExchanges,
"http://docs.oasis-open.org/wsbpel/2.0/process/executable":variables, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":correlationSets, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":faultHandlers, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":eventHandlers, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":assign, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensate, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensateScope, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":empty, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":exit, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":extensionActivity,
"http://docs.oasis-open.org/wsbpel/2.0/process/executable":flow, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":forEach, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":if, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":invoke, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":pick, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":receive, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":repeatUntil, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":reply, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":rethrow, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":scope, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":sequence, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":throw, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":validate, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":wait, "
http://docs.oasis-open.org/wsbpel/2.0/process/executable":while}' is
expected.
{org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler}
TID: [-1234] [] [2015-10-28 03:30:39,231] ERROR
{org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
 

Re: [Dev] [BPS] [Cluster] Error while deploying BPEL & HT packages

[Harsha Thirimanna]

Is this intermittent ? Because I also reported this once earlier  in dev
mail. This was happened intermittently earlier in standalone pack as well.
On Oct 28, 2015 10:15 PM, "Chamila Wijayarathna"  wrote:

> Hi all,
>
> Currently we are testing IS workflow feature with a BPS cluster. When
> creating a new workflow, we have observed following error at BPS terminal.
>
> ERROR
> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
>  
> null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:51:17:cvc-complex-type.2.4.a:
> Invalid content was found starting with element 'extensions'. One of '{"
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":import, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":partnerLinks, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":messageExchanges,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":variables, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":correlationSets,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":faultHandlers,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":eventHandlers,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":assign, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensate, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensateScope,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":empty, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":exit, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":extensionActivity,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":flow, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":forEach, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":if, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":invoke, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":pick, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":receive, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":repeatUntil, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":reply, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":rethrow, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":scope, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":sequence, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":throw, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":validate, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":wait, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":while}' is
> expected.
> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler}
> TID: [-1234] [] [2015-10-28 03:30:39,230] ERROR
> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
>  
> null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:51:17:cvc-complex-type.2.4.a:
> Invalid content was found starting with element 'extensions'. One of '{"
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":import, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":partnerLinks, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":messageExchanges,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":variables, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":correlationSets,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":faultHandlers,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":eventHandlers,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":assign, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensate, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensateScope,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":empty, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":exit, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":extensionActivity,
> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":flow, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":forEach, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":if, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":invoke, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":pick, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":receive, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":repeatUntil, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":reply, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":rethrow, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":scope, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":sequence, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":throw, "
> http://docs.oasis-open.org/wsbpel/2.0/process/executable":validate, "
> 

Re: [Dev] [BPS] [Cluster] Error while deploying BPEL & HT packages

[Nandika Jayawardana]

Hi,
Can you attach the actual bpel package generated. It looks like some
invalid content is generated into the bpel file.

Regards
Nandika

On Wed, Oct 28, 2015 at 10:20 PM, Harsha Thirimanna 
wrote:

> Is this intermittent ? Because I also reported this once earlier  in dev
> mail. This was happened intermittently earlier in standalone pack as well.
> On Oct 28, 2015 10:15 PM, "Chamila Wijayarathna"  wrote:
>
>> Hi all,
>>
>> Currently we are testing IS workflow feature with a BPS cluster. When
>> creating a new workflow, we have observed following error at BPS terminal.
>>
>> ERROR
>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
>>  
>> null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:51:17:cvc-complex-type.2.4.a:
>> Invalid content was found starting with element 'extensions'. One of '{"
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":import, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":partnerLinks, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":messageExchanges,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":variables, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":correlationSets,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":faultHandlers,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":eventHandlers,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":assign, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensate, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensateScope,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":empty, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":exit, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":extensionActivity,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":flow, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":forEach, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":if, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":invoke, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":pick, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":receive, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":repeatUntil, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":reply, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":rethrow, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":scope, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":sequence, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":throw, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":validate, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":wait, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":while}' is
>> expected.
>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler}
>> TID: [-1234] [] [2015-10-28 03:30:39,230] ERROR
>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
>>  
>> null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:51:17:cvc-complex-type.2.4.a:
>> Invalid content was found starting with element 'extensions'. One of '{"
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":import, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":partnerLinks, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":messageExchanges,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":variables, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":correlationSets,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":faultHandlers,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":eventHandlers,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":assign, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensate, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensateScope,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":empty, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":exit, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":extensionActivity,
>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":flow, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":forEach, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":if, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":invoke, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":pick, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":receive, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":repeatUntil, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":reply, "
>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":rethrow, "
>> 

Re: [Dev] [BPS] [Cluster] Error while deploying BPEL & HT packages

[Aparna Karunarathna]

Hi all,

I have attached the bpel package to the jira[1]

[1] https://wso2.org/jira/browse/IDENTITY-3950

Regards,
Aparna

On Wed, Oct 28, 2015 at 10:29 PM, Nandika Jayawardana 
wrote:

> Hi,
> Can you attach the actual bpel package generated. It looks like some
> invalid content is generated into the bpel file.
>
> Regards
> Nandika
>
> On Wed, Oct 28, 2015 at 10:20 PM, Harsha Thirimanna 
> wrote:
>
>> Is this intermittent ? Because I also reported this once earlier  in dev
>> mail. This was happened intermittently earlier in standalone pack as well.
>> On Oct 28, 2015 10:15 PM, "Chamila Wijayarathna" 
>> wrote:
>>
>>> Hi all,
>>>
>>> Currently we are testing IS workflow feature with a BPS cluster. When
>>> creating a new workflow, we have observed following error at BPS terminal.
>>>
>>> ERROR
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
>>>  
>>> null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:51:17:cvc-complex-type.2.4.a:
>>> Invalid content was found starting with element 'extensions'. One of '{"
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":import, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":partnerLinks,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":messageExchanges,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":variables, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":correlationSets,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":faultHandlers,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":eventHandlers,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":assign, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensate, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensateScope,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":empty, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":exit, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":extensionActivity,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":flow, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":forEach, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":if, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":invoke, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":pick, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":receive, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":repeatUntil, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":reply, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":rethrow, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":scope, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":sequence, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":throw, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":validate, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":wait, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":while}' is
>>> expected.
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler}
>>> TID: [-1234] [] [2015-10-28 03:30:39,230] ERROR
>>> {org.apache.ode.bpel.compiler.bom.BpelObjectFactory$BOMSAXErrorHandler} -
>>>  
>>> null:file:///home/ubuntu/manager/wso2bps-3.5.0/repository/bpel/-1234/aa-10/aa.bpel:51:17:cvc-complex-type.2.4.a:
>>> Invalid content was found starting with element 'extensions'. One of '{"
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":import, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":partnerLinks,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":messageExchanges,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":variables, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":correlationSets,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":faultHandlers,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":eventHandlers,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":assign, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensate, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":compensateScope,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":empty, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":exit, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":extensionActivity,
>>> "http://docs.oasis-open.org/wsbpel/2.0/process/executable":flow, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":forEach, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":if, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":invoke, "
>>> http://docs.oasis-open.org/wsbpel/2.0/process/executable":pick, "
>>>