![]() Wepwawet's standard was carried preceding the king from the palace or temple during processions, and during the New Kingdom, Wepwawet's standard even preceded that of Osiris. It is possible, given this context, that early on Wepwawet was a warlike deity and that in war, he also "opened the way" for the Egyptian army. The famous mace of Narmer shows such a standard in use as early as the 1st Dynasty. Wepwawet's image is generally portrayed with a uraeus and a hieroglyph that has been described as representing the king's placenta, surmounting a standard known as a shedshed. Like Shu, he was also referred to as the "one who has separated the sky from the earth. Wepwawet was also thought of as the messenger and champion of royalty. This attribute of the god is well established in New Kingdom funerary texts such as the Book of Going Forth by Day ( Book of the Dead), and the Book of That Which Is in the Underworld ( Amduat). We believe this refers to his role in leading the deceased through the underworld as a protector. Wepwawet's name means "the opener of the ways (or Roads)". This may be the origin of the misinterpretation of Wepwawet as a wolf, for Lycopolis can be interpreted as the "Town of the Wolf". This is the location of modern Asyut, which the Greeks called Lycopolis. Other cult centers for Wepwawet included Quban, el-Hargarsa, Memphis, Sais and particularly the thirteenth ancient nome of Upper Egypt. ![]() However, with the rise of the solar cult, particularly during the 12th Dynasty, Osiris was limited to the underworld and the local god and lord of the cemetery at Abydos was filled by Wepwawet, who gained the titles, "Lord of Abydos" and Lord of the Necropolis". Early on, Wepwawet's worship paralleled that of Khentyamentiu, but when Osiris absorbed that god's attributes, Anubis filled his funerary role. Like Anubis, Wepwawet was also a funerary deity, and was one of the earliest of the gods worshipped at Abydos. Egyptologists now believe that he was more likely associated with the jackal, though he is often depicted with a gray or white head. Wepwawet (Ophios, Upuaut), called the son of Isis, was one of several Egyptian deities to take the form of a canine, today often incorrectly identified as a wolf. "We discovered how fierce, deadly and powerful jaws were capable of tearing a wide range of prey," Gohar said.It was not unusual in ancient Egypt for more than one god to take the same form, with similar functions as another god. Moreover, big muscles on its head would have given it a powerful bite force, allowing it to capture large prey through snapping and biting. fish) before they were moved to the cheek teeth to be chewed into smaller pieces and swallowed," the researchers wrote in the study. anubis had long third incisors next to its canines, "which suggests that incisors and canines were used to catch, debilitate and retain faster and more elusive prey items (e.g. anubis's remains revealed that the protocetid whales had evolved a few new anatomical features and feeding strategies. ![]() anubis is the earliest (or most "primitive") whale in Africa from a group of semiaquatic whales known as the protocetids. et al (2021))īy analyzing the whale's partial remains - pieces of its skull, jaws, teeth, vertebrae and ribs - the team discovered that the 1,300-pound (600 kilogram) P. A map detailing the Fayum Depression in Egypt, where paleontologists found the fossil whale.
0 Comments
![]() Which breaks your overall exception handling. If you have done anything non-default with your ApplicationContext, you cannot get it to throw an exception for “No Handler Found”. I’m finding I do not like Spring Boot’s approach to MVC configuration. I think, many newcomers face this problem sooner or later, so spring-boot should explicitly say “You enabled annotatiton! Are you crazy?! Disable it asap!”. Just declare new ObjectMapper bean adding custom serializers here and disabling much of spring-boot’s (a great product for a spring application, I should say) cool features. But many people in my place would have done differently. And this is only because I’m very pedantic person and wanted to solve the problem, not workaround it. I don’t remember how I understood that was the problem. All examples in the internet say it should work, even source code of java8 jackson serializers (which should be enabled by default according to spring-boot’s documentation) say it should work, but it doesn’t! The documentation say, that `_DATES_AS_TIMESTAMPS=false` should work. The LocalDateTime fields serializing as arrays instead of ISO-8601 strings. Several years ago I spent many hours trying to solve a problem, that spring-boot ignores Jackson configuration from my application.properties file. □Īnd what is really bad in this situation, is the fact, that you can encounter the problem, which is not even related to this annotation at all from point of view of a person, who does not know all the implementation details. When I say “exactly” I mean: I also add comment to my web configuration explaining why adding here would be error. But in this case, where multiple sub-projects “collide”, it seems it could be improved.Ī few years ago I went through exactly the same path as you. I don’t want to be seen as “lecturing” the Spring team, who have done amazing job in having good documentation and straightforward behaviour. So there should be special treatment for this common use case – with additional logging and logged information helping people get through the maze of autoconfiguration. That’s what most tutorials are for, and that’s what it’s mostly used for, I guess. I had to turn on debug to see what gets autoconfigured, and then explore a bunch of classes to check the necessary conditions in order to figure out the situation.Īnd one of Spring Boot’s main use-cases is jar-packaged web applications. And require explicitly disabling autoconfiguration in order to get rid of the warning. My suggestion in situations like this is: log a warning. And they will keep doing it, and wasting a few hours before realizing they should remove it (or before extending a bunch of boot’s classes in order to achieve the same effect). So the autoconfiguration magic saved me doing a lot of stuff, but I still added a line explaining why something isn’t there.Īnd that’s because of the common use-cases – people are used to using So the most natural and common thing to do is to add it, especially if you don’t know how spring boot autoconfiguration works in detail. The bigger picture here resulted in me adding a comment in the main configuration class detailing why should not be put there. So, bottom line of the particular problem: don’t use in spring boot, just include spring-web as a maven/gradle dependency and it will be autoconfigured. What should you do when you want to customize your beans? As usual, extend WebMvcConfigurerAdapter (annotate the new class with and do your customizations. And it’s good that they extended the class that provides EnableWebMvc, rather than mirroring the functionality (which is obvious, I guess). Then realized doing it is redundant, after going through Spring Boot’s code and seeing that an inner class in the autoconfiguration class has a single-line javadoc statingĬonfiguration equivalent to answered my question whether spring boot autoconfiguration misses some of the EnableWebMvc “features”. I found them after I got the idea and implemented it that way. Most often – by keeping but also extending Spring Boot’s WebMvcAutoConfiguration. In fact, people that are having issues stemming from this automatically disabled autoconfiguration, are trying to address it in various ways. In this guide it says that Spring Boot adds it automatically, but doesn’t say what happens if you follow your previous experience and just put the annotation. ![]() ![]() The bad part (that wasted me a few hours) is that in no guide you can find that explicitly stated. It turns out that Spring Boot doesn’t mix well with the standard Spring MVC What happens when you add the annotation is that spring boot autoconfiguration is disabled. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |