text:
"Although they had toured with this play, Cornell and her husband Guthrie McClintic decided to open Romeo and Juliet in New York with a completely new production. Guthrie threw out the entire production and started over, with just a handful of the actors from the tour. Orson Welles was kept, but played Tybalt instead of Mercutio, making his Broadway debut. Maurice Evans played Romeo, while Ralph Richardson took the part of Mercutio, and Edith Evans played the Nurse. Guthrie's idea was to keep the play 'light, gay, hot sun, spacious' with no hint of the doom that would conclude the play. Also, he coached Cornell to read for meaning, sense and emotion, in place of the poetics of iambic pentameter. This was a great break with past productions, which up until then had relied upon Victorian prudery and notions of how a classic play should be performed. Guthrie reinstated the Prologue and believed that all twenty-three scenes were necessary, cutting only the obsolete comedy of the musicians and servants. For the first time. the carnal desires, the youthful romanticism, and the earthiness of language were given equal importance."
The production opened in December, 1934, and, as usual, the reviews were glowing. Burns Mantle called Cornell "the greatest Juliet of her time." Taking note of the freshness of approach, Richard Lockridge of the New York Sun wrote that Cornell played Juliet as "an eager child, rushing toward love with arms stretched out." Cornell herself said that her biggest secret of acting is to do away with all excesses and embellishments, to bring an interpretation to its utmost simplicity. Margot Stevenson from the original cast later said that Cornell was "just this big Italian girl in love!" Stark Young said in The New Republic: She makes you believe in love, that Juliet loves, and that the diapason and poetry of love are the reward for its torment. Of various [other] Juliets this must have been one of the last things to be said."
John Mason Brown wrote in the New York Post: "It is not often in our lifetime that we are privileged to enjoy the pleasant sensation of feeling that the present and the future have met for a few triumphant hours....Yet it was this very sensationthis uncommon sensation of having the present and future meet; eye-witnessing the kind of event to which we will be looking back with pride in the years to comethat forced its warming way, I suspect, into the consciousness of many of us last night as we sat spellbound. Miss Cornell's Juliet is luscious and charming. It finds her at her mellowest and most glamorous. It burns with the intensity Miss Cornell brings to all her acting. It moves gracefully and lightly; it is endlessly haunting in its pictorial qualities; and reveals a Miss Cornell who equals the beauty of the lyric lines she speaks with a new-found lyric beauty of her own voice.... To add that it is by all odds the most lovely and enchanting Juliet our present-day theatre has seen is only to toss it the kind of superlative it honestly deserves." (Source: Wikipedia item on Katharine Cornell, Section 7.1, under GNU Free Documentation License. The whole account of this actress is strongly recommended). Bernard Grebanier considered this production one of the best ever of the play. Photo: courtesy of the Hampden-Booth Library, New York.


text:
Live Fast, Drive Hard and Squeeze In
Bruce Weiner made a fortune in the candy business, and now he's selling off his automotive Skittles.
Mr. Weiner's taste-the-rainbow collection of 200 microcars goes up for auction Friday and next Saturday in Madison, Ga., in a 25,000-square-foot museum devoted to the cars' Lilliputian strangeness and ingenuity.
Dan Neil on Microcars
The Atlanta-based entrepreneur has collected antique firearms, watches, and what's likely the world's most authoritative survey of chewing gum (he once owned Fleer Confections, the inventors of Dubble Bubble gum). He's also had his fair share of Ferraris. But nothing has held his interest like microcars.
"Acquiring seven-figure collector cars is purely a function of money," said Mr. Weiner. "Collecting microcars is about the hunt, finding the best of what's out there and chasing it down." RM Auctions hopes to raise $6.1 million to $8.1 million in total.
The radical minimalism of these machines, built mostly in Europe in the 1950s and early '60s, reflected the region's postwar scarcity. (One resourceful builder beat old cooking pots into fender panels.) They typically measure 10 feet long or less, with less than 700-cc engine displacement and one or two seats—arranged side by side or in tandem, scooter style. The cars' tenure didn't last long: Europe's economic miracle was under way and more comfortable cars grew more affordable. By the time of the zanily bubblelicious 1966 Peel Trident, it was over.
In their time, microcars were utterly disposable. The collection's specimens —most with a shiny candy coating courtesy of the museum's restoration shop—owe something of their survival just to being adorable. "Due to their small size, toylike appearance and their abundance of character, microcars tended not to be scrapped so much as put away," writes Peter Svilans, the museum's former curator, in the catalog essay. Among the oldest cars is the golf-cart-like 1949 Voisin Biscooter prototype, with a skin of gleaming riveted aircraft aluminum, a cuirass worthy of a Fritz Lang ingénue.
The most familiar of these machines are the Messerschmitt KR 200 (Kabinenroller) and the BMW BMW -2.46 % Isetta, both products of former aviation firms in Germany forbidden from building aircraft. Plane builders from both sides of the war—like Ernst Heinkel, Enrico Piaggio and Gabriel Voisin—were "presented with an entirely new set of sobering, restrictive, ground-based parameters" for their postwar duties, writes Mr. Svilans.
Their aircraft experience led to the use of lightweight tubular structures called space frames and large, blisterlike canopies made of Plexiglas (thus the category of "bubble cars"). Likewise, their commitment to streamlining created cars that even now seem startlingly futuristic. The 1956 Paul Vallée Chantecler looks like a one-man submersible to explore off-world oceans.
The Isetta, designed by Italy's Iso Rivolta company in the early 1950s, became the most successful single-cylinder car in history. Built by licensees in several countries (most notably, by BMW in Munich) the instantly recognizable Isetta has a marvelously effective design in which the entire front panel of the car—including steering wheel, console and windshield—swings on a set of side-mounted hinges. It's like opening a refrigerator door and climbing in. Fans of the movie "Cars" will remember that the little Italian tire-changer, Luigi, is an Isetta, and Fred Astaire and Audrey Hepburn squeeze into one in the 1957 musical "Funny Face."
There were dozens of others: Goggomobile, Fulda and Bond. Many were brilliant. The Zundapp Janus was a double-ended microcar in which passengers, like the Roman God, faced both ways. The seats could fold flat into a bed—this at a time when Europeans loved cheap caravanning.
Not all of Mr. Weiner's cars are so nobly framed, of course. Some are gawky, silly, and look somehow incomplete without clowns tumbling out of them. Others represent genuinely bad engineering ideas. Parked in direct sunlight, the poorly ventilated bubble-top Peel Trident could probably cook a chicken in about an hour. And yet, these cars paint a remarkable picture of a time when Europe was desperately lacking in everything but talent.
"It tells me that it doesn't matter how devastated your society is," said Mr. Weiner. "You can always get back on your feet."

subset: commoncrawl


text:
Frigidaire FFHN2740PP 26.6 cu. ft. French Door Refrigerator - Pearl White
1 year parts and labor
Find Out More »
Organize groceries and quickly find what you're looking for with the 26.6 cu. ft. Frigidaire FFHN2740PP French door refrigerator . Its flexible storage system provides over 100 ways to organize food, beverages and condiments regardless of size. Adjustable half-width shelves accommodate tall items like drink containers. Three clear drawers open and close effortlessly, making it easy to locate produce, cold cuts and snacks. A full-width drawer gives you a convenient space for keeping large platters and trays, so they don't take up valuable shelf space. The pearl white Frigidaire FFHN2740P French door bottom-freezer refrigerator has a deep, frost-free freezer that delivers top-down storage. A basket at the top maximizes vertical space to provide quick access to the items you reach for most. An adjustable divider in the lower section gives you greater flexibility. The freezer includes a filtered ice maker that produces 37% more ice in a 24-hour period.
- French door design provides quick, eye-level access to your refrigerator's contents
- Adjustable interior storage gives you over 100 ways to organize and customize your refrigerator
- Full-width Cool-Zone™ drawer extends completely and provides space to easily store anything from sheet cakes and large platters to snacks and juice boxes
- Deep freezer storage with basket and adjustable divider keeps food organized and accessible
- Quick Ice delivers up to 37% more ice in a 24-hour period
- Effortless™ Glide freezer drawers glide smoothly, extend fully and give you easy access to what's inside
- Quiet Pack sound package reduces noise
- Refrigerator is ENERGY STAR® and Star-K® certified
Specifications & Dimensions
More Like This
View Product
View Product
View Product
View Product


text:
Serves 4 |
Prep Time 5 minutes |
Cook Time 10 minutes
1 Tbsp Eden Extra Virgin Olive Oil
4 cups collard greens or kale, remove and finely chop stem, thinly slice leaves on a diagonal
1 pinch Eden Sea Salt
4 ounces Eden Dried Cranberries
2 ounces Eden Tamari Roasted Almonds
2 tsp fresh lemon juice
Heat the oil in a large skillet and sauté the collard stems for 1 minute. Add the collard greens and sea salt. Sauté another 4 to 5 minutes. Add the cranberries and sauté another 1 to 2 minutes until the greens are tender. (If using dried cherries, coarsely chop before adding.) Remove from heat, sprinkle lemon juice over and toss in the almonds. Place in a serving bowl.
American, Condiments, Fruit, Gluten-Free, Good/High Fiber, Good/High Protein, Low Sodium, Macrobiotic, No Sweetener Added, Oils, Side Dish, Snacks, Vegan, Wheat-Free


text:
The Hectic Glow - Current Squad
Graeme Smith
Virender Sehwag
Ravi Bopara
Dale Benkenstein
Mike Hussey
Umar Akmal
Mark Boucher
Mushfiqur Rahim
Dinesh Kartik
Tim Bresnan
Dwayne Bravo
Harbhajan Singh
Darren Sammy
Andre Russell
Nathan Hauritz
Hamid Hassan
Looking to trade one of my keepers for another middle order bat really. Boucher/Rahim would have to go for someone fairly good though, before I start getting awful offers for them.
You better trade them quick though. Who is left having 1 keeper ?
Was stuck between Clarke and Trego for a while to hold a reserve allrounder's slot. Went for Clarke because I think he could play as a bowler if need be.
Hildreth has been picked already.
Damn you GF.
RIP Philip Hughes - 1988-2014
The Wheel of Mediocrity | Compton, Root, Carberry, Robson, Trott, Lyth, Moeen, Hales | The wheel is forever
Founder and Grand Wizard of the CW Football Thread Statluminati. Potential hater of abilities. Blocked on twitter by Michael Vaughan, Brad McNamara and AtlCricket for my hard hitting truths.
A follower of the schools of Machiavelli, Bentham, Locke, Hobbes, Sutcliffe, Bradman, Lindwall, Miller, Hassett and Benaud
Member of ESAS, JMAS, DMAS, FRAS and RTDAS
when you're winning, you have friends
scores and dozens, real friends
when you're winning, never lonely
when you keep winning
GF's pick in, you're up Cabinet
Would have taken Sharma earlier, but he's not played for over a year and don't know how the database factors in a serious accident.
Well it took over a month, but the draft is finally done.
Haha yeah! Probably quicker than last time around though.
Pews can create the database now.
There are currently 1 users browsing this thread. (0 members and 1 guests)


text:
Council Rock North High School football coach Adam Collachi thought he had something pretty good in lineman Curtis Cothran.
He didn't fully grasp how special, though, until a game against Bensalem.
"He probably ran parallel to the line of scrimmage for about 25 yards and made a tremendous play to stop a pretty good athlete for about a 2-yard loss. That's when I knew how good he really can be,'' Collachi said. "My old college coach [from West Chester] was there, and he said, 'Tell me a little bit more about this kid, because he's a freak of nature.'
"He called me a little later and said, 'I don't think you know what you've got on your hands,' and I said, 'Well, I think we do now.'''
Penn State's coaching staff apparently does, too. Although the Nittany Lions were involved with some of the biggest-name defensive ends in the country, they invited Cothran for a March 26 unofficial visit, a day after which the 6-foot-5, 235-pound junior soon committed.
He's expected to be among about a half-dozen current Lion recruits on hand for Saturday's Blue-White Game in what will be just his second time to Penn State.
"It did move pretty fast,'' Cothran said of his recruiting and decision to go to Penn State. "I'd get a letter here and there from them. When I went up there and they offered me, it was pretty obvious I wanted to go there. The coaching staff was just awesome. Everyone I talked to seemed to be looking for the best of my interests. Plus, from a personal standpoint, I've been watching Penn State my whole life, especially being from PA. It was kind of a trip.''
Cothran, whose recruitment was handled by John Butler, picked the Lions over Rutgers and Maryland. He said he had "seven or eight" scholarship offers, and Boston College, Syracuse, UConn, Temple, Northwestern, Purdue and Virginia were some of the other schools involved.
In Cothran, Penn State appears to have gotten a player with outstanding athletic ability which defensive line coach Larry Johnson can mold. Cothran said he has run the 40-yard dash in around 4.7 seconds. Before he gave up track and field to focus on training for football, he competed in the unusual event combination of the 100- and 200-meter dashes, the discus and the shot put.
"Athletically, he's tremendously gifted. His size and speed are something special,'' Collachi said. "He projects to put on 30 or 40 more pounds. His explosiveness and athletic ability really attracted the colleges.''
A two-way starter his last 20 games for Council Rock North, Cothran had 43 tackles, five sacks, caused two fumbles and blocked a kick for the Indians, who play him as a strong-side end in their 4-4 alignment. While those statistics might not be eye-popping, Collachi says the numbers are deceiving.
"I think there are three teams in our league that run at most four times per game, so his sack numbers aren't going to be that high,'' Collachi said. "He's strong at the point of attack, and he's a big reason for the improvement in our defense.''
Council Rock North allowed 18.3 points per game.
Collachi said Cothran's athletic ability was apparent when he was a freshman, but it was Cothran's willingness to work and try to improve that made him think it was worth it to throw him into the fire of the rugged suburban Philadelphia Class AAAA schedule as a sophomore. A self-described "die-hard Eagles fan,'' Cothran is critical of his own game and knows there are areas where he can improve; he likes to watch Julius Peppers to try to pick up little things to make himself better.
"I think my strength is my speed and my ability to change direction,'' Cothran said. "I think I have to work on my hand placement and just keeping linemen off me. I have long arms, and once I'm able able to master the best way to use my hands, keep full extension and keep linemen off me, the better I'll be.''
Cothran, who plans to major in kinesiology, only has been playing organized football since seventh grade - "I was always beating up people playing in the backyard, but I didn't know anything about Pop Warner football.''
Although Penn State likely would sign California's Eddie Vanderdoes or Virginia's Jonathan Allen in the event either of those blue-chip prospects picked it, the Lions appear to have filled their allotment of defensive end scholarship openings with Cothran and New Jersey's Garrett Sickels. Penn State also has a defensive line commitment from four-star New Jersey tackle Greg Webb.


text:
Popular search terms:
apply online, campus map, admissions events, tuition, transcripts, calendar, graduation, scholarships, nursing, bookstore, registrar, academic calendar, athletics
Are you interested in learning about the American criminal justice system? Are you interested in how the legislature, law enforcement, judicial, and correctional systems work together to preserve justice in America?
A major in criminal justice at Benedictine University can prepare you to work in any branch of the criminal justice system that interests you. Criminal justice students learn about the field of criminology as a foundation for their study of police systems, civil and criminal courts, and correctional systems. Students acquire both research and practical skills from instructors with extensive real world experience, including police chiefs, internal affairs officers, probation officers, attorneys, and professors. At the same time, criminal justice majors benefit from the University's proximity to downtown Chicago, a city known internationally for its history of crime syndicates and political corruption, as well as notorious criminal figures like Al Capone and Bugs Moran.
Students pursuing a degree in criminal justice have the opportunity to join honor societies such as Pi Gamma Mu, the international social science honor society, and Psi Chi, the national psychology honor society. The Sociology/Psychology/Criminal Justice Club gives students the opportunity to interact with peers while working in the community.
Graduates of the Criminal Justice program have been successful in gaining admission to law school, pursuing careers in local, federal, and state law enforcement, and finding employment in probation and parole. Our faculty are devoted to working with each student in guiding them through their academic career and toward a successful professional career.
Criminal Justice majors learn the principles of criminal justice, statistics, research methods, as well as how to do a senior thesis in the program's capstone course. Students also work with advisors to choose advanced criminal justice courses according to individual interests and select coursework that provides a breadth of knowledge about other important social science disciplines (sociology, psychology, economics, and political science/anthropology).
Majors must complete a minimum of 43 semester hours in the major with a grade of "C" or better in each course. Students must take the following:
Criminal Justice majors must also complete MATH 105, MATH 108, or MATH 110 with a grade of "C" or better (3); fulfill the social science requirements of the core by taking SOCL 100 (3), ECON 100 (3), and ANTH 200 (3); and take an Ethics course to meet the Philosophy core elective requirement.


text:
Oops! Looks like our kite got away from us. Sorry about that!
It seems the page you're looking for may have been moved or deleted. But don't worry, we'll help you get back to where you need to be. Here are some helpful places to look:
If all else fails, contact us, and let us know if something is broken or if we can help you find something.


text:
NEW YORK - The forecast for the Pinstripe Bowl calls for snow and scoring.
West Virginia and Syracuse play today at Yankee Stadium in a matchup of former Big East rivals and NFL prospect quarterbacks.
Snow is expected to fall in the New York area throughout the day, with accumulations of about 3 inches. Maybe that will help the defenses slow down a couple of offenses that have been among the best in the country this season.
Geno Smith and the Mountaineers are eighth in the nation in total offense at 518 yards a game. Ryan Nassib and the Orange are 21st at 473.
West Virginia (7-5) has scored at least 31 points 10 times this season. Syracuse (7-5) averaged 36 points a game while winning five of its last six.
The last time the Mountaineers faced the Orange, it was on the losing end of a 49-23 decision last season.
Nassib passed for 229 yards and four touchdowns in that contest.
They have everybody back on offense," said Mountaineers coach Dana Holgorsen. "That quarterback (Nassib) just keeps getting better and better. He has worked his way up, much like Geno, to where he is going to be a top draft pick and play at the next level."
West Virginia defensive coordinator Keith Patterson is familiar with Nassib during his career as Pittsburgh's coordinator.
"On Saturday, you're going to see a quarterback who's in command, in complete control," Patterson said. "Last year I think you saw some indecision. This year he's an operator."
Smith has struggled in his last two matchups against Syracuse.
They're very much a dial-up-a-defense kind of team, so you don't know what you're going to get," Holgorsen said. "Seventeen of the first 18 blitzes last year were different, so we have to identify that and get in the right play.
"(Smith) has matured a bunch, and from a scheme standpoint, he is going to be able to see that and make some pretty good checks; I feel comfortable about that."
Both teams are excited about playing in the bowl, despite the looming weather conditions.
"It counts as a win or it counts as a loss, so you better treat it like any other game," Holgorsen said. "At the end of the week you better be prepared to win, because everybody's going to expect you to win.
"Snow doesn't bother us much, but if the wind's blowing then that makes it miserable."
Today's game is set for 3 p.m. and will be televised on ESPN.
"Hopefully our experience in New York playing Syracuse will be better than last year, which was not very pleasant," Holgorsen said.
"We're going to be motivated to play based on what happened last year. We went up to Syracuse and they outcoached us and outplayed us.
"We will revisit that and obviously watch the film from last year, watch their film from this year and try to come up with the best plan."


