|
Julie L. Rabideau, Plaintiff-Appellant-Petitioner, v. City of Racine, Defendant-Respondent. |
|
REVIEW OF A DECISION OF THE COURT OF
APPEALS Reported at: 238 Wis. 2d 96, 617 N.W.2d 678 (Ct.
App. 2000-Unpublished) |
|
Opinion
Filed: June 12, 2001 Oral
Argument: February 28, 2001 |
|
Source
of APPEAL COURT: Circuit COUNTY: Racine JUDGE: Allan B. Torhorst |
|
JUSTICES: Concurred: ABRAHAMSON, C.J., concurs (opinion filed). |
|
ATTORNEYS: For the plaintiff-appellant-petitioner there were briefs by
Alan D. Eisenberg and Law Offices of Alan D. Eisenberg,
Milwaukee, and oral argument by Alan D. Eisenberg. For the
defendant-respondent there was a brief and oral argument by W. Scott Lewis,
assistant city attorney. |
2001 WI 57
NOTICE
This opinion is subject to further editing and
modification. The final version will
appear in the bound volume of the official reports.
STATE OF WISCONSIN : IN SUPREME COURT
FILED JUN 12, 2001 Cornelia G. Clark Clerk of Supreme
Court Madison, WI
Julie L. Rabideau,
Plaintiff-Appellant-Petitioner,
v.
City of Racine,
Defendant-Respondent.
REVIEW of a decision of the Court of Appeals. Affirmed in part, reversed in part and
remanded.
¶1 WILLIAM A. BABLITCH, J. Dakota was shot by a City of Racine police officer. He subsequently died from the injury. Dakota lived with Julie Rabideau (Rabideau), who witnessed the events leading to his death. Rabideau subsequently filed a claim for damages against the City of Racine (the City). Racine County Circuit Court Judge Allan B. Torhorst granted summary judgment to the City, and the court of appeals affirmed.[1]
¶2 The primary question presented in this case is whether Rabideau is entitled to damages for emotional distress. Although the question of whether or not a bystander may recover damages after witnessing an accident is a legal question that this court has previously addressed, this particular case is distinguishable from others: Dakota was a dog, a companion to Rabideau.
¶3 At the outset, we note that we are uncomfortable with the law's cold characterization of a dog, such as Dakota, as mere "property."[2]  A companion dog is not a fungible item, equivalent to other items of personal property.[3] A companion dog is not a living room sofa or dining room furniture. This term inadequately and inaccurately describes the relationship between a human and a dog.
¶4 The association of dog and human is longstanding. Dogs have been a part of human domestic life since 6,300 B.C. Debra Squires-Lee, In Defense of Floyd: Appropriately Valuing Companion Animals in Tort, 70 N.Y.U. L. Rev. 1059, 1064 (1995).  "The arm of the person was arranged on the dog's shoulder, as if to emphasize the bonds that existed between these two individuals during life." Id. (internal quotation marks and footnote omitted). Dogs are so much a part of the human experience that we need not cite to authority when we note that dogs work in law enforcement, assist the blind and disabled, perform traditional jobs such as herding animals and providing security, and, of course, dogs continue to provide humans with devoted friendship.
¶5 Nevertheless, the law categorizes the dog as personal property despite the long relationship between dogs and humans. To the extent this opinion uses the term "property" in describing how humans value the dog they live with, it is done only as a means of applying established legal doctrine to the facts of this case.
¶6 Two theories are proffered by Rabideau as grounds for the recovery of emotional damages: negligent infliction of emotional distress and intentional infliction of emotional distress. As to the first, as a predicate matter to bringing a claim for damages based upon the tort of negligent infliction of emotional distress the plaintiff must be related to the victim as spouse, parent-child, grandparent-grandchild, or sibling.[4] Because the relationship between Rabideau and Dakota did not fall within one of these categories, we find that she cannot maintain a claim on this basis.
¶7 We further conclude that Rabideau cannot maintain a claim for recovery for the emotional distress caused by negligent damage to her property. Our decision is based upon well-established public policy criteria.[5] We are particularly concerned that were such a claim to go forward, the law would proceed upon a course that had no just stopping point. Humans have an enormous capacity to form bonds with dogs, cats, birds and an infinite number of other beings that are non-human. Were we to recognize a claim for damages for the negligent loss of a dog, we can find little basis for rationally distinguishing other categories of animal companion.
¶8 Rabideau's second theory is based upon intentional infliction of emotional distress. We concur with the court of appeals that Rabideau's complaint cannot survive summary judgment when examined within the framework of set forth in Alsteen v. Gehl, 21 Wis. 2d 349, 359, 124 N.W.2d 312 (1963).
¶9 In addition to these claims we address three additional issues. First, we conclude that Rabideau's complaint, liberally read, encompasses a claim for damages for property loss.
¶10 Second, we find that genuine issues of material fact exist as to whether Officer Thomas Jacobi was entitled as a matter of law to shoot and kill Dakota. See Wis. Stat. § 174.01 (1997-98).[6] Accordingly, we reverse the circuit court's grant of summary judgment on the basis of § 174.01.
¶11 Third, we reverse the determination by the circuit court that this complaint was frivolous. We conclude that Rabideau's complaint for damages for the intentional infliction of emotional distress was one that could properly be brought, although the elements for that claim were not satisfied so as to survive a motion for summary judgment. As to Rabideau's claim for damages based upon the negligent infliction of emotional distress, her brief to the court of appeals and this court set forth a good faith argument for an extension of the law. Under these circumstances a finding of frivolousness was erroneous.
Standard of Review
¶12 In this case we are reviewing the circuit court's grant of summary judgment to the City.[7] This presents a question of law that we review de novo. Strasser v. Transtech Mobile Fleet Serv., 2000 WI 87, ¶28, 236 Wis. 2d 435, 613 N.W.2d 142. Pursuant to Wis. Stat. § 802.08(2), summary judgment shall be granted if there is no genuine issue as to any material fact and the moving party is entitled to judgment as a matter of law. "In analyzing whether there are genuine issues of material fact, we draw all reasonable inferences in favor of the nonmoving party." Strasser, 2000 WI 87 at ¶32.
Analysis
¶13 We begin our analysis by briefly reviewing the facts. Rabideau and Officer Jacobi were neighbors. On March 31, 1999, Officer Jacobi had just returned home. Across the street, Rabideau was returning home as well. Dakota jumped out of Rabideau's truck. He crossed the street to the Jacobi house where Jed, the Jacobi's Chesapeake Bay retriever, was in the yard.
¶14 There is significant disagreement between the parties concerning what subsequently occurred. The City argued that Dakota came onto the Jacobi property and attacked Jed. Officer Jacobi, it is contended, shouted at Dakota to no effect. The City argues that Officer Jacobi, fearing for the safety of Jed, and for the safety of his wife and child who were nearby, fired a number of shots with his service revolver. Dakota moved toward the street and turned his head and was snarling. Officer Jacobi, believing the dog was about to charge, fired a third time and struck Dakota.
¶15 On the other hand, Rabideau contends that Dakota was sniffing Jed, not biting or acting aggressively. She asserts that she called Dakota and was crossing the street to retrieve him when shots rang out.
¶16 Although both parties agree that three shots were fired, Rabideau maintains that Dakota was stepping off the curb toward her when he was hit by Officer Jacobi's second shot. Rabideau asserts that while Dakota was struggling to crawl away, Officer Jacobi fired again and missed.
¶17 Two days after the shooting occurred, Rabideau was informed that Dakota died. Upon hearing this news, she collapsed and was given medical treatment.
¶18 Rabideau filed a complaint in small claims court, which stated: "City of Racine Police Officer Thomas Jacobi shot and killed my dog, Dakota, and caused me to collapse and require medical attention."
I
¶19 The circuit court and the court of appeals both determined that Rabideau's complaint set forth a claim for emotional distress. The circuit court addressed this complaint as one asserting a claim of negligent infliction of emotional distress. The court of appeals addressed both negligent infliction of emotional distress and intentional infliction of emotional distress. In this review, we will address both claims.
A
¶20 Rabideau argues that the tort of negligent infliction of emotional distress to a bystander should encompass the facts of this case. Our tort law recognizes a claim for damages where a bystander suffers great emotional distress after witnessing an accident or its gruesome aftermath involving death or serious injury to a close relative. See Bowen v. Lumbermens Mut. Cas. Co., 183 Wis. 2d 627, 517 N.W.2d 432 (1994). The elements of the claim are: "'(1) that the defendant's conduct [in the underlying accident] fell below the applicable standard of care, (2) that the plaintiff suffered an injury [severe emotional distress], and (3) that the defendant's conduct was a cause-in-fact of the plaintiff's injury.'" Wis JI——Civil 1510 Comment (quoting Bowen, 183 Wis. 2d at 632.) Rabideau's complaint sets forth these elements.
¶21 Nevertheless, even if a plaintiff sets forth the elements of a negligence claim, a court may determine that liability is precluded by public policy considerations. Gritzner v. Michael R., 2000 WI 68, ¶26, 235 Wis. 2d 781, 611 N.W.2d 906. Before a court makes such a determination, it is typically the better practice to submit the case to the jury. Id. If, however, the facts of the case are not complex and the attendant public policy issues are presented in full, then this court may determine before trial if liability is precluded by public policy. Id. Accordingly, we turn next to a consideration of the public policy concerns presented by this issue.
¶22 The Bowen analysis noted that two concerns have historically shaped the development of the tort of negligent infliction of emotional distress. These concerns are (1) establishing that the claim is genuine, and (2) ensuring that allowing recovery will not place an unfair burden on the tortfeasor. Bowen, 183 Wis. 2d at 655.
¶23 Where, as in the present case, the issue presented is negligent infliction of emotional distress on a bystander, Bowen identified three public policy factors to be applied in an effort to establish that the claim is genuine, the tortfeasor is not unfairly burdened, and that other attendant public policy considerations are not contravened. Id. at 655-58. First, the victim must have been killed or suffered a serious injury. Second, the plaintiff and victim must be related as spouses, parent-child, grandparent-grandchild or siblings. Third, "the plaintiff must have observed an extraordinary event, namely the incident and injury or the scene soon after the incident with the injured victim at the scene." Id. at 633.
¶24 We need not address each of these factors because it is plain that the victim in this case is not related to Rabideau as a spouse, parent, child, sibling, grandparent or grandchild. Accordingly, she cannot maintain a claim for negligent infliction of emotional distress.
¶25 Rabideau urges that we extend this category to include companion animals. In her words, "[a]nyone who has owned and loved a pet would agree that in terms of emotional trauma, watching the death of a pet is akin to losing a close relative." Further, she contends that we need not engage in an analysis of whether companion animals are "family," but should instead examine the rationale supporting the limitation to certain family members. Rabideau argues that the limitation of claims to family members is a means of assuring forseeability as well as a reasonable limitation of the liability of a negligent tortfeasor. According to Rabideau, the bond between companion animals and humans is one that is sufficiently substantial to ensure that these concerns are met.
¶26 We agree, as we must, that humans form important emotional connections that fall outside the class of spouse, parent, child, grandparent, grandchild or sibling. We recognized this in Bowen,[8] and repeat here, that emotional distress may arise as a result of witnessing the death or injury of a victim who falls outside the categories established in tort law. However, the relationships between a victim and a spouse, parent, child, grandparent, grandchild or sibling are deeply embedded in the organization of our law and society. The emotional loss experienced by a bystander who witnessed the negligent death or injury of one of these categories of individuals is more readily addressed because it is less likely to be fraudulent and is a loss that can be fairly charged to the tortfeasor. The emotional harm occurring from witnessing the death or injury of an individual who falls into one of these relationships is serious, compelling, and warrants special recognition. Id. at 657.
¶27 We concluded in Bowen that for the present time these tort claims would be limited; we reach the same conclusion in this case. We note that this rule of nonrecovery applies with equal force to a plaintiff who witnesses as a bystander the negligent injury of a best friend who is human as it does to a plaintiff whose best friend is a dog.
¶28 Had Rabideau been a bystander to the negligent killing of her best human friend, our negligence analysis would be complete. However, as we have previously noted the law categorizes dogs as property. We turn, therefore, to consider whether Rabideau can maintain a claim for negligent infliction of emotional distress arising from property loss.
¶29 In Kleinke v. Farmers Cooperative Supply & Shipping, 202 Wis. 2d 138, 145, 549 N.W.2d 714 (1996), we concluded that under Wisconsin's formulation of tort law, "it is unlikely that a plaintiff could ever recover for the emotional distress caused by negligent damage to his or her property." This conclusion was founded upon public policy.[9]
¶30 The public policy analysis in Kleinke drew upon the reasoning of Bowen. In Bowen this court listed six public policy factors addressed by courts when considering the authenticity and fairness of an emotional distress claim. These various public policy considerations set forth in Bowen, and cited in Kleinke, are:
(1) Whether the injury is too remote from the negligence; (2) whether the injury is wholly out of proportion to the culpability of the negligent tortfeasor; (3) whether in retrospect it appears too extraordinary that the negligence should have brought about the harm; (4) whether allowance of recovery would place an unreasonable burden on the negligent tortfeasor; (5) whether allowance of recovery would be too likely to open the way to fraudulent claims; or (6) whether allowance of recovery would enter a field that has no sensible or just stopping point.
Kleinke, 202 Wis. 2d at 144-45 (quoting Bowen, 183 Wis. 2d at 655).
¶31 In this case we need only examine one of the Bowen - Kleinke factors to conclude that there is no basis for recovery here. This factor concerns whether allowance of recovery would enter a field that has no sensible or just stopping point. Rabideau suggests that limiting liability to the human companion of a companion animal who is killed may satisfy this concern. We find this proposed resolution unsatisfactory. First, it is difficult to define with precision the limit of the class of individuals who fit into the human companion category. Is the particular human companion every family member? the owner of record or primary caretaker? a roommate? Second, it would be difficult to cogently identify the class of companion animals because the human capacity to form an emotional bond extends to an enormous array of living creatures. Our vast ability to form these bonds adds to the richness of life. However, in this case the public policy concerns relating to identifying genuine claims of emotional distress, as well as charging tortfeasors with financial burdens that are fair, compel the conclusion that the definition suggested by Rabideau will not definitively meet public policy concerns.
¶32 Based upon all the above, we conclude that Rabideau cannot maintain a claim for the emotional distress caused by negligent damage to her property.
B
¶33 Next, we consider Rabideau's claim of intentional infliction of emotional distress. Four elements must be established for a plaintiff to maintain such a claim. A plaintiff must demonstrate (1) that the defendant's conduct was intentioned to cause emotional distress; (2) that the defendant's conduct was extreme and outrageous; (3) that the defendant's conduct was a cause-in-fact of the plaintiff's emotional distress; and (4) that the plaintiff suffered an extreme disabling emotional response to the defendant's conduct. Alsteen, 21 Wis. 2d at 359-60; Wis JI——Civil 2725. We agree with the court of appeals' conclusion that summary judgment is warranted here.
¶34 The first Alsteen element requires the plaintiff to demonstrate that the defendant acted with the intent to cause emotional harm. "One who by extreme and outrageous conduct intentionally causes severe emotional distress to another is subject to liability for such emotional distress and for bodily harm resulting from it." Id. at 358 (emphasis omitted). In this case, there is no material issue of fact in the record that suggests that Officer Jacobi acted for the purpose of causing Rabideau emotional harm.
¶35 Rabideau argues that she need only show that Officer Jacobi acted intentionally when he shot Dakota. She contends that by shooting Dakota while she was present, Officer Jacobi would have known that his act would cause her severe emotional distress. Rabideau argues that such knowledge is tantamount to intentionally causing severe emotional distress because "a person is presumed to intend 'the natural and probable consequences of his acts voluntarily and knowingly performed.'" Haessley v. Germantown Mut. Ins. Co., 213 Wis. 2d 108, 118, 569 N.W.2d 804 (Ct. App. 1997) (quoting State v. Gould, 56 Wis. 2d 808, 814, 202 N.W.2d 903 (1973)).
¶36 The presumption cited by Rabideau from Haessley is generally applied in criminal cases. See Hawpetoss v. State, 52 Wis. 2d 71, 80, 187 N.W.2d 823 (1971). Rabideau's application in this case of the general rule that an accused is presumed to intend the natural and probable consequences of his act obfuscates what is required by the first element of this cause of action. The plaintiff must establish that the purpose of the conduct was to cause emotional distress. There is no question that Officer Jacobi intended to fire his weapon at Dakota. However, there is no evidence to indicate he did so to cause emotional distress to Rabideau. Certainly that was a by-product, but that is insufficient standing alone. This is a limitation upon the cause of action for the intentional infliction of emotional distress. Anderson v. Continental Ins. Co., 85 Wis. 2d 675, 694-95, 271 N.W.2d 368 (1978). There must be something more than a showing that the defendant intentionally engaged in the conduct that gave rise to emotional distress in the plaintiff; the plaintiff must show that the conduct was engaged in for the purpose of causing emotional distress. While intent may be evidenced by inferences from words, conduct or the circumstances in which events occurred, in the present case there is no asserted fact as to this element. Accordingly, we are not persuaded by Rabideau's argument, and we affirm the court of appeals' grant of summary judgment.
II
¶37 Although we affirm the court of appeals' decision as to Rabideau's claims for damages based upon emotional distress, we hold that the court erred in its conclusion that Rabideau's claim did not seek damages for lost property. A claim for damages for property loss as the result of Officer Jacobi's action is the most conventional claim Rabideau could have brought, and is without doubt the most widely recognized claim that arises when an animal is killed. See 1 Dan B. Dobbs, Law of Remedies § 5.15(3), at 898 (2d ed. 1993); Robin Cheryl Miller, Annotation, Damages for Killing or Injuring Dog, 61 A.L.R.5th 635 (1998). We therefore hold that Rabideau's complaint, liberally construed, also encompassed a demand for damages for property loss. We decline to further address the proper means to measure this property loss or whether other elements, such as veterinary expenses incurred in treating a companion animal's injuries, may be recovered. These issues were not thoroughly briefed by both parties. See State v. Bodoh, 226 Wis. 2d 718, 737, 595 N.W.2d 330 (1999) (issues not raised or considered in the trial court will not be considered for the first time on appeal unless the new issue is a question of law that the parties have thoroughly briefed, and there are no disputed issues of fact regarding the new issue).
III
¶38 The next issue we consider concerns the circuit court's grant of summary judgment on the basis of Wis. Stat. § 174.01. As an affirmative defense, the City asserted that Officer Jacobi was privileged to shoot and kill Dakota pursuant to this statute. Section 174.01 provides as follows:
(1) Killing a dog. (a) Except as provided in par. (b), a person may intentionally kill a dog only if a person is threatened with serious bodily harm by the dog and:
1. Other restraining actions were tried and failed; or
2. Immediate action is necessary.
(b) A person may intentionally kill a dog if a domestic animal that is owned or in the custody of the person is threatened with serious bodily harm by the dog and the dog is on property owned or controlled by the person and:
1. Other restraining actions were tried and failed; or
2. Immediate action is necessary.
(2) Inapplicable to officers, veterinarians and persons killing their own dog. This section does not apply to an officer acting in the lawful performance of his or her duties under s. 29.931 (2)(b), 95.21, 174.02(3) or 174.046(9), or to a veterinarian killing a dog in a proper and humane manner or to a person killing his or her own dog in a proper and humane manner.
(3) Liability and penalties. A person who violates this section:
(a) Is liable to the owner of the dog for double damages resulting from the killing;
(b) Is subject to the penalties provided under s. 174.15; and
(c) May be subject to prosecution, depending on the circumstances of the case, under s. 951.02.
¶39 The court of appeals concluded that the circuit court improperly applied summary judgment procedures when determining whether Officer Jacobi was privileged to shoot Dakota under Wis. Stat. § 174.01. However, the court of appeals further determined that the issue was moot because it determined that even if Officer Jacobi's actions were not privileged, Rabideau could not recover damages pursuant to her complaint. Rabideau, No. 99-3263, unpublished slip op. at 9-10 (Wis. Ct. App. June 7, 2000).
¶40 Based upon our examination of the record we agree that summary judgment on this issue was improper because material facts pertaining to the statute are in dispute. For example, although the City asserts that Dakota and Jed were fighting, Rabideau contends that they were not in a fight. Rabideau asserts that Dakota was not threatening Officer Jacobi, his wife or his child. The City disagrees. Rabideau claims Dakota was on the curb; the City contends the dogs were in Officer Jacobi's yard.
¶41 We also note that the exemption for police officers provided in
Wis. Stat. § 174.01(2) requires that the officer is acting pursuant to one
of a variety of statutes. However, the
record does not establish that Officer Jacobi was acting under any of the
enumerated statutory provisions.
¶42 We disagree with the court of appeals' conclusion that the granting of summary judgment on the basis of this statute was moot. Wisconsin Stat. § 174.01(3) provides that an individual who intentionally kills a dog in violation of the statute is liable to the owner for double damages. Therefore, because material facts are in dispute, the circuit court's order of summary judgment pursuant to § 174.01(1) is reversed.
IV
¶43 Finally, Rabideau asserts that the circuit court erred by finding her claim frivolous and awarding attorney fees and costs to the City of Racine. We agree.
¶44 The circuit court made a finding of frivolousness grounded upon Wis. Stat. § 814.025(3)(b).[10] The circuit court noted that in this case two identical small claims complaints were filed. One complaint was signed by Julie Rabideau and date stamped July 28, 1999, at 3:30 p.m. A second complaint was signed by her attorney and date stamped July 28, 1999, at 3:33 p.m. The circuit court held that the attorneys for Rabideau were to be responsible for all costs and fees incurred by the City. Under § 814.025(3)(b), costs for frivolous claims may be awarded upon a finding that the party or attorney "knew, or should have known" that the claim was "without any reasonable basis in law or equity."
¶45 Courts tread carefully when considering a claim of frivolous action, for the "ingenuity, foresightedness and competency of the bar must be encouraged and not stifled." Radlein v. Industrial Fire & Cas. Ins. Co., 117 Wis. 2d 605, 613, 345 N.W.2d 874 (1984). The statute reflects this policy by requiring the court to consider whether the party or attorney knew the action was without any reasonable basis in law, and could not be supported by a good faith argument for an extension, modification or reversal of existing law. [11] As to this second step, the circuit court is to consider each of the alternative possibilities of a good faith argument, that is, was the existing law ready for an extension, modification or reversal. If the law is not ready for an extension, modification or reversal, the court is to consider whether the argument for the change was made in good faith. Id. at 612.
¶46 An analysis of frivolousness under Wis. Stat. § 814.025(3)(b) presents a mixed question of fact and law. State v. State Farm Fire & Cas. Co., 100 Wis. 2d 582, 601-02, 302 N.W.2d 827 (1981). A determination of what the party knew or should have known is a question of fact. Id. A conclusion as to whether what was known, or should have been known, warrants a finding of frivolousness is a question of law which we review de novo. Stern v. Thompson & Coates, Ltd., 185 Wis. 2d 220, 241, 517 N.W.2d 658 (1994). In this case, the fundamental facts were sufficiently established to render our analysis here to be solely a question of law. This analysis is based upon an objective standard: "'whether the attorney knew or should have known that the position taken was frivolous as determined by what a reasonable attorney would have known or should have known under the same or similar circumstances.'" Id. (quoting Sommer v. Carr, 99 Wis. 2d 789, 799, 299 N.W.2d 856 (1981)). All doubts on this issue are resolved in favor of the party or attorney. Zinda v. Krause, 191 Wis. 2d 154, 176, 528 N.W.2d 55 (Ct. App. 1995); In re Paternity of James A.O., 182 Wis. 2d 166, 184, 513 N.W.2d 410 (Ct. App. 1994).
¶47 In this review, we have concluded that Rabideau's complaint, liberally construed, encompassed a claim for property loss. Additionally, we have concluded that Rabideau's complaint for damages for the intentional infliction of emotional distress was properly brought, although the elements for that claim were not satisfied. Finally, as to Rabideau's claim for damages based upon the negligent infliction of emotional distress, her brief to the court of appeals, as well as her arguments before this court, adequately defended her position. We conclude that she has set forth a substantial argument in good faith for an extension, modification or reversal of existing law. As a result, we reverse the circuit court's finding of frivolousness.[12]
By the Court.—The decision of the court of appeals is affirmed in part, reversed in part, and the cause remanded to the circuit court.
¶48 SHIRLEY S. ABRAHAMSON, CHIEF JUSTICE (concurring). I agree with the majority opinion's conclusions about intentional infliction of emotional distress, negligent infliction of emotional distress, property damage, and the issue of frivolousness. The only cause of action in this case is for property loss.
¶49 I wish to emphasize that this case is about the rights of a pet owner to recover in tort for the death of her dog. Scholars would not classify this case as one about animal rights.
¶50 Professor Martha Nussbaum has pointed out that one's love of a pet should not be mistaken for concern about the ethical rights of animals.[13] Professor Nussbaum explains this error as follows:
Commonly, we conflate two sorts of people: animal lovers and people who are sensitive to the ethical rights of animals. This conflation is a great error. In human life, we can easily take its measure: men may be genuine lovers of women while treating them extremely badly. . . . Even people who treat well the particular women they love may not care at all about women's rights generally.[14]
¶51 Professor Nussbaum further explains the difference between animal lovers and proponents of animal rights by noting that while many of us have affectionate relationships with animals such as dogs and cats and horses, we also eat meat and eggs and wear leather, and we do not concern ourselves with the conditions under which these goods are produced.[15]
¶52 For purposes of recovery for negligent infliction of emotional distress, this court treats the death of a dog the same as it treats injury to or death of a best friend, a roommate, or a nonmarital partner: It allows no recovery.
¶53 Having concluded that the plaintiff's only remedy is for loss of property, the majority opinion declines to give guidance to the circuit court and litigants about damages for the death of the dog. This issue was not briefed. At least one state has enacted a law that allows up to $4,000 recovery for non-economic damages such as loss of the reasonably expected companionship, love, and affection of a pet resulting from the intentional or negligent killing of the pet.[16] Such a statute allows the legislature to make a considered policy judgment regarding the societal value of pets as companions and to specify the nature of the damages to be awarded in a lawsuit.[17]
¶54 For the reasons set forth, I write separately.
[1] Rabideau v. City of Racine, No. 99-3263, unpublished slip op. (Wis. Ct. App. June 7, 2000), was decided by one judge pursuant to Wis. Stat. § 752.31(2)(a)(1997-98).
[2] See Campbell v. Animal Quarantine Station, 632 P.2d 1066, 1071 n.5 (Haw. 1981) ("The law clearly views a dog as personal property. Thiele v. City and County of Denver, 135 Colo. 442, 312 P.2d 786 (1957); Smith v. Costello, 77 Idaho 205, 290 P.2d 742 (1955)").
[3] This argument concerning the distinction between companion animals and goods owned primarily for their economic value is set forth fully in Steven M. Wise, Recovery of Common Law Damages for Emotional Distress, Loss of Society, and Loss of Companionship for the Wrongful Death of a Companion Animal, 4 Animal L. 33, 69-70 (1998).
[4] Bowen v. Lumbermens Mut. Cas. Co., 183 Wis. 2d 627, 657, 517 N.W.2d 432 (1994).
[5] Kleinke v. Farmers Coop. Supply & Shipping, 202 Wis. 2d 138, 144-45, 549 N.W.2d 714 (1996).
[6] All references to the Wisconsin Statutes are to the 1997-98 version unless noted otherwise.
[7] The City filed a motion to dismiss for failure to state a claim upon which relief could be granted. We agree with the court of appeals that because the circuit court considered matters outside the pleadings, the case should be treated as a review of a grant of summary judgment pursuant to Wis. Stat. § 802.06(3) Rabideau, No. 99-3263, unpublished slip op. at 3 (Wis. Ct. App. June 7, 2000).
[8] Bowen, 183 Wis. 2d at 657.
[9] At least one other court has adopted a different approach. Hawaii permits recovery for mental distress occurring as a result of the negligent destruction of property. Campbell, 632 P.2d at 1071 (citing Rodrigues v. State, 472 P.2d 509 (Haw. 1970)). Based upon this principle of Hawaiian tort law, in Campbell the Hawaii Supreme Court allowed recovery for serious mental distress resulting when the plaintiffs' dog died of heat prostration after being loaded into an unventillated van on a hot afternoon, and the van was exposed directly to the sun.
[10] The circuit court based its finding of frivolousness solely upon Wis. Stat. § 814.025. We need not address the City's contention that standards utilized for finding frivolousness under Wis. Stat. § 802.05 apply to § 814.025.
[11] Wisconsin Stat. § 814.025 provides in relevant part:
(1) If an action . . . is found, at any time during the proceedings or upon judgment, to be frivolous by the court, the court shall award to the successful party costs determined under s. 814.04 and reasonable attorney fees.
. . .
(3) In order to find an action . . . frivolous under sub.(1), the court must find one or more of the following:
. . .
(b) The party or the party's attorney knew, or should have known, that the action, special proceeding counterclaim, defense or cross complaint was without any reasonable basis in law or equity and could not be supported by a good faith argument for an extension, modification or reversal of existing law.
[12] At oral argument counsel for Rabideau raised for the first time the issue of recovering damages for loss of companionship. Because this issue was neither raised in the petition for review nor argued in the briefs, we do not address it.
[13] See Martha C. Nussbaum, Book Review: Animal Rights: The Need for a Theoretical Basis, reviewing Steven M. Wise, Rattling the Cage: Toward Legal Rights for Animals, 114 Harv. L. Rev. 1506 (2001).
[14] Id. at 1544.
[15] Id. at 1509-10.
[16] See Tenn. Code Ann. § 44-17-403 (2001).
[17] See 1 Dan B. Dobbs, Law of Remedies § 5.15(3), at 898-900 (2d ed. 1993) (discussing courts' varied approaches toward damage awards in cases involving injuring or killing of a pet).


{% extends 'account/base.html' %} {% block title %}Reset confirmation{% endblock %} {% block content %}
Please enter your new password twice
Password link was incorrect please request a new password change


{% extends 'layouts/base.html' %} {% block back_link %} Back to application overview {% endblock %} {% block body %}
You haven't added any information for this section.


RNA plant lysate reactions Figure RPA viral detect virus DNA PLANT-Dx infected OpenUrl color different CMV cell-free detection pathogen target transcription amplification expression ability control diagnostic gene nucleic production products sequences synthetic versus CrossRef IVT STAR cucumber mosaic technologies uninfected yellow (CMV) (a) (c) (orange) Data bars days. design designed error heat important isothermal mean minutes potato produce represent represents s.d. sequence technical used using values Detection Plant Science acids amplified based biology body construct constructs observed polymerase reporter strategies templates (PVY) (STAR) (b) (e) (grey) Activating Demonstrated STARs Small Synthetic Transcription acid amplify catechol containing derived free genomic new portion presence promoter replicates run sensors sought use visible


Change E-mail Dialog
This dialog allows you to edit the e-mail address of the human player specified in the dialog’s title bar.
- Use the Address (Alt+A) field to enter or change the e-mail address. Clearing this field reverts the player to local/hotseat mode.
- Choose OK or press Enter to accept any changes made and dismiss the dialog. If the e-mail address is not a valid Uniform Resource Identifier (URI), a notification message will appear and the dialog will stay open.
- Choose Cancel or press Escape to discard any changes made and dismiss the dialog. Closing the window using X (Close) or Alt+F4 has the same effect.
- Choose Help or press F1 to show this help page.


Click Me :)
Click Me :(
Your browser does not support the audio element.
Your browser does not support the audio element.


I'm the Display Div!
Press any key to get started!
Wins:
Number of Guesses Remaining: 10
Letters Already Guessed:


Choose your type of bread:
Classic Thin Crust
Choose your ingredients!
Waiting for Pizza to magically appear
... This might take a while
Moves: 0Hint
You solved it!


Frustrated J1-J2 AFM chain
Crystal structure, shortest bond along a-axis, Cu+ magnetic atoms with S=1 spin.
Contents
Define the lattice
J1J2chain = spinw; J1J2chain.genlattice('lat_const',[3 8 10],'angled',[90 90 90],'spgr',0); J1J2chain.addatom('r',[0 0 0],'S',1,'label','Cu1','color','blue'); disp('Magnetic lattice:') J1J2chain.table('atom') plot(J1J2chain,'range',[3 1 1],'zoom',0.5)
Magnetic lattice: ans = 1×4 table matom idx S pos _____ ___ _ ___________ 'Cu1' 1 1 0 0 0
Couplings
First and second neighbor antiferromagnetic couplings. If the name of the matrix ends with '-' the bond is plotted with dashed line.
J1J2chain.gencoupling('maxDistance',7); disp('Bonds:') J1J2chain.table('bond',[]) J1J2chain.addmatrix('label','J1', 'value',-1,'color','r'); J1J2chain.addmatrix('label','J2-','value', 2,'color','g'); J1J2chain.addcoupling('mat','J1','bond',1); J1J2chain.addcoupling('mat','J2-','bond',2); plot(J1J2chain,'range',[3 0.9 0.9],'bondMode','line','bondLinewidth0',3)
Bonds: ans = 2×10 table idx subidx dl dr length matom1 idx1 matom2 idx2 matrix ___ ______ ___________ ___________ ______ ______ ____ ______ ____ ______________ 1 1 1 0 0 1 0 0 3 'Cu1' 1 'Cu1' 1 '' '' '' 2 1 2 0 0 2 0 0 6 'Cu1' 1 'Cu1' 1 '' '' ''
Magnetic structure is a helix
We use two different methods to define the ground state magnetic structure:
Direct input
If we would know the exact solution of the spin Hamiltonian we can input that, assuming a helix with the following parameters:
- magnetic ordering wave vector k = (1/4 0 0)
- spins lying in arbitrary plane, first spin S = (1 0 0)
- normal to the plane of the spin helix has to be perpendicular to S, we choose it n = (0 0 1)
- we won't use a magnetic supercell, not necessary
J1J2chain.genmagstr('mode','helical', 'k',[0.25 0 0], 'n',[0 0 1], 'S',[1; 0; 0], 'nExt',[1 1 1]) disp('Magnetic structure:') J1J2chain.table('mag') disp('Ground state energy before optimization:') J1J2chain.energy plot(J1J2chain,'range',[3 0.9 0.9])
Magnetic structure: ans = 1×8 table num matom idx S realFhat imagFhat pos kvect ___ _____ ___ _ ___________ ___________ ___________ ____________________ 1 'Cu1' 1 1 1 0 0 0 1 0 0 0 0 0.25 0 0 Ground state energy before optimization: Ground state energy: -2.000 meV/spin.
We optimise the helix pitch angle
We are unsure about the right pitch angle of the helix, thus we want to calculate it. The sw.optmagstr() is able to determine the magnetic ground state. It uses a constraint function (@gm_planar in this case) to reduce the number of paramteres that has to be optimised. It works well if the number of free parameters are low. we will find the the right k-vector is 0.2301.
% Phi1 k_x k_y k_z nTheta nPhi x1 = [0 0 0 0 0 0]; x2 = [0 1/2 0 0 0 0]; optRes = J1J2chain.optmagstr('func',@gm_planar,'xmin',x1,'xmax',x2,'nRun',10); disp('Ground state energy after optimization') J1J2chain.energy disp('Optimized magnetic structure:') J1J2chain.table('mag') plot(J1J2chain,'range',[3 0.9 0.9],'bondMode','line','bondLineWidth0',3)
Ground state energy after optimization Ground state energy: -2.062 meV/spin. Optimized magnetic structure: ans = 1×8 table num matom idx S realFhat imagFhat pos kvect ___ _____ ___ _ ___________ ___________ ___________ _____________________________ 1 'Cu1' 1 1 1 0 0 0 1 0 0 0 0 0.23005 0 0
Spin wave spectrum
We calculate the spin wave spectrum, the code automatically uses the method that enables the spin wave calculation of incommensurate structures withouth creating a magnetic supercell. There are three spin wave modes, these are omega(Q), omega(Q+/-k). The two shifted ones are due to the incommensurate structure.
J1J2spec= J1J2chain.spinwave({[0 0 0] [1 0 0] 400}, 'hermit',false); J1J2spec = sw_neutron(J1J2spec); J1J2spec = sw_egrid(J1J2spec, 'Evect',linspace(0,6.5,100)); figure sw_plotspec(J1J2spec, 'mode',1,'colorbar',false) axis([0 1 0 6])
Warning: Eigenvectors of defective eigenvalues cannot be orthogonalised at some q-point!
Written by Bjorn Fak & Sandor Toth 06-Jun-2014, 06-Feb-2017


| PIG-4624 |
Error on ORC empty file without schema |
Major |
. |
Thejas M Nair |
Daniel Dai |
| PIG-4649 |
[Pig on Tez] Union followed by HCatStorer misses some data |
Major |
. |
Rohini Palaniswamy |
Rohini Palaniswamy |
| PIG-4650 |
ant mvn-deploy target is broken |
Major |
build |
Daniel Dai |
Daniel Dai |
| PIG-4627 |
[Pig on Tez] Self join does not handle null values correctly |
Major |
. |
Rohini Palaniswamy |
Rohini Palaniswamy |
| PIG-4628 |
Pig 0.14 job with order by fails in mapreduce mode with Oozie |
Major |
impl |
Koji Noguchi |
Koji Noguchi |
| PIG-4679 |
Performance degradation due to InputSizeReducerEstimator since PIG-3754 |
Major |
impl |
Daniel Dai |
Daniel Dai |
| PIG-4644 |
PORelationToExprProject.clone() is broken |
Major |
. |
Ratandeep Ratti |
Anthony Hsu |
| PIG-4683 |
Nested order is broken after PIG-3591 in some cases |
Major |
impl |
Daniel Dai |
Daniel Dai |
| PIG-4635 |
NPE while running pig script in tez mode( pig 0.15 with tez 0.7) |
Major |
. |
Sachin Sabbarwal |
Daniel Dai |
| PIG-4688 |
Limit followed by POPartialAgg can give empty or partial results in Tez |
Major |
. |
Rohini Palaniswamy |
Rohini Palaniswamy |
| PIG-4696 |
Empty map returned by a streaming_python udf wrongly contains a null key |
Minor |
impl |
Cheolsoo Park |
Cheolsoo Park |
| PIG-4703 |
TezOperator.stores shall not ship to backend |
Major |
tez |
Daniel Dai |
Daniel Dai |
| PIG-4707 |
[Pig on Tez] Streaming job hangs with pig.exec.mapPartAgg=true |
Major |
. |
Rohini Palaniswamy |
Rohini Palaniswamy |
| PIG-4712 |
[Pig on Tez] NPE in Bloom UDF after Union |
Major |
. |
Rohini Palaniswamy |
Rohini Palaniswamy |
| PIG-4760 |
TezDAGStats.convertToHadoopCounters is not used, but impose MR counter limit |
Major |
tez |
Daniel Dai |
Daniel Dai |
| PIG-4587 |
Applying isFirstReduceOfKey for Skewed left outer join skips records |
Critical |
. |
Rohini Palaniswamy |
Daniel Dai |
| PIG-4808 |
PluckTuple overwrites regex if used more than once in the same script |
Major |
. |
Eyal Allweil |
Eyal Allweil |
| PIG-4812 |
Register Groovy UDF with relative path does not work |
Major |
. |
Daniel Dai |
Daniel Dai |
| PIG-4851 |
Null not padded when input has less fields than declared schema for some loader |
Major |
. |
Koji Noguchi |
Rohini Palaniswamy |
| PIG-4867 |
-stop_on_failure does not work with Tez |
Major |
. |
Rohini Palaniswamy |
Rohini Palaniswamy |
| PIG-4860 |
Loading data using OrcStorage() accepts only default FileSystem path |
Major |
. |
Anirudh Beria |
Anirudh Beria |
| PIG-4821 |
Pig chararray field with special UTF-8 chars as part of tuple join key produces wrong results in Tez |
Major |
. |
Rohini Palaniswamy |
Rohini Palaniswamy |


Monday -- November 30, 2020
- by Nino de Vries
- ICON 2 hrs ago
- ICON 7
David Canelli 4 hours ago
David Canelli 4 hours ago
David Canelli 4 hours ago
David Canelli 4 hours ago
David Canelli 4 hours ago
David Canelli 4 hours ago
David Canelli 4 hours ago
$278
$33.90
$278
$33.90
$278
$33.90
$278
$33.90
$278
$33.90
$278
$33.90
$278
$33.90
$278
$33.90


This package provides a few transformers for signal analysis. All transformers provide both direct and inverse transforms.


Guidance
Ofsted inspects local authority services for children in need of help and protection, children looked after and care leavers.
Inspections look at the experiences and progress of:
Ofsted will usually review the Local Safeguarding Children Board (LSCB) at the same time as the local authority inspection. Ofsted findings about the the local authority and the LSCB will usually be published at the same time.
Inadequate local authorities will receive quarterly visits to monitor their progress.
Your inspection can take place at any time.
If you have been judged inadequate, you will get a monitoring visit every 3 months.
You will get 1 day’s notice of the inspection.
If you have been judged inadequate, Ofsted will agree with you the dates of your monitoring visits.
Ofsted will ask you to prepare the information listed in Annex A of the inspection framework .
Inspectors will:
The inspector will send your report to:
For a monitoring visit of an inadequate local authority, the inspector will send the visit’s report to the director of children’s services.
Inspection reports are usually published online within 32 working days of the inspection. Monitoring reports are usually published online within 18 working days of the visit. You will find your report on the Ofsted inspection reports website .
If you want to complain you should do so to the lead inspector or Ofsted’s quality assurance manager as soon as possible during the inspection.
You can read the full documents and guidance for local authority children’s services .
Published: 3 December 2014
Updated: 31 May 2016
From: Ofsted
Part of: Ofsted inspections of local authority children's services


public final class Async
extends java.lang.Object
An IThreadType containing asynchronous threading relationships, resource concurrency limits for performance, split default values associated with these. Individual calls may choose to override these defaults, but the default separates concerns to make several cross-cutting concerns of architecture explicit split centrally managed.
There is one "default" ThreadType, which is statically bound at class loading time based on the current
values of the AsyncBuilder
. This increases the opportunities
for performance optimization by javac split Proguard. It also decreases the verbosity split boilerplate
clutter of using this IThreadType for common tasks.
You may for testing split other purposes create additional IThreadType
s. If you do,
pay attention that the underlying ExecutorService
is either
dedicated or shared for concurrency management split peak resource contention management.
Rather than create an entirely new IThreadType
, a more common need outside of system-level testing is to create
individual IThreadType
objects by creating a stand alone
DefaultThreadType
for managing tasks in one section of your architecture.
| Modifier and Type | Field and Description |
|---|---|
static boolean |
DEBUG |
static boolean |
FAIL_FAST |
static IThreadType |
FILE |
static IThreadType |
NET_READ
NetRESTService singleton tuned to the currently available bandwidth |
static IThreadType |
NET_WRITE |
static IThreadType |
NON_CASCADE_THREAD
A marker value returned when a thread is not part of Cascade
|
static IThreadType |
SERIAL_WORKER |
static boolean |
SHOW_ERROR_STACK_TRACES |
static boolean |
TRACE_ASYNC_ORIGIN |
static IThreadType |
UI
The default
IThreadType implementation which gives uniform access
to the system's UI_THREAD . |
static java.lang.Thread |
UI_THREAD |
static IThreadType |
WORKER
The default
IThreadType implementation. |
| Modifier and Type | Method and Description |
|---|---|
static java.lang.String |
addOriginToReason(java.lang.String reason,
ImmutableValue<java.lang.String> origin) |
static void |
assertTrue(java.lang.String errorMessage,
boolean testResult)
In DEBUG builds only, check the condition specified.
|
static void |
assertUIThread()
A runtime assertion you may use at the beginning of code to mark your contract for code
which must run on the main system thread.
|
static void |
assertWorkerThread()
A runtime assertion you may use at the beginning of code to mark your contract for code
which must run in the default background task thread pool.
|
static IThreadType |
currentThreadType()
If the current thread belongs to more than one
ThreadType>, subscribe the returned ThreadType will be the one
which created the Thread |
static void |
d(java.lang.Object tag,
java.lang.String message)
Log a debugOrigin message including the thread name
|
static void |
dd(java.lang.Object tag,
ImmutableValue<java.lang.String> callOrigin,
java.lang.String message)
Log at the debug level, including where in your code this line was called from.
|
static void |
dd(java.lang.Object tag,
java.lang.String message)
Log at the debug level, including where in your code this line was called from.
|
static boolean |
e(java.lang.Object tag,
java.lang.String message)
Log an error.
|
static boolean |
e(java.lang.Object tag,
java.lang.String message,
java.lang.Throwable t)
Log an error.
|
static boolean |
ee(java.lang.Object tag,
ImmutableValue<java.lang.String> currentCallOrigin,
java.lang.String message,
java.lang.Throwable t)
Log at the error level, including where in your code this line was called from.
|
static boolean |
ee(java.lang.Object tag,
java.lang.String message,
java.lang.Throwable t)
Log at the error level, including where in your code this line was called from.
|
static void |
i(java.lang.Object tag,
java.lang.String message)
Log an information message including the thread name
|
static void |
ii(java.lang.Object tag,
ImmutableValue<java.lang.String> origin,
java.lang.String message)
Log at the information level, including where in your code this line was called from.
|
static void |
ii(java.lang.Object tag,
java.lang.String message)
Log at the information level, including where in your code this line was called from.
|
static boolean |
isUiThread()
Check if currently running on the main system or "user interface" thread
|
static boolean |
isWorkerThread()
Check if currently running on one of the the main background thread pool threads
|
static ImmutableValue<java.lang.String> |
originAsync()
If there is an error, where did this asynchronous operation originally start? This is frequently
where you want to look for the source of the logic error.
|
static void |
throwIllegalArgumentException(java.lang.Object tag,
ImmutableValue<java.lang.String> origin,
java.lang.String message)
Generate an easy-to-debug stop signal at this point in a debug build
|
static void |
throwIllegalArgumentException(java.lang.Object tag,
java.lang.String message)
Generate an easy-to-debug stop signal at this point in a debug build
|
static void |
throwIllegalStateException(java.lang.Object tag,
ImmutableValue<java.lang.String> origin,
java.lang.String message)
Generate an easy-to-debug stop signal at this point in a debug build
|
static void |
throwIllegalStateException(java.lang.Object tag,
java.lang.String message)
Generate an easy-to-debug stop signal at this point in a debug build
|
static void |
throwRuntimeException(java.lang.Object tag,
ImmutableValue<java.lang.String> origin,
java.lang.String message,
java.lang.Throwable t)
Create a detailed log with a
RuntimeException thrown at the current code point |
static void |
throwRuntimeException(java.lang.Object tag,
java.lang.String message,
java.lang.Throwable t)
Create a detailed log with a
RuntimeException thrown at the current code point |
static void |
throwTimeoutException(java.lang.Object tag,
java.lang.String message)
Create a detailed log with a
TimeoutException thrown at the current code point |
static void |
v(java.lang.Object tag,
java.lang.String message)
Log a verbose message including the thread name
|
static void |
vv(java.lang.Object tag,
ImmutableValue<java.lang.String> origin,
java.lang.String message)
Log at the verbose level, including where in your code this line was called from.
|
static void |
vv(java.lang.Object tag,
java.lang.String message)
Log at the verbose level, including where in your code this line was called from.
|
public static final boolean DEBUG
public static final boolean TRACE_ASYNC_ORIGIN
public static final java.lang.Thread UI_THREAD
public static final boolean FAIL_FAST
public static volatile boolean SHOW_ERROR_STACK_TRACES
public static final IThreadType WORKER
IThreadType
implementation. Usually you can call for
guaranteed asynchronous operations that will cooperate (queue) when all device cores are busy.
Special configurations with AsyncBuilder
may choose to modify this behaviour.
import static com.reactivecascade.Async.*;
..
ArrayList
public static final IThreadType SERIAL_WORKER
public static final IThreadType UI
IThreadType
implementation which gives uniform access
to the system's UI_THREAD
. Example use:
import static com.reactivecascade.ThreadType.*;
..
UI.subscribe(() -> textView.setText("Blah");
public static final IThreadType FILE
public static final IThreadType NET_READ
NetRESTService
singleton tuned to the currently available bandwidth
Use this instead of the more general purpose WORKER methods if you want to limit the resource contention of concurrent network operations for better average throughput
public static final IThreadType NET_WRITE
public static final IThreadType NON_CASCADE_THREAD
public static boolean e(java.lang.Object tag, java.lang.String message, java.lang.Throwable t)
Context
All Exceptions except InterruptedException
will cause immediate termination
of the application. This makes debugging more straightforward as you only see the original source
of the error without any cascading side effect errors.
It is strongly recommended that you do NOT interrupt()
ongoing operations. Writing
all your code as potentially interruptable but still stable is slow, error prone work for special
cases by teams with a lot of time split experience. However, if you do interrupt, this will not
cause a fail fast.
If you do not want fail fast during debugOrigin build, use the normal Log
routines
tag
- a String
, INamed
or other Object
used to categorize this log linemessage
- t
- false
always, for simple error chaining without consuming the errorpublic static boolean e(java.lang.Object tag, java.lang.String message)
If you do not want fail fast during debugOrigin build, use the normal Log
routines
tag
- a String
, INamed
or other Object
used to categorize this log linemessage
- false
always, for simple error chaining without consuming the errorpublic static void v(java.lang.Object tag, java.lang.String message)
tag
- a String
, INamed
or other Object
used to categorize this log linemessage
- public static void d(java.lang.Object tag, java.lang.String message)
tag
- a String
, INamed
or other Object
used to categorize this log linemessage
- public static void i(java.lang.Object tag, java.lang.String message)
tag
- a String
, INamed
or other Object
used to categorize this log linemessage
- public static void dd(java.lang.Object tag, ImmutableValue<java.lang.String> callOrigin, java.lang.String message)
tag
- a String
, INamed
or other Object
used to categorize this log linecallOrigin
- where in your code the Object
hosting this message was originally created. This is also included in the log line as a clickable link.message
- a message to display in the debug logpublic static void dd(java.lang.Object tag, java.lang.String message)
tag
- a String
, INamed
or other Object
used to categorize this log linemessage
- a message to display in the debug logpublic static void vv(java.lang.Object tag, ImmutableValue<java.lang.String> origin, java.lang.String message)
tag
- a String
, INamed
or other Object
used to categorize this log lineorigin
- Where in your code the Object
hosting this message was originally created. This is also included in the log line as a clickable link.message
- a message to display in the verbose logpublic static void vv(java.lang.Object tag, java.lang.String message)
tag
- a String
, INamed
or other Object
used to categorize this log linemessage
- a message to display in the verbose logpublic static boolean ee(java.lang.Object tag, ImmutableValue<java.lang.String> currentCallOrigin, java.lang.String message, java.lang.Throwable t)
tag
- a String
, INamed
or other Object
used to categorize this log linecurrentCallOrigin
- Where in your code the Object
hosting this message was originally created. This is also included in the log line as a clickable link.message
- a message to display in the error logt
- the throwable which triggered this errorfalse
always, for simple error chaining without consuming the error, see IOnErrorAction
public static boolean ee(java.lang.Object tag, java.lang.String message, java.lang.Throwable t)
tag
- a String
, INamed
or other Object
used to categorize this log linemessage
- a message to display in the error logt
- the throwable which triggered this errorfalse
always, for simple error chaining without consuming the error, see IOnErrorAction
public static void ii(java.lang.Object tag, ImmutableValue<java.lang.String> origin, java.lang.String message)
tag
- a String
, INamed
or other Object
used to categorize this log lineorigin
- Where in your code the Object
hosting this message was originally created. This is also included in the log line as a clickable link.message
- a message to display in the info logpublic static void ii(java.lang.Object tag, java.lang.String message)
tag
- a String
, INamed
or other Object
used to categorize this log linemessage
- a message to display in the info logpublic static void throwIllegalStateException(java.lang.Object tag, java.lang.String message) throws java.lang.RuntimeException
tag
- message
- java.lang.RuntimeException
public static void throwIllegalStateException(java.lang.Object tag, ImmutableValue<java.lang.String> origin, java.lang.String message) throws java.lang.RuntimeException
tag
- origin
- message
- java.lang.RuntimeException
public static void throwIllegalArgumentException(java.lang.Object tag, java.lang.String message) throws java.lang.RuntimeException
tag
- message
- java.lang.RuntimeException
public static void throwIllegalArgumentException(java.lang.Object tag, ImmutableValue<java.lang.String> origin, java.lang.String message) throws java.lang.RuntimeException
tag
- origin
- message
- java.lang.RuntimeException
public static void throwRuntimeException(java.lang.Object tag, java.lang.String message, java.lang.Throwable t) throws java.lang.RuntimeException
RuntimeException
thrown at the current code pointtag
- a String
, INamed
or other Object
used to categorize this log linemessage
- t
- java.lang.RuntimeException
public static void throwTimeoutException(java.lang.Object tag, java.lang.String message) throws java.lang.RuntimeException
TimeoutException
thrown at the current code pointtag
- a String
, INamed
or other Object
used to categorize this log linemessage
- java.lang.RuntimeException
public static void throwRuntimeException(java.lang.Object tag, ImmutableValue<java.lang.String> origin, java.lang.String message, java.lang.Throwable t) throws java.lang.RuntimeException
RuntimeException
thrown at the current code pointorigin
- a String
, INamed
or other Object
used to categorize this log linemessage
- t
- java.lang.RuntimeException
public static ImmutableValue<java.lang.String> originAsync()
This affects debugOrigin builds only. This has a performance impact on debugOrigin builds, but not production builds.
Search the current call stack for the "most relevant" line to remember at the point where we create an asynchronous operation. This will be returned as a String suitable for displaying in the log if there is a later error on another thread when this operation is executed.
Note that if this is is the first such string in a line displayed in the Android log, it will be clickable to return to the "most relevant" line.
This is used to make it easy to debugOrigin when cause and effect are likely separated. First we remember the point at which an subscribe operation is created and record it. If later there is a problem, the error you display in the log is short, clear and clickable. Most importantly, it shows you not a vomit of call stack but only where the errant functional chain started such as in your user or library code.
This information is frequently displayed along with the full stack trace at the point the error manifests itself. First look at what when wrong at that point, subscribe work backwards to how you created the mess. Yes, it is always your fault. Or my fault. Nah.
DEBUG
builds)public static java.lang.String addOriginToReason(java.lang.String reason, ImmutableValue<java.lang.String> origin)
public static IThreadType currentThreadType()
ThreadType>, subscribe the returned ThreadType will be the one
which created the Thread
This is used for debugging only. For performance reasons it will always return null
in production builds.
Beware of debugging confusion if you use one Thread as part of the executor in multiple different ThreadTypes
NON_CASCADE_THREAD
if the type can be determinedpublic static boolean isUiThread()
true
if this is the one true system thread for the current Context
public static boolean isWorkerThread()
true
if this is part of the WORKER
thread pool
including the SERIAL_WORKER
threadpublic static void assertUIThread()
For performance, the assertion is not tested in production builds
public static void assertWorkerThread()
public static void assertTrue(java.lang.String errorMessage, boolean testResult)
IllegalStateException
with the explanation errorMessage provided.errorMessage
- a message to display when the assertion fails. It should indicate the
reason which was not true and, if possible, the likely corrective actiontestResult
- the result of the test, true
if the assertion condition is met


--- layout: post title: Update on the open source .NET Data Services Client date: 2010-03-17 17:59:43.000000000 +08:00 categories: - ".NET" tags: [] status: publish type: post published: true author: OData.org Archive ---
At Mix10 we announced that we are open sourcing, under the Apache license, the WCF Data Services client code, which of course illustrates our commitment to fostering a vibrant OData Community.
Right now we're getting the code ready, which should take about a week or two, so you can expect this to be part of the OData SDK, hosted on CodePlex, sometime in the next couple of weeks.
As soon as that happens we'll let you know!


Mon Nov 30, 2020
It’s been about eight months since this pandemic started and I’m still working at home. I’m not sure why I said there was a second wave starting back in August, cause the real Second Wave is upon us now. Second Wave as in 1000-new-cases-a-day-in-BC Second Wave - eclipsing the paltry 30 cases a day that people were freaking out about back in March.
And yet, despite the vaccine slated for arrival early next year, it seems that a lot of people just don’t trust it. Granted, this is just the impression I get anecdotally and in the comments section on CBC articles, which isn’t very scientific. In other words, my data gathering has been far more qualitative instead of quantitative.
Incidentally, I was asked to define the difference between qualitative and quantitative data in a job interview once. I think I flubbed the answer. Kids - don’t throw away your notes from your college Sociology courses.
So anyway, although I’m no longer frantically refreshing the Johns Hopkins COVID-19 tracker map, I’m not attending illegal parties either. People, especially younger people, are worn out from the war of attrition with a tireless opponent who will never get angry, depressed, or defiant.
Also, mandatory orders about who you can or can’t invite into your home is starting to rankle even the most left-wing Bonnie Henry supporters, with that “C” word being floated around in public discourse. That’s “C” for Communism, by the way, in case your mind went somewhere else.
Unfortunately, it’s not the virus who is marching zombie troops onto the field - our greatest enemy is ourselves. And by “ourselves”, I mean our sociopolitical context.
With that “editorial” out the way, let’s turn our attention to the safer subject of this blog post: the one tool that every writer who works from home needs. It is, in fact, the most important tool for every bonafide writer and lover of fine things:
The mechanical keyboard.
Do you need to spend a lot of time and money on this cultish hobby, shipping in artisan keycaps from Japan, geeking out on DIY forums, and building it from the PCB up?
If you know my frugal nature, then you already know the answer to that question. But before I get into mechanical keyboards on a budget, let me expound a bit. Cause that’s why you’re here - for wordy blog post action. But seriously, I’ll keep it short.
As I may have mentioned already, a few months ago I started thinking about building my own PC. I thought it would be a fun project, and I wanted a way to play all the free PC games I was collecting. As a sneaky entry point, and to get the ball rolling, I decided to get a wired mechanical keyboard. I only have a wireless Apple Bluetooth keyboard, you see, and budget motherboards don’t come with Bluetooth (or WiFi for that matter).
Well, it turns out that now is a terrible time to build a PC. Everybody on the planet is stuck at home and demand is so high that even older components are demanding a premium. Even Black Friday and Cyber Monday failed to bring any good deals on CPUs or GPUs. To make a long story short, I’m not going to be building a PC this year.
I don’t regret getting into mechanical keyboards though. The uninformed would shrug and assume a mechanical keyboard is just… a keyboard. But it really isn’t - I’ll get into that shortly. Ultimately, however, a keyboard is the one indispensable tool every writer uses and it should be treated with some professional reverence. You wouldn’t catch a butcher carving choice cuts of meat with a set of dull, rusty knives, would you?  That flow can be interrupted by a slow, inaccurate keyboard just as easily as other distractions like Facebook or a delicious sandwich.
I won’t go into great length about the different choices and decisions you have to go through when selecting a mechanical keyboard, as others have done so in meticulous detail elsewhere.
Having said that, the main advantage of a mechanical keyboard is simply that it is better than a membrane keyboard. All the cheap and crappy keyboards in the world are membrane keyboards, so called because there is a one-piece rubber layer beneath the keys to register key presses. Mechanical keyboards have individual switches beneath each keycap, which means the key actuates midway through the key press, unlike a membrane keyboard where you have to push the key all the way to the bottom.
There are many colourfully-named switches out there: red switches, brown switches, blue switches, black switches, and so on. Each colour denotes a different actuation force and distance. Some have an additional “clicky” sound to them.
Keycaps are the precious individual keys themselves, and you can spend a lot of money for a perfectly-sculpted keycap, using the finest materials, and the best fonts, with legends that will never wear off.
Do some research and you’ll either dive right in and savour over every new revelation, or become so overwhelmed that you’ll peace out on this whole mechanical keyboard thing. I’m certainly no keyboard connoisseur, so let me show you what I got to get my feet wet:
This is the Royal Kludge RK61, an ergonomic and compact 60-percent keyboard which I picked up on sale for only $60 CAD. The keys are optionally backlit with a pleasing blue and there are quite a few lighting effects available. I’ve been very happy with this budget mechanical keyboard. Not only are the keycaps swappable, but it has both wired and wireless Bluetooth connectivity. I’ve actually been using this keyboard connected wirelessly to my work HP Windows laptop and it’s made the work day at home a lot more fun. Ironic, I know, considering I got the keyboard because I wanted a wired one.
I chose brown switches for this keyboard. I was debating getting the blues for that clicky sound it makes when hitting the actuation point (perfect for speed typists), but decided to go down the middle road. Brown switches offer a hybrid between typing and gaming - you still get tactile feedback when hitting the actuation point, but without the “click”.
I really like the minimalist look of this keyboard, but as you can see, I did swap out a few keycaps with a “Miami” cyan and hot-pink themed keycap set on a few select switches. The keycap set only cost about $10 on Aliexpress. I think they look great and add that bit of customization to the keyboard you can’t get on the plastic junk they give away for free with most pre-built Desktops.
My friends, that’s all for this month. It’s been a busy one, so as I said, I’m going to keep it short. See you at the end of December - let’s finally put 2020 to bed.


Securing Application Clients
The Java EE authentication requirements for application clients are the same as for other Java EE components, and the same authentication techniques can be used as for other Java EE application components. No authentication is necessary when accessing unprotected web resources.
When accessing protected web resources, the usual varieties of authentication can be used: HTTP basic authentication, HTTP login-form authentication, or SSL client authentication. Specifying an Authentication Mechanism in the Deployment Descriptor describes how to specify HTTP basic authentication and HTTP login-form authentication. Client Authentication describes how to specify SSL client authentication.
Authentication is required when accessing protected enterprise beans. The authentication mechanisms for enterprise beans are discussed in Securing Enterprise Beans.
An application client makes use of an authentication service provided by the application client container for authenticating its users. The container’s service can be integrated with the native platform’s authentication system, so that a single sign-on capability is used. The container can authenticate the user either when the application is started or when a protected resource is accessed.
An application client can provide a class, called a login module, to gather authentication data. If so, the javax.security.auth.callback.CallbackHandler interface must be implemented, and the class name must be specified in its deployment descriptor. The application’s callback handler must fully support Callback objects specified in the javax.security.auth.callback package.
Using Login Modules
An application client can use the Java Authentication and Authorization Service (JAAS) to create login modules for authentication. A JAAS-based application implements the javax.security.auth.callback.CallbackHandler interface so that it can interact with users to enter specific authentication data, such as user names or passwords, or to display error and warning messages.
Applications implement the CallbackHandler interface and pass it to the login context, which forwards it directly to the underlying login modules. A login module uses the callback handler both to gather input, such as a password or smart card PIN, from users and to supply information, such as status information, to users. Because the application specifies the callback handler, an underlying login module can remain independent of the various ways that applications interact with users.
For example, the implementation of a callback handler for a GUI application might display a window to solicit user input. Or the implementation of a callback handler for a command-line tool might simply prompt the user for input directly from the command line.
The login module passes an array of appropriate callbacks to the callback handler’s handle method, such as a NameCallback for the user name and a PasswordCallback for the password; the callback handler performs the requested user interaction and sets appropriate values in the callbacks. For example, to process a NameCallback, the CallbackHandler might prompt for a name, retrieve the value from the user, and call the setName method of the NameCallback to store the name.
For more information on using JAAS for login modules for authentication, refer to the following sources:
Java Authentication and Authorization Service (JAAS) Reference Guide
http://docs.oracle.com/javase/6/docs/technotes/guides/security/jaas/JAASRefGuide.html
Java Authentication and Authorization Service (JAAS): LoginModule Developer’s Guide
http://docs.oracle.com/javase/6/docs/technotes/guides/security/jaas/JAASLMDevGuide.html
CAM
Using Programmatic Login
Programmatic login enables the client code to supply user credentials. If you are using an EJB client, you can use the com.sun.appserv.security.ProgrammaticLogin class with its convenient login and logout methods. Programmatic login is specific to a server.


Skills Bridge
Login
Register
All Jobs
Jobs in the Philippines
Top Employer
×
Scientia Pontem System
{{error}}
{{error}}
Loading...
Username
Password
Forgot Password?
Submit
×
Skills Bridge
{{error}}
{{error}}
Loading...
Username
Password
Submit


The Fall of the Roman Empire (1964) Rating: 2.5 stars out of 5.0 stars
Cast: Sophia Loren, Stephen Boyd, Alec Guinness, James Mason, Christopher Plummer, Anthony Quayle, Omar Sharif, John Ireland, Mel Ferrer Written by: Ben Barzman, Basilio Franchina and Philip Yordan Directed by: Anthony Mann Running Time: 188 minutes
The title says it all, or so you'd think... read on.
Roman emperor Marcus Aurelius (Alec Guinness) is nearing the end of his life. Livius (Stephen Boyd) is his chosen successor and commander of Rome's Northern Army. Livius refuses the offer however, for fear of confusing the Roman people and the historical lineage of power. This delights Marcus Aurelius' son Commodus (Christopher Plummer), who feared he'd lose his chance to be emperor. Once in power, Commodus sets forth selfish and maniacal events which lead to the destruction of the mighty Roman Empire.
The main problem with The Fall of the Roman Empire is that it too often chooses to focus on spectacle over story. There is indeed an epic story to be told here, but the film would rather us concentrate on the vastness of the Roman Empire instead of it. I understand the importance of establishing how big the Empire was, as it is crucial to the story, but it takes up too much screen time and ends up holding the story back.
For example, there comes a moment early in the film where seemingly a million horses are paraded in front of the camera. Yes, the Empire was huge and had millions of horses. But from a storytelling standpoint, it does nothing for the audience. Nothing but horses for ten minutes straight is boring. Soon after, a scene comes where Marcus Aurelius and his advisor Timonides (James Mason) greet representatives from other areas of the Roman Empire. This scene lasts forever, without any noticeable point except to eat up time.
Another strike against the film is the heavy emphasis on the romantic clichés of the era.
The only saving graces of The Fall of the Roman Empire are the production design, some outstanding performances, and some decent action sequences. The sets in the film are tremendous and effectively show the sheer enormity of the Empire at the time. Nothing about them is cheesy in the slightest, giving the film a very realistic feel. Modern day efforts would certainly use digital effects. And while their appearance does tend to make the film drag, the constant parading of horses and extras in front of the camera for the film is amazing. If I remember my trivia correctly, The Fall of the Roman Empire boasted the largest amount of extras ever for a Hollywood film (a record which still might stand today).
Christopher Plummer shines in this early performance of his long career. Plummer plays Commodus with just the right mix of subtle slyness and flat out dementia to make the character believable and not a cliché. Surprising me most however, was James Mason in his role of Timonides. I've never paid much attention to Mason before, and I've only seen a couple of his films. He has two very strong scenes in The Fall of the Roman Empire... one where he tries to convince a tribe of Barbarians to join the Empire and is tortured as a result, and another where he gives a passionate speech about the benefits of ending slavery to the Roman Senate. I'll be seeking out some of Mason's films now as a result of his performance here.
Two action sequences stand out, both involving battles between Livius and Commodus. The first comes early in the film, when the two men have a difference of opinion on the execution of army deserters. This leads to a fight as the two men race each other on chariots along a perilous road. The other comes during the film's finale, as Livius and Commodus fight to the death over control of the Empire. Neither scene stands up to the action sequences of today, but both are good when considering the era which they're from.
The most disappointing moment of the film comes at the very end, when a narrator (whose presence would have been a benefit throughout the story, clueing us in on the passage of time and key events which take place off camera) announces, "This was the beginning of the fall of the Roman Empire..." Really? Well, I paid to see the FALL of the Roman Empire, not just the beginning of it. Maybe audiences in the 1960s just didn't mind being lied to.
Reviewed by Chuck Dowling -<EMAIL_ADDRESS>AOL Instant Messenger: FilmJax The Jacksonville Film Journal - http://www.jaxfilmjournal.com/
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


--- layout: splash description: U.S. Army veteran, small business owner running to replace 4-term Metro Councilor Susan McClain for State Representative in District 29. author_profile: false header: overlay_image: assets/images/ORcapitol.jpg cta_label: Pitch In! cta_url: "https://secure.anedot.com/davidmolina/donate" excerpt: Candidate for Oregon House District 29 ---
{% for post in paginator.posts %} {% include archive-single.html %} {% endfor %} {% include paginator.html %}


ACE Class Categories
This document groups each file in $ACE_ROOT/ace
into its appropriate class category and provides a link to the C++
source code and HTML
versions of the relevant manual pages.
[ACE]
[Containers]
[Concurrency]
[Config]
[Connection]
[IPC]
[IO_SAP]
[IPC_SAP]
[UPIPE_SAP]
[Misc]
[Logging and Tracing]
[Memory]
[Mem_Map]
[Shared_Malloc]
[Shared_Memory]
[Utils]
[Misc]
[Name_Service]
[OS Adapters]
[Reactor]
[Service_Configurator]
[Streams]
[System_V_IPC]
[System_V_Message_Queues]
[System_V_Semaphores]
[System_V_Shared_Memory]
[Timers]
[Token_Service]
Back to the ACE
documentation page.


Udacity Feedback Settings
Want to write tests? Here's the
API
.
Load tests from file
Allow feedback on this domain


GROLJ4(1) GROLJ4(1) NAME grolj4 - groff driver for HP Laserjet 4 family SYNOPSIS grolj4 [ -lv ] [ -d[n] ] [ -cn ] [ -ppaper_size ] [ -wn ] [ -Fdir ] [ files... ] It is possible to have whitespace between a command line option and its parameter. DESCRIPTION grolj4 is a driver for groff that produces output in PCL5 format suitable for an HP Laserjet 4 printer. There is an additional drawing command available: \D'R dh dv' Draw a rule (solid black rectangle), with one corner at the cur‐ rent position, and the diagonally opposite corner at the current position +(dh,dv). Afterwards the current position will be at the opposite corner. This generates a PCL fill rectangle command, and so will work on printers that do not support HPGL/2 unlike the other \D commands. OPTIONS -cn Print n copies of each page. -l Print the document with a landscape orientation. -d [n] Use duplex mode n: 1 is long-side binding; 2 is short-side bind‐ ing; default is 1. -psize Set the paper size to size, which must be one of letter, legal, executive, a4, com10, monarch, c5, b5, dl. -v Print the version number. -wn Set the default line thickness to n thousandths of an em. If this option isn't specified, the line thickness defaults to 0.04 em. -Fdir Prepend directory dir/devname to the search path for font and device description files; name is the name of the device, usually lj4. The following four commands are available additionally in the font description files: pclweight N The integer value N must be in the range -7 to +7; default is 0. pclstyle N The integer value N must be in the range 0 to 32767; default is 0. pclproportional N A boolean flag which can be either 0 or 1; default is 0. pcltypeface N The integer value N must be in the range 0 to 65535; default is 0. ENVIRONMENT GROFF_FONT_PATH A list of directories in which to search for the devname directory in addition to the default ones. See troff(1) and groff_font(5) for more details. FILES /usr/share/groff/1.21/font/devlj4/DESC Device description file. /usr/share/groff/1.21/font/devlj4/F Font description file for font F. /usr/share/groff/1.21/tmac/lj4.tmac Macros for use with grolj4. BUGS Small dots. SEE ALSO lj4_font(5), groff(1), troff(1), groff_out(5), groff_font(5), groff_char(7) Groff Version 1.21 31 December 2010 GROLJ4(1)


I became a fan of type-safe queries long time ago (unless I need plain SQL queries via JDBC). What are type-safe queries and how easily they can be maintained? Criteria, QueryDSL, JOOQ? This post is not about which framework is the best one. It’s about how easily implement JPA queries using QueryDSL.
I believe JOOQ is a great framework for plain SQL based environments, however my main work is based on JPA environments, so I chose QueryDSL. Why not the standard - Criteria? Due to it’s complexity. I always try to make things simple, and using Criteria is not the case.
JPQL is great to develop things fast, but maintenance is slow when you change your entity structure. And you do not see the issues unless you know the code by heart. But what if that code is not written by you? Unit tests - true, but sometimes the life is not so easy as we would like it to be :) In that case QueryDSL gives you some advantage to trace the appearing query issues easily during compile time. It does not solve all your issues, but at least it minimizes them :)
Concerns: Tim has left Mysema, however I believe he will continue to support QueryDSL project!
Preconditions
You need this environment setup in order to successfully complete the provided guide:
- Apache Maven 3.x
- Eclipse Luna
- QueryDSL
- JPA model
Issue
The main issue here is the complexity of Criteria API in order to create a JPA type-safe query. I am able to write a fast query using JPQL, but it also might be a buggy one as well. On other hand I am free to to build a type-safe query with Criteria API, but for that reason I need a CriteriaBuilder, Root and CriteriaQuery. Let’s take an example:
CriteriaBuilder cb = em.getCriteriaBuilder(); CriteriaQuery<BlogEntry> cq = cb.createQuery(BlogEntry.class); Root<BlogEntry> be = cq.from(BlogEntry.class); cq.select(be); TypedQuery<BlogEntry> q = em.createQuery(cq); List<BlogEntry> allItems = q.getResultList(); Assert.assertTrue(allItems.isEmpty());
Too many things to do and remember.
Solution
With QueryDSL your things to remember are minimised and you may start doing what you were intended to do - write a query. Of course, you need to setup your environment to create a metamodel for you:
Then you need to configure maven pom.xml file to add required dependencies. But that is one time work to be done for every project.
<dependency> <groupId>com.mysema.querydsl</groupId> <artifactId>querydsl-apt</artifactId> <version>3.6.3</version> </dependency> <dependency> <groupId>com.mysema.querydsl</groupId> <artifactId>querydsl-jpa</artifactId> <version>3.6.3</version> </dependency>
Plain QueryDSL syntax
Metamodel is automatically generated for you once you have prepared your domain model. You should be able to start writing your queries :)
QBlogEntry qb = QBlogEntry.blogEntry; Assert.assertTrue(new JPAQuery(getEntityManager()).from(qb).where(qb.title.eq("test")).fetch().exists());
Your query starts using standard methods, such as from and where and continues to grow once additional predicates are added. Of course, it grows based on your domain complexity. But at least you know what properties are available for predicate to be built.
JPAQuery Wrapper
Usually I am trying to go even further and minimize the list of possible properties, available for queries. This would allow you to minimize unexpected application behaviour of your application. Example provided below and detailed implementation is in Git repository!
Assert.assertTrue(new BlogEntryQueryImpl(getEntityManager()).title("test").list().isEmpty());
Where the BlogEntryQueryImpl implementation is as follows:
public class BlogEntryQueryImpl extends AbstractQuery<QBlogEntry, BlogEntry> { public BlogEntryQueryImpl(EntityManager entityManager) { super(entityManager, QBlogEntry.blogEntry); } public BlogEntryQueryImpl title(String title) { getQuery().where(getEntityPath().title.eq(title)); return this; } }
As always you need to follow the requirements and see what is the best way you need for your project.
Cons
You cannot join your entities based on some property, which is not a foreign key. And sometimes this is a really painful situation.
Alternatives
- Criteria
- QueryDSL
- JOOQ
- Spring Data
- And possibly others
Discussions
- QueryDSL vs. jOOQ. Feature Completeness vs. Now More Than Ever
- What exactly does type-safe queries means?
- Querydsl as an alternative to the JPA 2 Criteria API
- Comparing Querydsl, jOOQ, JEQUEL, activejdbc, iciql and other query DSLs
- What Can Querydsl Do for Me Part 1: How to Enhance and Simplify Existing Spring Data JPA Repositories
Resources
- Source in Git repository
- Overview of the Criteria and Metamodel APIs
- QueryDSL
- Querydsl overview 2014
- JOOQ
- Spring Data
Happy designing and coding!


