// Ensure library/ is on include_path
set_include_path(implode(PATH_SEPARATOR, array(
realpath(APPLICATION_PATH . ‘/../library’),
realpath(APPLICATION_PATH . ‘/models’),

get_include_path(),
)));

It works for me

as it turned out –
my models were NOT being autoloaded
for whatever reason
and this is what i ended adding that wroked:

protected function _initAutoload()
{
$loader = new Zend_Application_Module_Autoloader(array(
“namespace” => “”,
“basePath” => APPLICATION_PATH));

// autoload
$loader->addResourceType(“model”, “models”, “Model”);
}

If you have defined a namespace in _initAutoload (in Bootstrap.php) the prefixes will change to YourNamespace_Model_SomeName and YourNamespace_Model_DbTable_SomeName.

You can change your models directory in the application.ini file with this line of code:
resources.frontController.modelsDirectory = APPLICATION_PATH “/my_models”

You can probably also add any directory to autoload.

Hope this helped to resolve your problems.

Fatal error: Class ‘Model_Press’ not found in
/path/to/library/MyLib/Db/PressService.php

im wondering why ZF 1.10 is not autoloading my model…

actually my dir structure is NOT
models/db it is the same as yours
i think you are referring to this:
/var/local/virtuals/www.acemetrix.com/library/AM/Db/PressService.php
which i should have generalised it as the path to db service layer
which resides in the library
ie, /path/to/library/MyCustomLib/Db/dbServiceLayer.php
which is how jon’s example here is setup

one last thing
yes you are correct about me running ZF1.10 not ZF1.18
i made a typo there
so if the Nayre posting above says the foloowing
“rename UsersTable into Application_Model_UsersTable”
which is now what you are telling me is wrong?

its now become pretty clear to me
that my issue is is that the when the service layer is called
the model for my object ‘press’ is not in the include path
or has not been loaded
which is weird since
1) if i print out the path
its has application/models in the path
and
2) i thought ZF 1.10 was supposed to autoload the models
nad if not then the init autoload statement would take care ofit

am i confusing the issue here?

Fatal error: Class ‘Application_Model_Press’ not found in /var/local/virtuals/www.acemetrix.com/library/AM/Db/PressService.php on line 32

first off im running ZF1.8
my include path looks like this:
/path/to/library:/path/to/application/models

ive tried adding this to my bootstrap (according to brett above):
protected function _initAutoload()
{
$autoloader = new Zend_Application_Module_Autoloader(array(
‘namespace’ => ‘Application’,
‘basePath’ => dirname(__FILE__),
));
return $autoloader;
}

ive also tried adding this to my bootstrap (according to http://www.zendcasts.com/forum/post/65/#p65)
protected function _initAutoload()
{
$moduleLoader = new Zend_Application_Module_Autoloader(array(
“namespace” => “”,
“basePath” => APPLICATION_PATH));

/** auto load */
$autoloader = Zend_Loader_Autoloader::getInstance();
$autoloader->setFallbackAutoloader(true);
return $moduleLoader;
}

ive tried cross referencing with the code jon has uploaded up on google
but obviously im missing something
pls help!
thanks

you should configure code for 1.10 .

how i can check for that info, i have that nick in db or its free to use?

The Zend documentation in Zend Framework 1.10 shows how to use a mapper with Zend_Db_Table. Is this analogues to the services you use in this screencast?

The default directory structure seems to be:
application/models –
application/models/DbTable – table classes
application/models/mappers – mappers (this part is from Rob Allen’s getting started tutorial)

Try adding this to your bootstrap php file:

protected function _initAutoload()
{
$autoloader = new Zend_Application_Module_Autoloader(array(
‘namespace’ => ‘App’,
‘basePath’ => dirname(__FILE__),
));
return $autoloader;
}

then UserService.php would be
$this->users = new App_Model_UsersTable();

and

UsersTable.php would be
class App_Model_UsersTable extends Zend_Db_Table_Abstract

// Ensure library/ is on include_path
set_include_path(implode(PATH_SEPARATOR, array(
realpath(APPLICATION_PATH . ‘/../library’),realpath(APPLICATION_PATH . ‘/models/’),
get_include_path()
)));

As you can see the path for the models already exist. Do you have any other ideas?
Thank you.

set_include_path(
APPLICATION_PATH . ‘/models’
. PATH_SEPARATOR . get_include_path()
);

// Define path to application directory
defined(‘APPLICATION_PATH’)
|| define(‘APPLICATION_PATH’, realpath(dirname(__FILE__).”/../application/” ));

// Define application environment
defined(‘APPLICATION_ENV’)
|| define(‘APPLICATION_ENV’, (getenv(‘APPLICATION_ENV’) ? getenv(‘APPLICATION_ENV’) : ‘production’));

// Ensure library/ is on include_path
set_include_path(implode(PATH_SEPARATOR, array(
realpath(APPLICATION_PATH . ‘/../library’),realpath(APPLICATION_PATH . ‘/models/’),
get_include_path()
)));

/** Zend_Application */
require_once ‘Zend/Application.php’;

// Create application, bootstrap, and run
$application = new Zend_Application(
APPLICATION_ENV,
APPLICATION_PATH . ‘/configs/application.ini’
);
$application->bootstrap()
->run();

Model_* is the default namespace for models in the Zend Framework. I believe I got around it by including the ‘models’ folder in my include paths for that particular video.

Nicola

The model is a fine place to do this depending on the size of your application. The use of a service layer is likely to make sense if your models are complex or are linked to multiple data sources. In such an instance, you might want to create a service layer that acts as a facade and brokers the commits across multiple persistence mechanisms.

ZF is very new for me, so therefor I have this newbee question:

Why a service layer? Why not put this code for select, insert, update … in the Model?

Sorry for this dump question

Regards, Magnus

I´m following the example but i can’t instanciate App_UserService in the controller it throw me a error of class not found . I´m using Zend 1.9. Does anyone have this problem?? Need same help here…. thank you

Spinto

if I want to use the configurations included in the db application.ini what should include in __construct and bootstarp ??

thanks

looking forward for the next webcast about zend_db

http://www.angryobjects.com/2009/03/30/writing-robust-php-backends-with-zend-framework/

albeit without the actual demo or code

just to add, these casts are excellent

Though a lot of the simple operations (and some more complex ones, as I understand it) should be handled by Zend_Db_Table_Abstract’s magic functions.

Just thinking in-text here… Assuming you declare all the available tables in the service layer, you could make them publicly available and still have the table functionality ($service->users->CreateTestUser()), while also having the ability to just load the one particular table you need if your action is only working on one table (say, updating a user’s email address).

Just throwing this out there, I don’t quite have the experience to dictate either way.

Thanks for posting the video, your casts are very helpful.

that’s a great point, however often when you’re managing relationships between tables (e.g. a user with many posts, a post with many tags), then the relationships don’t belong in either table. The “service” layer is a very light version of what Evans’ would call an aggregate root, or an entry point into a domain. The thinking here is that you want to encapsulate the complexity of multiple Zend_Db_Table’s (and perhaps other non-database related data sources) in a class that hides the implementation details from its consumers. Also, if you’re just doing simple CRUD, then the Active Record pattern (implemented in Doctrine as well as Propel) makes more sense since it really works well in handling the simple saves on one table. This pattern falls apart when you need to do joins that are more dynamic, or you need to start aggregating or doing reporting against larger data sets.

my 2 cents.

so more like:
$users = new UsersTable();
$users->CreateTestUser();

Thinking after a few tables, keeping all the CRUD in a single class might be a bit unwieldy, and this is the other approach I’ve seen while researching Zend_Db.