<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>bearparc - Softwareentwicklung und Projektmanagement &#187; Business Logic Layer</title>
	<atom:link href="http://www.bearparc.info/category/application-server/business-logic-layer/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bearparc.info</link>
	<description>A software development blog for the qualified developer</description>
	<lastBuildDate>Tue, 18 Oct 2011 19:37:30 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Bringt Spring noch Vorteile gegenüber EJB 3.0 ?</title>
		<link>http://www.bearparc.info/2007/04/29/bringt-spring-noch-vorteile-gegenuber-ejb-30/</link>
		<comments>http://www.bearparc.info/2007/04/29/bringt-spring-noch-vorteile-gegenuber-ejb-30/#comments</comments>
		<pubDate>Sun, 29 Apr 2007 17:23:16 +0000</pubDate>
		<dc:creator>Gabi</dc:creator>
				<category><![CDATA[Application Server]]></category>
		<category><![CDATA[Business Logic Layer]]></category>
		<category><![CDATA[Framework]]></category>
		<category><![CDATA[J2ee]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[JBoss]]></category>
		<category><![CDATA[Weblogic]]></category>

		<guid isPermaLink="false">http://www.bearparc.info/2007/04/29/bringt-spring-noch-vorteile-gegenuber-ejb-30/</guid>
		<description><![CDATA[Was ist Spring? Spring ist ein beliebtes, aber nicht standardisiertes open source J2EE-framework. Es baut auf light-weight Komponenten POJOs auf. Unterstützt das Prinzip der Dependency Injection, Aspektorientierten Programmierung (AOP, dadurch können vor allem technische Aspekte wie Security oder Transaktionsmanagement isoliert werden) sowie mehrere standardisierte O/R-Mapper. Spring wird auch oft als Ersatz für EJBs implementiert. Mit [...]]]></description>
		<wfw:commentRss>http://www.bearparc.info/2007/04/29/bringt-spring-noch-vorteile-gegenuber-ejb-30/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Neues in EJB 3.0</title>
		<link>http://www.bearparc.info/2007/04/23/neues-in-ejb-30/</link>
		<comments>http://www.bearparc.info/2007/04/23/neues-in-ejb-30/#comments</comments>
		<pubDate>Mon, 23 Apr 2007 22:58:52 +0000</pubDate>
		<dc:creator>Gabi</dc:creator>
				<category><![CDATA[Application Server]]></category>
		<category><![CDATA[Business Logic Layer]]></category>
		<category><![CDATA[Framework]]></category>
		<category><![CDATA[J2ee]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Liferay]]></category>
		<category><![CDATA[objektorientiertes Design]]></category>

		<guid isPermaLink="false">http://www.bearparc.info/2007/04/23/neues-in-ejb-30/</guid>
		<description><![CDATA[Was ändert sich in EJB 3.0 gegenüber EJB 2.x? Metadata Annotations ersetzen Deploymentdescriptoren: Annotations werden mit @ gekennzeichnet z.B. @Stateless, @Remote. Die zugehörigen Java Objects incl. Default-Werte werden beim Kompilieren generiert. Deploymentdescirptoren können jedoch zusätzlich noch optional verwendet werden z.B. um die Default-Werte zu überschreiben. Code Beispiel für dependency injection: @Resource(name="jdbc/OracleDS", resourceType="javax.sql.DataSource") Verwendung von POJO’s [...]]]></description>
		<wfw:commentRss>http://www.bearparc.info/2007/04/23/neues-in-ejb-30/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>POJO</title>
		<link>http://www.bearparc.info/2007/04/23/pojo/</link>
		<comments>http://www.bearparc.info/2007/04/23/pojo/#comments</comments>
		<pubDate>Mon, 23 Apr 2007 20:32:35 +0000</pubDate>
		<dc:creator>Martin</dc:creator>
				<category><![CDATA[Application Server]]></category>
		<category><![CDATA[Business Logic Layer]]></category>
		<category><![CDATA[J2ee]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Liferay]]></category>

		<guid isPermaLink="false">http://www.bearparc.info/2007/04/23/pojo/</guid>
		<description><![CDATA[Plain old Java Object, mit POJO&#8217;s baut man das Domain Model auf, ohne umfangreiche Konventionen wie bei Entity Beans einhalten zu müssen. Man konzentriert sich auf die fachlichen Aspekte (Rich Domain Model), so daß in der Session-Beans nur noch Transaction-Handling Security Pooling &#8211; Skalierbarkeitsaspekt vorhanden sind. Auch diese lassen sich per AOP deklarativ in POJOs beschreiben. In einer Architektur [...]]]></description>
		<wfw:commentRss>http://www.bearparc.info/2007/04/23/pojo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Entity Beans</title>
		<link>http://www.bearparc.info/2007/03/15/entity-beans/</link>
		<comments>http://www.bearparc.info/2007/03/15/entity-beans/#comments</comments>
		<pubDate>Thu, 15 Mar 2007 11:13:00 +0000</pubDate>
		<dc:creator>Martin</dc:creator>
				<category><![CDATA[Application Server]]></category>
		<category><![CDATA[Business Logic Layer]]></category>
		<category><![CDATA[Weblogic]]></category>

		<guid isPermaLink="false">http://www.bearparc.info/2007/03/15/entity-beans/</guid>
		<description><![CDATA[An entity bean represents an object that contains data, such as a customer, an account, or an inventory item. Entity beans contain data values and methods that can be invoked on those values. The values are saved in a database (using JDBC) or some other data store. Entity beans can participate in transactions involving other [...]]]></description>
		<wfw:commentRss>http://www.bearparc.info/2007/03/15/entity-beans/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Message-Driven Beans</title>
		<link>http://www.bearparc.info/2007/03/09/message-driven-beans/</link>
		<comments>http://www.bearparc.info/2007/03/09/message-driven-beans/#comments</comments>
		<pubDate>Fri, 09 Mar 2007 21:24:04 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Application Server]]></category>
		<category><![CDATA[Business Logic Layer]]></category>

		<guid isPermaLink="false">http://www.bearparc.info/2007/03/09/message-driven-beans/</guid>
		<description><![CDATA[Message-driven beans, introduced in the EJB 2.0 specification, are enterprise beans that handle asynchronous messages received from JMS Message Queues. JMS routes messages to a message-driven bean, which selects an instance from a pool to process the message. Message-driven beans are managed in the WebLogic Server EJB container. Because they are not called directly by [...]]]></description>
		<wfw:commentRss>http://www.bearparc.info/2007/03/09/message-driven-beans/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Session Beans</title>
		<link>http://www.bearparc.info/2007/03/09/session-beans/</link>
		<comments>http://www.bearparc.info/2007/03/09/session-beans/#comments</comments>
		<pubDate>Fri, 09 Mar 2007 21:23:01 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Application Server]]></category>
		<category><![CDATA[Business Logic Layer]]></category>

		<guid isPermaLink="false">http://www.bearparc.info/2007/03/09/session-beans/</guid>
		<description><![CDATA[A session bean is a transient EJB instance that serves a single client. Session beans tend to implement procedural logic; they embody actions more than data. The EJB container creates a session bean at a client&#8217;s request. It then maintains the bean as long as the client maintains its connection to the bean. Sessions beans [...]]]></description>
		<wfw:commentRss>http://www.bearparc.info/2007/03/09/session-beans/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