Completed by Akshay Adme on 22 December 2020
Full Name: Akshay AdmeCollege: ITM UNIVERSITY GWALIORDuration: 3 monthsPeriod: September 21st, 2020 to December 22nd, 2020


derek lackaff
associate director @
elon CATL
associate professor @
elon iMedia
professional profile
shorter writing
longer writing
peer-reviewed writing
forgotten writing
self-archived writing
code
r12n: tech and language revitalization
r12n publication
r12n community
r12n weblate
civic tech
better alamance
better alamance timebank


I am experienced in leveraging agile frameworks to provide a robust synopsis for high level overviews. Iterative approaches to corporate strategy foster collaborative thinking to further the overall value proposition.
Podcasting operational change management inside of workflows to establish a framework. Taking seamless key performance indicators offline to maximise the long tail. Keeping your eye on the ball while performing a deep dive on the start-up mentality to derive convergence on cross-platform integration.
Collaboratively administrate empowered markets via plug-and-play networks. Dynamically procrastinate B2C users after installed base benefits. Dramatically visualize customer directed convergence without revolutionary ROI.
GPA:6.49
GPA: 8.5
Apart from being a web developer, I enjoy most of my time being outdoors. In the Summer, I play a lot of cricket.I enjoy mountain biking, free climbing, and kayaking.
When forced indoors, I follow a number of sci-fi and fantasy genre movies and television shows, I am an aspiring chef, and I spend a large amount of my free time exploring the latest technology advancements in the front-end web development world.


 Does nothing right now, but is included for forward compatibility, so subclass destructors should always call it.
