Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

PowerBuilder to Workspace?

4 posts in General Discussion Last posting was on 2008-06-18 17:33:10.0Z
Cory Johnson Posted on 2008-04-21 14:55:46.0Z
Sender: 3afe.480caa37.1804289383@sybase.com
From: Cory Johnson
Newsgroups: sybase.public.workspace.general
Subject: PowerBuilder to Workspace?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <480caaf2.3b1e.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 21 Apr 2008 07:55:46 -0700
X-Trace: forums-1-dub 1208789746 10.22.241.41 (21 Apr 2008 07:55:46 -0700)
X-Original-Trace: 21 Apr 2008 07:55:46 -0700, 10.22.241.41
Lines: 10
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:687
Article PK: 1088365

Are there any documents/guidelines out there for migrating
from PB to Workspace as a Sybase J2EE development
environment? Or is there no migration path between these 2
at all?

My main concern is the use of the '4GL event model' in
PowerBuilder and how that may or may not apply in the
Workspace environment

Thanks...


"Paul Horan[TeamSybase]" Posted on 2008-04-22 05:07:56.0Z
From: "Paul Horan[TeamSybase]" <phoran AT sybase DOT com>
Newsgroups: sybase.public.workspace.general
References: <480caaf2.3b1e.1681692777@sybase.com>
Subject: Re: PowerBuilder to Workspace?
Lines: 39
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <480d72ac$1@forums-1-dub>
Date: 21 Apr 2008 22:07:56 -0700
X-Trace: forums-1-dub 1208840876 10.22.241.152 (21 Apr 2008 22:07:56 -0700)
X-Original-Trace: 21 Apr 2008 22:07:56 -0700, vip152.sybase.com
X-Authenticated-User: teamsybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:688
Article PK: 1088366


<Cory Johnson> wrote in message news:480caaf2.3b1e.1681692777@sybase.com...
> Are there any documents/guidelines out there for migrating
> from PB to Workspace as a Sybase J2EE development
> environment? Or is there no migration path between these 2
> at all?
>
> My main concern is the use of the '4GL event model' in
> PowerBuilder and how that may or may not apply in the
> Workspace environment
>
> Thanks...

I'm not sure if I understand your question. PB is not a J2EE development
environment at all, and you don't write PowerScript in Workspace, There's
never been a "migration plan" between the two IDEs...

I would recommend using the two tools concurrently, for the tasks they're
designed for:
If you've licensed the PowerDesigner data modeling components, you'd do that
task inside Workspace. You'd also do database tooling (stored
procedure/trigger development and debugging) using the Workspace Data
Tooling component. You'd write your Windows client side apps using
PowerBuilder. If your architecture called for server-side components, you
could write them in Java using the Java development features that are part
of Eclipse (which you get with or without Workspace). You could also write
your server components in PowerBuilder - and deploy them to EAServer
directly, or any J2EE server using the PB App Server plugin. If the app
server is EAServer, there's a tooling component for that in Workspace too.
There are other features and components available in the Workspace bundle,
but none of them are replacements for PowerBuilder... In fact, the JSF
development features of Workspace allow you to incorporate PB datawindow
objects into your JSF applications.

In other words, a migration strategy from one to the other is not really
relevant.

Paul Horan[TeamSybase]


Cory Johnson Posted on 2008-04-28 17:01:11.0Z
Sender: 3eab.4815fe65.1804289383@sybase.com
From: Cory Johnson
Newsgroups: sybase.public.workspace.general
Subject: Re: PowerBuilder to Workspace?
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <481602d7.3efd.1681692777@sybase.com>
References: <480d72ac$1@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 28 Apr 2008 10:01:11 -0700
X-Trace: forums-1-dub 1209402071 10.22.241.41 (28 Apr 2008 10:01:11 -0700)
X-Original-Trace: 28 Apr 2008 10:01:11 -0700, 10.22.241.41
Lines: 68
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:693
Article PK: 1088369


> <Cory Johnson> wrote in message
> > news:480caaf2.3b1e.1681692777@sybase.com... Are there
> > any documents/guidelines out there for migrating from PB
> > to Workspace as a Sybase J2EE development environment?
> > Or is there no migration path between these 2 at all?
> >
> > My main concern is the use of the '4GL event model' in
> > PowerBuilder and how that may or may not apply in the
> > Workspace environment
> >
> > Thanks...
>
> I'm not sure if I understand your question. PB is not a
> J2EE development environment at all, and you don't write
> PowerScript in Workspace, There's never been a "migration
> plan" between the two IDEs...
>
> I would recommend using the two tools concurrently, for
> the tasks they're designed for:
> If you've licensed the PowerDesigner data modeling
> components, you'd do that task inside Workspace. You'd
> also do database tooling (stored procedure/trigger
> development and debugging) using the Workspace Data
> Tooling component. You'd write your Windows client side
> apps using PowerBuilder. If your architecture called for
> server-side components, you could write them in Java
> using the Java development features that are part of
> Eclipse (which you get with or without Workspace). You
> could also write your server components in PowerBuilder -
> and deploy them to EAServer directly, or any J2EE server
> using the PB App Server plugin. If the app server is
> EAServer, there's a tooling component for that in
> Workspace too. There are other features and components
> available in the Workspace bundle, but none of them are
> replacements for PowerBuilder... In fact, the JSF
> development features of Workspace allow you to incorporate
> PB datawindow objects into your JSF applications.
>
> In other words, a migration strategy from one to the other
> is not really relevant.
>
> Paul Horan[TeamSybase]
>
>

