1 00:00:01,150 --> 00:00:02,170 Welcome, my friends. 2 00:00:02,320 --> 00:00:03,550 Welcome to this section. 3 00:00:03,670 --> 00:00:11,530 In this section, we will deal with important symbolic objects, namely two objects, the symbolic config 4 00:00:11,530 --> 00:00:13,080 and the solar context. 5 00:00:13,610 --> 00:00:20,590 First, we'll go through the tittie of what actually a Soviet country is and where it is used, as well 6 00:00:20,590 --> 00:00:30,820 as how so context is used and how and what are the other factors that we will decide between so config 7 00:00:30,820 --> 00:00:32,520 and some context. 8 00:00:33,250 --> 00:00:37,690 So we will do the Tyrepac part first and then we will do a practical application. 9 00:00:37,690 --> 00:00:44,230 We'll create to select and recheck how solar config is different from some context. 10 00:00:45,040 --> 00:00:47,400 So let us get it to the 30 Berkovic. 11 00:00:49,700 --> 00:00:56,300 First, we'll start with Soviet country, so Soviet country is an object containing some initial barometer's 12 00:00:56,300 --> 00:01:03,490 or configuration information created by this Soviet container and passed the Soviet during initialization, 13 00:01:03,920 --> 00:01:10,310 the first thing to understand is Soviet conflict is an object which is created during initialization 14 00:01:10,310 --> 00:01:13,640 by the Soviet is created by this Soviet container. 15 00:01:14,270 --> 00:01:16,240 Now, where is it used? 16 00:01:16,250 --> 00:01:23,090 It is used for creating a for getting the initial barometer's or to get some configuration information. 17 00:01:23,420 --> 00:01:25,970 Configuration information can be the name of the subject. 18 00:01:25,970 --> 00:01:30,160 Or if you want to get the Soviet context, these are the configuration informations. 19 00:01:30,440 --> 00:01:37,200 The initial parameters are set in the segment and those parameters to this Soviet config. 20 00:01:37,340 --> 00:01:40,910 We will do this later so you'll understand it better. 21 00:01:40,910 --> 00:01:43,100 But this is the definition of the Soviet config. 22 00:01:43,520 --> 00:01:46,290 Soviet config is for a particular subject. 23 00:01:46,310 --> 00:01:47,830 Now, this is an important concept. 24 00:01:47,870 --> 00:01:50,400 Soviet conflict is for a particular subject. 25 00:01:50,420 --> 00:01:56,730 That means one should store servlet specific information in some of them using this object. 26 00:01:57,320 --> 00:02:03,200 So for every servlet, that is a separate servlet config, OK, that's what you have to understand. 27 00:02:03,880 --> 00:02:08,330 Now, let's go to the next slide to how to get this object. 28 00:02:08,330 --> 00:02:15,560 How to get subnet config from your table from the public will actually be subnet has got a method called 29 00:02:15,560 --> 00:02:16,780 get servlet config. 30 00:02:16,790 --> 00:02:25,580 You can use get subnet config to get this object config and uses of subnet config get init barometer's 31 00:02:25,580 --> 00:02:27,390 which is set in between. 32 00:02:27,410 --> 00:02:30,080 The production will be set using tags. 33 00:02:30,080 --> 00:02:38,830 We set the init parameter tag the use and we set the parameters and we get these parameters from this 34 00:02:38,830 --> 00:02:39,620 Soviet config. 35 00:02:40,040 --> 00:02:41,120 Get it back to me. 36 00:02:42,440 --> 00:02:47,730 That is there's a method called getting a parameter and we get it to this Soviet config. 37 00:02:47,750 --> 00:02:51,950 So this is one of the uses of Soviet config, the other use of reconfigures. 38 00:02:51,950 --> 00:02:57,920 If you want to get configuration details like select name or the subnet context itself, you can get 39 00:02:57,920 --> 00:03:04,760 the Silicon X from the Soviet config config object that's created during the initialization lifecycle 40 00:03:04,760 --> 00:03:06,560 phase of this subnet. 41 00:03:07,070 --> 00:03:07,270 OK. 42 00:03:07,920 --> 00:03:15,140 Now, let us go to the next step, which is the subject context for the Soviet context is the object 43 00:03:15,140 --> 00:03:16,920 created by Soulik container. 44 00:03:16,940 --> 00:03:23,540 Again, the subnet container creates this object config as well as this other context, the shared initial 45 00:03:23,540 --> 00:03:28,760 parameters, same thing as config you can share and you should have barometer's or configuration information 46 00:03:28,760 --> 00:03:34,310 for the whole application, not just a particular subject, but the entire application. 47 00:03:34,310 --> 00:03:41,540 Also, villagers can share one servlet context and so comes to the next point, which is the importance 48 00:03:41,540 --> 00:03:42,320 of the context. 49 00:03:42,320 --> 00:03:43,640 Object is only one. 50 00:03:44,480 --> 00:03:50,840 So the config for every subject that is a subject, config merfolk subject context that is only one 51 00:03:50,900 --> 00:03:56,240 subject context and is used by different subjects is shared by different subjects of the application. 52 00:03:56,240 --> 00:03:58,370 So the scope is entire application. 53 00:03:58,610 --> 00:04:00,710 Okay, let's go to the next slide. 54 00:04:01,250 --> 00:04:07,700 How to get this object will be servlet has got this object method called get subnet context so you can 55 00:04:07,700 --> 00:04:16,280 get that from get some context from the A.P. servlet plus or you can get it from your silverleaf config, 56 00:04:16,400 --> 00:04:17,900 from eSolar config object. 57 00:04:17,910 --> 00:04:20,010 Also you can get some context. 58 00:04:20,350 --> 00:04:22,320 Which of you choose is fine. 59 00:04:22,890 --> 00:04:28,420 Now the uses of servlet context just get in it parameter of application scope, not just select scope 60 00:04:28,430 --> 00:04:33,470 but applications scope from the same as this object config. 61 00:04:33,650 --> 00:04:40,640 You set it in the next segment and then but you get it in the application scope so that all the subjects 62 00:04:40,640 --> 00:04:42,830 are shedding this init barometer. 63 00:04:43,040 --> 00:04:50,990 Whatever you need to shit that needs to be in the subject, context, uses of unsubtly, context and 64 00:04:50,990 --> 00:04:52,510 other use of context. 65 00:04:52,610 --> 00:04:58,250 This is also important and we will discuss about this later when we talk about active use and barometer's 66 00:04:59,690 --> 00:05:08,420 get sick and remove active use of application school to share data between Soler's, you use attributes 67 00:05:08,840 --> 00:05:16,490 and these attributes can be set and then set by one set set by one servlet and get by another subnet 68 00:05:16,490 --> 00:05:17,720 or you remove the attribute. 69 00:05:17,930 --> 00:05:21,080 So all these facilities are available to the subject context. 70 00:05:21,080 --> 00:05:22,640 But now you should not get sick. 71 00:05:22,640 --> 00:05:27,290 Remove attributes of application scope can be done in this subject context. 72 00:05:27,830 --> 00:05:28,100 No. 73 00:05:28,130 --> 00:05:33,530 Let us go to the differences that we have seen between this config and this subject context. 74 00:05:33,890 --> 00:05:37,460 The first difference is the civil conflict is subject specific. 75 00:05:37,460 --> 00:05:44,810 I told you already servlet conflict is every subject will have one subject conflict so that it is a 76 00:05:44,810 --> 00:05:45,770 subject specific. 77 00:05:46,040 --> 00:05:48,620 So a context just for the whole application, which means. 78 00:05:48,780 --> 00:05:56,160 All the servlet are shedding a single it's context, second point is barometers of Soviet conflict at 79 00:05:56,160 --> 00:06:00,520 present as they value bear in in its bottom servlet. 80 00:06:00,520 --> 00:06:02,430 So this is a specific technical thing. 81 00:06:02,580 --> 00:06:04,800 And we do this actually good. 82 00:06:05,150 --> 00:06:14,230 We will see that we are using the tag inside this bag and how we configure the parameters in the public 83 00:06:14,240 --> 00:06:14,590 country. 84 00:06:14,850 --> 00:06:20,790 Barometers of servlet context of present doesn't value betting on the bottom, which is outside of servlet 85 00:06:20,790 --> 00:06:21,450 and inside. 86 00:06:22,560 --> 00:06:27,650 This is because it's an application by a wide, wide object. 87 00:06:27,930 --> 00:06:31,320 So it will be in the Web app, not in a particular subject. 88 00:06:31,320 --> 00:06:36,470 And here public confidence will be established because it is specific to the examiner. 89 00:06:36,690 --> 00:06:42,570 OK, servlet config object is talking about getting by Gex of config method. 90 00:06:42,840 --> 00:06:44,510 This I have already told you so. 91 00:06:44,520 --> 00:06:49,050 The context object is maintained by servlet connection method. 92 00:06:49,350 --> 00:06:58,680 This also happened to use servlet config and only one subnet needs information shared by OK and use 93 00:06:58,920 --> 00:07:03,440 servlet context when whole application needs information shared by the. 94 00:07:03,540 --> 00:07:10,620 If you want many subnets to share the same data, then use of the context if if we're only required 95 00:07:10,620 --> 00:07:12,500 for one servlet use of the country. 96 00:07:12,820 --> 00:07:17,190 OK, so this is what I wanted to tell you about the conference of the context. 97 00:07:17,520 --> 00:07:19,410 This is what we are doing in this lecture. 98 00:07:19,890 --> 00:07:25,670 In the next lecture we will start creating servlet conflicts and so on and not Bueso. 99 00:07:25,680 --> 00:07:32,910 Next we will create and we will see how these differences can be seen in an application in using a servlet 100 00:07:32,910 --> 00:07:34,980 config and subject context. 101 00:07:35,280 --> 00:07:36,390 OK, thank you.