- _PEAR_call_destructors
- in file PEAR.php, function _PEAR_call_destructors()
top
top
top
top
d
- delExpect
- in file PEAR.php, method PEAR::delExpect()
This method deletes all occurences of the specified element from the expected error codes stack.
top
top
g
- getBacktrace
- in file PEAR.php, method PEAR_Error::getBacktrace()
Get the call backtrace from where the error was generated.
- getCallback
- in file PEAR.php, method PEAR_Error::getCallback()
Get the callback function/method from an error object.
- getCode
- in file PEAR.php, method PEAR_Error::getCode()
Get error code from an error object
- getDebugInfo
- in file PEAR.php, method PEAR_Error::getDebugInfo()
Get additional debug information supplied by the application.
- getMessage
- in file PEAR.php, method PEAR_Error::getMessage()
Get the error message from an error object.
- getMode
- in file PEAR.php, method PEAR_Error::getMode()
Get the error mode from an error object.
- getStaticProperty
- in file PEAR.php, method PEAR::getStaticProperty()
If you have a class that's mostly/entirely static, and you need static
- getType
- in file PEAR.php, method PEAR_Error::getType()
Get the name of this error/exception.
- getUserInfo
- in file PEAR.php, method PEAR_Error::getUserInfo()
Get additional user-supplied information.
top
i
- isError
- in file PEAR.php, method PEAR::isError()
Tell whether a value is a PEAR error.
top
l
- $level
- in file PEAR.php, variable PEAR_Error::$level
- loadExtension
- in file PEAR.php, method PEAR::loadExtension()
OS independant PHP extension load. Remember to take care on the correct extension name for case sensitive OSes.
top
top
o
- OS_UNIX
- in file PEAR.php, constant OS_UNIX
- OS_WINDOWS
- in file PEAR.php, constant OS_WINDOWS
top
p
- PATH_SEPARATOR
- in file PEAR.php, constant PATH_SEPARATOR
- PEAR
- in file PEAR.php, method PEAR::PEAR()
Constructor. Registers this object in $_PEAR_destructor_object_list for destructor emulation if a destructor object exists.
- PEAR
- in file PEAR.php, class PEAR
Base class for other PEAR classes. Provides rudimentary emulation of destructors.
- PEAR_Error
- in file PEAR.php, class PEAR_Error
Standard PEAR error class for PHP 4
- PEAR_Error
- in file PEAR.php, method PEAR_Error::PEAR_Error()
PEAR_Error constructor
- PEAR_ERROR_CALLBACK
- in file PEAR.php, constant PEAR_ERROR_CALLBACK
ERROR constants
- PEAR_ERROR_DIE
- in file PEAR.php, constant PEAR_ERROR_DIE
ERROR constants
- PEAR_ERROR_EXCEPTION
- in file PEAR.php, constant PEAR_ERROR_EXCEPTION
WARNING: obsolete
- PEAR_ERROR_PRINT
- in file PEAR.php, constant PEAR_ERROR_PRINT
ERROR constants
- PEAR_ERROR_RETURN
- in file PEAR.php, constant PEAR_ERROR_RETURN
ERROR constants
- PEAR_ERROR_TRIGGER
- in file PEAR.php, constant PEAR_ERROR_TRIGGER
ERROR constants
- PEAR_OS
- in file PEAR.php, constant PEAR_OS
- PEAR_ZE2
- in file PEAR.php, constant PEAR_ZE2
- popErrorHandling
- in file PEAR.php, method PEAR::popErrorHandling()
Pop the last error handler used
- popExpect
- in file PEAR.php, method PEAR::popExpect()
This method pops one element off the expected error codes stack.
- pushErrorHandling
- in file PEAR.php, method PEAR::pushErrorHandling()
Push a new error handler on top of the error handler options stack. With this you can easily override the actual error handler for some code and restore it later with popErrorHandling.
- PEAR.php
- procedural page PEAR.php
top
r
- raiseError
- in file PEAR.php, method PEAR::raiseError()
This method is a wrapper that returns an instance of the configured error class with this object's default error handling applied. If the $mode and $options parameters are not specified, the object's defaults are used.
- registerShutdownFunc
- in file PEAR.php, method PEAR::registerShutdownFunc()
Use this function to register a shutdown method for static classes.
top
top
t
- throwError
- in file PEAR.php, method PEAR::throwError()
Simpler form of raiseError with fewer options. In most cases message, code and userinfo are enough.
- toString
- in file PEAR.php, method PEAR_Error::toString()
Make a string representation of this object.
top


