Development Strategy

Hi,
Assume that we want to develop applications which will run on EP. We have the following choices for development tools;
- Web Dynpro for Java/ABAP
- Pure Java (JSP)
- Portal Application (PAR). Applications Developed with PDK --> is this correct?
My question is all about Portal Applications. I appeciate if you help me to make it clear,
Q1. What is the language used for Portal Applications? May be I've to ask, What languages can be used for Portal Applications?
Q2. Is Javascript coding possible with Portal Applications?
Q3. In what circumstances we have to choose development of a Portal Application instead of a WD of JSP applications?
My best regards

Hi,
In addition to the above....
Webdynpro is preferred when minimum coding is required and applications are to be developed fast with minimal time and effort.
WD is also used when components are to be reused. Also highly skilled programmers are not needed to develop a WD application.
Java script can be used with Portal applications. Refer docs on creating Portal Applications. U'll get to know better.
Regards,
Pooja.

Similar Messages

FAO Adobe: What is Adobe's mobile development strategy?

We've been trying to establish where Adobe is going with mobile development but just can't figure it out. Can anyone clarify please?
For example, when will Dreamweaver be updated to properly support the latest versions of Phonegap/Cordova (i.e. v3.x)? Or is there no commitment to Phonegap? Blackberry, WebOS, Symbian are still shown but not supported. And Windows Phone is supported but not shown.
There seems to be a lack of interest from Adobe for Phonegap/Dreamweaver support.
Alongside our investment in Flash, which is now killed off, we previously invested time in native app development, then started using FlashBuilder because of Adobe's support for mobile app development, but Flashbuilder isn't properly supported now. Then switched to dreamweaver/phonegap because of Adobe's commitment to develop once and distribute to many platforms. But it seems to be a dwindling commitment and Phonegap isn't planned to support Blackberry 10. Creative Cloud seemed like a step towards supporting better development and faster access to updated software but the products have hardly been updated since we adopted it. So, we're just trying to establish if there is a strategy or go back to native app development with eclipse and xcode or look for another solution.
We've recently seen "Adobe Experience Manager" in the press but it seems like a lot of marketing blurb with no real substance in terms of a development strategy and how the Adobe products fit in.
Any clarification of the strategy would be really useful. Anyone got any ideas?

Hi Ronny,
you only have the two possibilities which where shown: Backweb or Attachments. As you say I got more bad experience with Attachments due to the fact that you need BP's or Activities. If you are using SAP Portal my recommendation is Backweb. I installed it under CRM 3.0 and it is really good. Easy to use and reliable. Admins need 30 min for training, Enduser about 5 Minutes and it works - what should I say more
Andreas

Development Strategy Input Request

I have a client who wishes to add Purchase Requests from an existing external Java application into SRM 7.0 on a SAP ECC 5.0 ERP platform. Their request proposes that this could be easily accomplished using the "BAPI_REQUISITION_CREATE" transaction.
We've downloaded the NetWeaver 7.02 ABAP Trial to evaluate possible development strategies. With a desire to follow established Best Practices we could use some advice on the best development approach.
Does the NetWeaver 7.02 ABAP platform offer the best and most appropriate development environment? If so, can we add SRM functionality to test on?
Will the Trial version suffice for the development simple non-UI application for the submission of Purchase Requests? We do not have SAP deployed in our development environment.
Which would be the better approach, ABAP or Java? If Java is the recommended approach, is the Trial development environment suffice?
Any guidance or recommendations would be greatly appreciated. Thanks in advance!

Hi,
In addition to the above....
Webdynpro is preferred when minimum coding is required and applications are to be developed fast with minimal time and effort.
WD is also used when components are to be reused. Also highly skilled programmers are not needed to develop a WD application.
Java script can be used with Portal applications. Refer docs on creating Portal Applications. U'll get to know better.
Regards,
Pooja.

UI5 Development Strategy

Hi All,
I am new to UI5.
I am getting confused because of UI5 development options.
If i am not wrong, we can deploy UI5 to ABAP server or to a Java server.
What is SAP's standard recommendation?
To develop UI5 and store as BSP in ABAP repository or
To develop and deploy to Java server
Thanks
Rakesh

Hi,
Rakesh Varman Gopalakrishnan wrote:
If i am not wrong, we can deploy UI5 to ABAP server or to a Java server.
Yes we can deploy UI5 application to ABAP or JAVA server.
What is SAP's standard recommendation?
To develop UI5 and store as BSP in ABAP repository or
To develop and deploy to Java server
It depends on your systems, server infrastructure. if you are using SAP Gateway and want to consume those OData services then you can develop application to consume it and then deploy the application to GW ABAP application server.
Regards,
Chandra

Mobile Development Strategy

Iu2019m confused with some of the surrounding technologies for the development of mobile applications. For a mobile application I am working on, I have exposed a u201Cbapiu201D as a web service through ICF. I can consume the web service in my mobile application. The intended audience for the application would be licensed u201Cprofessionalu201D (named) users so I assume licensing should not be a problem.
The question, what role and why do I concern myself with the following when developing mobile applications?
Mobile Infrastructure, Gateway, SUP (Sybase unwired platform), PI(XI), .Net Connector (NCo) 3.0.

Hello Russ,
When you are creating a simple application (no big data transactions and less user), it could be feasible to use the way as you said.
But when there is need for the following, we need such infrastructure to manage applications.
1. dynamic data distribution
2. multiple mobile platform support
3. trusted and reliable data flow.
4. data conflict detection
and many more.
You can find more info about the the insfrastructure architecture here
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0c9feea-935e-2e10-a997-c1baec36f9f4?QuickLink=index&overridelayout=true&50968377078543
Thanks, Senti

Migration/Development Strategy

Hi,
Can any one provide me the information about:
- Strategy for migrating Intranet/Exisitng web site to Oracle Portal.
- Methodology for new Portal devlopment.
Many Thanks,
Divyesh Desai

Hi,
You could find some info. on this on www.portalstudio.oracle.com
Thanks,
Anu

Developing with ADF BC or TopLink

