You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Quinton McCombs <qu...@bellsouth.net> on 2002/12/13 07:20:27 UTC

Changes to intake service

I am about to start working going through the entire intake service and
making some changes.  When I first got started with intake, it was a
little confusing at first (2.1).  Seeing the posts on the user's list,
this is an area where many people seem to have some trouble.  My main
goal is to make it a little easier to get working for people new to
Turbine.
 
Here is a brief list of things that I am planning to address.
- Better error reporting to the log file.  It can be very difficult to
troubleshoot a simple mistake in intake.xml.
- Fix the problem of not being able to set a mapped property to null.  
- Update the documentation to fully describe the types of fields,
attributes, available rules, etc.  
- Backport any bug fixes in the fulcrum version back to the coupled
version.
- Update the javadocs
- Better error handling
- Develop some JUnit tests
 
Is there anything else that anyone would like to suggest?
 
Have we decided on what to do about logging?  I suppose that I could
just keep it using the current logging mechanism if that debate is not
over yet.  
 
 
 


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Changes to intake service

Posted by Laurie Harper <zo...@holoweb.net>.
One thing I'd like to see changed is IntakeTool.get() returning null 
instead of throwing Exception. That would be much more friendly to 
template writers as well as less cumbersome in Java code.

At the very least, change it to throw MissingResourceException or 
something, not just Exception :-(

L.

Quinton McCombs wrote:

> I am about to start working going through the entire intake service and
> making some changes.  When I first got started with intake, it was a
> little confusing at first (2.1).  Seeing the posts on the user's list,
> this is an area where many people seem to have some trouble.  My main
> goal is to make it a little easier to get working for people new to
> Turbine.
>
> Here is a brief list of things that I am planning to address.
> - Better error reporting to the log file.  It can be very difficult to
> troubleshoot a simple mistake in intake.xml.
> - Fix the problem of not being able to set a mapped property to null.
> - Update the documentation to fully describe the types of fields,
> attributes, available rules, etc.
> - Backport any bug fixes in the fulcrum version back to the coupled
> version.
> - Update the javadocs
> - Better error handling
> - Develop some JUnit tests
>
> Is there anything else that anyone would like to suggest?
>
> Have we decided on what to do about logging?  I suppose that I could
> just keep it using the current logging mechanism if that debate is not
> over yet.
>
>
>
>
>
> --
> To unsubscribe, e-mail:
> For additional commands, e-mail:



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Changes to intake service

Posted by Rodney Schneider <ro...@actf.com.au>.
Hi Quinton,

It would be good if you could fix the bug mentioned in TTWS20.  If you 
need me to make some patches for this, let me know.

Thanks,

-- Rodney


On Fri, 13 Dec 2002 17:20, you wrote:
> I am about to start working going through the entire intake service
> and making some changes.  When I first got started with intake, it
> was a little confusing at first (2.1).  Seeing the posts on the
> user's list, this is an area where many people seem to have some
> trouble.  My main goal is to make it a little easier to get working
> for people new to Turbine.
>
> Here is a brief list of things that I am planning to address.
> - Better error reporting to the log file.  It can be very difficult
> to troubleshoot a simple mistake in intake.xml.
> - Fix the problem of not being able to set a mapped property to null.
> - Update the documentation to fully describe the types of fields,
> attributes, available rules, etc.
> - Backport any bug fixes in the fulcrum version back to the coupled
> version.
> - Update the javadocs
> - Better error handling
> - Develop some JUnit tests
>
> Is there anything else that anyone would like to suggest?
>
> Have we decided on what to do about logging?  I suppose that I could
> just keep it using the current logging mechanism if that debate is
> not over yet.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Changes to intake service

Posted by Jon Scott Stevens <jo...@latchkey.com>.
on 2002/12/13 5:53 AM, "Scott Eade" <se...@backstagetech.com.au> wrote:

>> From: "Quinton McCombs" <qu...@bellsouth.net>
>> 
>> Have we decided on what to do about logging?  I suppose that I could
>> just keep it using the current logging mechanism if that debate is not
>> over yet.  
> It looks like commons-logging is the go for now.

+1

-jon

-- 
StudioZ.tv /\ Bar/Nightclub/Entertainment
314 11th Street @ Folsom /\ San Francisco
        http://studioz.tv/


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Changes to intake service

Posted by Scott Eade <se...@backstagetech.com.au>.
> From: "Quinton McCombs" <qu...@bellsouth.net>
> 
> Have we decided on what to do about logging?  I suppose that I could
> just keep it using the current logging mechanism if that debate is not
> over yet.  
It looks like commons-logging is the go for now.

Cheers,

Scott
-- 
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au
.Mac Chat/AIM: seade at mac dot com


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>