In Maven and other recent project and source management, we often find this term: "artifact".
I found some of the definition in the Wikipedia.
Artifacts are byproducts of software development process. Uses cases, class diagrams, UML models, requirements document, project plans, business cases and risk assessments are examples of artifacts.
Sometimes it refers also to the code or executable software produced, e.g. in the case of our Maven 2, artifact identifies to the code and executable software produced.
Monday, December 25, 2006
Merry Christmas!
Merry Christmas 2006!
Dear friends, may the joy of Christmas fill your soul today!
Regards,
Daniel
Dear friends, may the joy of Christmas fill your soul today!
Regards,
Daniel
Friday, December 22, 2006
Develop with pleasure!
I, Endy and T Budi S have received the personal licenses for IntelliJ IDEA 6.0 and its sister product TeamCity, for our role as speakers in the last 2 months' JaMU 23 and JaMU 24. Thanks for the support from JetBrains, s.r.o to our JUG and JaMU in Indonesia!
I installed the version 6.0.2 smoothly. My, GWT studio, Geronimo integration, Glassfish integration, JBoss integration, Javascript Intention Powerpack, Struts Assitant, Tomcat integration, WebLogic integration and Websphere integration!
Cool stuff!
I installed the version 6.0.2 smoothly. My, GWT studio, Geronimo integration, Glassfish integration, JBoss integration, Javascript Intention Powerpack, Struts Assitant, Tomcat integration, WebLogic integration and Websphere integration!
Cool stuff!
Thursday, December 21, 2006
New Features in the JSP 2.0
I dunno where I've been, since this is an ancient artifact from the Jurassic era.
Since my current project is a surgeon on a JSP/Servlet from some time around year 2000 code, I stumbled upon this page...
Six Cool New JSP and Servlet Features at OnJava.com.
Though it's been around since 2004, I think those features are still cool! Two years ago I'm exploring custom tags using Java codes, but now the custom tags can be JSPs too!!
Today's people always talking about Freemarker, Velocity and many other cool template engine. But I still love JSPs, which is easier to debug, though some people could abuse, yet, I still have the confindence that people indeed can write good and maintainable JSP code.
I began rewriting some of the code, and using the EL expression 1.0. It needs a lot of rework for this old and hard to maintain JSP codes, but I think the effort will be worthed it!
I've just hoping that we'll be moving to Tomcat 5.5 on JDK 5, but I'm just happy to find out these features work just fine in Tomcat 5.0 (RI for JSP 2.0!) which we are using on JDK 1.4.2.
The new feature I will surely use is the new JSP tag definition! After the tag components has been matured you can begin writing the corresponding Java classes, but for experiments, creations of new ones and debugging, better use the JSP version!
Now I've got a complete prototyping scripting tool!
Since my current project is a surgeon on a JSP/Servlet from some time around year 2000 code, I stumbled upon this page...
Six Cool New JSP and Servlet Features at OnJava.com.
- Servlets as Welcome Files
- Mapping Filters to RequestDispatchers
- Using Listeners with Servlet Requests
- Using EL Code Within Template Text
- Writing Tag Files (in JSP!)
- Writing EL-Qualified Functions
Though it's been around since 2004, I think those features are still cool! Two years ago I'm exploring custom tags using Java codes, but now the custom tags can be JSPs too!!
Today's people always talking about Freemarker, Velocity and many other cool template engine. But I still love JSPs, which is easier to debug, though some people could abuse, yet, I still have the confindence that people indeed can write good and maintainable JSP code.
I began rewriting some of the code, and using the EL expression 1.0. It needs a lot of rework for this old and hard to maintain JSP codes, but I think the effort will be worthed it!
I've just hoping that we'll be moving to Tomcat 5.5 on JDK 5, but I'm just happy to find out these features work just fine in Tomcat 5.0 (RI for JSP 2.0!) which we are using on JDK 1.4.2.
The new feature I will surely use is the new JSP tag definition! After the tag components has been matured you can begin writing the corresponding Java classes, but for experiments, creations of new ones and debugging, better use the JSP version!
Now I've got a complete prototyping scripting tool!
Saturday, December 9, 2006
JEE Learning Track
(Yes, it's no longer J2EE, it's been renamed JEE now!)
This early morning I read somebody asking, what is the learning track for a Java SE developer if he wants to learn the Java EE platform.
I try to list down and compile the track to learn based on my own experience:
This early morning I read somebody asking, what is the learning track for a Java SE developer if he wants to learn the Java EE platform.
I try to list down and compile the track to learn based on my own experience:
- Download and install an JSP/Servlet Container (recommended: Apache Tomcat 5.5)
- Learn to deploy a simple JSP/Servlet application, like one from Sun, one from BEA, etc.
- Some usage of the JSP headers
- Try to deploy a Servlet
- Folder structure of a simple WAR file
- Folder structure of an EAR file
- Setting up the web.xml (this is one of the intricated process)
- Setting up the correct mapping and filter
- (I will continue this later...)
Thursday, December 7, 2006
Why Maven sucks...
OK, while I'm one who preach the usage of Apache Maven 2, I need to be even with ones who rejects the idea. Here is a list of some reasons while people think that Maven sucks...
- Some of the people who maintains the repository were not discipline and not consistent
- Not for building leading edge technologies (snapshot build, nightly build, candidate release, alpha, beta, etc)
- Not everyone could afford to download the 11GB++ repository
- Too bandwidth consuming for firsttimers (or someone who just wants to give a try)
- Takes time to setup
- (I will add up several thing later...)
Wednesday, December 6, 2006
What Maven Good At...
As usual, somebody at JUG-ID started a flame by throwing a fireball: "Maven is a junk!".
The most popular greeting in the JUG-ID is: "Salam hangat," (or translated to "Warm greeting,"). Well, I think that the most popular greeting has reasons for it. One of the things that makes the mailing list become 'warm' because there are lots of flames around, such as "Java vs .NET", "Sun sucks", "Maven sucks", "Vacuum cleaner sucks" also!, etc.
At some point then we realized that the flame thrower has points. And also some people thinks "JUG-ID sucks" as well. At least at some times ago I think that way ("JUG-ID sucks").
Now, I try list down what Maven Good At...
(and on the next post, "Why Maven sucks"... as well)
1) Reducing the Project Lead Time
2) Force project to follow certain rules
3) Dependency management
4) One place to change dependency
5) No need to store jar files in the versioning system anymore
6) (This list will grow...)
The most popular greeting in the JUG-ID is: "Salam hangat," (or translated to "Warm greeting,"). Well, I think that the most popular greeting has reasons for it. One of the things that makes the mailing list become 'warm' because there are lots of flames around, such as "Java vs .NET", "Sun sucks", "Maven sucks", "Vacuum cleaner sucks" also!, etc.
At some point then we realized that the flame thrower has points. And also some people thinks "JUG-ID sucks" as well. At least at some times ago I think that way ("JUG-ID sucks").
Now, I try list down what Maven Good At...
(and on the next post, "Why Maven sucks"... as well)
1) Reducing the Project Lead Time
2) Force project to follow certain rules
3) Dependency management
4) One place to change dependency
5) No need to store jar files in the versioning system anymore
6) (This list will grow...)
Mevenide plugin for NetBeans 2.3 has been released!
http://blogs.codehaus.org/archives/001409_mevenide_maven2_for_netbeans_23_release.html
NetBeans users, welcome to the Maven 2 world!
NetBeans users, welcome to the Maven 2 world!
Maven 2: Snare and Pitfalls
Last Saturday I presented Maven 2 at JaMU 24.
The world of Maven is still growing, expanding, and there are lots of unexplored area. Newcomers could be discouraged to use Maven 2 because of certain things which could make them stuck.
Here are some of the snare and pitfall while setting up Maven 2:
1) Creating the "~/.m2" folder in Windows environment
The "~" (tilde) is a common representation of user folder in the UNIX/Linux systems. In Windows, it usually maps to "C:\Documents and Settings\your.username", "C:\Documents and Settings\your.username.DOMAIN", or "C:\Documents and Settings\your.username.DOMAIN.001", etc.
When we try to create a folder in the Window Explorer using the File - New Folder menu, Windows will display a stupid dialog telling you "you must type a filename". Obviously we want to create a folder, so the message should be "you must type a folder name".
After struggling for a while I eventually managed to create the folder using Cygwin's bash shell. Of course this is not solving the problem when you don't have Cygwin installed. And Cygwin brings POSIX personality to NT platform. I believe there are some other way to create such files, like calling the Windows API to create the folder. But I eventually found the simplest thing to create the folder, unzip a folder with that name using your favorite zip tools!
I included the file in the starter kits (uploaded to JUG-ID file repository).
2) Got the message "generics are not supported in -source 1.3"
What has happened right here?! You are sure of using JDK 5 already, but yet you still got this message.
The problem is that the default setting for maven-compiler-plugin is to use the JDK 1.3. So the workaround is to add this to your pom.xml file in the section:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.5</source>
<target>1.5</target>
</configuration>
</plugin&g;
3) Setting up the right environment variables to run the Maven 2
The world of Maven is still growing, expanding, and there are lots of unexplored area. Newcomers could be discouraged to use Maven 2 because of certain things which could make them stuck.
Here are some of the snare and pitfall while setting up Maven 2:
1) Creating the "~/.m2" folder in Windows environment
The "~" (tilde) is a common representation of user folder in the UNIX/Linux systems. In Windows, it usually maps to "C:\Documents and Settings\your.username", "C:\Documents and Settings\your.username.DOMAIN", or "C:\Documents and Settings\your.username.DOMAIN.001", etc.
When we try to create a folder in the Window Explorer using the File - New Folder menu, Windows will display a stupid dialog telling you "you must type a filename". Obviously we want to create a folder, so the message should be "you must type a folder name".
After struggling for a while I eventually managed to create the folder using Cygwin's bash shell. Of course this is not solving the problem when you don't have Cygwin installed. And Cygwin brings POSIX personality to NT platform. I believe there are some other way to create such files, like calling the Windows API to create the folder. But I eventually found the simplest thing to create the folder, unzip a folder with that name using your favorite zip tools!
I included the file in the starter kits (uploaded to JUG-ID file repository).
2) Got the message "generics are not supported in -source 1.3"
What has happened right here?! You are sure of using JDK 5 already, but yet you still got this message.
The problem is that the default setting for maven-compiler-plugin is to use the JDK 1.3. So the workaround is to add this to your pom.xml file in the section:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.5</source>
<target>1.5</target>
</configuration>
</plugin&g;
3) Setting up the right environment variables to run the Maven 2
Wednesday, November 29, 2006
Maven within 3 days
I am a bit nervous, coz within 3 days I will be presenting the Maven 2 material at Java Meeting Up (JaMU) 24, on December 2nd, 2006. The session will be held at Sun Microsystem Indonesia office, Wisma Metropolitan, 13th floor.
Being a presenter seems not one of my talents. I have to be really prepared in order not to be nervous. And I still don't know how the situation will be like..
What is relieving is that I'm not alone. Endy will present the Subversion material, so after all it is not a very long session.
Being a presenter seems not one of my talents. I have to be really prepared in order not to be nervous. And I still don't know how the situation will be like..
What is relieving is that I'm not alone. Endy will present the Subversion material, so after all it is not a very long session.
Wednesday, October 25, 2006
Friday, October 20, 2006
Apache 2-on-2: Struts 2 in Maven 2
Since our last 2 CRs has been launched, I haven't had the leisure of working less 10 hours a day. And mostly have to come even on Saturdays or Sundays.
This last 2 days I eventually managed to deploy Apache Struts 2 on Maven 2. The archetype plugin has done a great job in providing base for the application. A version 1.0 of the archetype exists. But the existence of the 2.0.1-SNAPSHOT version caught up my eyes. Later I decided to explore the latter.
It needs around 3 manual downloads for the Maven 2, because the struts2-archetype-starter still use some of the snapshot jars. I believe the version 1.0 is easier and steadier to construct, but what good to use the older version for exploration? If this is for development into production, I'd better use the older and more stable version. But I'm doing this to satisfy my curiousity anyway...
After the successful attempt, I eventually decided to base the CubiClicks not on WebWork 2.2.4, but on the Struts 2. I hope it (CubiClicks) could be released within 6 months..
This last 2 days I eventually managed to deploy Apache Struts 2 on Maven 2. The archetype plugin has done a great job in providing base for the application. A version 1.0 of the archetype exists. But the existence of the 2.0.1-SNAPSHOT version caught up my eyes. Later I decided to explore the latter.
It needs around 3 manual downloads for the Maven 2, because the struts2-archetype-starter still use some of the snapshot jars. I believe the version 1.0 is easier and steadier to construct, but what good to use the older version for exploration? If this is for development into production, I'd better use the older and more stable version. But I'm doing this to satisfy my curiousity anyway...
After the successful attempt, I eventually decided to base the CubiClicks not on WebWork 2.2.4, but on the Struts 2. I hope it (CubiClicks) could be released within 6 months..
Friday, September 15, 2006
Application Server equals Middleware?
When I first encounter the Java 2 Enterprise Edition world, I encountered only application servers. Then some comparison news, publications, etc. would put all the application servers manufacturers as major middleware vendors. Then I had this equation on my mind:
application server == middleware
Then through further readings, experiences, discussions, etc I concluded that:
application server != middleware
They are of different kind level of abstraction!
application server == middleware
Then through further readings, experiences, discussions, etc I concluded that:
application server != middleware
They are of different kind level of abstraction!
Some (Java) middleware parts are running on Java application server. But to make Java Middleware *EQUALS TO* Java Application Server, is a big big mistake that I have made.
The equation just doesn't seem to balance out...
The equation just doesn't seem to balance out...
These are components of middlewares:
Messaging
Integration Platform
Portal
Installation of JBoss: A Trivial 4 Step Task
It really is a "4 step task":
1. Download
2. Unzip it!
3. Setup the JDK environment, if you haven't yet
4. Run the script
It works!
I have to admit that this is, the simplest application server that runs it the first time I installed, whether I'm running it in the Windows environment, Linux or Solaris boxes.
1. Download
Go to http://prdownloads.sourceforge.net/jboss/jboss-4.0.4.GA.zip?download
Choose your favorite sourceforge download site. I recommend download the zip version, as it is simpler to handle in multiplatform environment (my personal opinion).
Warning: 75,587kb download!
2. Unzip It!
Assuming that you are running a Windows environment, it is quite trivial task to install JBoss Application Server.
Run your favorite compression tools, unzip the jboss-4.0.4.GA.zip into your folder application server, e.g. c:\opt\env\jboss-4.0.4.GA
Then check that you have these foldere under you "c:\opt\jboss-4.0.4.GA" folder:
If you find these folders, everything seems to be ok this far.
3. Setup the JDK environment
This steps is required when you haven't done it yet. It is kind of setting the JAVA_HOME, CLASSPATH environment variables etc.
I would suggest to put it into a batch file or shell script for easier reuse. In my Windows environment, I would make c:\opt\env\set5.bat for setting up JDK 5, and c:\opt\env\set4.bat for setting up JDK 1.4.2.
The file set5.bat should contain at least:
set JAVA_HOME=c:\opt\env\jdk1.5.0_07
set JBOSS_HOME=c:\opt\env\jboss-4.0.4.GA
set CLASSPATH=%JAVA_HOME%\lib;%JAVA_HOME%\jre\lib;%JAVA_HOME%\jre\lib\ext;.
set PATH=%JAVA_HOME%\bin;%PATH%
Of course you have to tailor it to suit your environment settings.
4. Run the script
Run your script, open the command prompt and type this:
c:\>%JBOSS_HOME%\bin\run
If your command line shows message like these, than congratulations! You have successfully installed the JBoss Application Server. If this is your first time installing an Java application server, welcome to the new world of Java Enterprise Edition environment!
===============================================================================
.
JBoss Bootstrap Environment
.
JBOSS_HOME: c:\opt\env\jboss-4.0.4.GA\bin\\..
.
JAVA: c:\opt\env\jdk1.5.0_07\bin\java
.
JAVA_OPTS: -Dprogram.name=run.bat -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcIn
terval=3600000
.
CLASSPATH: c:\opt\env\jdk1.5.0_07\lib\tools.jar;d:\opt\env\jboss-4.0.4.GA\bin\\run.jar
.
===============================================================================
.
21:37:13,093 INFO [Server] Starting JBoss (MX MicroKernel)...
21:37:13,125 INFO [Server] Release ID: JBoss [Zion] 4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)
21:37:13,171 INFO [Server] Home Dir: c:\opt\env\jboss-4.0.4.GA
21:37:13,171 INFO [Server] Home URL: file:/c:/opt/env/jboss-4.0.4.GA/
21:37:13,171 INFO [Server] Patch URL: null
21:37:13,171 INFO [Server] Server Name: default
21:37:13,171 INFO [Server] Server Home Dir: D:\opt\env\jboss-4.0.4.GA\server\default
21:37:13,171 INFO [Server] Server Home URL: file:/D:/opt/env/jboss-4.0.4.GA/server/default/
21:37:13,171 INFO [Server] Server Log Dir: D:\opt\env\jboss-4.0.4.GA\server\default\log
21:37:13,171 INFO [Server] Server Temp Dir: D:\opt\env\jboss-4.0.4.GA\server\default\tmp
21:37:13,171 INFO [Server] Root Deployment Filename: jboss-service.xml
21:37:15,453 INFO [ServerInfo] Java version: 1.5.0_07,Sun Microsystems Inc.
21:37:15,453 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_07-b03,Sun Microsystems Inc.
21:37:15,453 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
21:37:17,062 INFO [Server] Core system initialized
21:37:29,828 INFO [WebService] Using RMI server codebase: http://daniel:8083/
21:37:29,843 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
21:37:32,031 INFO [NamingService] JNDI bootstrap JNP=/0.0.0.0:1099, RMI=/0.0.0.0:1098, backlog=50, no client SocketFact
ory, Server SocketFactory=class org.jboss.net.sockets.DefaultSocketFactory
21:37:47,703 INFO [Embedded] Catalina naming disabled
21:37:47,750 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rul
e set.
21:37:47,765 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rul
e set.
21:37:49,687 INFO [Http11BaseProtocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
21:37:49,687 INFO [Catalina] Initialization processed in 1922 ms
21:37:49,687 INFO [StandardService] Starting service jboss.web
21:37:49,703 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.17
21:37:49,734 INFO [StandardHost] XML validation disabled
21:37:49,765 INFO [Catalina] Server startup in 78 ms
21:37:50,750 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
21:37:51,828 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
21:37:58,656 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
21:38:02,500 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp9122jbossws-exp.war/
21:38:02,875 INFO [SubscriptionManager] Bound event dispatcher to java:/EventDispatcher
21:38:03,937 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-ht
tpil.war/
21:38:11,000 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-conso
le.war/
21:38:14,875 INFO [MailService] Mail Service bound to java:/Mail
21:38:15,625 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.
rar
21:38:15,687 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
21:38:15,781 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
21:38:15,843 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
21:38:16,015 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
21:38:16,093 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
21:38:19,562 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=D
efaultDS' to JNDI name 'java:DefaultDS'
21:38:20,109 INFO [A] Bound to JNDI name: queue/A
21:38:20,109 INFO [B] Bound to JNDI name: queue/B
21:38:20,109 INFO [C] Bound to JNDI name: queue/C
21:38:20,109 INFO [D] Bound to JNDI name: queue/D
21:38:20,125 INFO [ex] Bound to JNDI name: queue/ex
21:38:20,140 INFO [testTopic] Bound to JNDI name: topic/testTopic
21:38:20,140 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
21:38:20,140 INFO [testDurableTopic] Bound to JND
I name: topic/testDurableTopic
21:38:20,140 INFO [testQueue] Bound to JNDI name: queue/testQueue
21:38:20,531 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
21:38:20,562 INFO [DLQ] Bound to JNDI name: queue/DLQ
21:38:20,781 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding
,name=JmsXA' to JNDI name 'java:JmsXA'
21:38:20,984 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
21:38:21,515 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
21:38:22,000 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
21:38:22,015 INFO [JkMain] Jk running ID=0 time=0/62 config=null
21:38:22,031 INFO [Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)] Started i
n 1m:8s:860ms
1. Download
2. Unzip it!
3. Setup the JDK environment, if you haven't yet
4. Run the script
It works!
I have to admit that this is, the simplest application server that runs it the first time I installed, whether I'm running it in the Windows environment, Linux or Solaris boxes.
1. Download
Go to http://prdownloads.sourceforge.net/jboss/jboss-4.0.4.GA.zip?download
Choose your favorite sourceforge download site. I recommend download the zip version, as it is simpler to handle in multiplatform environment (my personal opinion).
Warning: 75,587kb download!
2. Unzip It!
Assuming that you are running a Windows environment, it is quite trivial task to install JBoss Application Server.
Run your favorite compression tools, unzip the jboss-4.0.4.GA.zip into your folder application server, e.g. c:\opt\env\jboss-4.0.4.GA
Then check that you have these foldere under you "c:\opt\jboss-4.0.4.GA" folder:
- bin
- client
- docs
- lib
- server
If you find these folders, everything seems to be ok this far.
3. Setup the JDK environment
This steps is required when you haven't done it yet. It is kind of setting the JAVA_HOME, CLASSPATH environment variables etc.
I would suggest to put it into a batch file or shell script for easier reuse. In my Windows environment, I would make c:\opt\env\set5.bat for setting up JDK 5, and c:\opt\env\set4.bat for setting up JDK 1.4.2.
The file set5.bat should contain at least:
set JAVA_HOME=c:\opt\env\jdk1.5.0_07
set JBOSS_HOME=c:\opt\env\jboss-4.0.4.GA
set CLASSPATH=%JAVA_HOME%\lib;%JAVA_HOME%\jre\lib;%JAVA_HOME%\jre\lib\ext;.
set PATH=%JAVA_HOME%\bin;%PATH%
Of course you have to tailor it to suit your environment settings.
4. Run the script
Run your script, open the command prompt and type this:
c:\>%JBOSS_HOME%\bin\run
If your command line shows message like these, than congratulations! You have successfully installed the JBoss Application Server. If this is your first time installing an Java application server, welcome to the new world of Java Enterprise Edition environment!
===============================================================================
.
JBoss Bootstrap Environment
.
JBOSS_HOME: c:\opt\env\jboss-4.0.4.GA\bin\\..
.
JAVA: c:\opt\env\jdk1.5.0_07\bin\java
.
JAVA_OPTS: -Dprogram.name=run.bat -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcIn
terval=3600000
.
CLASSPATH: c:\opt\env\jdk1.5.0_07\lib\tools.jar;d:\opt\env\jboss-4.0.4.GA\bin\\run.jar
.
===============================================================================
.
21:37:13,093 INFO [Server] Starting JBoss (MX MicroKernel)...
21:37:13,125 INFO [Server] Release ID: JBoss [Zion] 4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)
21:37:13,171 INFO [Server] Home Dir: c:\opt\env\jboss-4.0.4.GA
21:37:13,171 INFO [Server] Home URL: file:/c:/opt/env/jboss-4.0.4.GA/
21:37:13,171 INFO [Server] Patch URL: null
21:37:13,171 INFO [Server] Server Name: default
21:37:13,171 INFO [Server] Server Home Dir: D:\opt\env\jboss-4.0.4.GA\server\default
21:37:13,171 INFO [Server] Server Home URL: file:/D:/opt/env/jboss-4.0.4.GA/server/default/
21:37:13,171 INFO [Server] Server Log Dir: D:\opt\env\jboss-4.0.4.GA\server\default\log
21:37:13,171 INFO [Server] Server Temp Dir: D:\opt\env\jboss-4.0.4.GA\server\default\tmp
21:37:13,171 INFO [Server] Root Deployment Filename: jboss-service.xml
21:37:15,453 INFO [ServerInfo] Java version: 1.5.0_07,Sun Microsystems Inc.
21:37:15,453 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_07-b03,Sun Microsystems Inc.
21:37:15,453 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
21:37:17,062 INFO [Server] Core system initialized
21:37:29,828 INFO [WebService] Using RMI server codebase: http://daniel:8083/
21:37:29,843 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
21:37:32,031 INFO [NamingService] JNDI bootstrap JNP=/0.0.0.0:1099, RMI=/0.0.0.0:1098, backlog=50, no client SocketFact
ory, Server SocketFactory=class org.jboss.net.sockets.DefaultSocketFactory
21:37:47,703 INFO [Embedded] Catalina naming disabled
21:37:47,750 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rul
e set.
21:37:47,765 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rul
e set.
21:37:49,687 INFO [Http11BaseProtocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
21:37:49,687 INFO [Catalina] Initialization processed in 1922 ms
21:37:49,687 INFO [StandardService] Starting service jboss.web
21:37:49,703 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.17
21:37:49,734 INFO [StandardHost] XML validation disabled
21:37:49,765 INFO [Catalina] Server startup in 78 ms
21:37:50,750 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
21:37:51,828 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
21:37:58,656 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
21:38:02,500 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp9122jbossws-exp.war/
21:38:02,875 INFO [SubscriptionManager] Bound event dispatcher to java:/EventDispatcher
21:38:03,937 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-ht
tpil.war/
21:38:11,000 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-conso
le.war/
21:38:14,875 INFO [MailService] Mail Service bound to java:/Mail
21:38:15,625 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.
rar
21:38:15,687 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
21:38:15,781 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
21:38:15,843 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
21:38:16,015 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
21:38:16,093 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
21:38:19,562 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=D
efaultDS' to JNDI name 'java:DefaultDS'
21:38:20,109 INFO [A] Bound to JNDI name: queue/A
21:38:20,109 INFO [B] Bound to JNDI name: queue/B
21:38:20,109 INFO [C] Bound to JNDI name: queue/C
21:38:20,109 INFO [D] Bound to JNDI name: queue/D
21:38:20,125 INFO [ex] Bound to JNDI name: queue/ex
21:38:20,140 INFO [testTopic] Bound to JNDI name: topic/testTopic
21:38:20,140 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
21:38:20,140 INFO [testDurableTopic] Bound to JND
I name: topic/testDurableTopic
21:38:20,140 INFO [testQueue] Bound to JNDI name: queue/testQueue
21:38:20,531 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
21:38:20,562 INFO [DLQ] Bound to JNDI name: queue/DLQ
21:38:20,781 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding
,name=JmsXA' to JNDI name 'java:JmsXA'
21:38:20,984 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
21:38:21,515 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
21:38:22,000 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
21:38:22,015 INFO [JkMain] Jk running ID=0 time=0/62 config=null
21:38:22,031 INFO [Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)] Started i
n 1m:8s:860ms
Java is Open: A WebLogic sample on the Sun Developer site
Well, quite surprising that the sample code to call an EJB in the Sun Developer's Network was using the BEA WebLogic implementation code. I thought that Sun wouldnot allow it. But I was wrong. That's why we call it: Java is open.
Application Server equals Middleware?
When I first encounter the Java 2 Enterprise Edition world, I encountered only application servers. Then some comparison news, publications, etc. would put all the application servers manufacturers as major middleware vendors. Then I had this equation on my mind:
application server == middleware
Then through further readings, experiences, discussions, etc I concluded that:
application server != middleware
They are of different kind level of abstraction!
application server == middleware
Then through further readings, experiences, discussions, etc I concluded that:
application server != middleware
They are of different kind level of abstraction!
Some (Java) middleware parts are running on Java application server. But to make Java Middleware *EQUALS TO* Java Application Server, is a big big mistake that I have made.
The equation just doesn't seem to balance out...
The equation just doesn't seem to balance out...
These are components of middlewares:
Messaging
Integration Platform
Portal
Thursday, September 14, 2006
Installation of JBoss: A Trivial 4 Step Task
It really is a "4 step task":
1. Download
2. Unzip it!
3. Setup the JDK environment, if you haven't yet
4. Run the script
It works!
I have to admit that this is, the simplest application server that runs it the first time I installed, whether I'm running it in the Windows environment, Linux or Solaris boxes.
1. Download
Go to http://prdownloads.sourceforge.net/jboss/jboss-4.0.4.GA.zip?download
Choose your favorite sourceforge download site. I recommend download the zip version, as it is simpler to handle in multiplatform environment (my personal opinion).
Warning: 75,587kb download!
2. Unzip It!
Assuming that you are running a Windows environment, it is quite trivial task to install JBoss Application Server.
Run your favorite compression tools, unzip the jboss-4.0.4.GA.zip into your folder application server, e.g. c:\opt\env\jboss-4.0.4.GA
Then check that you have these foldere under you "c:\opt\jboss-4.0.4.GA" folder:
Also there exist some files (copyright.txt), jar-version.xml, lgpl.html, readme.html, readme_j2ee.html).
If you find these folders, everything seems to be ok this far.
3. Setup the JDK environment
This steps is required when you haven't done it yet. It is kind of setting the JAVA_HOME, CLASSPATH environment variables etc.
I would suggest to put it into a batch file or shell script for easier reuse. In my Windows environment, I would make c:\opt\env\set5.bat for setting up JDK 5, and c:\opt\env\set4.bat for setting up JDK 1.4.2.
The file set5.bat should contain at least:
set JAVA_HOME=c:\opt\env\jdk1.5.0_07
set JBOSS_HOME=c:\opt\env\jboss-4.0.4.GA
set CLASSPATH=%JAVA_HOME%\lib;%JAVA_HOME%\jre\lib;%JAVA_HOME%\jre\lib\ext;.
set PATH=%JAVA_HOME%\bin;%PATH%
Of course you have to tailor it to suit your environment settings.
4. Run the script
Run your script, open the command prompt and type this:
c:\>%JBOSS_HOME%\bin\run
If your command line shows message like these, than congratulations! You have successfully installed the JBoss Application Server. If this is your first time installing an Java application server, welcome to the new world of Java Enterprise Edition environment!
===============================================================================
.
JBoss Bootstrap Environment
.
JBOSS_HOME: c:\opt\env\jboss-4.0.4.GA\bin\\..
.
JAVA: c:\opt\env\jdk1.5.0_07\bin\java
.
JAVA_OPTS: -Dprogram.name=run.bat -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcIn
terval=3600000
.
CLASSPATH: c:\opt\env\jdk1.5.0_07\lib\tools.jar;d:\opt\env\jboss-4.0.4.GA\bin\\run.jar
.
===============================================================================
.
21:37:13,093 INFO [Server] Starting JBoss (MX MicroKernel)...
21:37:13,125 INFO [Server] Release ID: JBoss [Zion] 4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)
21:37:13,171 INFO [Server] Home Dir: c:\opt\env\jboss-4.0.4.GA
21:37:13,171 INFO [Server] Home URL: file:/c:/opt/env/jboss-4.0.4.GA/
21:37:13,171 INFO [Server] Patch URL: null
21:37:13,171 INFO [Server] Server Name: default
21:37:13,171 INFO [Server] Server Home Dir: D:\opt\env\jboss-4.0.4.GA\server\default
21:37:13,171 INFO [Server] Server Home URL: file:/D:/opt/env/jboss-4.0.4.GA/server/default/
21:37:13,171 INFO [Server] Server Log Dir: D:\opt\env\jboss-4.0.4.GA\server\default\log
21:37:13,171 INFO [Server] Server Temp Dir: D:\opt\env\jboss-4.0.4.GA\server\default\tmp
21:37:13,171 INFO [Server] Root Deployment Filename: jboss-service.xml
21:37:15,453 INFO [ServerInfo] Java version: 1.5.0_07,Sun Microsystems Inc.
21:37:15,453 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_07-b03,Sun Microsystems Inc.
21:37:15,453 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
21:37:17,062 INFO [Server] Core system initialized
21:37:29,828 INFO [WebService] Using RMI server codebase: http://daniel:8083/
21:37:29,843 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
21:37:32,031 INFO [NamingService] JNDI bootstrap JNP=/0.0.0.0:1099, RMI=/0.0.0.0:1098, backlog=50, no client SocketFact
ory, Server SocketFactory=class org.jboss.net.sockets.DefaultSocketFactory
21:37:47,703 INFO [Embedded] Catalina naming disabled
21:37:47,750 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rul
e set.
21:37:47,765 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rul
e set.
21:37:49,687 INFO [Http11BaseProtocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
21:37:49,687 INFO [Catalina] Initialization processed in 1922 ms
21:37:49,687 INFO [StandardService] Starting service jboss.web
21:37:49,703 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.17
21:37:49,734 INFO [StandardHost] XML validation disabled
21:37:49,765 INFO [Catalina] Server startup in 78 ms
21:37:50,750 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
21:37:51,828 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
21:37:58,656 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
21:38:02,500 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp9122jbossws-exp.war/
21:38:02,875 INFO [SubscriptionManager] Bound event dispatcher to java:/EventDispatcher
21:38:03,937 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-ht
tpil.war/
21:38:11,000 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-conso
le.war/
21:38:14,875 INFO [MailService] Mail Service bound to java:/Mail
21:38:15,625 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.
rar
21:38:15,687 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
21:38:15,781 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
21:38:15,843 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
21:38:16,015 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
21:38:16,093 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
21:38:19,562 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=D
efaultDS' to JNDI name 'java:DefaultDS'
21:38:20,109 INFO [A] Bound to JNDI name: queue/A
21:38:20,109 INFO [B] Bound to JNDI name: queue/B
21:38:20,109 INFO [C] Bound to JNDI name: queue/C
21:38:20,109 INFO [D] Bound to JNDI name: queue/D
21:38:20,125 INFO [ex] Bound to JNDI name: queue/ex
21:38:20,140 INFO [testTopic] Bound to JNDI name: topic/testTopic
21:38:20,140 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
21:38:20,140 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
21:38:20,140 INFO [testQueue] Bound to JNDI name: queue/testQueue
21:38:20,531 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
21:38:20,562 INFO [DLQ] Bound to JNDI name: queue/DLQ
21:38:20,781 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding
,name=JmsXA' to JNDI name 'java:JmsXA'
21:38:20,984 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
21:38:21,515 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
21:38:22,000 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
21:38:22,015 INFO [JkMain] Jk running ID=0 time=0/62 config=null
21:38:22,031 INFO [Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)] Started i
n 1m:8s:860ms
1. Download
2. Unzip it!
3. Setup the JDK environment, if you haven't yet
4. Run the script
It works!
I have to admit that this is, the simplest application server that runs it the first time I installed, whether I'm running it in the Windows environment, Linux or Solaris boxes.
1. Download
Go to http://prdownloads.sourceforge.net/jboss/jboss-4.0.4.GA.zip?download
Choose your favorite sourceforge download site. I recommend download the zip version, as it is simpler to handle in multiplatform environment (my personal opinion).
Warning: 75,587kb download!
2. Unzip It!
Assuming that you are running a Windows environment, it is quite trivial task to install JBoss Application Server.
Run your favorite compression tools, unzip the jboss-4.0.4.GA.zip into your folder application server, e.g. c:\opt\env\jboss-4.0.4.GA
Then check that you have these foldere under you "c:\opt\jboss-4.0.4.GA" folder:
- bin
- client
- docs
- lib
- server
Also there exist some files (copyright.txt), jar-version.xml, lgpl.html, readme.html, readme_j2ee.html).
If you find these folders, everything seems to be ok this far.
3. Setup the JDK environment
This steps is required when you haven't done it yet. It is kind of setting the JAVA_HOME, CLASSPATH environment variables etc.
I would suggest to put it into a batch file or shell script for easier reuse. In my Windows environment, I would make c:\opt\env\set5.bat for setting up JDK 5, and c:\opt\env\set4.bat for setting up JDK 1.4.2.
The file set5.bat should contain at least:
set JAVA_HOME=c:\opt\env\jdk1.5.0_07
set JBOSS_HOME=c:\opt\env\jboss-4.0.4.GA
set CLASSPATH=%JAVA_HOME%\lib;%JAVA_HOME%\jre\lib;%JAVA_HOME%\jre\lib\ext;.
set PATH=%JAVA_HOME%\bin;%PATH%
Of course you have to tailor it to suit your environment settings.
4. Run the script
Run your script, open the command prompt and type this:
c:\>%JBOSS_HOME%\bin\run
If your command line shows message like these, than congratulations! You have successfully installed the JBoss Application Server. If this is your first time installing an Java application server, welcome to the new world of Java Enterprise Edition environment!
===============================================================================
.
JBoss Bootstrap Environment
.
JBOSS_HOME: c:\opt\env\jboss-4.0.4.GA\bin\\..
.
JAVA: c:\opt\env\jdk1.5.0_07\bin\java
.
JAVA_OPTS: -Dprogram.name=run.bat -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcIn
terval=3600000
.
CLASSPATH: c:\opt\env\jdk1.5.0_07\lib\tools.jar;d:\opt\env\jboss-4.0.4.GA\bin\\run.jar
.
===============================================================================
.
21:37:13,093 INFO [Server] Starting JBoss (MX MicroKernel)...
21:37:13,125 INFO [Server] Release ID: JBoss [Zion] 4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)
21:37:13,171 INFO [Server] Home Dir: c:\opt\env\jboss-4.0.4.GA
21:37:13,171 INFO [Server] Home URL: file:/c:/opt/env/jboss-4.0.4.GA/
21:37:13,171 INFO [Server] Patch URL: null
21:37:13,171 INFO [Server] Server Name: default
21:37:13,171 INFO [Server] Server Home Dir: D:\opt\env\jboss-4.0.4.GA\server\default
21:37:13,171 INFO [Server] Server Home URL: file:/D:/opt/env/jboss-4.0.4.GA/server/default/
21:37:13,171 INFO [Server] Server Log Dir: D:\opt\env\jboss-4.0.4.GA\server\default\log
21:37:13,171 INFO [Server] Server Temp Dir: D:\opt\env\jboss-4.0.4.GA\server\default\tmp
21:37:13,171 INFO [Server] Root Deployment Filename: jboss-service.xml
21:37:15,453 INFO [ServerInfo] Java version: 1.5.0_07,Sun Microsystems Inc.
21:37:15,453 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_07-b03,Sun Microsystems Inc.
21:37:15,453 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
21:37:17,062 INFO [Server] Core system initialized
21:37:29,828 INFO [WebService] Using RMI server codebase: http://daniel:8083/
21:37:29,843 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
21:37:32,031 INFO [NamingService] JNDI bootstrap JNP=/0.0.0.0:1099, RMI=/0.0.0.0:1098, backlog=50, no client SocketFact
ory, Server SocketFactory=class org.jboss.net.sockets.DefaultSocketFactory
21:37:47,703 INFO [Embedded] Catalina naming disabled
21:37:47,750 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rul
e set.
21:37:47,765 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rul
e set.
21:37:49,687 INFO [Http11BaseProtocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
21:37:49,687 INFO [Catalina] Initialization processed in 1922 ms
21:37:49,687 INFO [StandardService] Starting service jboss.web
21:37:49,703 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.17
21:37:49,734 INFO [StandardHost] XML validation disabled
21:37:49,765 INFO [Catalina] Server startup in 78 ms
21:37:50,750 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
21:37:51,828 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
21:37:58,656 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
21:38:02,500 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp9122jbossws-exp.war/
21:38:02,875 INFO [SubscriptionManager] Bound event dispatcher to java:/EventDispatcher
21:38:03,937 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-ht
tpil.war/
21:38:11,000 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-conso
le.war/
21:38:14,875 INFO [MailService] Mail Service bound to java:/Mail
21:38:15,625 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.
rar
21:38:15,687 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
21:38:15,781 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
21:38:15,843 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
21:38:16,015 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
21:38:16,093 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
21:38:19,562 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=D
efaultDS' to JNDI name 'java:DefaultDS'
21:38:20,109 INFO [A] Bound to JNDI name: queue/A
21:38:20,109 INFO [B] Bound to JNDI name: queue/B
21:38:20,109 INFO [C] Bound to JNDI name: queue/C
21:38:20,109 INFO [D] Bound to JNDI name: queue/D
21:38:20,125 INFO [ex] Bound to JNDI name: queue/ex
21:38:20,140 INFO [testTopic] Bound to JNDI name: topic/testTopic
21:38:20,140 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
21:38:20,140 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
21:38:20,140 INFO [testQueue] Bound to JNDI name: queue/testQueue
21:38:20,531 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
21:38:20,562 INFO [DLQ] Bound to JNDI name: queue/DLQ
21:38:20,781 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding
,name=JmsXA' to JNDI name 'java:JmsXA'
21:38:20,984 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
21:38:21,515 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
21:38:22,000 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
21:38:22,015 INFO [JkMain] Jk running ID=0 time=0/62 config=null
21:38:22,031 INFO [Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)] Started i
n 1m:8s:860ms
Subscribe to:
Posts (Atom)