text:
Another open carry story about Starbucks
Social Situations
Activism Discussion and Planning
> Another open carry story about Starbucks
October 6, 2010, 01:26 AM
If you enjoyed reading about "Another open carry story about Starbucks" here in TheHighRoad.org archive, you'll LOVE our community. Come join
today for the full version!
October 6, 2010, 02:22 AM
"a group of about 35 "open carry" gun advocates -- those who are legally licensed to carry their guns in full view"
uh oh.. I guess I should find out where I can get one of them so called licenses eh?
October 6, 2010, 09:40 AM
What is the focus of discussion on this article? Is it the questioning of Mr. Brewster or is it about the demonstration in response to it? It certainly isn't whether the the reporter got every little fact straight (better they mistakenly said "how" it was legal for the group to OC than that it wasn't).
Russ Jackson
October 6, 2010, 09:58 AM
If people were open carrying at the coffee shop down the street as mentioned I bet the four officers would not have been shot. Why was it brought up in the report? It had nothing to do with this scenerio. I wish Open Carriers would be a little more friendly with the LEO's. It will take time for them as well as unknowing civilians to accept this. Especially when they have no idea it is legal. Trying to get a rise out of a LEO isn't going to help the cause. I know it is your right not to show ID but how it is handled is more important. It just seems like some...not all are looking to get into a pissing match. The last thing a retail wants is a scene with LEO's and Open Carry. I think when you Open Carry you are trying to train others about this option including the Police. While it is new there will be challenges until it is the norm. It will take time be patient...This Is Just My Opinion.
After thinking about it more why not ask the LEO if he would like to see your ID prior to him asking? This would calm the situation and not disrespect the LEO infront of patrons.
Remember when CCW became much easier the local Sheriff Office was hesitant and would ask you fifty questions and now it is an in and out pleasant experience. Be patient and give it time and take The High Road..Russ
October 6, 2010, 10:16 AM
Good point. If you're going to OC with the intent of "educating" the public and LEOs you should understand that being calm and friendly with concerned persons furthers the educational opportunity. If you're not required to show ID, does it spoil your opportunity to educate the public and LEOs on the normality of OC if you insist on not cooperating where not required?
October 6, 2010, 10:38 AM
I wish Open Carriers would be a little more friendly with the LEO's.
I understand where you're coming from on this. I used to feel the same way about Open Carry and firearms activism in general. However, my interaction with Law Enforcement in similar situations to open carry have changed my mind about activism and OC, interacting with the police, etc.
Law Enforcement needs to be met with intelligent and measured activism like this in order for them to review and understand the law and our rights, just like the average person needs their perspective changed regarding firearms in public.
The positive that comes from this is that where Law Enforcement in many areas had a gray area of what they think is the law (many on the road have a notoriously poor grasp of gun rights), but now there is dialogue going on in cop shops and between Chiefs/Captains and DAs about clarifications regarding OC and gun rights in general. There's also conversation between officers after one or two interact with them regarding gun rights.
I've seen this work very well in areas like New Hampshire where members of the Free State Project are interacting from a position of asserting their rights rather than the usual "Yes sir, officer. Anything you say, officer." position that got us where we are now.
It's an adversarial conversation the moment an officer begins interviewing you because they're trained to take control of the situation verbally and psychologically. Not knowing your rights and being able to articulate them in a measured and agreeable way doesn't help local Law Enforcement get any better at handling the encounters that will increase in number as more people OC or CC (where legal) in their jurisdiction.
It's not just the public that need to be made used to the idea that guns are the province of free people. Law Enforcement also needs education on the subject.
I'm happy to help in that regard, as are others. And, I've found I can do it with a smile instead of making it a shouting match or tense negotiation.
The guy in the above story was simply asserting his rights as a free man.
What's so bad about that?
Russ Jackson
October 6, 2010, 11:04 AM
I agree that in this video and recording the person seemed to be ok. However we did not see his body language with the LEO. My comments were more about the presumed agenda with Open Carriers. Not the actual agenda: Which is the right to Open Carry. If I was going to assemble an open carry event or events in a particular city. Prior to this I would stop into the local Police Station and inform them of my intentions. That way they could address the Officers about Open Carry and prepare themselves.
Now that the city in which this event took place I am sure all the Officers have been trained on how to handle this situation. People and Police make the wrong decisions all the time. How these mistakes or lack of knowledge of the Law are handled after the original is really the issue.
Walking around with a Gun on your belt and a Chip on ones shoulder is not the way to proceed. In this video it did not seem like a line in the sand was drawn. In others it seems like the Open Carriers were just looking for a conflict.
I wish we could write a protocol on this issue. Especially since it seems to happen all the time...Russ
October 6, 2010, 11:07 AM
I think it hurts your chances of being seen as a friendly neighborhood guntoter :) if you get snarky with the officer. The area, as pointed out, is a little sensitive about guns. I think it is a much better idea to simply smile and show ID, regardless of whether or not it's legally required.
Why do you carry a gun? Is it so that you can get belligerent with people who may tread on your toes a little bit over your 2A rights? Or is it so you can "problem solve a situation" as the fellows on the Magpul Dynamics video say?
:D I do however completely support the convergence of dozens of lawabiding open-carry citizens on one place. That was just cool to see.
October 6, 2010, 11:39 AM
Why do you carry a gun? Is it so that you can get belligerent with people who may tread on your toes a little bit over your 2A rights?
This was NOT a 2A rights issue.
October 6, 2010, 11:47 AM
I have never understood this...criminals do not open carry so stopping those that open carry to see if they are criminals is nonsensical.
October 6, 2010, 11:51 AM
Walking around with a Gun on your belt and a Chip on ones shoulder is not the way to proceed.
However, even when you're a smiling and nice person, you still have to remember that you're in a conversation with an agent of the state who is allowed to lie to you at any point in their interaction with no repercussions including threat of arrest, jail, etc.
So, if you don't know the law and how it applies, they surely will not preserve your rights at any point. Or they may but cannot be relied upon to provide truthful and open interaction like you may believe they should or will.
Of course, there's nothing wrong with being gentlemanly in an interaction with police, regardless of the individual officer's attitude. That's the course of action I take.
October 6, 2010, 11:58 AM
This was not a demonstration about the 2nd amendment. It was a show of support for a person who had their 4th amendment rights violated. Waiting for the lock in 5, 4, 3, 2......
Art Eatman
October 6, 2010, 12:13 PM
If you enjoyed reading about "Another open carry story about Starbucks" here in TheHighRoad.org archive, you'll LOVE our community. Come join
today for the full version!
vBulletin® v3.8.6, Copyright ©2000-2016, Jelsoft Enterprises Ltd.


text:
Adults help to develop success in youths
Three dozen boys and girls received Youth Asset Builder awards during a luncheon celebrating youths Wednesday. Considering the developmental assets that help young people grow to be healthy, caring and responsible adults, we also want to give a tip of the cap to the parents, teachers, coaches and other mentors who are helping these 36 youngsters become assets to their community.
Indeed, some of these folks also were honored Wednesday - Brandon Aydt, Kim Bonnell, Paul Jones, Nikki Reineke, Sandy Reinhart, Jean Snyder and Donald Swartz. Hats off to them and the unsung others who assist in the development of our youth.
For a list of the 40 developmental assets identified as building blocks by the Search Institute, visit www.search-institute.org/content/40-developmental-assets-adolescents-ages-12-18


text:
1920's slang word, meaning excellent.
person 1: that movie was so darb!
person 2: i know, it was so excellent!
person 2: i know, it was so excellent!
po mitchy Април 14, 2005
Trending Now
Can you define these popular missing words?
Top Definition
To be easy.
That test was pretty darb. Almost as darb as Ian Smith!
po Awesomesauce94 Јануар 24, 2011
Cigarettes: usage from early 20th century.
He likes his nails, but I prefer my darling darbs.
po Robert Lee Август 24, 2004
1920s slang for something or someone regarded as excellent or remarkable.
I'm gonna level with you: thanks for getting me that swell job down at that speakeasy. You're the darb!
po 1920s Electro-Mod Фабруар 23, 2011
1920's, A person with ready money, who can always be relied upon to pay the check.
Don't worry about the check, Myrtle, Al is darbs.
po Bob Proczko Октобар 16, 2006
slang term for a cigarette. Preferred vernacular of bogan types.
"tick us a darb yah c*nt"
po out of darbs Март 2, 2008
A polite word to replace the word fuck in sentances
Why don't you just darb off!
po kwbs1984 Септембар 10, 2011


