tikal-development Mailing List for Tikal

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Hi ,

Same as Eclipse Software Update.

Windows --> Preferences --> Install/Update --> Proxy Setting

Itai

Hi,

How can I configure http proxy setting for TUM to connect with the update site?  I'm looking forward to your response.  Thanks.

Regards,

Tony Lam

GumTree Project Lead

Australian Nuclear Science and Technology Organisation

-----Original Message-----
From: Lior Kanfi [mailto:li...@ti...] 
Sent: Sunday, February 05, 2006 10:09 PM
To: Yanai Franchi
Subject: RE: [Fwd: Follow up on meeting in Ethos]

to mailing list.
On Fri, 2006-02-03 at 09:47 +0200, Yanai Franchi wrote:
> Hi,
> 
> Please note that Spring2 can be integrated with EJB3. You can inject
> POJO into EJB3 services using Spring2(and its AspectJ integration).
> The code looks much cleaner than the traditional Spring1.2.x/EJB2.1
> integration (The "getBean" from the EJB is both "Spring intrusive"
> eliminating the dependency injection) and the way we delegate from an
> EJB to a POJO service ("Buisness-interface" pattern). 
> 
>  
> 
> Please have a look on the following urls for some example:
> 
> http://www.jroller.com/page/malbari?entry=javaee_5_spring_2_and.
> 
>  
> 
>
http://chris-richardson.blog-city.com/the_ejb_cult_part_3__integrating_sprin
g_and_ejb_30_dependency_injection.htm
> 
>  
> 
>  
> 
> Though, it is only on implemented Spring2 and JEE 1.5 (both
> implementations not released yet), we may consider add these materials
> into our Spring course (the EJB chapter).
> 
>  
> 
> Thank you,
> 
> Yanai
> 
>  
> 
>                                    
> ______________________________________________________________________
> From: Lior Kanfi [mailto:li...@ti...] 
> Sent: Tuesday, January 31, 2006 3:32 PM
> To: Yanai Franchi
> Subject: [Fwd: Follow up on meeting in Ethos]
> 
> 
>  
> 
> Can you send him the slide about EJB3 vs. Spring, and also explain him
> how can he use CORBA in JBoss environment.
> 
> Thank you,
> Lior
> -------- Forwarded Message --------
> From: Eran Roseberg <era...@gm...>
> To: Li...@ti...
> Subject: Follow up on meeting in Ethos
> Date: Tue, 31 Jan 2006 09:52:24 +0200
> 
> Hi Lior, Thank you for the enriching presentation.   Could you please
> send me the presentation about EJB 3.0 and Spring, that you mentioned,
> and clarify the issue of CORBA support with Spring.   Regards,   Eran
> Roseberg, Ethos Networks.
> 
> -- 
> Lior Kanfi <li...@ti...>
> Tikal 
> 
> 
> 
>  
> 
> 
-- 
Lior Kanfi <li...@ti...>
Tikal

Great info... (really helps)
Thanks

On Sun, 2006-02-05 at 11:04 +0200, Ronen Naor wrote:
> If you have several web projects in Maven 2, and all of them use a g
> group of identical JSP pages, you can use the derived war concept to
> solve the problem.
> 
> The idea is very simple, instead of writing in your POM, a dependency
> to a JAR, like you usually write, you write a dependency to your
> shared common WAR.
> 
> For example: 
> 
> <dependency>
> 
>       <groupId>my-company</groupId>
> 
>       <artifactId>common-web</artifactId>
> 
>       <version>1.0-SNAPSHOT</version>        
> 
>       <type>war</type>
> 
> </dependency>  
> 
> The common war will be overlaid on the target project war. 
> 
> In case you need to exclude files from the common war, you can add
> exclusion instruction to your POM, for example:
> 
>             <plugins>
> 
>                         <plugin>
> 
> 
> <artifactId>tikal-maven-war-plugin</artifactId>
> 
> 
> <groupId>com.tikal.maven.plugins</groupId>
> 
>                                                 <configuration>
> 
> 
> <dependentWarExcludes>**/*</dependentWarExcludes>
>                                                 
> 
>                                                 </configuration>
> 
>                         </plugin>
> 
>             </plugins>
> 
>                         
> 
> 

If you have several web projects in Maven 2, and all of them use a g
group of identical JSP pages, you can use the derived war concept to
solve the problem.

The idea is very simple, instead of writing in your POM, a dependency to
a JAR, like you usually write, you write a dependency to your shared
common WAR.

For example: 

<dependency>

      <groupId>my-company</groupId>

      <artifactId>common-web</artifactId>

      <version>1.0-SNAPSHOT</version>        

      <type>war</type>

</dependency>  

The common war will be overlaid on the target project war. 

In case you need to exclude files from the common war, you can add
exclusion instruction to your POM, for example:

            <plugins>

                        <plugin>

<artifactId>tikal-maven-war-plugin</artifactId>

<groupId>com.tikal.maven.plugins</groupId>

                                                <configuration>

<dependentWarExcludes>**/*</dependentWarExcludes>

                                                </configuration>

                        </plugin>

            </plugins>