We are a Higher Education PeopleSoft Student Administration, Financial and HR shop and are interested in gaining expertise with technology that will benefit us for when we implement Fusion Application technology. We are in the process of developing a web application using JDeveloper ADF and would like to know if we should focus our development using ADF BC or TopLink. I was under the impression that TopLink would be the best way to go, but I encountered a comment on a web site ( http://www.odtug.com/fusionjava_sig.htm ) "Fusion Java Development SIG topics of interest do not include:Non-Fusion technologies supported by JDeveloper (JSP/Struts, TopLink and JClient) and I would like to know if we should rethink our development strategy and focus on ADF BC.
Thank you

The decision of whether to go with TopLink or ADF BC as the implementation for persistence usually depends on the background of the developers.
I wrote about it here:
http://blogs.oracle.com/shay/2006/03/10
Since most of the developers at Oracle who are going to work on the Fusion generation of applications are coming from a 4GL background (Forms, BC4J, Peopletools etc) - the decision was made to use ADF Business Components in Fusion Applications.
This combination also provide us with the most out of the box features and less coding.

Development Methodology

Hi Friends and Experts,
Can any one please let me know what is Development methodology used in ABAP.

***********Please reward points ,if found useful
Hi,
ASAP: Accelerated Systems Application and Products in Data Processing
ASAP methodoligy means nothing but standard process for implementation of SAP, It consists of 5 phases.
1. Project preperation - consists of identifying team members and developing strategy as how to go.
2. Business Blue print - consists of identifying the client current process, reqeirement and how SAP provides solution.
Consists of detailed documentaion
3. Realization -The purpose of this phase is to implement all the business and process requirements based on the
Business Blueprint.
4 Final Preparation - The purpose of this phase is to complete testing, end-user training,
5 Go Live and Support
All the functinal consultatns need good rapo with Abapers. right from uploading of legacy data, devoloping customised reports, BDC's, Forms etc, here functinal consultatns need to give guidence as to get the requried data for reports and all.. like the table name, fields etc
All implementation projects have the the following phases:
Scoping - What is to be implemented i.e. which submodules are to be implemented some clients may not require credit management for example. Look at the project scope document carefully it will tell you what SAP sub-modules in SAP you should be prepared for. Usually the sales people along with project manager do it.
As is - Here you understand the existing business processes of the client . Your BPOcollect all the ISO-documentation (if client is ISO certified), reports and forms at this stage and you analyse how and when the reports/forms are generated, where the data is coming from. You also do a Level -2 training for your BPO so he is made aware of all the required transactions in SAP.
Once this is over BPO can start learning with the consultants help more about SAP. This is crucial because if you miss out any transactions the BPO may forget about some of his Business processes which may come up later. It is a good practice to ask the BPO to make flow charts to explain business processes.
To-Be - Parallely you map these processes to SAP. Processes that you are not sure of as to whether they are present in SAP or not you try to do a configuration of those processes, and along with the BPO(Business process owner he is the clients employee who knows about the clients business processes probably a middle management guy, ther can more than one), BPO involvement is required as he may be able to tell you his requirements better. Once you do the business modelling you
will also be made aware of the gaps between as-is and to-be , here decisons have to be made as to wether a ABAP development/system modification is required or not and so on. Involve the BPO as much as possible and document everything it is good practice do not be lazy about it.
Business blueprint: Here the as-is and to-be and gap analysis is explained. This is the document that you will be using to do your configuration in the realization phase.
Realization phase: Here you do the configuration in the development server (there are three clients -development,quality, production). You also decide on the master data format, so that BPO can go collect the master data. You also gove ABAP specifications for forms, reports etc, system modifications etc. Unit testing: Your BPOs and a few key users sit down and test your configuration in your module only. It is good to test the BDCs that you need for uploading data at this stage so you have more realistic data and your BDCs are tested.
Integration testing:
Once all modules unit testing is over then the configuration is trasported to the Quality server, where testing for all the modules is done by BPOs and end user, this is to check if any problems are there in integration between various modules. Once all is okay from the QA server config is transported to the production server.
Go live preparation
Data uploading: The collected master data is checked and the uploaded into production server(sever and client I have used interchangeably). Now you are ready for go live i.e. users can now use the production server.
With Regards,
BVS

Open Hub in BW 3.1

Hi,
Can someone please clarify me about open hub steps in SAP BW version 3.1. I no more have access to 3.1 system as of now but has to put my views for a new development strategy. I am not sure whether it had something like InfoSpoke what we use in version 3.5 (I worked in 3.5 too).
Also if you can throw some light on its licensing then it would be great. I am not sure license would be required or not when customer uses open hub to extract data from SAP BW 3.1 InfoProvide.
Ritika Sharma

I need to clarify if any of you have idea about SAP BW 3.1, whether it has InfoSpoke? And will our customer need to have license if data from InfoProviders has to be extracted?
We have to use InfoSpoke as a one time activity to extract data from SAP BW InfoProviders.
Any clarification on the same would be appreciated.
Ritika Sharma

Brief introduction of J2EE

un Microsystems, Inc. in 1996 launched a new pure object-oriented programming language, called Java. Java technology has become the software industry appears one of the most important technology, this platform has nothing to do with the emergence of the programming language, immediately set off a revolution in the software industry, the Internet is now the most popular programming language . Java is a way to explain through the implementation of the language, characterized as: a simple, object-oriented, not dependent on the structure of machines, with portability, robustness, security, and provided with a mechanism and the modern network The perfect combination of technology. At present, in accordance with the Sun Microsystems Web site (http://java.sun.com) announced the standards, depending on the Java language applications will be divided into three platforms:
Java 2 Platform Micro Edition as J2ME, Java 2 Platform Micro Edition. For the development of handheld computers, mobile phones and other mobile communications equipment for use on embedded systems.
Java 2 Platform Standard Edition as J2SE, Java 2 Platform Standard Edition. Mainly used for the development of general desktop applications.
Java 2 Platform Enterprise Edition called J2EE, Java 2 Enterprise Edition platform, To be used for rapid design, development, deployment and management of enterprise-class software system.
J2EE is to use Java to develop a set of extended enterprise norms, it provides component-based design, development, deployment and management of enterprise application solutions. J2EE standards must be based on the J2SE platform, which not only consolidated the Standard Edition of the many advantages, For example, "a compiler, run everywhere" cross-platform features, convenient and efficient database technology to provide seamless connectivity JDBC (Java Data Base Connectivity, Java database connectivity), in Internet applications to ensure data integrity of the security model and support multi - Threading technology, At the same time also against Servlet / JSP, EJB, JMS, JTS / JTA, JCAT and XML technology to provide a comprehensive support. J2EE has been able to establish a set of enterprise-class software application development, shorten the product development cycle structure of the standard system.
In fact, J2EE has become the industrial development of enterprise-class standards and mainstream platform. J2EE for the establishment of a high-availability, high scalability, easy maintenance of enterprise-class system provides the perfect mechanism and the framework model. In J2EE to provide the unified development platform, can greatly reduce development costs and the application of multi-storey complex, the need for high-availability, high security and high scalability software services and the lack of funding for businesses, J2EE the middle Integrated framework of the competent and fully meet their requirements. At the same time, J2EE itself with the comprehensive directory services support and a high degree of security mechanisms and efficient performance show, and many other advantages, for the smooth integration of enterprise application systems have played an enormous role.
J2EE-based enterprise applications, without any particular operating system, network environment, the shackles of hardware platforms.Applications can be developed and deployed in the heterogeneous environment, and to ensure that the system of portability. Therefore, as long as the J2EE development of a standardized system can be deployed to various operating system platforms and network platforms. J2EE as a long-term stable performance, enterprise-class applications platform, to protect 7 ? 24 hours of uninterrupted services to meet customers, partners, the needs of enterprises is an ideal platform for the operation of Internet globalization is an inevitable requirement for the development of the objective. J2EE high scalability features in today's "on demand" (IBM Corporation to the end of 2002) the popularity of e-commerce strategies of the times, made an outstanding contribution. J2EE using load-balancing strategy, the system software and hardware resources to maximize utilization and performance, eliminate bottlenecks in the system. Allow the deployment of integrated multiple servers, and can be highly scalable systems, the preservation of existing enterprise IT assets to reduce repetitive investment in the future but also to meet the needs of business applications.
J2EE Technical
In J2EE platforms, including a large number of technology, in order to provide developers with more comprehensive support.
Servlet Technology Servlet Web application development is the foundation. It is entirely in Java language development is the Java platform on the CGI technology. It runs on the server-side J2EE containers, with high efficiency, to dynamically load and dynamically generate Web pages. Servlet Specializes in process control and conduct of business, the expansion of services for enterprise development strategy tailored and flexible.
JSP technology Its essence is still Servlet, only to create two different ways. JSP documents from HTML files, Java and JSP label procedures constitute a fragment. JSP will be the first through the analyzer generates the Servlet source files, and then compile this document Servlet running. JSP Servlet and, with very high operating efficiency.
JNDI technology Java Naming and Directory Interface, as JNDI. J2EE application components are usually located in different physical address of the machine, so the need for a mechanism to facilitate client users to find and use J2EE components and enterprise system resources. In J2EE system, the use of JNDI technical positioning various objects, including EJB objects, database-driven targets, JDBC data source object and connect information, and other objects. JNDI functions for the application to provide a unified interface to complete the standard definition of directory operations, such as through the object properties to find the target and positioning.

Very hard to read. OP needs to work on his grammar. Not especially accurate either.
When, inevitably, people start arriving here and asking "pls send me teh intro 2 jeee" I suggest they read this link instead:
[http://java.sun.com/developer/technicalArticles/J2EE/Intro/|http://java.sun.com/developer/technicalArticles/J2EE/Intro/]
(They won't of course...)

Export Import to Maintain Test and Production Environments

We have developed an application using Locally built Database Providers in Oracle Portal 9.0.2.6 which is installed to 2 schemas, has 5 different providers, and over 100 Portal major components (Forms, Reports, and Calendars) and over 200 minor components (LOV's and Links). We have used export/import transport sets with some luck, but it is a struggle becuase the import procedures are not very robust. Many things (such as missing LOV's, corrupt components, preexisting versions, etc, etc.) can cause an import to fail. And the cleanup necessary to finally achieve a successful import can be very time-consuming.
Having a robust import mechanism is very important to our strategy for keeping installed (our own and clients') portal instances up-to-date with our latest release. Some of the enhancements that would make it much easier to develop and maintain Portal applications include:
Within the Portal:
1. Ability to copy an entire provider within the same portal (rather than one component at a time).
2. Ability to change the schema to which a Provider is associated.
3. When copying a component from one provider to another, the dependent items (i.e. LOVs and Links) should be copied to new second provider as well. (i.e. rather rebuilding each LOV in each provider and then editing each form to point to the new LOVs)
Transport Sets:
4. Should allow for changing provider names and provider schema, and global component name changes, and resetting unqiue id's on import (to create copy rather than overwrite).
5. Should allow the option to ignore errors and import all components which pass pre-check (rather than failing all components if all items do not pass pre-check).
How are other Portal Developers dealing with installing and then rolling out new sets of Locally built Database Providers from Development environments to Production? Are there any whitepapers on the best practices for replicating/installing a portal application to a new portal instance and then keeping it updated?
Oracle, are any of my wish-list items above on the future enhancement lists? Or have others figured out workarounds?
Thanks,
Trenton

There are a couple of references which can be found on Portalstudio.oracle.com that are of some use:
1. A FAQ for Portal 9.0.2.6 Export/Import http://portalstudio.oracle.com/pls/ops/docs/FOLDER/COMMUNITY/OTN_CONTENT/MAINPAGE/DEPLOY_PERFORM/9026_EXPORT_IMPORT_FAQ_0308.HTM
2. Migration Instructions by Larry Boussard (BRUSARDL)
3. Migrating Oracle Portal from Dev Systems to Production Systems bt Dheeraj Kataria.
These are all useful documents for a successful first-time Export-Import. However, the limitations and lack of robustness I listed in my first post, make the process so time-consuming and error fraught as to not be a practical development strategy.

About project

Hi ,
Any body pls explain about different steps present in a project development and supporting .
And how we will submit our project to the client .
I want detail description about real time environment Technical terms.

Different stages involved in implementation project
ASAP Methodology:
1) Project preperation - It consists of identifying team members and developing strategy as how to go.
2) Business Blueprint - consists of identifying the client current process, reqeirement and how SAP provides solution. Consists of detailed documentaion
3) Realization -This phase is to implement all the business and process requirements based on the Business Blueprint.
4) Final Preparation - This phase is to complete testing, end-user training,
5) Go-Live - The project end date
6) Support & Maitainance - Support to the enduser

