<?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; Weblogic</title>
	<atom:link href="http://www.bearparc.info/category/application-server/weblogic/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bearparc.info</link>
	<description>A software development blog for the qualified developer</description>
	<lastBuildDate>Thu, 04 Feb 2010 13:55:11 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</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[JBoss]]></category>
		<category><![CDATA[Java]]></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>JMS &#8211; Java message service Funktionsweise und Beispiele</title>
		<link>http://www.bearparc.info/2007/04/05/jms-java-message-service-funktionsweise-und-beispiele/</link>
		<comments>http://www.bearparc.info/2007/04/05/jms-java-message-service-funktionsweise-und-beispiele/#comments</comments>
		<pubDate>Thu, 05 Apr 2007 16:01:01 +0000</pubDate>
		<dc:creator>Martin</dc:creator>
				<category><![CDATA[Application Server]]></category>
		<category><![CDATA[J2ee]]></category>
		<category><![CDATA[Weblogic]]></category>

		<guid isPermaLink="false">http://www.bearparc.info/2007/04/05/jms-java-message-service-funktionsweise-und-beispiele/</guid>
		<description><![CDATA[Java Message Service (JMS) ist ein API für den Austausch von Nachrichten zwischen zwei oder mehr Clients, die in der Programmiersprache Java geschrieben sind. Die API und der zugehörige Dienst unterstützten zwei unterschiedliche Ansätze zum Versenden von Nachrichten, zum einen die Nachrichtenschlangen (Message Queues) und zum anderen ein Anmelde-Versendesystem (Publish-Subscribe). Für die Anwendung braucht man [...]]]></description>
		<wfw:commentRss>http://www.bearparc.info/2007/04/05/jms-java-message-service-funktionsweise-und-beispiele/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>J2EE Connector Architecture</title>
		<link>http://www.bearparc.info/2007/04/03/j2ee-connector-architecture/</link>
		<comments>http://www.bearparc.info/2007/04/03/j2ee-connector-architecture/#comments</comments>
		<pubDate>Tue, 03 Apr 2007 13:15:18 +0000</pubDate>
		<dc:creator>Gabi</dc:creator>
				<category><![CDATA[Application Server]]></category>
		<category><![CDATA[Weblogic]]></category>

		<guid isPermaLink="false">http://www.bearparc.info/2007/04/03/j2ee-connector-architecture/</guid>
		<description><![CDATA[The J2EE Connector Architecture adds simplified Enterprise Information System (EIS) integration to the J2EE platform. It provides a Java solution to the problem of connectivity between the multitude of application servers and EISes. By using the Connector Architecture, it is no longer necessary for EIS vendors to customize their product for each application server. By [...]]]></description>
		<wfw:commentRss>http://www.bearparc.info/2007/04/03/j2ee-connector-architecture/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>JDBC</title>
		<link>http://www.bearparc.info/2007/03/31/jdbc/</link>
		<comments>http://www.bearparc.info/2007/03/31/jdbc/#comments</comments>
		<pubDate>Sat, 31 Mar 2007 10:32:49 +0000</pubDate>
		<dc:creator>Gabi</dc:creator>
				<category><![CDATA[Application Server]]></category>
		<category><![CDATA[Weblogic]]></category>

		<guid isPermaLink="false">http://www.bearparc.info/2007/03/31/jdbc/</guid>
		<description><![CDATA[Java Database Connectivity (JDBC) provides access to backend database resources. Java applications access JDBC using a JDBC driver, which is a database vendor-specific interface for a database server. Although any Java application can load a vendor&#8217;s JDBC driver, connect to the database, and perform database operations, WebLogic Server provides a significant performance advantage by offering [...]]]></description>
		<wfw:commentRss>http://www.bearparc.info/2007/03/31/jdbc/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>JNDI</title>
		<link>http://www.bearparc.info/2007/03/30/jndi/</link>
		<comments>http://www.bearparc.info/2007/03/30/jndi/#comments</comments>
		<pubDate>Fri, 30 Mar 2007 10:31:41 +0000</pubDate>
		<dc:creator>Gabi</dc:creator>
				<category><![CDATA[Application Server]]></category>
		<category><![CDATA[Weblogic]]></category>

		<guid isPermaLink="false">http://www.bearparc.info/2007/03/30/jndi/</guid>
		<description><![CDATA[The Java Naming and Directory Interface (JNDI) is a standard Java API that enables applications to look up an object by name. WebLogic Server or a user application binds the Java objects it serves to a name in a naming tree. An application can look up objects, such as RMI objects, Enterprise JavaBeans, JMS Queues [...]]]></description>
		<wfw:commentRss>http://www.bearparc.info/2007/03/30/jndi/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SSL</title>
		<link>http://www.bearparc.info/2007/03/29/ssl/</link>
		<comments>http://www.bearparc.info/2007/03/29/ssl/#comments</comments>
		<pubDate>Thu, 29 Mar 2007 10:27:48 +0000</pubDate>
		<dc:creator>Gabi</dc:creator>
				<category><![CDATA[Application Server]]></category>
		<category><![CDATA[Weblogic]]></category>

		<guid isPermaLink="false">http://www.bearparc.info/2007/03/29/ssl/</guid>
		<description><![CDATA[Data exchanged with the HTTP and T3 protocols can be encrypted with the Secure Sockets Layer (SSL) protocol. Using SSL assures the client that it has connected with an authenticated server and that data transmitted over the network is private. SSL uses public key encryption. Public key encryption requires you to produce identity and trust [...]]]></description>
		<wfw:commentRss>http://www.bearparc.info/2007/03/29/ssl/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SOAP</title>
		<link>http://www.bearparc.info/2007/03/28/soap/</link>
		<comments>http://www.bearparc.info/2007/03/28/soap/#comments</comments>
		<pubDate>Wed, 28 Mar 2007 10:30:51 +0000</pubDate>
		<dc:creator>Gabi</dc:creator>
				<category><![CDATA[Application Server]]></category>
		<category><![CDATA[Weblogic]]></category>

		<guid isPermaLink="false">http://www.bearparc.info/2007/03/28/soap/</guid>
		<description><![CDATA[SOAP (Simple Object Access Protocol) is a lightweight, XML-based protocol used to exchange information in a decentralized, distributed environment. The protocol consists of an envelop that describes the SOAP message, encoding rules, and conventions for representing remote procedure calls and responses. All information is embedded in a Multipurpose Internet Mail Extensions (MIME)-encoded package that can [...]]]></description>
		<wfw:commentRss>http://www.bearparc.info/2007/03/28/soap/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RMI-IIOP</title>
		<link>http://www.bearparc.info/2007/03/28/rmi-iiop/</link>
		<comments>http://www.bearparc.info/2007/03/28/rmi-iiop/#comments</comments>
		<pubDate>Wed, 28 Mar 2007 10:26:49 +0000</pubDate>
		<dc:creator>Gabi</dc:creator>
				<category><![CDATA[Application Server]]></category>
		<category><![CDATA[Weblogic]]></category>

		<guid isPermaLink="false">http://www.bearparc.info/2007/03/28/rmi-iiop/</guid>
		<description><![CDATA[Remote Method Invocation over Internet Inter-ORB Protocol (RMI-IIOP) is a protocol that allows CORBA client programs to execute WebLogic RMI objects, including enterprise beans. RMI-IIOP is based on two specifications from the Object Management Group (http://www.omg.com): Java-to-IDL mapping Objects-by-value The Java-to-IDL specification defines how an Interface Definition Language (IDL) is derived from a Java interface. [...]]]></description>
		<wfw:commentRss>http://www.bearparc.info/2007/03/28/rmi-iiop/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RMI</title>
		<link>http://www.bearparc.info/2007/03/27/rmi/</link>
		<comments>http://www.bearparc.info/2007/03/27/rmi/#comments</comments>
		<pubDate>Tue, 27 Mar 2007 10:25:48 +0000</pubDate>
		<dc:creator>Gabi</dc:creator>
				<category><![CDATA[Application Server]]></category>
		<category><![CDATA[Weblogic]]></category>

		<guid isPermaLink="false">http://www.bearparc.info/2007/03/27/rmi/</guid>
		<description><![CDATA[Remote Method Invocation (RMI) is the standard Java facility for distributed applications. RMI allows one Java program, called the server, to publish Java objects that another Java program, called a client, can execute. In most applications, WebLogic Server is the RMI server and a Java client application is the client. But the roles can be [...]]]></description>
		<wfw:commentRss>http://www.bearparc.info/2007/03/27/rmi/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>T3</title>
		<link>http://www.bearparc.info/2007/03/26/t3/</link>
		<comments>http://www.bearparc.info/2007/03/26/t3/#comments</comments>
		<pubDate>Mon, 26 Mar 2007 10:24:52 +0000</pubDate>
		<dc:creator>Gabi</dc:creator>
				<category><![CDATA[Application Server]]></category>
		<category><![CDATA[Weblogic]]></category>

		<guid isPermaLink="false">http://www.bearparc.info/2007/03/26/t3/</guid>
		<description><![CDATA[T3 is an optimized protocol used to transport data between WebLogic Server and other Java programs, including clients and other WebLogic Servers. WebLogic Server keeps track of every Java Virtual Machine (JVM) with which it connects, and creates a single T3 connection to carry all traffic for a JVM. For example, if a Java client [...]]]></description>
		<wfw:commentRss>http://www.bearparc.info/2007/03/26/t3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
