Difference between node and element in context.

Hi
I have below context elements.
Root Context
Node Test
Value T1
Now there are 2 ways I can access to value attribute t1.
1.
wdContext.currentTestElement().getT1()
2.
wdContext.nodeTest().currentTestElement().getT1();
What is difference.

Thanks for comments,
But after working on it now as I find is :
If your elements are subject to exist n times at runtime, in that case currentcontextelement automatically gives you access to active context node. Wereas, nodexxx() gives access to the node element as a group, after which you can access to any elemt inside that node group. e.g.
wdContext.nodeTest().getElementAt(n)
Thanks

Similar Messages

What is the difference between Lightroom and Elements?

I'm trying to decide between Photoshop Elements and Lightroom--both for a Mac. They seem to have very similar photo editing features. Could anyone tell me some of the differences so that I can see which would be better for my work? One feature that I have to have is the ability to add text to a photo. In Photoshop I can do this with the text tool and layers. Is this a feature of Lightroom too?

Ligtroom is far more like a cross between Bridge and Camera RAW than anything like Elements. LR is designed to work with and process larger quantities of RAW files. It also works with TIFF and jpeg but these are secondary to RAW. LR has some local adjustment ability, with limited brushes and tools. LR has sophistocated databased library structure that allows search and keywording functions even when images are off line. LR allows easy batch editing and synching of RAW settings to multiple files and the creation of multiple 'recipies" in RAW conversion without the need to create multiple files. You don't need to make jpegs to create a simple web page or print files from LR. It will do these directly from the RAW files. LR is completely non-destructive. Exporting an image will make a new file with the changes you specify. Nothing you do will alter the original file.
Elements is for pixel pushing. It allows far more local controls, and manipulation at a pixel level compared to the mostly global controls of LR. In other words it's easier to work on individual parts of an image in Elements. Elements is designed for you to spend more time on an individual file compared to LR which is designed to work on larger quantities of files in a less intricate manner. Cloning, etc are easier/more powerful in Elements. Elements supports stitching and layers. Elements lets you work with text and images. LR does not in any meaningful way (except maybe adding a watermark). Making changes in Elements and then saving the file will permanently change it.
In a nutshell if you're working with larger quantities of images you may prefer LR. However you'll probably still need a pixel editor (like Elements) occasionally. If you work in lower image quantities then Elements is the way to go. You'll still have Bridge to find files/process raw files, but not files that are *offline*. I would suggest Elements first and then add LR when you need its powerfull organisational/search/RAW conversion/non-destructive workflow abilities.
Gordon

Would someone tell me the difference between PS13 and Elements !

what are the differences between elements 13 and PS 13

I'm sure there's a link somewhere which lays out the differences explicitly. But from a top level, Elements is a slimmed down version of Photoshop that is geared towards a quicker and easier user experience. It has more "one click" options for optimizing color, reducing redeye, etc - the main, basic edits that most people want to do to their photos. Photoshop, on the other hand, is an advanced photo editor and comes with a learning curve; it's designed to be a full fledged digital editor from the "film" photographer, to the digital artist, compositors, layout, etc. Even basic edits can be difficult to figure out until you know your way around the program. It' more powerful, but more difficult to learn. That said, some people don't want to spend the time learning it, they just want some basic, quick editing tools.
I can't remember the list off the top of my head, but Elements had a couple restrictions that made it a non-starter for me. First and foremost, Elements won't let you edit multiple layers in 16 bits. Something that won't affect many, but for any high level compositing it's a not go. On top of that, they removed features like the pen tool, paths, curves, channels, smart objects, etc. These probably don't mean anything to you, but to those of use that use PS these are the basic building blocks of our work.

Difference Between Normal and External Context Mapping

Hi,
I wonder the Difference Between Normal and External Context Mapping.
I1ve already read the docs and articles but I didnt understand.
Thanks,
Jorge Luiz
Edited by: Jorge Castro on Oct 9, 2008 4:23 PM