ASAP Methodlology : Its very urgent

Hi all,

I heard that ASAP methodology works good with R/3 and it is having drawbacks when it comes to BW. Could you please tell me wat all the issues( problems ) we face wen we implement BW with ASAP methodology.
P.S: And also send me if u have any docs of ASAP methodology.
Thanks and regards,
Shiva shekar k.
Message was edited by:
 shiva shekar k

Hi,
What is ASAP?
ASAP: Accelerated Systems Application and Products in Data Processing
All implementation projects have the the following phases:
Scoping - What is to be implemented i.e. which submodules are to be implemented some clients may not require credit management for example. Look at the project scope document carefully it will tell you what SAP sub-modules in SAP you should be prepared for. Usually the sales people along with project manager do it.
As is - Here you understand the existing business processes of the client . Your BPOcollect all the ISO-documentation (if client is ISO certified), reports and forms at this stage and you analyse how and when the reports/forms are generated, where the data is coming from. You also do a Level -2 training for your BPO so he is made aware of all the required transactions in SAP.
Once this is over BPO can start learning with the consultants help more about SAP. This is crucial because if you miss out any transactions the BPO may forget about some of his Business processes which may come up later. It is a good practice to ask the BPO to make flow charts to explain business processes.
To-Be - Parallely you map these processes to SAP. Processes that you are not sure of as to whether they are present in SAP or not you try to do a configuration of those processes, and along with the BPO(Business process owner he is the clients employee who knows about the clients business processes probably a middle management guy, ther can more than one), BPO involvement is required as he may be able to tell you his requirements better. Once you do the business modelling you
will also be made aware of the gaps between as-is and to-be , here decisons have to be made as to wether a ABAP development/system modification is required or not and so on. Involve the BPO as much as possible and document everything it is good practice do not be lazy about it.
Business blueprint: Here the as-is and to-be and gap analysis is explained. This is the document that you will be using to do your configuration in the realization phase.
Realization phase: Here you do the configuration in the development server (there are three clients -development,quality, production). You also decide on the master data format, so that BPO can go collect the master data. You also gove ABAP specifications for forms, reports etc, system modifications etc. Unit testing: Your BPOs and a few key users sit down and test your configuration in your module only. It is good to test the BDCs that you need for uploading data at this stage so you have more realistic data and your BDCs are tested.
Integration testing:
Once all modules unit testing is over then the configuration is trasported to the Quality server, where testing for all the modules is done by BPOs and end user, this is to check if any problems are there in integration between various modules. Once all is okay from the QA server config is transported to the production server.
Go live preparation
Data uploading: The collected master data is checked and the uploaded into production server(sever and client I have used interchangeably). Now you are ready for go live i.e. users can now use the production server.
Read ASAP methodology for more details you will understand better.
Thirumallasetty
ASAP methodoligy means nothing but standard process for implementation of SAP, It consists of 5 phases.
1. Project preperation - consists of identifying team members and developing strategy as how to go.
2. Business Blue print - consists of identifying the client current process, reqeirement and how SAP provides solution.
 Consists of detailed documentaion