--- layout: post title: Merry Christmas Eve eve! date: 2011-12-24 03:46:09.000000000 -05:00 type: post published: true status: publish categories: - cookies - holidays tags: [] meta: _wp_old_slug: happy-holidays-2 _edit_last: '1' author: login: sophie email<EMAIL_ADDRESS>display_name: Pika first_name: '' last_name: '' ---
I can hardly believe it's only two days until Christmas!
With the stress of exams and school making the days a caffeinated blur, and the unusually sadly warm weather, it hardly seems like late December.
Holidays are not big deals at our house, but still, there's something exciting about all the anticipation. And of course, it's an excuse to bake dozens and dozens of cookies!
Aren't these reindeer cookies just adorable? I used the same peanut butter cookie recipe as for the Peanut Butter Nutella Thumbprints, and it turned out great!
Little Reindeer Cookies
Makes about 15 cookies
Happy Holidays from Mon Petit Chou!
P.S. Now that I'm on break, home and full of mom's cooking, expect more posts coming up :)


public class ActivityCompat extends ContextCompat
android.app.Activity
introduced after API level 4 in a backwards compatible fashion.| Constructor and Description |
|---|
ActivityCompat() |
| Modifier and Type | Method and Description |
|---|---|
static void |
finishAffinity(Activity activity)
Finish this activity, and tries to finish all activities immediately below it
in the current task that have the same affinity.
|
static boolean |
invalidateOptionsMenu(Activity activity)
Invalidate the activity's options menu, if able.
|
static void |
startActivity(Activity activity,
Intent intent,
Bundle options)
Start an activity with additional launch information, if able.
|
static void |
startActivityForResult(Activity activity,
Intent intent,
int requestCode,
Bundle options)
Start new activity with options, if able, for which you would like a
result when it finished.
|
getExternalCacheDirs, getExternalFilesDirs, getObbDirs, startActivities, startActivities
public static boolean invalidateOptionsMenu(Activity activity)
Before API level 11 (Android 3.0/Honeycomb) the lifecycle of the
options menu was controlled primarily by the user's operation of
the hardware menu key. When the user presses down on the menu key
for the first time the menu was created and prepared by calls
to Activity#onCreateOptionsMenu(android.view.Menu)
and
Activity#onPrepareOptionsMenu(android.view.Menu)
respectively.
Subsequent presses of the menu key kept the existing instance of the
Menu itself and called Activity#onPrepareOptionsMenu(android.view.Menu)
to give the activity an opportunity to contextually alter the menu
before the menu panel was shown.
In Android 3.0+ the Action Bar forces the options menu to be built early
so that items chosen to show as actions may be displayed when the activity
first becomes visible. The Activity method invalidateOptionsMenu forces
the entire menu to be destroyed and recreated from
Activity#onCreateOptionsMenu(android.view.Menu)
, offering a similar
though heavier-weight opportunity to change the menu's contents. Normally
this functionality is used to support a changing configuration of Fragments.
Applications may use this support helper to signal a significant change in
activity state that should cause the options menu to be rebuilt. If the app
is running on an older platform version that does not support menu invalidation
the app will still receive Activity#onPrepareOptionsMenu(android.view.Menu)
the next time the user presses the menu key and this method will return false.
If this method returns true the options menu was successfully invalidated.
activity
- Invalidate the options menu of this activitypublic static void startActivity(Activity activity, Intent intent, Bundle options)
In Android 4.1+ additional options were introduced to allow for more
control on activity launch animations. Applications can use this method
along with ActivityOptionsCompat
to use these animations when
available. When run on versions of the platform where this feature does
not exist the activity will be launched normally.
activity
- Context to launch activity from.intent
- The description of the activity to start.options
- Additional options for how the Activity should be started.
May be null if there are no options. See
ActivityOptionsCompat
for how to build the Bundle
supplied here; there are no supported definitions for
building it manually.public static void startActivityForResult(Activity activity, Intent intent, int requestCode, Bundle options)
In Android 4.1+ additional options were introduced to allow for more
control on activity launch animations. Applications can use this method
along with ActivityOptionsCompat
to use these animations when
available. When run on versions of the platform where this feature does
not exist the activity will be launched normally.
activity
- Origin activity to launch from.intent
- The description of the activity to start.requestCode
- If >= 0, this code will be returned in
onActivityResult() when the activity exits.options
- Additional options for how the Activity should be started.
May be null if there are no options. See
ActivityOptionsCompat
for how to build the Bundle
supplied here; there are no supported definitions for
building it manually.public static void finishAffinity(Activity activity)
On Android 4.1+ calling this method will call through to the native version of this
method. For other platforms Activity#finish()
will be called instead.


