DC or non DC

[Former Member]

Hi Friends,

For developing small size webdynpro application I want to decide which approach is ok.

I want to go for without using DC as I dont have idea about DC approach.

will that be okay?

and.. can I version the webdynpro prject wihout DC approach?

Or, instead or versioing can I ask other people to make local projects, and later on all can be used to cerate webdynpro iviews.

Thanks in advance!

Message was edited by: Nav

[Former Member · Accepted solution]

Hi,

Can u please post all ur questions regarding webdynpro under forum category 'Application Server -> Webdynpro '? Kindly post all ur questions related to portal content development in this forum.

Regards,

Harini S

[Former Member · Accepted solution]

Thanks Srinivasan, Murali.

so, I got idea that I should go ahead with plain webdynpro aplications as of now.

as you said I can import these plain projects into DC project later on..is it possible? then at that time I can reengineer the application if the applications is expected as huge later on.

is that correct?

Thanks!

Thanks Harini!

Yes from now onwards I will put webdynpro questions in webdynpro forum, but sometimes here I find quick solutions.

[Murali_Shanmu]

Hi

To start with, you can put JDI away. If you are going to create small applications, it is not required. JDI is required when you have lot of developments going on in parallel.

Murali.

[Former Member]

Hi,

You can develop a plain Web Dynpro application in case you have no idea about DC of Web Dynpro type. Later the project can be imported/ included in the DC. There is no suggested way of version management without JDI (DTR) in the NWDS environment.

You can create iViews in portal for your Web Dynpro applications, using a template.

Regards

Srinivasan T