Ahh... Matt Raible...
Its nothing more than nice (!). Once you want to do anything that is not
default -- you're f#$ked...
I wouldn't waste time on it... (unless you're reading his book "Spring
Live", and need to follow the examples).

On Tue, 2006-01-31 at 10:27 -0800, Arik Levin (Tikal) wrote:

> I have found some new projects (to me anyway) 
> The first 2 projects are for quick kickoff for web app
> like Spring JSF etc... + hibernate 
> 
> http://appfuse.dev.java.net
> http://equinox.dev.java.net    
> 
> The last one is about web app wizard impl. Currently
> integrated with Struts and JSF (Spring support will
> come later) 
>    
> http://www.superinterface.com/easywizard.htm
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Tikal-development mailing list
> Tik...@li...
> https://lists.sourceforge.net/lists/listinfo/tikal-development

I have found some new projects (to me anyway) 
The first 2 projects are for quick kickoff for web app
like Spring JSF etc... + hibernate 

http://appfuse.dev.java.net
http://equinox.dev.java.net    

The last one is about web app wizard impl. Currently
integrated with Struts and JSF (Spring support will
come later) 

http://www.superinterface.com/easywizard.htm

  _____  

From: Lior Kanfi [mailto:li...@ti...] 
Sent: Wednesday, January 25, 2006 5:23 PM
To: Yanai Franchi
Subject: Re: Which logging framework to use ?

to mailing list.

On Wed, 2006-01-25 at 10:41 +0200, Yanai Franchi wrote:

Hi,

Following my conversation with Rafi, I did a small research regarding a
logging framework. Specifically, I checked the following loging frameworks:

1.      Log4J

2.      Apache-commons logging

3.      JDK logging

4.      SLF4J.

I'll start with the bottom line. Assuming we do NOT need an abstraction
bridging between different logging implementations, my recommendation is to
use Log4J. 

Why not  commons-logging and what is the alternative to commons-logging?

If you want to know about the actual problems commons-logging causes and why
using class loader hacks to implement a dynamic discovery process is
generally a bad idea, read the article Taxonomy of class loader
<http://www.qos.ch/logging/classloader.jsp>  problems encountered when using
Jakarta Commons Logging.

Commons loggiing solves a theoretical problem (I am using the word
'theoretical' here, since almost everyone that uses it, uses Log4J as the
logging implementation anyway), it is just unfortunate that it became so
popular so fast.

However, there are alternatives. If you really need to use a Logging facade
(which I do not think you do), you should try out Simple Logging Facade for
Java <http://www.slf4j.org/>  (SLF4J), which uses static (compile time)
binding of the Logging implementation, e.g. avoids the above stated
problems. They even have a gradual migration path
<http://www.slf4j.org/manual.html#gradual>  from Commons Logging. 

Why shouldn't we use Java Util Logging (JUL)?

While Log4j and JUL are almost conceptually identical, they do differ in
terms of functionality. Their difference can be summarized as, "Whatever JUL
can do, Log4j can also do - and more." They differ most in the areas of
useful appender/handler implementations, useful formatter/layout
implementations, and configuration flexibility. 

JUL contains four concrete handler implementations, while Log4j includes
over a dozen appender implementations. JUL's handlers are adequate for basic
logging - they allow you to write to a buffer, to a console, to a socket,
and to a file. Log4j's appenders, on the other hand, probably cover every
logging output destination that you could think of. They can write to an NT
event log or a Unix syslog, or even send e-mail. 

JUL contains two formatter classes: the XMLFormatter and SimpleFormatter.
Log4j includes the corresponding layouts: the XMLLayout and SimpleLayout.
Log4j also offers the TTCCLayout, which formats LoggingEvents into
content-rich strings, and the HTMLLayout, which formats LoggingEvents as an
HTML table. 