3. Realization -The purpose of this phase is to implement all the business and process requirements based on the
 Business Blueprint.
4 Final Preparation - The purpose of this phase is to complete testing, end-user training,
5 Go Live and Support
All the functinal consultatns need good rapo with Abapers. right from uploading of legacy data, devoloping customised reports, BDC's, Forms etc, here functinal consultatns need to give guidence as to get the requried data for reports and all.. like the table name, fields etc
Thanks,
Medha.

Can anyone explain steps in ASAP Methodology

Can anyone explain steps in ASAP Methodology

Hi,
What is ASAP?
ASAP: Accelerated Systems Application and Products in Data Processing
All implementation projects have the the following phases:
Scoping - What is to be implemented i.e. which submodules are to be implemented some clients may not require credit management for example. Look at the project scope document carefully it will tell you what SAP sub-modules in SAP you should be prepared for. Usually the sales people along with project manager do it.
As is - Here you understand the existing business processes of the client . Your BPOcollect all the ISO-documentation (if client is ISO certified), reports and forms at this stage and you analyse how and when the reports/forms are generated, where the data is coming from. You also do a Level -2 training for your BPO so he is made aware of all the required transactions in SAP.
Once this is over BPO can start learning with the consultants help more about SAP. This is crucial because if you miss out any transactions the BPO may forget about some of his Business processes which may come up later. It is a good practice to ask the BPO to make flow charts to explain business processes.
To-Be - Parallely you map these processes to SAP. Processes that you are not sure of as to whether they are present in SAP or not you try to do a configuration of those processes, and along with the BPO(Business process owner he is the clients employee who knows about the clients business processes probably a middle management guy, ther can more than one), BPO involvement is required as he may be able to tell you his requirements better. Once you do the business modelling you
will also be made aware of the gaps between as-is and to-be , here decisons have to be made as to wether a ABAP development/system modification is required or not and so on. Involve the BPO as much as possible and document everything it is good practice do not be lazy about it.
Business blueprint: Here the as-is and to-be and gap analysis is explained. This is the document that you will be using to do your configuration in the realization phase.
Realization phase: Here you do the configuration in the development server (there are three clients -development,quality, production). You also decide on the master data format, so that BPO can go collect the master data. You also gove ABAP specifications for forms, reports etc, system modifications etc. Unit testing: Your BPOs and a few key users sit down and test your configuration in your module only. It is good to test the BDCs that you need for uploading data at this stage so you have more realistic data and your BDCs are tested.
Integration testing:
Once all modules unit testing is over then the configuration is trasported to the Quality server, where testing for all the modules is done by BPOs and end user, this is to check if any problems are there in integration between various modules. Once all is okay from the QA server config is transported to the production server.
Go live preparation
Data uploading: The collected master data is checked and the uploaded into production server(sever and client I have used interchangeably). Now you are ready for go live i.e. users can now use the production server.
Read ASAP methodology for more details you will understand better.
ASAP methodoligy means nothing but standard process for implementation of SAP, It consists of 5 phases.
1. Project preperation - consists of identifying team members and developing strategy as how to go.
2. Business Blue print - consists of identifying the client current process, reqeirement and how SAP provides solution.
Consists of detailed documentaion
3. Realization -The purpose of this phase is to implement all the business and process requirements based on the
Business Blueprint.
4 Final Preparation - The purpose of this phase is to complete testing, end-user training,
5 Go Live and Support
All the functinal consultatns need good rapo with Abapers. right from uploading of legacy data, devoloping customised reports, BDC's, Forms etc, here functinal consultatns need to give guidence as to get the requried data for reports and all.. like the table name, fields etc
Reward If Helpfull,
Naresh

