Hi Marco,
Again, my issue was at my end ( fancy that).

I hadn't set the to one Entity I was using, I found that I cold really 
easily use others in the same namespace and then sorted out the issue.

I think it was a confusing annotation line.

I was about to post "its all right I got it" post.

Completely agree about the abstraction.

Thank you very much for the answer.

Stay well,
Barry

On Friday, 9 May 2014 16:36:27 UTC+10, Marco Pivetta wrote:
>
> Hi Barry,
>
> This is just some misconception about ZF2 modules that is probably based 
> on ZF1 knowledge.
>
> Modules share everything: after bootstrap, Admin can access Assets, Assets 
> can access Admin (services, classes, entities, etc)
>
> How the modules are structured doesn't make that much of a difference, 
> just try to keep a clear separation or dependency direction (don't build 
> bidirectional links across modules, since that basically means that they 
> are just one).
>
> Cheers,
>
> Marco Pivetta 
>
> http://twitter.com/Ocramius      
>
> http://ocramius.github.com/
>  
>
> On 9 May 2014 06:25, Barry Steele <[email protected] <javascript:>>wrote:
>
>> Hi,
>> I am building a system that will have several modules (Assets,Admin,...)
>>
>> The Assets module is a system formanage real assets.
>>
>> THe Admin module will be to maintain systems information, preferences, 
>> etc.  Part of the Admin will be to allow an admin role to modify a range of 
>> reference catefgories and look up fields.  This use case requires access to 
>> then same model as the Assets module.
>>
>> Is there a standard (Doctrine/ZF2 ) structure to do this?
>>
>> Currently I have the following set up:
>>
>> /application
>>    /config
>>   /modules
>>      /Assets
>>            /src
>>                 /Assets
>>                      /Controller
>>                      /Form
>>                      /Model 
>>      /Admin
>>           /src
>>               /Admin
>>                     /Controller
>>                                /AdminController   -- wants to be able to 
>> access \Assets\Model\XXXX
>>
>> Is is standard to raise the Model higher p the tree in these situations?
>>
>> In Namespace Admin, what is the best way to acess the Assets model for 
>> Admin?  
>>
>> Admin needs to do other things that just interact with the Assets model.
>>
>> Stay well
>> Barry
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "doctrine-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To post to this group, send email to [email protected]<javascript:>
>> .
>> Visit this group at http://groups.google.com/group/doctrine-user.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to