I understand your comments regarding using PowerBuilder for
building components and deploying them to EAServer or any
other J2EE server - we currently are using PB components and
EAServer for this. I also am aware that Workspace supports
datawindows, but my question centers around the JSP Targets
within PowerBuilder.
PowerBuilder is used for our Windows app development (no
issues there) and we are currently using version 10.0.1 of
PB to do all our web development using the JSP target. As
part of the JSP target, you can make use of the '4GL event
model' on the jsp pages, and we've made fairly extensive use
of that.

Of course this event model is specific to PowerBuilder, so I
was wondering if there's a way of getting all these JSPs
we'be built in PowerBuilder into Workspace via some sort of
migration or something and it would preserve or rework the
code related to the 4GL model to work under Workspace
Seeing as how Workspace is now the recommended J2EE tool
from Sybase, and PowerBuilder support for the JSP target has
ended with version 11.2, I'm wondering if we're looking at a
rewrite of our pages if/when we switch to a different J2EE
tool


Chris Pollach Posted on 2008-06-18 17:33:10.0Z
From: "Chris Pollach" <cpollach@travel-net.com>
Newsgroups: sybase.public.workspace.general
References: <480d72ac$1@forums-1-dub> <481602d7.3efd.1681692777@sybase.com>
Subject: Re: PowerBuilder to Workspace?
Lines: 82
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <485946d6$1@forums-1-dub>
Date: 18 Jun 2008 10:33:10 -0700
X-Trace: forums-1-dub 1213810390 10.22.241.152 (18 Jun 2008 10:33:10 -0700)
X-Original-Trace: 18 Jun 2008 10:33:10 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:718
Article PK: 1088402

Cory;

I think that you have a good question as I can definitely see the end of
Web Targets in general in PB 11.5 beta.

--
Regards ... Chris
ISUG - NA RUG Director
http://chrispollach.pbdjmagazine.com

<Cory Johnson> wrote in message news:481602d7.3efd.1681692777@sybase.com...
>> <Cory Johnson> wrote in message
>> > news:480caaf2.3b1e.1681692777@sybase.com... Are there
>> > any documents/guidelines out there for migrating from PB
>> > to Workspace as a Sybase J2EE development environment?
>> > Or is there no migration path between these 2 at all?
>> >
>> > My main concern is the use of the '4GL event model' in
>> > PowerBuilder and how that may or may not apply in the
>> > Workspace environment
>> >
>> > Thanks...
>>
>> I'm not sure if I understand your question. PB is not a
>> J2EE development environment at all, and you don't write
>> PowerScript in Workspace, There's never been a "migration
>> plan" between the two IDEs...
>>
>> I would recommend using the two tools concurrently, for
>> the tasks they're designed for:
>> If you've licensed the PowerDesigner data modeling
>> components, you'd do that task inside Workspace. You'd
>> also do database tooling (stored procedure/trigger
>> development and debugging) using the Workspace Data
>> Tooling component. You'd write your Windows client side
>> apps using PowerBuilder. If your architecture called for
>> server-side components, you could write them in Java
>> using the Java development features that are part of
>> Eclipse (which you get with or without Workspace). You
>> could also write your server components in PowerBuilder -
>> and deploy them to EAServer directly, or any J2EE server
>> using the PB App Server plugin. If the app server is
>> EAServer, there's a tooling component for that in
>> Workspace too. There are other features and components
>> available in the Workspace bundle, but none of them are
>> replacements for PowerBuilder... In fact, the JSF
>> development features of Workspace allow you to incorporate
>> PB datawindow objects into your JSF applications.
>>
>> In other words, a migration strategy from one to the other
>> is not really relevant.
>>
>> Paul Horan[TeamSybase]
>>
>>
>
> I understand your comments regarding using PowerBuilder for
> building components and deploying them to EAServer or any
> other J2EE server - we currently are using PB components and
> EAServer for this. I also am aware that Workspace supports
> datawindows, but my question centers around the JSP Targets
> within PowerBuilder.
> PowerBuilder is used for our Windows app development (no
> issues there) and we are currently using version 10.0.1 of
> PB to do all our web development using the JSP target. As
> part of the JSP target, you can make use of the '4GL event
> model' on the jsp pages, and we've made fairly extensive use
> of that.
>
> Of course this event model is specific to PowerBuilder, so I
> was wondering if there's a way of getting all these JSPs
> we'be built in PowerBuilder into Workspace via some sort of
> migration or something and it would preserve or rework the
> code related to the 4GL model to work under Workspace
> Seeing as how Workspace is now the recommended J2EE tool
> from Sybase, and PowerBuilder support for the JSP target has
> ended with version 11.2, I'm wondering if we're looking at a
> rewrite of our pages if/when we switch to a different J2EE
> tool