Is Adobe Air doomed?

Now that I have your attention - I don't subscribe to the "sky is falling", "Adobe is making the worst mistake ever" kind of panic-based cries out there in regards to the latest strategy shift annoucements regarding flash.
Knowing quite well the capabilities/limitations of HTML5/js, the horrible tooling and the apparent W3C decisions like "let's just ignore Sqllite as a client side db and support an inferior name/value pair store like indexdb with a 2MB limit as a standard", there is no doubt in my mind that Adobe Air is still a phenomenal cross platform mobile development strategy.
This is only true, though, IFF it is also true that Adobe is doubling up on Air for a cross platform native development platform.
Just going through this forum in detail, I see so many unanswered posts (from months ago) and so many people frustrated with the lack of response. Part of winning people back and turning around the public announcement mistakes recently committed goes through creating a happy developer echo system. Adobe Air developers should be able to successfully use this phenomenal technology and create significant commercial successes and then the proof will be in the pudding.
Adobe - you have to partially dedicate a number of your Air development team resources to this forum and have every single question properly answered in very little time. This will dramatically turn around developer loyalty, create a significant number of commercial successes and allow the platform to prove itself as a bellter alternative to HTML5/css3/js.
And - please start by helping me out with my question that has received 0 replies in a week. Tell me I haven't provided enough information or something - please...!
http://forums.adobe.com/thread/943234