Jorge,
With this type of Mapping (also called Reverse Mapping) you can map the context of an using component, to that of the used component.
You can find an example of this concept in WDA ALV: If you look at component SALV_WD_TABLE (which you declare as used when you intend to use ALV), you'll see that it has a node DATA declared as external. In your using component, you map your actual data node to this node.
This allows the ALV to leave the DATA node type open and so to be reused, adjusting it's structure depending on the using component's data.
Edited by: Alejandro Bindi on Oct 9, 2008 4:42 PM
Made a mistake! Have not used this in a while...Ext. mapping is the OTHER way...Using -map-> Used Fixed.

Camera differences between Photoshop and Photoshop Elements

Does photoshop elements support RAW in the same way as the full programme does through Bridge?
Message title was edited by: Brett N

Here are the documented differences:
Adobe Camera Raw differences between Photoshop and Photoshop Elements
More info about Elements raw support can be found here:
FAQ: Will Photoshop Elements work with my camera, or Why won't my raw files open?

Difference between size and length of a node

Dear All ,
Can anybody please let meknow what is the difference between size and length of a node in webdynpro java
what is the code for finding a node that how many attributes it is holding in runtime
Thanks in advance.

Dear Krishnakk
You can call the SIZE() method of the NODES and LENGTH() method on ATTRIBUTES.
Like if you have node Employee and Employee_ID and Employee_Name are attibute under it. suppose you have already populated the node employee.
***what is the code for finding a node that how many attributes it is holding in runtime
You have to identified the which node will be called based on the user actions;
You can fin the size of the node to identify number of the rows holding at runtime. loop through for to find the attributes
IWDMessageManager messageManager = wdComponentAPI.getMessageManager();
if(wdContext.nodeEmployee.size() > 0)
         //Print Node size
         messageManager.reportSuccess("Size of the Node ::"+wdContext.nodeEmployee.size() );
         for(int i=0; i<wdContext.nodeEmployee.size(); i++
                 //Print Length of the Attributes Employee ID and Name
                 messageManager.reportSuccess("Length of the Employee Name ::"+wdContext.nodeEmployee().getEmployeeElementAt(i).getEmployee_ID().length());
                 messageManager.reportSuccess("Length of the Employee ID ::"+wdContext.nodeEmployee().getEmployeeElementAt(i).getEmployee_Name().length());
Hope it will helps
Best Regards
Arun Jaiswal

What is the difference between SWF and F4V in the context of Streaming or progressive Download?

Hello everybody,
I am absolutely a beginner in working with Captivate and furthermore my technological know how is not that good.
So, I have problems to understand if the export formats SWF and F4V are both capable to be published in the Internet as streaming video and as progressive Download? Well so, I do not really understand the difference between streaming and progessive download either?
Furthermore I was asking myself if this issue depends on how I imported flash videos (there are these two options) in my Captivate project during the production phase?
I would be very thankful for some helping information!
Greetings,
Mareike the beginner

Welcome to our community
I'm not certain I fully understand the differences myself, but will toss out what I believe to be true about the formats. Hopefully, if I'm incorrect in my bellief, someone with more definitive knowledge will chime in.
It was explained to me a couple of years back and is my understanding that "streaming" only applies to a video based format such as F4V, FLV and it doesn't apply to SWF. With SWF, you may specify a preload value. So when the SWF transmits from the web server to the PC, a certain percentage has to be received before play begins. But that's not streaming. It's preloading.
For streaming to occur, the web server establishes a communication channel between the server and the destination PC. This channel is monitored to see what speed is in use. Only enough information is then transmitted to be comfortable at that speed. If the speed improves during the connection, the server serves data at a faster rate. If the connection degrades, the information transmitted is also scaled back so as to accommodate the lower speed.
With SWF, after it has all been downloaded, a savvy user is able to poke around in their temporary internet files and save the SWF for play later. With streaming, this isn't possible because as the stream is viewed, it evaporates from memory.
Seriously hoping others will chime in here to confirm or deny this.
Cheers... Rick
Helpful and Handy Links
Begin learning Captivate 5 moments from now! $29.95
Captivate Wish Form/Bug Reporting Form
Adobe Certified Captivate Training
SorcererStone Blog
Captivate eBooks

Mapping: Difference between createIf and ifWithoutElse

Suppose i have some condition based on which i am creating a node. Is there any difference between createIf and ifWithoutElse for creating the node (with or without context change)?

Hi Mala,
1. IfWithoutElse is usually used to set the filters in mapping. When If condition is satisfied the value of then is returned in output.
Else value is depends upon the mapping, i.e. where u want this value ( target or in function)
2. Createif is used to insert any structuring element in the target structure if it is not present in source.
To create a condition based node you have to go to CreateIf function as ifWithoutElse is boolean function deals with the true n false status of values and not with node creation.
Regards,
Shri
Reward points if u understood the concept.

What's the Difference Between OLAP and OLTP?

HI,
What's the difference between OLAP and OLTP ? and which one is Best?
-Arun.M.D

Hi,
The big difference when designing for OLAP versus OLTP is rooted in the basics of how the tables are going to be used. I'll discuss OLTP versus OLAP in context to the design of dimensional data warehouses. However, keep in mind there are more architectural components that make up a mature, best practices data warehouse than just the dimensional data warehouse.
Corporate Information Factory, 2nd Edition by W. H. Inmon, Claudia Imhoff, Ryan Sousa
Building the Data Warehouse, 2nd Edition by W. H. Inmon
With OLTP, the tables are designed to facilitate fast inserting, updating and deleting rows of information with each logical unit of work. The database design is highly normalized. Usually and at least to 3NF. Each logical unit of work in an online application will have a relatively small scope with regard to the number of tables that are referenced and/or updated. Also the online application itself handles the majority of the work for joining data to facilitate the screen functions. This means the user doesn't have to worry about traversing across large data relationship paths. A heavy dose of lookup/reference tables and much focus on referential integrity between foreign keys. The physical design of the database needs to take into considerations the need for inserting rows when deciding on physical space settings. A good book for getting a solid base understanding of modeling for OLTP is The Data Modeling Handbook: A Best-Practice Approach to Building Quality Data Models by Michael C. Reingruber, William W. Gregory.
Example: Let's say we have a purchase oder management system. We need to be able to take orders for our customers, and we need to be able to sell many items on each order. We need to capture the store that sold the item, the customer that bought the item (and where we need to ship things and where to bill) and we need to make sure that we pull from the valid store_items to get the correct item number, description and price. Our OLTP data model will contain a CUSTOMER_MASTER, A CUSTOMER_ADDRESS_MASTER, A STORE_MASTER, AN ITEM_MASTER, AN ITEM_PRICE_MASTER, A PURCHASE_ORDER_MASTER AND A PURCHASE_ORDER_LINE_ITEM table. Then we might have a series of M:M relationships for example. An ITEM might have a different price for specific time periods for specific stores.
With OLAP, the tables are designed to facilitate easy access to information. Today's OLAP tools make the job of developing a query very easy. However, you still want to minimize the extensiveness of the relational model in an OLAP application. Users don't have the wills and means to learn how to work through a complex maze of table relationships. So you'll design your tables with a high degree of denormalization. The most prevalent design scheme for OLAP is the Star-Schema, popularized by Ralph Kimball. The star schema has a FACT table that contains the elements of data that are used arithmatically (counting, summing, averaging, etc.) The FACT Table is surrounded by lookup tables called Dimensions. Each Dimension table provides a reference to those things that you want to analyze by. A good book to understand how to design OLAP solutions is The Data Warehouse Toolkit: Practical Techniques for Building Dimensional Data Warehouses by Ralph Kimball.
Example: let's say we want to see some key measures about purchases. We want to know how many items and the sales amount that are purchased by what kind of customer across which stores. The FACT table will contain a column for Qty-purchased and Purchase Amount. The DIMENSION tables will include the ITEM_DESC (contains the item_id & Description), the CUSTOMER_TYPE, the STORE (Store_id & store name), and TIME (contains calendar information such as the date, the month_end_date, quarter_end_date, day_of_week, etc).
Database Fundamentals > Data Warehousing and Business Intelligence with Mike Lampa
Search Advice from more than 250 TechTarget Experts
Your question may have already been answered! Browse or search more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.

Can someone explain the difference between TIER_WEB and TIER_WEBDEV

Hi All,
We have two sets of values in Context file as below.
<TIER_ADWEB oa_var="s_isAdWeb">NO</TIER_ADWEB>
<TIER_ADFORMS oa_var="s_isAdForms">NO</TIER_ADFORMS>
<TIER_ADFORMSDEV oa_var="s_isAdFormsDev">NO</TIER_ADFORMSDEV>
<TIER_ADWEBDEV oa_var="s_isAdWebDev">NO</TIER_ADWEBDEV>
Could you explain the difference between
TIER_WEB and TIER_WEBDEV
and
TIER_ADFORMS and TIER_ADFORMSDEV

These values in a shared APPL_TOP system. Pl see ML Doc 745580.1 (Apply Patches in a Shared Application Tier File System Environment) for an explanation.Not necessarily in Shared APPL_TOP, even in traditional multi-node installation you will find these values in the application context file.
I never came across any document which describes the difference between TIER_WEBDEV and TIER_WEB, I just can say that these variables always have the same value.

What is the difference between lap and oltp

HI experts, I want to know the difference between OLAP and OLTP and why OLTP cannot be used in bw instead of OLAP? Need realtime anwsers please!!!!!!!!!!

hi navin...
Online transactional processing (OLTP) is designed to efficiently process high volumes of transactions, instantly recording business events (such as a sales invoice payment) and reflecting changes as they occur.
Online analytical processing (OLAP) is designed for analysis and decision support, allowing exploration of often hidden relationships in large amounts of data by providing unlimited views of multiple relationships at any cross-section of defined business dimensions.
OLTP databases are typically input sources for data warehouses or data marts. The data warehouse in turn is the typical source of data for an OLAP database. The value in an OLAP database is that many complex calculations and predefined queries are preprocessed and results are stored and are available via an OLAP exploitation application allowing quick access to cross-sections of business data. Rapid access to the aggregate information across defined business dimensions allows quick navigation and understanding of relationships.
The challenge is to find a solution that will both supply the necessary functionality while addressing the technical considerations of your organization. Some other important considerations include choosing technologies that can leverage existing investments in both hardware and software, and are open and integrated so that your applications are adaptable. This ensures flexibility and agility to meet future business demands.
There are several different modeling techniques. Snowflake and star schemas are just two of many choices. Deciding the best approach for your situation will depend on several factors, most importantly understanding the business issue, the users and their information needs. There is a wealth of information available, including courses, texts and guidelines on this subject alone
OLAP systems organize data in a multidimensional model that is suitable for decision support. OLAP is the analytical counterpart of OLTP, or Online Transactional Processing. SAP's BW is an OLAP system
The Impact of the OLAP/OLTP Cultural Conflict on Data Warehousing....check this link....
http://www.georgetown.edu/users/allanr/Impact.pdf
also check...
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci977813,00.html
The big difference when designing for OLAP versus OLTP is rooted in the basics of how the tables are going to be used. I'll discuss OLTP versus OLAP in context to the design of dimensional data warehouses. However, keep in mind there are more architectural components that make up a mature, best practices data warehouse than just the dimensional data warehouse.
Corporate Information Factory, 2nd Edition by W. H. Inmon, Claudia Imhoff, Ryan Sousa
Building the Data Warehouse, 2nd Edition by W. H. Inmon
With OLTP, the tables are designed to facilitate fast inserting, updating and deleting rows of information with each logical unit of work. The database design is highly normalized. Usually and at least to 3NF. Each logical unit of work in an online application will have a relatively small scope with regard to the number of tables that are referenced and/or updated. Also the online application itself handles the majority of the work for joining data to facilitate the screen functions. This means the user doesn't have to worry about traversing across large data relationship paths. A heavy dose of lookup/reference tables and much focus on referential integrity between foreign keys. The physical design of the database needs to take into considerations the need for inserting rows when deciding on physical space settings. A good book for getting a solid base understanding of modeling for OLTP is The Data Modeling Handbook: A Best-Practice Approach to Building Quality Data Models by Michael C. Reingruber, William W. Gregory.
Example: Let's say we have a purchase oder management system. We need to be able to take orders for our customers, and we need to be able to sell many items on each order. We need to capture the store that sold the item, the customer that bought the item (and where we need to ship things and where to bill) and we need to make sure that we pull from the valid store_items to get the correct item number, description and price. Our OLTP data model will contain a CUSTOMER_MASTER, A CUSTOMER_ADDRESS_MASTER, A STORE_MASTER, AN ITEM_MASTER, AN ITEM_PRICE_MASTER, A PURCHASE_ORDER_MASTER AND A PURCHASE_ORDER_LINE_ITEM table. Then we might have a series of M:M relationships for example. An ITEM might have a different price for specific time periods for specific stores.
With OLAP, the tables are designed to facilitate easy access to information. Today's OLAP tools make the job of developing a query very easy. However, you still want to minimize the extensiveness of the relational model in an OLAP application. Users don't have the wills and means to learn how to work through a complex maze of table relationships. So you'll design your tables with a high degree of denormalization. The most prevalent design scheme for OLAP is the Star-Schema, popularized by Ralph Kimball. The star schema has a FACT table that contains the elements of data that are used arithmatically (counting, summing, averaging, etc.) The FACT Table is surrounded by lookup tables called Dimensions. Each Dimension table provides a reference to those things that you want to analyze by. A good book to understand how to design OLAP solutions is The Data Warehouse Toolkit: Practical Techniques for Building Dimensional Data Warehouses by Ralph Kimball.
Example: let's say we want to see some key measures about purchases. We want to know how many items and the sales amount that are purchased by what kind of customer across which stores. The FACT table will contain a column for Qty-purchased and Purchase Amount. The DIMENSION tables will include the ITEM_DESC (contains the item_id & Description), the CUSTOMER_TYPE, the STORE (Store_id & store name), and TIME (contains calendar information such as the date, the month_end_date, quarter_end_date, day_of_week, etc).
Database Fundamentals > Data Warehousing and Business Intelligence with Mike Lampa
Search Advice from more than 250 TechTarget Experts
Your question may have already been answered! Browse or search more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
hope it helps...

Difference between ok_code and sy-ucomm

Hi,
Can any one tell me the difference between ok_code and sy-ucomm

Hi,
Actually OK_CODE and SY-Ucomm are the same. But experts suggest use of OK code for following reason:
In each PAI event that a user triggers by choosing either a pushbutton on the screen or an element in a GUI status, the corresponding function code is placed into the system field SYST-UCOMM or SY-UCOMM and placed in the OK_CODE field (as long as the function code is not empty). Empty function codes are placed in neither the SY-UCOMM field nor the OK_CODE field.
In your ABAP programs, you should work with the OK_CODE field instead of SY-UCOMM. There are two reasons for this: Firstly, the ABAP program has full control over fields declared within it, and secondly, you should never change the value of an ABAP system field. However, you should also always initialize the OK_CODE field in an ABAP program for the following reason:
In the same way that the OK_CODE field in the ABAP program and the system field SY-UCOMM receive the contents of the corresponding screen fields in the PAI event, their contents are also assigned to the OK_CODE screen field and system field SYST-UCOMM in the PBO event. Therefore, you must clear the OK_CODE field in the ABAP program to ensure that the function code of a screen is not already filled in the PBO event with an unwanted value. This is particularly important when the next PAI event can be triggered with an empty function code (for example, using ENTER). Empty function codes do not affect SY-UCOMM or the OK_CODE field, and consequently, the old field contents are transported.

Difference between schema and DTD

Difference between schema and DTD
<author>
<firstname></firstname>
<lastname></lastname>
</author>
How will u write dtd and schema for above XML ?

DTD:
<!ELEMENT author(firstname, lastname)>
<!ELEMENT firstname(#PCDATA)>
<!ELEMENT lastname(#PCDATA)>
Schema:
<xs:element name="author">
<xs:complexType>
<xs:sequence>
<xs:element name="firstname" type="xs:string"/>
<xs:element name="lastname" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>

Difference between scalable and failover cluster

Difference between scalable and fail over cluster

A scalable cluster is usually associated with HPC clusters but some might argue that Oracle RAC is this type of cluster. Where the workload can be divided up and sent to many compute nodes. Usually used for a vectored workload.
A failover cluster is where a standby system or systems are available to take the workload when needed. Usually used for scalar workloads.

What is the main difference between ws_upload and gui_upload?

Hi All,
What is the main difference between ws_upload and gui_upload?
In what contexts should we use these two function modules??
Thanks,
Creasy

search the forum before posting.
You can find lot of posts related.

Difference between node and element in context.

Similar Messages

Maybe you are looking for