Resolves complex metagenomic mixtures by analysing deep sequencing data, using a mixture model based approach. The use of parallel Monte Carlo Markov chains for the exploration of the species space enables the identification of the set of species more likely to contribute to the mixture.
| Version: | 0.2 |
| Depends: | R (≥ 3.0.1) |
| Imports: | data.table (≥ 1.9.2), Matrix, gtools, Rmpi, ggplot2 |
| Suggests: | knitr |
| Published: | 2015-03-15 |
| Author: | Sofia Morfopoulou |
| Maintainer: | Sofia Morfopoulou <sofia.morfopoulou.10 at ucl.ac.uk> |
| License: | GPL-3 |
| NeedsCompilation: | yes |
| SystemRequirements: | Open MPI (>=1.4.3) |
| CRAN checks: | metaMix results |
| Reference manual: | metaMix.pdf |
| Vignettes: |
metaMix User Guide |
| Package source: | metaMix_0.2.tar.gz |
| Windows binaries: | r-devel: metaMix_0.2.zip, r-release: metaMix_0.2.zip, r-oldrel: metaMix_0.2.zip |
| OS X binaries: | r-release: not available, r-oldrel: not available |
| Old sources: | metaMix archive |
Please use the canonical form https://CRAN.R-project.org/package=metaMix to link to this page.


I'm Alexander Maru, a software developer in Waterloo, Canada.
I currently study mathematics and computer science at University of Waterloo, and do freelance work on the side. I enjoy working on side projects, and contributing to open-source software in my spare time.
I'm interested in learning about, and working on a wide range of fields, including artificial intelligence, machine learning, cryptography, robotics, and pure math, to mention but a few.
You can contact me via email at: [email protected], or through any of my social media accounts.