[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [smila-dev] [bpel-dev] Editing SMILA pipelines in BPEL Designer

Hi Bob,
 
would be fine for me - but I'm not the one who decides that.
 
Igor is currently on vacation, I'm sure he will answer your question next week.
 
Tobias

________________________________

Von: smila-dev-bounces@xxxxxxxxxxx im Auftrag von Bob Brodt
Gesendet: Mo 17.1.11 17:01
An: Smila project developer mailing list
Cc: bpel-dev@xxxxxxxxxxx
Betreff: Re: [smila-dev] [bpel-dev] Editing SMILA pipelines in BPEL Designer



Hi Igor & Tobias,

I would like to start building SWTBot tests for the BPEL Designer to try to catch regressions. The plan is to come up with an initial suite that tests basic functionality, and then add to it whenever a new bug fix is applied.

There is a sample extension activity in the eclipse cvs repo (org.eclipse.bpel/examples/plugins/org.eclipse.bpel.extensionsample.model and org.eclipse.bpel/examples/plugins/org.eclipse.bpel.extensionsample.ui) but it is pretty simple and limited in scope.

I was wondering if I could use the extensions that you guys are working on for SMILA once they are finished, and import the source as an additional example into the BPEL designer project.

Please let me know if you have any concerns or objections.

Thanks!

_______________________________________
Robert ("Bob") Brodt
Senior Software Engineer, JBoss Riftsaw
JBoss by Red Hat

----- Original Message -----
> Tanks Bob for looking at it!
>
> BTW: I hope you'll be able to provide us the fix soon since now we are
> really keen on using the BPEL designer for creating and maintaining
> SMILA's workflows.
>
> Cheers
> Igor
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: bpel-dev-bounces@xxxxxxxxxxx
> [mailto:bpel-dev-bounces@xxxxxxxxxxx] Im Auftrag von Bob Brodt
> Gesendet: Freitag, 14. Januar 2011 01:23
> An: Smila project developer mailing list
> Cc: bpel-dev@xxxxxxxxxxx
> Betreff: Re: [bpel-dev] [smila-dev] Editing SMILA pipelines in BPEL
> Designer
>
> Hi gang,
>
> This is apparently a bit more complicated than I had originally
> thought. The problem stems from the fact that an <extensionActivity>
> element is not treated the same as other BPEL elements when it is
> deserialized, instead the model object for the child element (in this
> case, an <invokePipelet> or <invokeService>) is created in the place
> of an ExtensionActivity object. In doing so, the
> ReconciliationBPELReader fails to add the newly constructed object to
> a parent (e.g. a Sequence or Scope or some other structured
> container). This of course leads to all kinds of problems because the
> assumption is that all model objects are ultimately contained (through
> a hierarchy) by the root Process.
>
> This definitely looks like a bug in the editor. I'll keep y'all posted
> on my progress.
>
> _______________________________________
> Robert ("Bob") Brodt
> Senior Software Engineer, JBoss Riftsaw
> JBoss by Red Hat
>
> ----- Original Message -----
> > > I'll have a look at this today...
> > That would be great!
> >
> > Cheers
> > Igor
> >
> > ----- Original Message -----
> > > Hello Igor,
> > >
> > > I fixed the bugs from your report
> > > (https://bugs.eclipse.org/bugs/show_bug.cgi?id=332926
> > > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=332926> ).
> > >
> > > @BPEL Designer Dev Team:
> > > I have no idea, how to synchronize the changes made in the
> > > "Source"
> > > view back to the EMF objects to see them in the "Design" view.
> > > Even
> > > changing the activity name in the source view is not working, I
> > > suspected that at least that would work out of the box. Any
> > > suggestions or examples to accomplish that task?
> > >
> > > Thanks,
> > > Tobias Liefke
> > _______________________________________________
> > smila-dev mailing list
> > smila-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/smila-dev
> _______________________________________________
> bpel-dev mailing list
> bpel-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/bpel-dev
> _______________________________________________
> smila-dev mailing list
> smila-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/smila-dev
_______________________________________________
smila-dev mailing list
smila-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/smila-dev


<<winmail.dat>>