Full loads and how the tables in BW are rebuilt
I have a question. If i am doing full loads every time how does the underlying BW table look. for example if I have 100 records the 1st time, then 80 what is the record count in the BW table? does it do some sort of automatic deletion every time so it has 80 records?
Hi,
For cube if you load the same data Key Figure values will be added when you report on it. So, the cube fact table will have double entries. If you want to add/ modify / delete data from the cube then probably you should go for delta loads.
Hope this helps.
PB
Similar Messages
-
How to load and display the external flv video files in dynamicly and the how to control the flv fil
How to load and display the external flv video files in dynamicly using AS 3.0
and How to control the flv file add the play paus button and add seekbar.
I have using to load the flv file following code
var flvPlaceHolder1:MovieClip = new MovieClip();
var vid1:Video = new Video(734, 408);
flvPlaceHolder1.addChild(vid1);
addChild(flvPlaceHolder1);
flvPlaceHolder1.x = 1059;
flvPlaceHolder1.y = 152;
var nc1:NetConnection = new NetConnection();
nc1.connect(null);
var ns1:NetStream = new NetStream(nc1);
vid1.attachNetStream(ns1);
var listener1:Object = new Object();
listener1.onMetaData = function(evt:Object):void {};
ns1.client = listener1;
ns1.play("GV-1600 TURNING.flv");
ns1.addEventListener(NetStatusEvent.NET_STATUS, statusChanged1);
function statusChanged1(ns1:NetStatusEvent):void
trace(ns1.info.code);
if (ns1.info.code == 'NetStream.Buffer.Empty')
trace('the video has ended');
removeChild(flvPlaceHolder1);
//trace('removeChild');
gotoAndPlay(1786);
then how to add the play,paus ,full screen button and seekbar,volumebar.I have to Create the flash presentation for our company product
In this presentation the left side the text animation are displayed then right side the our product video is displayed.
In this presentation i need the following option :
1, The first product video and animation is finished then the next product is played
2, then the video displayed (size width and height 400x300) , I click this video to increase the size(ex:1000x700)
3, then the playing video i control it play, stop, paus button and volume bar, seek bar.
4, then this presentation is displayed on 42 inches LCD TV so this full presentation is run full screen.
I have finished first two steps 1 and 2
the following are the screen short and code:-
code :-
var count=0;
var flvPlaceHolder2:MovieClip = new MovieClip();
var vid2:Video = new Video(734, 408);
flvPlaceHolder2.addChild(vid2);
addChild(flvPlaceHolder2);
flvPlaceHolder2.x = 1059;
flvPlaceHolder2.y = 152;
var nc2:NetConnection = new NetConnection();
nc2.connect(null);
var ns2:NetStream = new NetStream(nc2);
vid2.attachNetStream(ns2);
var listener2:Object = new Object();
listener2.onMetaData = function(evt:Object):void {};
ns2.client = listener2;
ns2.play("GS-4000.flv");
this.addEventListener(Event.ENTER_FRAME, BtnFadeIn2);
function BtnFadeIn2(event:Event):void
if (this.currentFrame == 387)
/*flvPlaceHolder2.x = 30;
flvPlaceHolder2.y = 140;
vid2.width=1800;
vid2.height=800;
trace('Screen size is changed');*/
if(count==0)
flvPlaceHolder2.x = 30;
flvPlaceHolder2.y = 140;
vid2.width=1800;
vid2.height=800;
count++;
ns2.addEventListener(NetStatusEvent.NET_STATUS, statusChanged2);
function statusChanged2(ns2:NetStatusEvent):void
trace(ns2.info.code);
if (ns2.info.code == 'NetStream.Buffer.Empty')
trace('the video has ended');
removeChild(flvPlaceHolder2);
//trace('removeChild');
gotoAndPlay(433);
flvPlaceHolder2.buttonMode=true;
flvPlaceHolder2.addEventListener(MouseEvent.CLICK,home2);
function home2(e:MouseEvent):void
if(vid2.width==734 && vid2.height==408)
flvPlaceHolder2.x = 30;
flvPlaceHolder2.y = 140;
vid2.width=1800;
vid2.height=800;
else
flvPlaceHolder2.x = 1059;
flvPlaceHolder2.y = 152;
vid2.width=734;
vid2.height=408; -
How row migration get eliminated by export and import the table.
Hi ,
Please let me know,how row migration get eliminated by export and import the table.
Another method,deleting migrated rows and inserting those rows from copied table,
i think the concept behind this method is,inserting these rows into new block.
pls correct me if i am wrong.
Thanks,
Kumar.Hi!
You can also use ALTER TABLE MOVE command, or if you are on 9i you can use DBMS_REDEFINITION package.
If you have a maintainance window the easiest way would be to use alter table move.
Regards,
PP -
How the tables are linked to each other in ERP and CRM?
Dear All,
Can anyone provide the info for the below query ?
"How the tables are linked to each other in ERP and CRM"
Quick response is highly appreciated.
Best Regards
SucchiDear Buijink ,
Thanks for the info.
Here in this table SMOFTABLES , it is giving the CRM adopter objects with R/3 tables . But my requirement is more on corresponding CRM Tables , the data fetching from R/3 tables will store in which CRM tables.To be clear the adopter objects extract the data from different R/3 tables but stores in to which tables?
Thanks in advance
Best Regards
Succhi -
help please to start working... with English at me in any way without translator... if somebody can explain in Russian as to start the program, I will be very grateful
Tell how to enter the program and to start working in it. I paid, loaded and installed the program Photoshop CCOnline Chat Now button near the bottom for Activation and Deactivation problems may help
http://helpx.adobe.com/x-productkb/policy-pricing/activation-deactivation-products.html -
How to programmatically load and show the front panel of a vi but NOT run it?
Is there a way to load and show the front panel of a vi but NOT run it? I am starting with the AsynchronousCallAndForget.vi from the example finder and inserted an invoke node with the FP Open method call prior to the Start Asynchronous Call node. The vi I am loading has the "Run when opened" unchecked and the menu bar IS visible so I can manually click the run arrow. Thanks!
Solved!
Go to Solution.Why are you using the Async call? If you simply open the VI reference, then call the FP.Open method this works fine. You can then call the VI run method with Wait Until Done set to false if you wish to run it Asynchronously, this is how we did it in ye olde days before we had this new fangled "Start Asynchronous Call" stuff.
Charles Chickering
Architecture is art with rules.
...and the rules are more like guidelines -
How i can access and edit the table of database(.mdb) file through Labview
Dear sir,
I want to access and edit the table of database(.mdb) file through Labview and it should save.
please tell me how i can do it.
i am waiting for reply.
regards
Rajendrathere are options aplenty for this. First off, do you have the database connectivity toolset? If so, You can do it from there. Following the examples in labview. Or you can do a search for ADO or access database, and find plenty of VIs that can do this.
Paul <--Always Learning!!!
sense and simplicity.
Browse my sample VIs? -
Hi how to handel the lock and unlock the table
Hi,
i am having the one scenario like,for lock and unlock the table i used the function modules ENQUEUE_E_TABLE and DEQUEUE_E_TABLE but it allowing the edit the first user and suppose to try the editing the second user it is giving the error message it correct but again the second user press any button it is leaving the program it should not happened please help me that.
regards,
Hari.Hi,
i assume it's in table JEST
so select:
SELECT * FROM JEST
WHERE OBJNR = aufk-OBJNR
AND STAT IN S_STATI
Andreas -
EXACT DIFFERENCE BETWEEN FULL LOAD AND REPAIRFULL LOAD?
HI Champ,
Can anyone explain me the exact difference between full load and Repairfull load?Give e some senario where we can go for this?Please.....
10zinHi,
Full repair can be said as a Full with selections. But the main use or advantage of Full repair load is that it wont affect delta loads in the system. If you load a full to a target with deltas running you again will have to initialize them for deltas to continue. But if you do full repair it wont affect deltas.
This is normally done we when we lose some data or there is data mismatch between source system and BW.
Check the OSS Note 739863 'Repairing data in BW' for all the details
Symptom
Some data is incorrect or missing in the PSA table or in the ODS object (Enterprise Data Warehouse layer).
There may be a number of reasons for this problem: Errors in the relevant application, errors in the user exit, errors in the DeltaQueue, handling errors in the customers posting procedure (for example, a change in the extract structure during production operation if the DeltaQueue was not yet empty; postings before the Delta Init was completed, and so on), extractor errors, unplanned system terminations in BW and in R/3, and so on.
Solution
Read this note in full BEFORE you start actions that may repair your data in BW. Contact SAP Support for help with troubleshooting before you start to repair data.
BW offers you the option of a full upload in the form of a repair request (as of BW 3.0B). If you want to use this function, we recommend that you use the ODS object layer.
Note that you should only use this procedure if you have a small number of incorrect or missing records. Otherwise, we always recommend a reinitialization (possibly after a previous selective deletion, followed by a restriction of the Delta-Init selection to exclude areas that were not changed in the meantime).
1. Repair request: Definition
If you flag a request as a repair request with full update as the update mode, it can be updated to all data targets, even if these already contain data from delta initialization runs for this DataSource/source system combination. This means that a repair request can be updated into all ODS objects at any time without a check being performed. The system supports loading by repair request into an ODS object without a check being performed for overlapping data or for the sequence of the requests. This action may therefore result in duplicate data and must thus be prepared very carefully.
The repair request (of the "Full Upload" type) can be loaded into the same ODS object in which the 'normal' delta requests run. You will find this request under the "Repair Request" option in the InfoPackage (Maintenance) menu.
2. Prerequisites for using the "Repair Request" function
2.1. Troubleshooting
Before you start the repair action, you should carry out a thorough analysis of the possible cause of the error to make sure that the error cannot recur when you execute the repair action. For example, if a key figure has already been updated incorrectly in the OLTP system, it will not change after a reload into BW. Use transaction RSA3 (Extractor Checker) in the source system for help with troubleshooting. Another possible source of the problem may be your user exit. To ensure that the user exit is correct, first load a user exit with a Probe-Full request into the PSA table and check whether the data is correct. If it is not correct: Search for the error in the exit user. If you do not find it, we recommend that you deactivate the user exit for testing purposes and request a new Full Upload. It If the data arrives correctly, it is highly probable that the error is indeed in the user exit.
We always recommend that you load the data into the PSA table in the first step and check the result there.
2.2. Analyze the effects on the downstream targets
Before you start the Repair request into the ODS object, make sure that the incorrect data records are selectively deleted from the ODS object. However, before you decide on selective deletion, you should read the Info Help for the "Selective Deletion" function, which you can access by pressing the extra button on the relevant dialog box. The activation queue and the ChangeLog remain unchanged during the selective deletion of the data from the ODS object, which means that the incorrect data is still in the change log afterwards. After the selective deletion, you therefore must not reconstruct the ODS object if it is reconstructed from the ChangeLog. (Reconstruction is usually from the PSA table but, if the data source is the ODS object itself, the ODS object is reconstructed from its ChangeLog). You MUST read the recommendations and warnings about this (press the "Info" button).
You MUST also take into account the fact that the delta for the downstream data targets is created from the changelog. If you perform selective deletion and then reload data into the deleted area, this may result in data inconsistencies in the downstream data targets.
If you only use MOVE and do not use ADD for updates in the ODS object, selective deletion may not be required in some cases (for example, if incorrect records only have to be changed, rather than deleted). In this case, the DataMart delta also remains intact.
2.3. Analysis of the selections
You must be very precise when you perform selective deletion: Some applications do not provide the option of selecting individual documents for the load process. Therefore, you must first ensure that you can load the same range of documents into BW as you would delete from the ODS object. This note provides some application-specific recommendations to help you "repair" the incorrect data records.
If you updated the data from the ODS object into the InfoCube, you can also delete it there using the "Selective deletion" function. However, if it is compressed at document level there and deletion is no longer possible, you must delete the InfoCube content and fill the data in the ODS object again after repair.
You can only perform this action after a thorough analysis of all effects of selective data deletion. We naturally recommend that you test this first in the test system.
The procedure generally applies for all SAP applications/extractors. The application determines the selections. For example, if you cannot use the document number for selection but you can select documents for an entire period, then you are forced to delete and then update documents for the entire period in the data target. Therefore, it is important to look first at the selections in the InfoPackage exactly before you delete data from the data target.
Some applications have additional special features:
Logistics cockpit: As preparation for the repair request, delete the SetUp table (if you have not already done so) and fill it selectively with concrete document numbers (or other possible groups of documents determined by the selection). Execute the Repair request.
Caution: You can currently use the transactions that fill SetUp tables with reconstruction data to select individual documents or entire ranges of documents (at present, it is not possible to select several individual documents if they are not numbered in sequence).
FI: The Repair request for the Full Upload is not required here. The following efficient alternatives are provided: In the FI area, you can select documents that must be reloaded into BW again, make a small change to them (for example, insert a period into the assignment text) and save them -> as a result, the document is placed in the delta queue again and the previously loaded document under the same number in the BW ODS object is overwritten. FI also has an option for sending the documents selectively from the OLTP system to the BW system using correction programs (see note 616331).
3. Repair request execution
How do you proceed if you want to load a repair request into the data target? Go to the maintenance screen of the InfoPackage (Scheduler), set the type of data upload to "Full", and select the "Scheduler" option in the menu -> Full Request Repair -> Flag request as repair request -> Confirm. Update the data into the PSA and then check that it is correct. If the data is correct, continue to update into the data targets."
Refer.
Repair full request
Re: Repair full request
Steps to perform repair full request
full repair request
repair full request
Re: Repair Full Request
Thanks,
JituK -
Full Load" and "Full load with Repair full request"
Hello Experts,
Can any body share with me what is the difference between a "Full Load" and "Full load with Repair full request"?
Regards.Hi......
What is function of full repair?? what it does?
How to delete init from scheduler?? I dont see any option like that in infopackage
For both of you question there is a oss note 739863-Repairing data in BW ..........Read the following.....
Symptom
Some data is incorrect or missing in the PSA table or in the ODS object (Enterprise Data Warehouse layer).
Other terms
Restore data, repair data
Reason and Prerequisites
There may be a number of reasons for this problem: Errors in the relevant application, errors in the user exit, errors in the DeltaQueue, handling errors in the customers posting procedure (for example, a change in the extract structure during production operation if the DeltaQueue was not yet empty; postings before the Delta Init was completed, and so on), extractor errors, unplanned system terminations in BW and in R/3, and so on.
Solution
Read this note in full BEFORE you start actions that may repair your data in BW. Contact SAP Support for help with troubleshooting before you start to repair data.
BW offers you the option of a full upload in the form of a repair request (as of BW 3.0B). If you want to use this function, we recommend that you use the ODS object layer.
Note that you should only use this procedure if you have a small number of incorrect or missing records. Otherwise, we always recommend a reinitialization (possibly after a previous selective deletion, followed by a restriction of the Delta-Init selection to exclude areas that were not changed in the meantime).
1. Repair request: Definition
If you flag a request as a repair request with full update as the update mode, it can be updated to all data targets, even if these already contain data from delta initialization runs for this DataSource/source system combination. This means that a repair request can be updated into all ODS objects at any time without a check being performed. The system supports loading by repair request into an ODS object without a check being performed for overlapping data or for the sequence of the requests. This action may therefore result in duplicate data and must thus be prepared very carefully.
The repair request (of the "Full Upload" type) can be loaded into the same ODS object in which the 'normal' delta requests run. You will find this request under the "Repair Request" option in the InfoPackage (Maintenance) menu.
2. Prerequisites for using the "Repair Request" function
2.1. Troubleshooting
Before you start the repair action, you should carry out a thorough analysis of the possible cause of the error to make sure that the error cannot recur when you execute the repair action. For example, if a key figure has already been updated incorrectly in the OLTP system, it will not change after a reload into BW. Use transaction RSA3 (Extractor Checker) in the source system for help with troubleshooting. Another possible source of the problem may be your user exit. To ensure that the user exit is correct, first load a user exit with a Probe-Full request into the PSA table and check whether the data is correct. If it is not correct: Search for the error in the exit user. If you do not find it, we recommend that you deactivate the user exit for testing purposes and request a new Full Upload. It If the data arrives correctly, it is highly probable that the error is indeed in the user exit.
We always recommend that you load the data into the PSA table in the first step and check the result there.
2.2. Analyze the effects on the downstream targets
Before you start the Repair request into the ODS object, make sure that the incorrect data records are selectively deleted from the ODS object. However, before you decide on selective deletion, you should read the Info Help for the "Selective Deletion" function, which you can access by pressing the extra button on the relevant dialog box. The activation queue and the ChangeLog remain unchanged during the selective deletion of the data from the ODS object, which means that the incorrect data is still in the change log afterwards. After the selective deletion, you therefore must not reconstruct the ODS object if it is reconstructed from the ChangeLog. (Reconstruction is usually from the PSA table but, if the data source is the ODS object itself, the ODS object is reconstructed from its ChangeLog). You MUST read the recommendations and warnings about this (press the "Info" button).
You MUST also take into account the fact that the delta for the downstream data targets is created from the changelog. If you perform selective deletion and then reload data into the deleted area, this may result in data inconsistencies in the downstream data targets.
If you only use MOVE and do not use ADD for updates in the ODS object, selective deletion may not be required in some cases (for example, if incorrect records only have to be changed, rather than deleted). In this case, the DataMart delta also remains intact.
2.3. Analysis of the selections
You must be very precise when you perform selective deletion: Some applications do not provide the option of selecting individual documents for the load process. Therefore, you must first ensure that you can load the same range of documents into BW as you would delete from the ODS object. This note provides some application-specific recommendations to help you "repair" the incorrect data records.
If you updated the data from the ODS object into the InfoCube, you can also delete it there using the "Selective deletion" function. However, if it is compressed at document level there and deletion is no longer possible, you must delete the InfoCube content and fill the data in the ODS object again after repair.
You can only perform this action after a thorough analysis of all effects of selective data deletion. We naturally recommend that you test this first in the test system.
The procedure generally applies for all SAP applications/extractors. The application determines the selections. For example, if you cannot use the document number for selection but you can select documents for an entire period, then you are forced to delete and then update documents for the entire period in the data target. Therefore, it is important to look first at the selections in the InfoPackage exactly before you delete data from the data target.
Some applications have additional special features:
Logistics cockpit: As preparation for the repair request, delete the SetUp table (if you have not already done so) and fill it selectively with concrete document numbers (or other possible groups of documents determined by the selection). Execute the Repair request.
Caution: You can currently use the transactions that fill SetUp tables with reconstruction data to select individual documents or entire ranges of documents (at present, it is not possible to select several individual documents if they are not numbered in sequence).
FI: The Repair request for the Full Upload is not required here. The following efficient alternatives are provided: In the FI area, you can select documents that must be reloaded into BW again, make a small change to them (for example, insert a period into the assignment text) and save them -> as a result, the document is placed in the delta queue again and the previously loaded document under the same number in the BW ODS object is overwritten. FI also has an option for sending the documents selectively from the OLTP system to the BW system using correction programs (see note 616331).
3. Repair request execution
How do you proceed if you want to load a repair request into the data target? Go to the maintenance screen of the InfoPackage (Scheduler), set the type of data upload to "Full", and select the "Scheduler" option in the menu -> Full Request Repair -> Flag request as repair request -> Confirm. Update the data into the PSA and then check that it is correct. If the data is correct, continue to update into the data targets.
And also search in forum, will get discussions on this
Full repair loads
Regarding Repair Full Request
Instead of doing of all these all steps.. cant I reload that failed request again??
If some goes wrong with delta loads...it is always better to do re-init...I mean dlete init flag...full repair..all those steps....If it is an infocube you can go for full update also instead of full repair...
Full Upload:
In full upload all the data records are fetched....It is similar to full repair..Incase of infocube to recover missed delta records..we can run full upload.....but in case of ODS does'nt support full upload and delta upload parallely...so inthis case you have to go for full repair...otherwise delta mechanism will get corrupted...
Suppose your ODS activation is failing since there is a Full upload request in the target.......then you can convert full upload to full repair using the program : RSSM_SET_REPAIR _ FULL_FLAG
Hope this helps.......
Thanks==points as per SDN.
Regards,
Debjani.....
Edited by: Debjani Mukherjee on Oct 23, 2008 8:32 PM -
Load and Unload Alias Table - Aggregate Storage
Hi everyone,<BR><BR>Here I am again with another question about aggregate storage...<BR><BR>There is no "load" or "unload" alias table listed as a parameter for "alter database" in the syntax guidelines for aggregate storage (see <a target=_blank class=ftalternatingbarlinklarge href="http://dev.hyperion.com/techdocs/eas/eas_712/easdocs/techref/maxl/ddl/aso/altdb_as.htm">http://dev.hyperion.com/techdo...l/ddl/aso/altdb_as.htm</a> )<BR><BR><BR>Is this not a valid parameter for aggregate storage? If not, how do you load and unload alias tables if you're running a batch script in MaxL and you need the alias table update to be automated?<BR><BR>Thanks in advance for your help.<BR><BR>
Hi anaguiu2, <BR><BR>I have the same problem now. Do you find a solution about the load and unload alias table - Aggregate storage ? Could you give me your solution used if you have one. <BR><BR>Thanks, Manon
-
Can we load and unload the files in the run time?
Can we load and unload the files in the run time?
For example there are four files named "test1.h & test1.c" and another set "test2.h & test2.c" (I attached them as attachment to this post).
test1.h contains code:
int variable; //variable declared as integer
test1.c contains code:
variable = 1; //variable assigned a value
test1.h contains code:
char *variable; //variable declared as string
test1.c contains code:
variable = "EXAMPLE"; //variable assigned a string
So here, in this case can I dynamically load / unload the first & second group of files so that the same variable name "variable" can be used both as integer and string? And if yes, how is that to be done?
Solved!
Go to Solution.
Attachments:
test.zip 1 KBWhat do you mean by "dynamically"?
If you want to have a variable that either is an int or a char in the same program run, I'm afraid your only option is to define it as a variant and assign from time to time the proper data type in the variant according to some condition. Next, every time you access the variable you must firstly check which data type is stored in it, next access it in the proper way.
If on the other hand your option or to have a run in which the variable is an int, next you stop the program and in a following run it is a char, you may have it by using some appropriade preprocessor clause:
#ifdef CHAR_TYPE
#include "test1.h"; // variable defined as a char
#else
#include "test2.h"; // variable defined as int
#endif
Next, every time you want to access the variable you must proceed in the same vay:
#ifdef CHAR_TYPE
variable = "string";
#else
variable = 1;
#endif
Does it worth the effort?
Additionally, keep in mind that this "dynamical" approach can work only in the IDE, where you can properly #define your CHAR_TYPE or not depending on your wishes: when you compile the program, it will have only one #include depending on the definition of the macro.
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos? -
Approach for holding the same message and updating the table field Status
Hi,
I have a scenario a (first) proxy asynchronous to JDBC synchronous and then(second) proxy asynchronous.
my first proxy calls sends records (which has a status entry " in process" ) to JDBC it updates or inserts.
JDBC sends a response (may be a count of records updated or inserted)
now i need to handle some how to get the records which have been inserted or updated, so that i can map and change the table entry status field" in process" to " active".
Can i handle this without stored procedures.If so how
Can it be done through BPM where i retain inital mapping or any other solution. please help.Hi Robin,
Ok (but that would be the apt method)
Some other approaches :
1. Make a async scenario (Proxy to DB), which will update or insert records. Write a trigger in DB which will fetch updated/inserted records and send it to XI. Then you update them in R/3 (via proxy). So you will have two async interfaces (one is Proxy to DB and other one DB to Proxy)
2. go for BPM. Receive (from proxy), transform sync send, transform send (to proxy) . I will not prefer this as it will be a performance hinderance.
Regards
Suraj -
Creating tables on SQL studio and viewing the table in the SAP system
i have just created a table using the SQL studio and wants to use it view it in the SAP system using the SAP logon. till now i have not found a way to create it therefore any help is much appreciated.
Hmm... you want to see tables via SAPLogon ??
Ok, let's assume you really want to access tables via ABAP instead.
For that you've two options:
1. Create the table in the ABAP dictonary (SE11) exactly like you created it in the database and activate the table.
After that you can access the table via SE16 or any ABAP as you like.
2. You don't create the table in the ABAP dictonary and use native SQL to access the data.
Neither of these options is meant to be the way to do it.
The correct way would be to design the whole table in the ABAP dictionary and create the table on the database from that.
regards,
Lars -
As a JSF Developer, I want to understand technically how the JSF View Components are rendered as html and how there events are binded to Server.I want to know how flows goes to the server and server understands the method which is to be called of managed bean. I know it is with annotation @ManagedBean and method name, but how Call is binded with annotation @ManagedBean.
In short, i want to know the internal implementation of JSF Framework.As a JSF Developer, I want to understand technically how the JSF View Components are rendered as html and how there events are binded to Server.I want to know how flows goes to the server and server understands the method which is to be called of managed bean. I know it is with annotation @ManagedBean and method name, but how Call is binded with annotation @ManagedBean.
In short, i want to know the internal implementation of JSF Framework.
Maybe you are looking for
-
HTTP status code returned by site-wide error handler is 200 OK?
I'm using a developer install of ColdFusion 11. I set up the following page at http://localhost:8500/test/index.cfm: <cfthrow type="application" message="This is an error"> When I visit that page, the HTTP status code returned is 500, as expected. I
-
More than one hierarchy in a dimension
Hi, I'm doing my first steps into Oracle BI and came now to the point to design a Business Model. My star schema model is defined and implemented with OWB. It contains dimensions with two ore more hierarchies, using partially the same levels and spli
-
How can i organize my photo albumbs(not greyed out)
So i was trying to organize some photos of mine from the computer and the internet. I created folders in my pc and made my ipad synced with them as albums(folder names=albums). Then i downloaded an image from the internet in my ipad and i wanted to m
-
HT5494 Java for Mac OS X v10.6 Update 11 breaks VisualVM
/Developer/Applications/Utilities/Java VisualVM.app fails to launch after updating to Java for Mac OS X 10.6 Update 11 (JRE 1.6.0_37). The application bundle in /usr/share/java/Tools depends on /System/Library/Java/Support/VisualVM.bundle, which is d
-
Hello, I have a iPod touch 4g,last time when I paired with my friends iPhone it showed his iPhone's name along with devices connected earlier in the bluetooth list after I updated my software to ios 5.1 the names of friends devices appear as D1:FG:12