text:
Date: 02/02/06
Author: Jeff Steidl
This document and accompanying demo application show how to configure Oracle's JMS Connector implementation for OEMS JMS (Database). They also demonstrate how to develop, assemble and configure a JMS application.
The demo application simulates the playing of a simple numbers game.
The game rules are as follows: There are 3 players and one dealer. During phase one, the dealer provides each participant (including the dealer) a random number from 1 to 100. During phase two each participant may either keep their number from phase one, or get a new random number. Phase two is performed one participant at a time, and a participant is always aware of the other participant's current values. The goal of the game is have the highest number at the end of phase two.
In the demo application, an MDB is the dealer. Three app-client instances are the players. The players send requests (join game, draw, pass) to the MDB via a JMS queue. The MDB sends global game state information (join request accepted/rejected, random number values, player turn notification) to the app-clients via a JMS topic.
This demo requires that the following sofware components are installed and configured correctly:
This document uses ellipses inside of an xml block:
<some-element> ... </some-element>
Ellipses may also be used to indicate the context of an XML block:
<some-element> ... <some-sub-element> SubElementSetting </some-sub-element>
In this case <some-sub-element> is being discussed, and <some_element> is only shown to indicate the context of <some-sub-element> .
The following are used to represent directories:
Developing a J2EE application which uses JMS and a custom JMS Connector configuration involves the following:
This document will focus on those aspects of the above steps that are necessary for creating a J2EE application which makes use of Oracle's JMS Connector with OEMS JMS (Database).
The Application Component Provider develops application components such as MDBs and app-clients. For application components using JMS, the following tasks are typically performed as part of that process:
This section concludes with some key points concerning the development of application components.
Writing code that sends and receives JMS messages requires using the following types of objects:
The remainder of this section shows how the object types and activities in the above table map to the MyChannel class (see MyChannel.java ).
As per the "Use After Demo Initialization" column in the above table, the Connection, Session, MessageProducer and MessageConsumer objects are the only ones used after initialization is done, so only those are declared as class variables in MyChannel:
private Connection connection; private Session session; private MessageProducer producer; private MessageConsumer consumer;
The remaining objects are local variables within the MyChannel constructor where initialization is performed.
Initialization involves the look-up and creation of objects as per the "Use During Demo Initialization" column in the above table:
public MyChannel(String connectionFactoryName, String destinationName) throws Exception { Context ctx = new InitialContext(); // Get the destination. Destination destination = (Destination) ctx.lookup(destinationName); // Get the connection factory. ConnectionFactory cf = (ConnectionFactory) ctx.lookup(connectionFactoryName); // Use the connection factory to create a connection. connection = cf.createConnection(); // Start the connection. connection.start(); // Use the connection to create a session. session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); // Use the session and destination to create a message producer and a message consumer. producer = session.createProducer(destination); consumer = session.createConsumer(destination); }
Note that connectionFactoryName and destinationName are the JNDI locations of references to the connection factory and destination, respectively. We will get back to those later.
The above initialization code is just a simple example. A small sample of other activities that may be performed by real initialization code is:
Also, real code may not limit the above activities to "initialization" code. For example:
As per the "Use After Demo Initialization" column in the above table, the Session object ( session) is used to create messages and the MessageProducer object ( producer) is used to send messages:
public void send(Serializable obj) throws JMSException { // Use the session to create a new message. ObjectMessage msg = session.createObjectMessage(obj); // Use the message producer to send the message. producer.send(msg); }
The above message production code is just a simple example which creates and sends an ObjectMessage (where the message payload can be any Serializable object). Other activities that may be performed by real message production code include:
As per the "Use After Demo Initialization" column in the above table, the MessageConsumer object ( consumer) is used to receive messages:
public Serializable receive() throws JMSException { // Use the message consumer to receive a message. ObjectMessage msg = (ObjectMessage) consumer.receive(); return msg.getObject(); }
The above message consumption code is just a simple example which waits forever for a message and then (assuming it's an ObjectMessage) extracts and returns the payload. Other activities that may be performed by real message consumption code include:
As per the "Use After Demo Initialization" column in the above table, the Connection object ( connection) is used to close everything:
public void close() throws JMSException { // Close the connection (and all of its sessions, producers and consumers). connection.close(); }
The above resource release code is just a simple example which closes everything (connection, sessions, producers, consumers) at once. Real resource release code may:
In the previous section, the matter of the JNDI locations of the connection factory and destination was left open. The problem is that the Application Component Provider may not have any idea what the actual JNDI locations will be when the application is finally deployed. The solution is for the Application Component Provider to just make up a name, declare that name in a deployment descriptor, and leave the task of picking an actual JNDI location to the Deployer (who may also get some assistance from the Application Assembler). Each application component only sees its own logical names, so the Application Component Provider for one component need not be concerned about conflicts with the names used in other components (which may have been created by one or more independent Application Component Providers).
Note: While any name will work, the J2EE spec recommends that these names start with "jms/".
Let's say that the Application Component Provider who wrote the app-client wanted to declare the logical name "jms/PlayerConnectionFactory" to represent (reference) a connection factory. This can be done by inserting the following into application-client.xml (as a sub-element of the <application-client> element):
<resource-ref> <res-ref-name>jms/PlayerConnectionFactory</res-ref-name> ... </resource-ref>
Note: "resource-ref" is short for "resource manager connection factory reference". So this type of logical name is, more specifically, a resource manager connection factory reference name.
We have told the Deployer we need a connection factory, but not what type of connection factory. If the application component needs a QueueConnectionFactory and the Deployer gives it a TopicConnectionFactory the application isn't likely to work. To tell the Deployer that the application component can use any type of connection factory that implements the javax.jms.ConnectionFactory interface, add the <res-type> element:
<resource-ref> <res-ref-name>jms/PlayerConnectionFactory</res-ref-name> <res-type>javax.jms.ConnectionFactory</res-type> ... </resource-ref>
Note: There is some subtlety going on with the element names. The first subelement name ( <res-ref-name> ) includes "ref" because it is the name of the reference, not the name of an actual resource manager connection factory. The second subelement name ( <res-type> ) does not include "ref" because it is the type (interface) required to be implemented by an actual resource manager connection factory, not the type of the reference. The main element ( <resource-ref> ) includes "ref" because it is declaring a reference, not an actual resource manager connection factory. This naming convention is used for the remaining elements in this section, as well as for the <message-destination-ref> -related elements discussed in the next section.
The last missing piece of information is who is responsible for "signing on to the resource manager". That is, who provides the username and password to the JMS resource provider when a Connection is created using this connection factory. Again, the Deployer needs to know -- if the application doesn't provide the username/password (and the resource provider requires it), then the Deployer needs to know to provide this information. (See "Oracle Containers for J2EE: Resource Adapter Administrator's Guide" for information on container-managed sign-on and the oc4j-ra.xml file.)
To tell the Deployer that the application component will not provide the username/password (and that the "Container" must be configured to do so), add:
To tell the Deployer that the application component will provide the username/password, add:
Currently OC4J does not support container-managed sign-on in the app-client container (it does support it in the Web and EJB containers), so we must use the following for the app-client:
<resource-ref> <res-ref-name>jms/PlayerConnectionFactory</res-ref-name> <res-type>javax.jms.ConnectionFactory</res-type> <res-auth>Application</res-auth> </resource-ref>
The <resource-ref> element also has a <res-sharing-scope> sub-element which defaults to "Shareable". It should generally be left set that way (which can be accomplished by just omitting the sub-element). If the application component may modify connections created using this connection factory in a way which makes the connections unusable by other application components, then <res-sharing-scope> should be set to "Unshareable" (and as per J2EE4.6, the application component is not portable).
The last thing that needs to be done to make the above <resource-ref> example valid is to check that it is in the correct sequence with respect to the other sub-elements of the <application-client> element. This ordering requirement is rooted in the app-client schema file in the definition of the type corresponding to <application-client> . As per that document, the correct ordering for the sub-elements of <application-client> used by this demo is:
Moving on to the MDB, let's say that the Application Component Provider who wrote the MDB wanted to declare the logical name "jms/DealerConnectionFactory" to represent (reference) a connection factory that implements the javax.jms.ConnectionFactory interface and has container-managed sign on. The syntax works the same as for the app-client case:
<resource-ref> <res-ref-name>jms/DealerConnectionFactory</res-ref-name> <res-type>javax.jms.ConnectionFactory</res-type> <res-auth>Container</res-auth> </resource-ref>
For MDBs the <resource-ref> element must be placed in the ejb-jar.xml file under the MDB's <message-driven> element. Again there is an ordering requirement, this time rooted in the EJB schema file. As per that document, the correct ordering for the sub-elements of <message-driven> used by this demo is:
Let's say that the Application Component Provider who wrote the app-client wanted to declare the logical name "jms/PlayerCommandDestination" to represent (reference) a destination. This can be done by inserting the following into application-client.xml (as a sub-element of the <application-client> element):
<message-destination-ref> <message-destination-ref-name>jms/PlayerCommandDestination</message-destination-ref-name> ... </message-destination-ref>
Note: "message-destination-ref" is short for "message destination reference". So this type of logical name is, more specifically, a message destination reference name.
As was the case for declaring logical names for connection factories, the Deployer needs more than just a name to go on. If the application component expects point-to-point semantics (a queue) and the Deployer gives it pub/sub semantics (a topic) the application isn't likely to work. To tell the Deployer (and Application Assembler who also plays a role in configuring destinations) that the application component expects the destination to have point-to-point semantics, add:
To tell the Deployer (and Application Assembler) that the application component expects the destination to have pub/sub semantics, add:
One more piece of information is still required, and that is how does the application component use the destination? Does it consume messages from the destination, produce messages to the destination, or both? To tell the Deployer (and Application Assembler) that the application component consumes messages from the destination, add:
To tell the Deployer (and Application Assembler) that the application component produces messages to the destination, add:
To tell the Deployer (and Application Assembler) that the application component both consumes messages from and produces message to the destination, add:
If the application component wants to send messages to a queue, the finished <message-destination-ref> (as far as the Application Component Provider is concerned) is:
<message-destination-ref> <message-destination-ref-name>jms/PlayerCommandDestination</message-destination-ref-name> <message-destination-type>javax.jms.Queue</message-destination-type> <message-destination-usage>Produces</message-destination-usage> </message-destination-ref>
The Application Component Provider creating the app-client would also like to declare a destination named "jms/PlayerResponseDestination" with pub/sub semantics from which the app-client can receive messages:
<message-destination-ref> <message-destination-ref-name>jms/PlayerResponseDestination</message-destination-ref-name> <message-destination-type>javax.jms.Topic</message-destination-type> <message-destination-usage>Consumes</message-destination-usage> </message-destination-ref>
The last thing that needs to be done to make the above <message-destination-ref> example valid is to check that it is in the correct sequence with respect to the other sub-elements of the <application-client> element.
Moving on to the MDB, let's say that the Application Component Provider who wrote the MDB wanted to declare the logical name "jms/ToPlayerDest" to represent (reference) a destination with pub/sub semantics to which the MDB will send messages. The syntax works the same as for the app-client case:
<message-destination-ref> <message-destination-ref-name>jms/ToPlayerDest</message-destination-ref-name> <message-destination-type>javax.jms.Topic</message-destination-type> <message-destination-usage>Produces</message-destination-usage> </message-destination-ref>
For MDBs the <message-destination-ref> element must be placed in the ejb-jar.xml file under the MDB's <message-driven> element. Again the correct sequence of elements must be used.
After a logical name is declared, it can be used by the application component code to reference JMS resources. Logical names (references declared with <resource-ref> and <message-destination-ref> elements) are types of environment entries, and all environment entries are placed in the "java:comp/env/" JNDI subcontext. So in order for the app-client to use the logical names:
In the app-client code for this demo ( Player.java ), the above JNDI locations are assigned to strings:
String factoryName = "java:comp/env/jms/PlayerConnectionFactory"; String commandDestName = "java:comp/env/jms/PlayerCommandDestination"; String responseDestName = "java:comp/env/jms/PlayerResponseDestination";MyChannel constructor
MyChannel command = new MyChannel(factoryName, commandDestName); MyChannel response = new MyChannel(factoryName, responseDestName);MyChannel constructor
(Note that the lookups will not actually work until some more configuration is performed. This is because the logical names have only been declared by the Application Component Provider, and do not yet reference anything. The Deployer will map those logical names such that they reference actual connection factories and destinations. This additional configuration is discussed in the Configuring the Application for Deployment section.)
Likewise, the logical names declared in ejb-jar.xml:
chan = new MyChannel("java:comp/env/jms/DealerConnectionFactory", "java:comp/env/jms/ToPlayerDest");
The previous three tasks do not apply when using an MDB to receive messages. This is because for MDB inbound messaging the EJB container is responsible for performing JNDI lookups, creating connections and sessions, and receiving messages. However, the MDB provider must create and declare an MDB class. The MDB class for this demo can be found in Dealer.java .
The MDB class must implement javax.ejb.MessageDrivenBean and javax.jms.MessageListener:
public class Dealer implements MessageDrivenBean, MessageListener {
MDBs are required to provide a no-argument constructor:
public Dealer() {}
Implementing MessageDrivenBean means providing a setMessageDrivenContext method:
private MessageDrivenContext m_ctx = null; public void setMessageDrivenContext(MessageDrivenContext ctx) { m_ctx = ctx; }
The MessageDrivenContext ( m_ctx) may be used later by the MDB. For example, it may be used to roll-back a global transaction:
MDBs are required to provide an ejbCreate method. This method typically allocates resources needed by the MDB. Although the MDB class does not allocate resources for receiving messages, it may (as in this example) allocate resources for sending messages:
MyChannel chan; public void ejbCreate() { try { chan = new MyChannel("java:comp/env/jms/DealerConnectionFactory", "java:comp/env/jms/ToPlayerDest"); } catch (Throwable ex) { ex.printStackTrace(); } }
Implementing MessageListener means providing an onMessage method:
public void onMessage(Message msg) { // code to process received messages goes here... }
Implementing MessageDrivenBean also means providing an ejbRemove method. This method typically deallocates resources allocated by the ejbCreate method:
public void ejbRemove() { try { chan.close(); } catch (Throwable ex) { ex.printStackTrace(); } }
In order for the class created in the previous section to be used as an MDB, it must be declared to be an MDB in the deployment descriptors. This can be done by inserting the following into ejb-jar.xml (as a sub-element of the <enterprise-beans> element):
<message-driven> <ejb-name>DealerEjbName</ejb-name> <ejb-class>Dealer</ejb-class> ... </message-driven>
The <ejb-name> is whatever the Application Component Provider would like to name the MDB. This name will be used later by the Application Assembler and Deployer in order to reference this MDB. The <ejb-class> must be the MDB's fully qualified Java class name.
One more piece of information is still required, and that is who is responsible for managing transactions? If the MDB manages its own transactions, add the following to ejb-jar.xml (as a sub-element of the <message-driven> element):
If the MDB expects the container to manage transactions, add:
If for some reason the Application Component Provider feels the MDB should only be used with queues, or only with topics, then the <message-destination-type> element may be used. (This element is an optional subelement of <message-driven> .) If the MDB should only be used with queues, use:
If the MDB should only be used with topics, use:
In many cases the MDB will not care whether the source destination is a queue or a topic, and the <message-destination-type> element may then be omitted.
Finally, when placing the above elements in the ejb-jar.xml file, the correct sequence must be used.
Some key points to note about developing application components:
The Application Assembler takes application components such as MDBs and app-clients and ties them together. For applications using JMS, the following tasks are typically performed as part of that process:
In a typical JMS application, it is common for one application component to send messages to another application component. In order for this to work, JMS requires that the first application component send messages to a JMS Destination, and that the second application compoment receive messages from that same JMS Destination. However, as was seen in the "Declare Logical Names for JMS Resources" task, the Application Component Providers may have chosen any logical names they like, so there is not necessarily any correspondence between the message destination reference names in one application component and another. For example, the application-client (Player) in this demo has a message destination reference named "jms/PlayerResponseDestination" (see application-client.xml), and the MDB (Dealer) in this demo has a message destination reference named "jms/ToPlayerDest" (see ejb-jar.xml). It is the Application Assembler's job to know that messages sent by the the MDB (to "jms/ToPlayerDest") are supposed to be received by the application-client (from "jms/PlayerResponseDestination"). More importantly, the Application Assembler records this knowledge in the deployment descriptors so the Deployer will know to map both of those message destination references to the same JMS Destination.
This section covers the first step of that process - declaring message destinations. The next section will show how to link the message destination references (and MDBs) created by the Application Component Provider to the message destinations created by the Application Assembler. The mapping from logical destinations (message destinations) to physical destinations by the Deployer is covered in the Map Logical Destinations to RA Destinations section.
First, if the ejb-jar.xml does not contain an <assembly-descriptor> element, add one:
<assembly-descriptor> ... </assembly-descriptor>
Note: There is no real reason for selecting the ejb-jar.xml file instead of the application-client.xml file (which can also support the elements described in this section). Declaring some message destinations in one file and others in another file is also allowed.
Message destinations are declared using a <message-destination> element, which is a subelement of <assembly-descriptor> . Since the messages in the above example go from the Dealer to the Player, let's create a message destination named "DealerToPlayerMessages":
<message-destination> <message-destination-name>DealerToPlayerMessages</message-destination-name> </message-destination>
Note: The message destination name is another type of logical name since message destinations are logical destinations which need to be mapped to physical destinations by the Deployer.
The application-client in this demo also has a message destination reference named "jms/PlayerCommandDestination" (see application-client.xml) which is used to send commands from the player to the dealer. There is no message destination reference for this set of messages in ejb-jar.xml because the MDB class receives these messages without ever looking up a destination (so no logical name is needed). Let's create a message destination named "PlayerToDealerMessages" for this:
<message-destination> <message-destination-name>PlayerToDealerMessages</message-destination-name> </message-destination>
The Application Assembler needs to link the message destination references created by the Application Component Providers to the message destinations created in the previous section. This is done by adding <message-destination-link> elements which name the appropriate message destination. For example, in ejb-jar.xml the message destination reference named "jms/ToPlayerDest" was previously declared:
<message-destination-ref> <message-destination-ref-name>jms/ToPlayerDest</message-destination-ref-name> <message-destination-type>javax.jms.Topic</message-destination-type> <message-destination-usage>Produces</message-destination-usage> </message-destination-ref>
That message destination reference can be linked to the message destination named "DealerToPlayerMessages" by adding a <message-destination-link> element:
<message-destination-ref> <message-destination-ref-name>jms/ToPlayerDest</message-destination-ref-name> <message-destination-type>javax.jms.Topic</message-destination-type> <message-destination-usage>Produces</message-destination-usage> <message-destination-link>DealerToPlayerMessages</message-destination-link> </message-destination-ref>
In application-client.xml we would like to link the message destination reference named "jms/PlayerResponseDestination" to that same message destination. This can be done exactly the same way:
<message-destination-ref> <message-destination-ref-name>jms/PlayerResponseDestination</message-destination-ref-name> <message-destination-type>javax.jms.Topic</message-destination-type> <message-destination-usage>Consumes</message-destination-usage> <message-destination-link>DealerToPlayerMessages</message-destination-link> </message-destination-ref>
In a really large application there may be multiple levels of assembly leading to name conflicts (where two different message destinations in two different deployment files have the same name). These conflicts can be resolved by qualifying the message destination name with the name of the deployment file where the message destination is declared, like so:
<message-destination-ref> <message-destination-ref-name>jms/PlayerResponseDestination</message-destination-ref-name> <message-destination-type>javax.jms.Topic</message-destination-type> <message-destination-usage>Consumes</message-destination-usage> <message-destination-link>dealer-ejb.jar#DealerToPlayerMessages</message-destination-link> </message-destination-ref>
The last unlinked message destination reference (named "jms/PlayerCommandDestination") is also in application-client.xml and should be linked to the message destination named "PlayerToDealerMessages":
<message-destination-ref> <message-destination-ref-name>jms/PlayerCommandDestination</message-destination-ref-name> <message-destination-type>javax.jms.Queue</message-destination-type> <message-destination-usage>Produces</message-destination-usage> <message-destination-link>PlayerToDealerMessages</message-destination-link> </message-destination-ref>
The very last message destination link that is needed by this demo is for the MDB inbound messaging. There is no message destination reference for MDB inbound messaging, so the <message-destination-link> element is a direct subelement of the <message-driven> element in ejb-jar.xml:
<message-driven> ... <message-destination-link>PlayerToDealerMessages</message-destination-link>
The <message-destination-link> element must be placed in the correct sequence with respect to the other subelements of <message-driven> .
If the MDB's transaction type has been set to "Container", then a transaction attribute should be defined for the MDB's onMessage method.
Although this is listed as an Application Assembler task, it may be performed by the Application Component Provider or by the Deployer.
To define the transaction attribute for the onMessage method of the MDB named "DealerEjbName", add the following to ejb-jar.xml as a subelement of <assembly-descriptor> :
<container-transaction> <method> <ejb-name>DealerEjbName</ejb-name> <method-name>onMessage</method-name> </method> <trans-attribute>Required</trans-attribute> </container-transaction>
(There are some other transaction options defined by the EJB spec. They are not covered in this demo because if you need to use those options with your MDBs, you're probably doing something wrong.)
There is an ordering requirement rooted in the EJB schema file. As per that document, the correct ordering for the sub-elements of <assembly-descriptor> used by this demo is:
The application .ear file may contain a number of jar files (whatever their actual file-extension may be). In order for the application server to know what it should do with each of the jar files (if anything), each module (each jar file containing one or more application components) must be listed in the application.xml file using a <module> element.
Jar files containing EJBs (like the MDB included in this demo) should use the <ejb> module type:
<module> <ejb>dealer-ejb.jar</ejb> </module>
Jar files containing an application-client should use the <java> module type:
<module> <java>player-client.jar</java> </module>
Jar files containing a resource adapter (such as the JMS Connector) should use the <connector> module type:
<module> <connector>OEMSJMSDRADeploy.rar</connector> </module>
Note that one of this demo's jar files, common.jar, is not listed as a module. This is because it does not contain any application components, just some classes that are used by both the application-client and the MDB. So instead of being listed in the application.xml file, common.jar is listed in the Class-Path in the MANIFEST.MF files for player-client.jar and dealer-ejb.jar.
The person responsible for administering the resource provider may have to determine the number and type of RP destinations required by the application by inspecting the application's deployment descriptors. The Application Assembler determined that two destinations are required, and recorded that information into the application component deployment descriptors by declaring exactly two <message-destination> s. The <message-destination-link> s left by the Application Assembler can be followed back to the <message-destination-ref> elements created by the Application Component Provider(s), and their <message-destination-type> subelements show that one of those destinations should be a queue and one should be a topic.
Alternatively, someone else (e.g., the deployer, the person responsible for configuring the JMS Connector, the application assembler, etc) may provide information about the required RP destinations via some other mechanism (not covered by the J2EE standard).
The RP must provide the following destinations:
This is because all of the JMS Connector and application configuration described after this point has already been performed for you using those RP destination names. However, you can use whatever RP destination names you like as long as you perform the configuration processes described after this point using the names you have selected.
* Note: These JNDI names are the JNDI locations of the RP destinations within the resource provider's JNDI context. Access to that JNDI context is acheived by declaring a resource provider reference.
To create the above destinations, start sqlplus:
sqlplus sys as sysdba
Enter the password for the system dba account when prompted. Then execute the oemsjmsd.sql script:
@ oemsjmsd.sql
Note that if oemsjmsd.sql is not in the current directory, the full path to the file should be given in the above step.
The oemsjmsd.sql script creates a table named QTab, and then uses that table to create (and start) a queue named MY_QUEUE (which OEMS JMS (Database) calls Queues/MY_QUEUE for JNDI purposes):
DBMS_AQADM.CREATE_QUEUE_TABLE( Queue_table => 'QTab', Queue_payload_type => 'SYS.AQ$_JMS_MESSAGE', sort_list => 'PRIORITY,ENQ_TIME', multiple_consumers => false, compatible => '8.1.5'); DBMS_AQADM.CREATE_QUEUE( Queue_name => 'MY_QUEUE', Queue_table => 'QTab'); DBMS_AQADM.START_QUEUE( queue_name => 'MY_QUEUE');
The oemsjmsd.sql script also creates a table named TTab, and then uses that table to create (and start) a topic named MY_TOPIC (which OEMS JMS (Database) calls Topics/MY_TOPIC for JNDI purposes):
DBMS_AQADM.CREATE_QUEUE_TABLE( Queue_table => 'TTab', Queue_payload_type => 'SYS.AQ$_JMS_MESSAGE', sort_list => 'PRIORITY,ENQ_TIME', multiple_consumers => true, compatible => '8.1.5'); DBMS_AQADM.CREATE_QUEUE( Queue_name => 'MY_TOPIC', Queue_table => 'TTab'); DBMS_AQADM.START_QUEUE( queue_name => 'MY_TOPIC');
Before an application (or JMS Connector) running in OC4J can access a resource provider, a resource provider reference must be declared with the <resource_provider> element. The resource provider reference holds miscellaneous data (e.g., the class name described below) that OC4J uses to interact with the resource provider. The resource provider reference also provides a JNDI subcontext through which resource provider resources can be accessed. The resource provider reference (and said JNDI access) can be made local to the application (by placing it in orion-application.xml), or available to all applications (by placing it in %ORACLE_HOME%/j2ee/home/config/application.xml). This demo uses a local resource provider reference.
The two pieces of information you must provide whenever declaring a resource provider reference are the name you wish to use for the resource provider reference and the Java class which implements the resource provider interface. For OEMS JMS (Database) the class is oracle.jms.OjmsContext. To declare a resource provider reference named OEMSJMSDReference, use:
<resource-provider class="oracle.jms.OjmsContext" name="OEMSJMSDReference"> ... </resource-provider>
The resource provider reference maps the resource provider's JNDI context (which contains RP connection factories and RP destinations) to a JNDI subcontext accessible by the application and, more importantly, the JMS Connector. That JNDI subcontext is java:comp/resource/ name where " name" is the name of the resource provider reference. For example, if the resource provider reference is named OEMSJMSDReference, and the JNDI name of a resource provider queue is Queues/MY_QUEUE, then that RP queue is accessible to the application and JMS Connector at JNDI location java:comp/resource/OEMSJMSDReference/Queues/MY_QUEUE. The reason it is more important for the JMS Connector to be able to access RP resources than for the application to be able to do so is that, when using the JMS Connector, the application need not (and in general should not) directly look up or use any RP resources.
OEMS JMS (Database) requires Oracle Database Streams Advanced Queuing (AQ).
First create a local data-source (see data-sources.xml file):
<managed-data-source login-timeout='-1' connection-pool-name='MyChannelDemoDataSourcePool' jndi-name='jdbc/xa/MyChannelDemoDataSource' name='oemsjmsdthin' tx-level='global' manage-local-transactions='false'/> <connection-pool name='MyChannelDemoDataSourcePool'> <proxy-interface sql-object='Connection' interface='oracle.jdbc.internal.OracleConnection'/> <proxy-interface sql-object='Statement' interface='oracle.jdbc.OracleStatement'/> <proxy-interface sql-object='CallableStatement' interface='oracle.jdbc.OracleCallableStatement'/> <proxy-interface sql-object='PreparedStatement' interface='oracle.jdbc.OraclePreparedStatement'/> <proxy-interface sql-object='ResultSet' interface='oracle.jdbc.OracleResultSet'/> <connection-factory factory-class='oracle.jdbc.pool.OracleDataSource' user='MyChannelDemoUser' password='MyChannelDemoPassword' url='jdbc:oracle:thin:@localhost:5521:db'> </connection-factory> </connection-pool>
Note: You will need to replace "localhost" with the database host name, "5521" with the database port, and "db" with the database SID.
Then tell OC4J where the data-sources.xml file has been placed by adding a <data-sources> element to orion-application.xml:
<data-sources path="data-sources.xml"/>
Note: The data-sources path is relative to the orion-application.xml file.
Finally, set the datasource for the resource provider reference by adding a <property> subelement to the previously created <resource-provider> element:
<resource-provider class="oracle.jms.OjmsContext" name="OEMSJMSDReference"> <property name="datasource" value="jdbc/xa/MyChannelDemoDataSource"></property> </resource-provider>
Configuring Oracle's JMS Connector typically includes the following tasks:
Oracle's JMS Connector is a Resource Adapter (RA). The RA configuration files included with this demo are provided "ready to run". This section is included anyways, to provide information that will be useful when you want to perform your own JMS Connector configuration for real applications. (For brevity, this document refers to JMS Connector connection factories and destiations as "RA connection factories" and "RA destinations".)
The JMS Connector acts as a "value added" wrapper for the resource provider:
The JMS Connector also acts as a compatability layer for the resource provider, allowing things like container-managed transactions and MDBs. Specific instances of the JMS Connector based on Oracle's JMS Connector implementation can be configured for a number of different resource providers, including OEMS JMS (Database).
The ra.xml file contains a lot of content that does not need to (and should not) be changed when using Oracle's JMS Connector. (The reason for this is that the ra.xml file is based on the J2EE Connector Architecture 1.5 schema file, which is a generic schema intended to work with many types of resource adapters, including non-JMS resource adapters, and other JMS resource adapter implementations.)
The ra.xml file included with this demo can be quickly modified to work with any of the supported resource providers by making the following changes:
The ra.xml file included with this demo contains inline documentation which describes the file's contents.
Similar to how a resource provider reference was needed to interact with the resource provider, a JMS Connector instance is needed to interact with the JMS Connector. A JMS Connector instance is created with the <connector> element (a subelement of the <oc4j-connectors> element in the oc4j-connectors.xml file).
The two pieces of information you must provide whenever creating a JMS Connector instance are:
<connector name="OEMSJMSDRAInstanceName" path="OEMSJMSDRADeploy.rar"> ... </connector>
The JMS Connector instance can be made local to the application by:
The <connectors> element used to point to the oc4j-connectors.xml file is a subelement of the <orion-application> element and should look something like this:
<connectors path="oc4j-connectors.xml"/>
Many of the same considerations for RP connection factores also apply to RA connection factories.
RA resources (RA connection factories and RA destinations) are either placed at the root of JNDI or within some JNDI subcontext. Any number of JNDI subcontexts may be used, where one or more RA resources are placed in each JNDI subcontext. When the RA is deployed locally (i.e., no other applications will be able to see the RA's resources in their JNDI context), the JNDI organization scheme is not critical. When an RA is deployed independently and RA resources are made visible to all applications, more consideration needs to be given to this issue. Like using subdirectories on a hard-drive to keep things organized, you should use subcontexts to keep JNDI organized. One scheme, for example, would be to use a JNDI subcontext like ApplicationName/JMSRA where ApplicationName is the name of the application which will be using the RA resources. If the RA connection factories are generic and can be used by multiple applications, then they could be placed somewhere like JMSRA (and leave the RA destinations created for specific applications in application-specific JNDI subcontexts). If two applications communicate via one or more RA destinations, then those destinations could be placed in their own JNDI subcontext.
All of the RA resources are in the JNDI subcontext OEMSJMSDRASubcontext. Since the RA is deployed locally, this is a sufficient organization strategy.
The RA must provide the following connection factories:
This is because all of the RA and application configuration described after this point (including creating the above RA connection factories) has already been performed for you using those JNDI locations. However, you can use whatever (otherwise unused) JNDI locations you like as long as you perform the configuration processes described after this point using the JNDI locations you have selected.
The demo application only uses the two RA connection factories listed above. However, in order to provide examples of all 6 types of JMS connection factories the following RA connection factories are also created in oc4j-ra.xml:
To create an RA connection factory at JNDI location OEMSJMSDRASubcontext/MyCF, insert the following into oc4j-ra.xml (as a sub-element of the <oc4j-connector-factories> element):
<connector-factory location="OEMSJMSDRASubcontext/MyCF" ... > ... </connector-factory>
To indicate what type of RA connection factory should be created, add a <connectionfactory-interface> element:
<connector-factory location="OEMSJMSDRASubcontext/MyCF" ... > ... <connectionfactory-interface>javax.jms.ConnectionFactory</connectionfactory-interface> </connector-factory>
The value of the <connectionfactory-interface> element must match one of the <connectionfactory-interface> values defined in the ra.xml file.
As described previously, the RA connection factory makes use of the RP connection factory. Before it can do that, you must tell the RA connection factory where it can find an appropriate RP connection factory. To tell this RA connection factory to use the RP connection factory located in the resource provider's JNDI context at ConnectionFactories/CF, add a <config-property> element which sets the "jndiLocation" property:
<connector-factory location="OEMSJMSDRASubcontext/MyCF" ... > <config-property name="jndiLocation" value="ConnectionFactories/CF"/> <connectionfactory-interface>javax.jms.ConnectionFactory</connectionfactory-interface> </connector-factory>
Note: An "appropriate" RP connection factory is one that is compatible with the <connectionfactory-interface> . In the case of oracle.j2ee.ra.jms.generic.XABackedConnectionFactory the RP connection factory must implement javax.jms.XAConnectionFactory. In all other cases the RP connection factory must implement the interface defined by <connectionfactory-interface> .
If the "jndiLocation" property is not set here (i.e., the <config-property> element is ommitted), then the default "jndiLocation" for this <connectionfactory-interface> is used, as set in ra.xml.
Finally, indicate the RA instance with which this RA connection factory will be used. (This must match the "name" attribute of the <connector> element which was set previously.)
<connector-factory location="OEMSJMSDRASubcontext/MyCF" connector-name="OEMSJMSDRAInstanceName"> <config-property name="jndiLocation" value="ConnectionFactories/CF"/> <connectionfactory-interface>javax.jms.ConnectionFactory</connectionfactory-interface> </connector-factory>
The above <connector-factory> settings are (just about) the bare minimum required by the schema file. Real applications may include a number of other subelements pertaining to features such as container-managed sign-on and connection pooling. See "Oracle Containers for J2EE: Resource Adapter Administrator's Guide" for complete coverage of <connector-factory> settings.
The person responsible for configuring the JMS Connector will need to determine or be told the number and type of RA destinations required. Some level of cooperation between the person responsible for configuring the JMS Connector and the person responsible for administering the resource provider may be required in order to know which RP destiations should be wrapped by which RA destinations.
Alternatively, automatic destination wrapping may be used. This allows any number of RP destinations to be accessed via as few as two RA destinations (one for queues and one for topics). (Automatic destination wrapping is not covered in this text and is [by default] not used by the demo, but it is described in the demo files Player.java and oc4j-connectors.xml -- just open each file and search for "automatic destination wrapping".)
The RA must provide the following destinations:
This is because all of the JMS Connector and application configuration described after this point (including creating the above RA destinations) has already been performed for you using those JNDI locations. However, you can use whatever JNDI locations you like as long as you perform the configuration processes described after this point using the JNDI locations you have selected.
To create an RA destination at JNDI location OEMSJMSDRASubcontext/MyQ, insert the following into oc4j-connectors.xml (as a sub-element of the <connector> element created previously):
<adminobject-config location="OEMSJMSDRASubcontext/MyQ"> ... </adminobject-config>
To indicate what type of RA destination should be created, add an <adminobject-class> element:
<adminobject-config location="OEMSJMSDRASubcontext/MyQ"> <adminobject-class>oracle.j2ee.ra.jms.generic.AdminObjectQueueImpl</adminobject-class> ... </adminobject-config>
The value of the <adminobject-class> element must be either oracle.j2ee.ra.jms.generic.AdminObjectQueueImpl (to create a queue) or oracle.j2ee.ra.jms.generic.AdminObjectTopicImpl (to create a topic).
Just as RA connection factories act as wrappers for RP connection factories, RA destinations act as wrappers for RP destinations. In order for the RA to look up the RP destination, the RA needs the name of the resource provider reference and the RP's JNDI name for the RP destination (the JNDI location of the RP destination within the resource provider's JNDI context):
<adminobject-config location="OEMSJMSDRASubcontext/MyQ"> <adminobject-class>oracle.j2ee.ra.jms.generic.AdminObjectQueueImpl</adminobject-class> <config-property name="jndiName" value="Queues/MY_QUEUE"/> <config-property name="resourceProviderName" value="OEMSJMSDReference"/> </adminobject-config>
The Deployer takes J2EE application and adds configuration information which may be specific to an app-server provider as well as to a specific deployment. For applications using JMS, the following tasks are typically performed as part of that process:
As covered previously, the app-client component declares a logical name for a connection factory in the application-client.xml file:
<resource-ref> <res-ref-name>jms/PlayerConnectionFactory</res-ref-name> <res-type>javax.jms.ConnectionFactory</res-type> <res-auth>Application</res-auth> </resource-ref>
The Deployer maps that logical name ( jms/PlayerConnectionFactory) to an RA connection factory which implements the javax.jms.ConnectionFactory interface and is located in JNDI at OEMSJMSDRASubcontext/MyCF:
<resource-ref-mapping location = "OEMSJMSDRASubcontext/MyCF" name = "jms/PlayerConnectionFactory"/>
The above mapping is in the orion-application-client.xml file.
Similarly, in the orion-ejb-jar.xml file the Deployer maps the logical name jms/DealerConnectionFactory to the RA XA connection factory located in JNDI at OEMSJMSDRASubcontext/MyXACF:
<resource-ref-mapping location = "OEMSJMSDRASubcontext/MyXACF" name = "jms/DealerConnectionFactory"/>
The app-client was non-transactional, so it was given a non-XA connection factory. The MDB is transactional (it has a <trans-attribute> of Required), so it requires an XA connection factory.
Note: Sending and receiving messages using producers/consumers derived from a non-XA connection factory will not work within a global transaction. Likewise, sending and receiving messages using producers/consumers derived from an XA connection factory will not work outside of a global transaction.
As described in the Link to Message Destinations task, the Application Assembler has provided the necessary information about which sets of message destination references should be mapped to a single physical JMS Destination. For each <message-destination> , the Deployer must map all <message-destination-ref> s and MDBs linked to that <message-destination> to the same destination.
For example, in ejb-jar.xml a <message-destination> named DealerToPlayerMessages is declared. In file application-client.xml the <message-destination-ref> named jms/PlayerResponseDestination is linked to that <message-destination> , and in file ejb-jar.xml the <message-destination-ref> named jms/ToPlayerDest is also linked to that <message-destination> . Note that the <message-destination-type> for both of these is javax.jms.Topic. The Deployer maps both of these <message-destination-ref> s to an RA topic at JNDI location OEMSJMSDRASubcontext/MyT by adding this to the orion-application.xml file:
<message-destination-ref-mapping location = "OEMSJMSDRASubcontext/MyT" name = "jms/PlayerResponseDestination"/>
and this to the orion-ejb-jar.xml file:
<message-destination-ref-mapping location = "OEMSJMSDRASubcontext/MyT" name = "jms/ToPlayerDest"/>
Note: In 10.1.3 DP4 this was required. However, in 10g R3 the trail from <message-destination-ref> to <message-destination-link> to <message-destination> to <message-destination-mapping> is followed automatically for EJBs. So the above <message-destination-ref-mapping> is not actually required, and the orion-ejb-jar.xml file for this demo does not include it.
Similarly, in ejb-jar.xml a <message-destination> named PlayerToDealerMessages is declared. In file application-client.xml the <message-destination-ref> named jms/PlayerCommandDestination is linked to that <message-destination> , and in file ejb-jar.xml the MDB is also linked to that <message-destination> . The Deployer maps both of these to an RA queue at JNDI location OEMSJMSDRASubcontext/MyQ. The <message-destination-ref> is handled by adding another <message-destination-ref-mapping> to the orion-application.xml file:
<message-destination-ref-mapping location = "OEMSJMSDRASubcontext/MyQ" name = "jms/PlayerCommandDestination"/>
Mapping the MDB to a physical destination is done as part of the MDB's activation specification (described more in the next section). The Deployer sets the DestinationName property to OEMSJMSDRASubcontext/MyQ in the orion-ejb-jar.xml file:
<config-property> <config-property-name>DestinationName </config-property-name> <config-property-value>OEMSJMSDRASubcontext/MyQ </config-property-value> </config-property>
To configure an MDB for deployment, add a <message-driven-deployment> element to the orion-ejb-jar.xml file as a subelement of <enterprise-beans> :
<enterprise-beans> ... <message-driven-deployment name="DealerEjbName" ... > ... </message-driven-deployment>
Note that the "name" attribute must be set to the same value as the <ejb-name> element for the given MDB in the ejb-jar.xml file.
In order for the MDB to be activated by messages received by the JMS Connector, the MDB and JMS Connector must be connected. This is done by setting the "resource-adapter" attribute equal to the name of the JMS Connector instance:
<message-driven-deployment name="DealerEjbName" resource-adapter="OEMSJMSDRAInstanceName"> ... </message-driven-deployment>
When the MDB is deployed, the application server provides the MDB's activation specification to the JMS Connector. The activation specification is a collection of properties which may be defined in the ejb-jar.xml file via <activation-config-property> elements:
<activation-config-property> <activation-config-property-name>ExamplePropertyName </activation-config-property-name> <activation-config-property-value>ExampleValue </activation-config-property-value> </activation-config-property>orion-ejb-jar.xml <config-property>
<config-property> <config-property-name>ExamplePropertyName </config-property-name> <config-property-value>ExampleValue </config-property-value> </config-property>
Since activation specification properties are specific to a given resource adapter, using the app-server-specific orion-ejb-jar.xml file is the recommended approach.
One of the activation specification properties ( DestinationName) was already covered in the previous section. When messages are sent to the destination defined by that property (and are not filtered by any MessageSelector property), the messages are then delivered to the MDB. DestinationName is a required property.
Another required property is ConnectionFactoryJndiName. This defines the connection factory the JMS Connector should use to create a connection (which it then uses to retreive messages from the above destination on behalf of the MDB). Since the MDB in this demo is transactional (it has a <trans-attribute> of Required), the JMS Connector needs an XA connection factory and the ConnectionFactoryJndiName property is set to OEMSJMSDRASubcontext/MyXACF.
The last property which is always required is DestinationType. When using a resource provider which implements JMS 1.0.2b (and not JMS 1.1), it must be set to javax.jms.Queue if the destination is a queue and javax.jms.Topic if the destination is a topic. When using a resource provider which implements JMS 1.1 it may also be set to javax.jms.Destination (for either a queue or a topic).
This demo only requires the activation specification properties described above. However, the orion-ejb-jar.xml file included with this demo contains documentation for all of the properties supported by Oracle's JMS Connector implementation.
The jndi.properties file is typically used to control what happens when an application client creates and uses a javax.naming.InitialContext. The
See the Configuring the Environment section for more on the format and content of the jndi.properties file.
There are several ways to manipulate the class search path. This demo uses the "Class-Path" section of the MANIFEST.MF files. (There is one MANIFEST.MF file for each application component, as well as a top-level MANIFEST.MF for the application.)
Often, the class path needs of application components other than application clients are satisfied by the class paths provided by default. However, this demo contains some classes which are used by both the application client and the MDB. Those classes have been placed in their own jar file ( common.jar). In order to allow those application components to locate those common classes, common.jar is listed in the "Class-Path" section of the MANIFEST.MF files for both the application client and the MDB. Since this dependency is known at the Application Assembler level, it may be configured there rather than by the Deployer.
The application client does not get the same default class paths as other application components. This means that a number of app-server and J2EE-standard jar files need to be included in the "Class-Path" section of the MANIFEST.MF file for the application client. (A brute-force solution is to simply include every jar file in %ORACLE_HOME%/j2ee/home and %ORACLE_HOME%/j2ee/home/lib in addition to any required 3rd party jar files.)
The following instructions are for running this demonstration on a standalone or managed instance of Oracle Containers for J2EE 10g Release 3.
Make sure the following environment variables are defined:
Please check to make sure that the following properties are configured correctly in the ant-oracle.properties file located in the root of the sample's distribution (NOTE: Some of these properties will default to the values of corresponding environment variables as noted below. If you have these variables set up in your environment you will not have to alter the values in the file unless ant is unable to access environment variables on your platform). Modify these variables as needed for your environment:
If oracleas.host, oracleas.admin.port, oracleas.admin.user or oracleas.admin.password is changed, update %HOWTO_HOME%/src/client/jndi.properties as well. That file should have the following format:
java.naming.factory.initial=com.evermind.server.ApplicationClientInitialContextFactory java.naming.provider.url=ormi://${oracleas.host}:${oracleas.admin.port}/how-to-connect-to-oemsjmsd java.naming.security.principal=${oracleas.admin.user} java.naming.security.credentials=${oracleas.admin.password}
If db.host, db.sid, or db.port is changed, update %HOWTO_HOME%/src/META-INF/data-sources.xml as well. The url definition in that file should have the following format:
If you are running a managed version of Oracle Application Server 10g, you must change the following values to match your configuration:
The properties in the ant-oracle.properties file which are not listed above are not used by this demo and can be ignored.
Finally, please make sure that the ant command associated with the OC4J ant distribution is in your execution path ( %OC4J_HOME%/ant/bin).
Start an OC4J 10.1.3 instance as follows:
%ORACLE_HOME%/bin/oc4j start
Note that the oc4j command expects the JAVA_HOME environment variable to point to a full JDK installation.
%ORACLE_HOME%/opmn/bin/opmnctl startall
To build the application, type the following command from the %HOWTO_HOME% directory:
You should now have the newly created how-to-connect-to-oemsjmsd.ear in your %HOWTO_HOME%/dist directory.
This command will also attempt to deploy the application if the build is successful. It will first test whether OC4J is running.
Note that you can also deploy the application separately. Ensure the %ORACLE_HOME% environment variable is defined, and from the %HOWTO_HOME% directory, type the command:
ant deploy
From three terminal windows (all with environment entries set as described above), go to the %HOWTO_HOME% directory and start a player. There are four players available, and each can be started with an ant command:
ant larry ant curly ant moe ant joe
For example, do ant larry from the first terminal, ant curly from the second, and ant moe from the third.
The three app-client players will join the game run by the MDB dealer and play the game described in the Introduction.
You have learned:
|Object Type
|Use During Demo Initialization
|Object Type
|Use After Demo Initialization
|look up ConnectionFactory and Destination
|create Connection
|create Session
|close everything
|create MessageProducer and MessageConsumer
|create MessageProducer and MessageConsumer
|create messages
|send messages
|receive messages
|JNDI Name *
|Java interface
|JNDI Location
|Java interface
|JNDI Location
|Java interface
|JNDI Location
|Java interface


text:
Download PDF |
Print Detail Page |
Request a Quote |
I'm Interested
Bayliner went all-out to equip the 217 with all the space, comforts and storage of a pontoon boat, with thrilling V-hull performance. Lounging on the transom sunpad is sure to be popular with its flip-up backrest. Seating covers nearly the entire boat, while optional filler cushions create a queensized lounge/playpen in the bow.
Have a question about the 2012 Bayliner 217 Deck Boat?


text:
Culturing milk on the farm can help producers control mastitis, reduce antibiotic use
Culturing milk on the farm can help producers control mastitis, reduce antibiotic use
Dairy producers who culture their own milk gain valuable information about the health of their herd and can develop treatment plans based on homegrown bacteria.
"They are able to target treatment more effectively and reduce unneeded antibiotic use significantly," Phil Durst, Michigan State University (MSU) senior Extension educator, said.
On-farm milk culturing is beneficial because it allows farmers to determine which cows are having problems and to design treatment plans that improve milk quality.
Durst says that the one person in charge of culturing the milk should be extremely concerned with following protocol. Improper sampling can lead to inaccurate results.
"Make sure you are collecting samples properly, because 99.9 percent of contaminated samples result from mistakes during collection," Durst said.
"Whoever is in charge of culturing should have some sort of authority in the parlor as well as additional training with a veterinarian," Durst said. "This will ensure the success of the culturing beyond short term."
Good recordkeeping practices are important to keep track of each cow's results. Include Cow ID and date in these records.
You can find culturing supplies at many different supply stores, and startup and maintenance costs are relatively cheap.
Dairy producers should visit Michigan State University Extension News for more information about how to culture milk on the farm and methods for mastitis control. This online resource features helpful articles about various topics submitted by MSU Extension experts throughout the state. Find MSU Extension News at news.msue.msu.edu.


text:
PSE started in 1995, on the day we saw children eating in the filth of the dump-site in Stung Meanchey in Phnom-Penh in Cambodia. It was appalling. Having seen that, it was not possible to continue to live normally. Something had to be done.
First we started to bring meals to the garbage dump, but very soon we realized that the situation went beyond our forces and resources. We returned to France to alarm our families, friends, and everyone we knew. To tell them what we had discovered, and thanks to their overwhelming mobilization we were able to return to Cambodia and create "Pour un Sourire d'Enfant" (for a child's smile).


text: Bluco's line of manual rollover positioners can be used as stand-alone fixturing solutions or alongside existing Bluco fixturing systems. The positioners provide 360 degrees of rotation, enabling full access to all sides of the workpiece, and the rotation is clocked in 22.5-degree increments so that the workpiece can be located at the optimal weld position of each joint. Positioners can also be provided with custom increments. Several styles and lengths of positioners are available.


text:
Wiki > System > ReferenceManual > AdminDocumentationCategory > PreviewBackground
Background Image for PreviewPreview looks like the real page, but the links lead to an oops dialog warning users of not-yet-saved topics. In addition, a background with a "PREVIEW" watermark is shown to have visual clue that you are previewing a topic. You can change the background image by specifying the name of an attached background image file in the PREVIEWBGIMAGE setting in the DefaultPreferences. Remarks:
Related Topics: AdminDocumentationCategory
Edit | Attach | Print version | History: r1 | Backlinks | View wiki text | More topic actions
r1 - 01 Jul 2010 - 00:09:09 - ProjectContributor
Copyright © by the contributing authors. All material on this site is the property of the contributing authors.
Ideas, requests, problems regarding Wiki? Send feedback


text:
Quality Education in the Benedictine Tradition
April 26, 2013
Megan DePrimio, a senior communication major from Ligonier, will attend the 2013 National Association of Collegiate Marketing Administrators (NACMA) convention June 13 to 15 at the World Center Marriott Resort in Orlando, Fla. DePrimio is one of 10 students in the U.S. who were awarded stipends of $800 as part of the Mike Cleary Student Stipend Program and the only recipient from an NCAA Division III school. NACMA is a national organization that provides educational and networking opportunities, enhancement of acceptable operating standards and ethics and establishment of the overall prestige and understanding of the profession of athletics marketing administrators. DePrimio expects to receive a bachelor of arts degree in communication from Saint Vincent College in May. After graduation, she plans to pursue a year-long internship or graduate assistant position with a goal of working in collegiate athletic marketing. A member of the dean's list, she has been honored with membership in Sigma Tau Delta English honor society, Lambda Pi Eta communication honor society (vice president) and Alpha Lambda Delta freshman honor society. She has experience in public relations and marketing for the Saint Vincent women's basketball team, served as a game day promotions and social media intern with the Pittsburgh Power football team, marketing intern with the Pittsburgh Steelers, marketing intern with University of Pittsburgh athletics, marketing and communication intern with Excela Health and as a sales and marketing intern with WTAE-TV. DePrimio has also worked with the Saint Vincent College School of Communication, the Marketing and Communication Department and the Saint Vincent Review student newspaper. A member of the women's basketball team from 2009 to 2013, she served as vice president of the Advertising Club, as a member of the Women in Business Student Association and the Marketing Matrix Club and as a member of the Saint Vincent Certified Emerging Leadership Program.
Photo: Megan DePrimio
Follow us on Twitter: @MySaintVincent Like us on Facebook:


text:
Top Definition
An award given to the best all-around division 1A college football player every season.
The recent Heisman Trophy winners.
2006- Reggie Bush
2005- Matt Leinart
2004- Carson Palmer
2006- Reggie Bush
2005- Matt Leinart
2004- Carson Palmer
po Snick and Fsquirrel Мај 30, 2006
Trending Now
Can you define these popular missing words?
A trophy awarded to the best player in college football.
Jay Bergwanger won the first Heisman Trophy.
po Fifi McFeef Јануар 1, 2008
A masturbation position, primarily used in the shower to keep from slipping. One hand on the wall, the other hand.. well you know.
Dude, I was jacking off in the shower, and I had to do the Heisman Trophy because the tub was so slippery.
po Bobbybagpipes Јул 10, 2008


text:
Top Definition
The step beyond gay. A man that has taken time to go out of his way to make sure u know he's gay. This term doen't apply to women because lesbians rule... sept if they're butch and goss
"Holy crap look at that dude's scarf and pink button-down shirt thats open at the top. He's so homogay"
por Taildrag 20 de Setembro de 2005
Trending Now
Can you define these popular missing words?
when something is more gay than gay. thus, makes it homo gay.
"Hawthorne High School is homo gay."
por pedro 16 de Fevereiro de 2005
extremely gay, therefore just about as gay as it gets.
Woah my friend, you ARE the homogay.
por Molly Williams 03 de Março de 2003
A term (noun or adjective) to describe someone who too closely follows the 'gay stereotype.'
Usually used amongst super-christians.
Usually used amongst super-christians.
The homogays are staging capchta images to convert our children.
por Gatodo 11 de Maio de 2011
Very gay person.
Jonny is very homogay.
por jonny 11 de Março de 2003
used on SNL (saturday night live) by mango meaning just gay...probably could be used as super ultra uber gay
"Why does everyone think I'm the homo gay?"
-Mango (Chris Kattan)
-Mango (Chris Kattan)
por the homo gay 12 de Março de 2005
The splicing of "homosexual" and its more common synonym, "gay". Saying "homogay" takes off two syllables that would otherwise need to be said in saying "homosexual". Semi-formal way of saying "gay".
He is homogay. (ho-mo-gay instead of ho-mo-sex-u-al)
por SamusAX 11 de Dezembro de 2004