I have created a project that clearly reproduces the bug. Here are the steps:
1) Create a UrlLoader and point it to https://www.google.com
2) Load it
3) Run in Flash Builder 4.6/Air 3.1 and then run in Android emulator. The former works with an http status 200. The latter gives you an ioerror 2032.
Here is the self contained View code which works with a TabbedViewNavigatorApplication:
<?xml version="1.0" encoding="utf-8"?>
<s:View xmlns:fx="http://ns.adobe.com/mxml/2009"
 xmlns:s="library://ns.adobe.com/flex/spark"
 xmlns:mx="library://ns.adobe.com/flex/mx"
 xmlns:ns1="*"
 xmlns:local="*"
 creationComplete="windowedapplication1_creationCompleteHandler(event)"
 actionBarVisible="true" tabBarVisible="true">
 <fx:Script>
 <![CDATA[
 import mx.events.FlexEvent;
 protected var requestTokenUrl:String = "https://www.google.com";
 protected function windowedapplication1_creationCompleteHandler(event:FlexEvent):void
 var loader:URLLoader = new URLLoader();
 loader.addEventListener(ErrorEvent.ERROR, onError);
 loader.addEventListener(AsyncErrorEvent.ASYNC_ERROR, onAsyncError);
 loader.addEventListener(SecurityErrorEvent.SECURITY_ERROR, securityErrorHandler);
 loader.addEventListener(HTTPStatusEvent.HTTP_RESPONSE_STATUS, httpResponseStatusHandler);
 loader.addEventListener(IOErrorEvent.IO_ERROR, ioErrorHandler);
 var urlRequest:URLRequest = new URLRequest(requestTokenUrl);
 loader.load(urlRequest);
 protected function requestTokenHandler(event:Event):void
 protected function httpResponse(event:HTTPStatusEvent):void
 label.text += event.status;
 // TODO Auto-generated method stub
 private function completeHandler(event:Event):void {
 label.text += event.toString();
 trace("completeHandler data: " + event.currentTarget.data);
 private function openHandler(event:Event):void {
 label.text += event.toString();
 trace("openHandler: " + event);
 private function onError(event:ErrorEvent):void {
 label.text += event.toString();
 trace("onError: " + event.type);
 private function onAsyncError(event:AsyncErrorEvent):void {
 label.text += event.toString();
 trace("onAsyncError: " + event);
 private function onNetStatus(event:NetStatusEvent):void {
 label.text += event.toString();
 trace("onNetStatus: " + event);
 private function progressHandler(event:ProgressEvent):void {
 label.text += event.toString();
 trace("progressHandler loaded:" + event.bytesLoaded + " total: " + event.bytesTotal);
 private function securityErrorHandler(event:SecurityErrorEvent):void {
 label.text += event.toString();
 trace("securityErrorHandler: " + event);
 private function httpStatusHandler(event:HTTPStatusEvent):void {
 label.text += event.toString();
 //label.text += event.responseHeaders.toString();
 trace("httpStatusHandler: " + event);
 private function httpResponseStatusHandler(event:HTTPStatusEvent):void {
 label.text += event.toString();
 trace("httpStatusHandler: " + event);
 private function ioErrorHandler(event:IOErrorEvent):void {
 label.text += event.toString();
 label.text += event.text;
 trace("ioErrorHandler: " + event);
 ]]>
 </fx:Script>
 <fx:Declarations>
 
 </fx:Declarations>
 <s:Label id="label" y="185" width="100%" color="#0A0909" horizontalCenter="0" text=""/>
</s:View>

Development Strategy

Similar Messages

Maybe you are looking for