While the TTCCLayout and HTMLLayout are useful, Log4j really pulls ahead of
JUL in the formatter/handler arena because of the PatternLayout.
PatternLayout instances can be configured with an enormous amount of
flexibility via string conversion patterns, similar to the conversion
patterns used by the printf function in C. In PatternLayout conversion
patterns, special conversion characters are used to specify the information
included in layout's formatted output. For example, "%t" is used to specify
the name of the thread that started the logging of the message; "%C" is used
to specify the name of the class of the object that started the logging of
the message; and "%m" specifies the message. "%t: %m" would result in output
such as "main thread: This is my message." "%C - %t: %m" would result in
output such as " org.nrdc.My-Class - main thread: This is my message." The
Pattern-Layout is extremely useful, and JUL's two formatter classes don't
come anywhere near to matching its versatility. It's not uncommon for JUL
users to write their own custom formatter class, whereas most Log4j users
generally need to just learn how 

Log4j allows developers to associate layout instances with appender
instances, and configure layouts on a per-instance basis. This includes
PatternLayout instances - you can set the conversion pattern each uses in
the configuration file. During development, it usually isn't a problem to
recompile an application to adjust its logging configuration; after
deployment, however, you may want to be able to tweak or even completely
reconfigure your application's logging without recompiling. In that case,
Log4j offers more flexibility, especially pre-Tiger JDK.

Log4j provides a lot of functionality that JUL lacks, although JUL is
catching up. JUL could definitely be extended to do what Log4j does - you
could write more handlers, reimplement the PatternLayout for JUL, and
upgrade JUL's configuration mechanism, all without extreme difficulty. But
why do that when Log4j has had those features for years? 

GUI for Log4J

There are several GUI on top of Log4J we can use:

1.      Lumbermill - http://traxel.com/lumbermill/ - Lumbermill is a Swing
log processing and distribution system for Log4j and Sun JSR-47
(java.util.logging). The Lumbermill project is hosted on SourceForge
<http://sourceforge.net/projects/lumbermill/> .

2.      Chansaw - http://logging.apache.org/log4j/docs/chainsaw.html - It's
a GUI-based Log viewer.

Thank you,

Yanai

-- 
Lior Kanfi <li...@ti...>
Tikal 

http://www.infonoia.com/en/content.jsp?d=inf.05.07

  _____  

From: Lior Kanfi [mailto:li...@ti...] 
Sent: Friday, January 20, 2006 6:26 PM
To: Yanai Franchi
Subject: Re: add this one to your log4j.xml file in order to print
jdbcparateres

Please, post it to tik...@li...,
<mailto:tik...@li....>  before posting subscribe
to the list the sourceforge site.

On Thu, 2006-01-19 at 12:49 +0200, Yanai Franchi wrote: 

   <category name="org.hibernate.type">

      <priority value="DEBUG"/>

  </category>

-- 
Lior Kanfi <li...@ti...>
Tikal 

On Thu, 2006-01-19 at 09:22 +0200, Lior Kanfi wrote:

> -------- Forwarded Message --------
> From: MySQL Network <sup...@my...>
> To: Lior Kanfi <li...@ti...>
> Subject: MySQL Tip Of The Month, Jan 2006: Restoring Data Since Last
> Backup
> Date: Wed, 18 Jan 2006 19:42:33 +0100
> 
> 
> MySQL Tip Of The Month
> January 2006: Restoring Data Since Last Backup
> ==============================================
> 
> Even if you're running backups daily with a utility like mysqldump, 
> there's still the problem of restoring data created or changed after 
> the last backup.  However, by using a binary log, you can may be able 
> to recover interim data.  
> 
> 
> Setting Up Binary Logging
> 
> Binary logging will record all transactions executed and attempted 
> on the server.   The mysqlbinlog utility can be used to extract the 
> SQL statements from the log to be executed again. To enable binary 
> logging, add the following line to your server's options file 
> (i.e., /etc/my.cnf or c:\my.ini, depending on your system) in 
> the [mysqld] group and then restart the server daemon:
> 
>   log-bin = /var/log/mysql/bin
> 
> The path where you backup data and keep log files should be on 
> a separate hard drive for added safety.   Also, the directory should 
> be a secure one.  You can limit binary logging to specific databases 
> or you can omit certain databases (e.g., mysql, which contains user 
> passwords) from the log (see the documentation on binary logs). 
> To make interim restoration simpler, have mysqldump flush the logs 
> when you run a backup.
> 
> 
> Simple Interim Recovery
> 
> With daily backups and the binary logs running, it's simple to recover 
> data.  For example, suppose that your data is backed up each night 
> using mysqldump.  Suppose further that on January 10, 2006 at 10:00 a.m. 
> your data is lost and you want to recover it.  To begin with, you may 
> want to stop the MySQL server and then restart it in such a way that 
> you will be the only user to have access to it. This can be done like so:
> 
>   mysqld --port=3307 --socket=/tmp/mysql_restore.sock
> 
> You can use any non-privileged port that is unused by other services.
> The --socket option will temporarily name a different socket file for 
> Unix systems. On Windows systems, you would provide a named pipe 
> (e.g., MySQL_restore) instead of a path and file name:
> 
>   mysqld-nt --port=3307 --enable-named-pipe --socket=MySQL_restore
> 
> You can now proceed with restoring the dump file from the previous 
> night's backup like so:
> 
>   mysql -u root -pmypwd  --socket=/tmp/mysql_restore.sock \
>       < /var/backup/20060109.sql
> 
> The actual names of the paths and files will be different for your 
> server.  
> 
> Next you need to determine the name of the latest binary log file.  
> To do this, enter the following SQL statement:
> 
>   SHOW MASTER LOGS;
> 
> You're now ready to restore the transactions since the dump file was 
> created. If you are flushing the logs each day when making your 
> nightly backups, you would restore the entire binary log file from 
> the command-line like so:
> 
>   mysqlbinlog /var/log/mysql/bin.123456 \
>      | mysql -u root -pmypwd --socket=/tmp/mysql_restore.sock
> 
> In this example, the results of mysqlbinlog are piped to the mysql 
> client for processing. When it's finished, restart the MySQL server 
> without the temporary port and socket file options.
> 
> These couple of steps will restore the data as it stood at the time 
> of the previous backup and then all SQL statements that were entered 
> since the logs were flushed will be re-entered. 
> 
> Position Recovery
> The scenario in the previous section is based on the assumption that 
> you want to restore all of the server's data. However, if the reason 
> you need to perform the recovery is because some data was inadvertently
> deleted by an SQL statement, a simple full recovery using the binary 
> logs will only repeat the mistake.  For such a situation, a better 
> solution would be to restore the data until a specific position and 
> then again starting after the undesirable transactions.
> 
> The mysqlbinlog has options to recover data from and to a specific 
> position in the log: --start-position and --stop-position.  
> To determine the position numbers, run mysqlbinlog for a range of times
> around when the unwanted transaction was executed using a start and 
> stop time, and redirect the results to a text file for you to examine:
> 
>   mysqlbinlog --start-date="2006-01-10 9:55:00" \
>      --stop-date="2006-01-10 10:05:00" \
>      /var/log/mysql/bin.123456 > /tmp/mysql_restore.sql
> 
> Positions are labeled with log_pos followed by a number. Once you find 
> in the text file the log position where you want to stop the recovery 
> and the position in which you'd like to resume a recovery, make note 
> of them.  After restoring the backup file, with the position numbers 
> noted, you would then enter something like the following from 
> the command-line:
> 
>   mysqlbinlog --stop-position="368312" \
>      /var/log/mysql/bin.123456 \
>      | mysql -u root -pmypwd --socket=/tmp/mysql_restore.sock
> 
>   mysqlbinlog --start-position="368315" \
>      /var/log/mysql/bin.123456 \
>      | mysql -u root -pmypwd --socket=/tmp/mysql_restore.sock
> 
> The first line above will recover all of the transactions up until 
> the stop position given. The next line will recover all transactions 
> from the starting position given until the end of the binary log. 
> 
> 
> Conclusion
> 
> With binary logging, complete recovery up to any particular point 
> can be achieved fairly easily and quickly with a standard installation 
> of MySQL. The key is to perform backups and to flush the logs on 
> a regular basis.  With these safeguards in place, it's just a matter 
> of being familiar with the procedures for recovering your data so 
> that you may act quickly and accurately when called upon. To be 
> better prepard for a crisis, you may want to practice restoring 
> data as described here, but on a test server.
> 
> 
> -------------------------------------------------------------------------
> 
> This tip of the month was sent to you as part of the MySQL Network
> subscription you are a technical contact to. If you wish to receive 
> no further such e-mails, please write to <sup...@my...> 
> with a word "UNSUBSCRIBE" in the e-mail subject or body.
> 
> If you decide to do so, please also make sure that your e-mail will
> be sent out from under the same e-mail address you received this
> mail to.
> 
> If you have any other or further questions, please do not hesitate
> to contact Indrek Siitan, Administrative Coordinator of Support at
> MySQL AB, at <sup...@my...> or +1-650-491-0131.
> 
> 
> -- 
> Lior Kanfi <li...@ti...>
> Tikal

-- 
Lior Kanfi <li...@ti...>
Tikal

tikal-development Mailing List for Tikal

tikal-development — tikal development list