• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: JDBC Model - to - JNDI Model Relationship Question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: JDBC Model - to - JNDI Model Relationship Question


  • Subject: Re: JDBC Model - to - JNDI Model Relationship Question
  • From: Chuck Hill <email@hidden>
  • Date: Fri, 27 Feb 2004 13:29:51 -0800
  • Organization: Global Village Consulting, Inc.

I've never tried it, but inheritance with an abstract super-class might work. The search base would be ou=people,dc=company,dc=com and the two sub-classes would have an rdn of uid=myusername,ou=employees and uid=myusername,ou=others.

That is the only way I can think of that might make EOF generate the proper queries.

Chuck


Anthony Glover wrote:

Hi,

I have two models:

One is a JDBC model with an AppUser entity.
The other is a JNDI model with an InetOrgPerson entity.

The InetOrgPerson entity is based upon an OpenLDAP schema and contains a relativeDistinguishedName as the primary key.

I also have this same attribute in my AppUser entity and it is used to establish a relationship between the two models.

The values I use for the key are like "uid=myusername". Also, my search base is something like "ou=employees,ou=people,dc=company,dc=com". Note that my directory tree also has "ou=others,ou=people,dc=company,dc=com".

This all seems to work and I am able to traverse from an AppUser over to an InetOrgPerson.

The problem that I have is that I am now needing to be able to traverse a relationship from AppUser over to InetOrgPerson in which the search base may be either an 'employee' or an 'others'. I think the only solution to my problem is to combine the two branches and place everyone in the same "ou=people,dc=company,dc=com" tree and eliminate the extra division of employees and other.

Has anyone ran into this type of problem before with LDAP modeling? Any other ideas on best how to resolve this issue. I'm hesitant to combine the groups of users, but it was just an arbitrary division on my part when setting up the directory and it is probably overkill anyway.

Thanks,
Tony
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.



--

Chuck Hill                                 email@hidden
Global Village Consulting Inc.             http://www.global-village.net

It is a funny thing about life; if you refuse to accept
anything but the best, you very often get it."
  --  W. Somerset Maugham

<shamelessPlug>
  Practical WebObjects
  http://www.amazon.com/exec/obidos/tg/detail/-/1590592964
</shamelessPlug>
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >JDBC Model - to - JNDI Model Relationship Question (From: Anthony Glover <email@hidden>)

  • Prev by Date: JDBC Model - to - JNDI Model Relationship Question
  • Next by Date: Re: Is WebObjects Dead?
  • Previous by thread: JDBC Model - to - JNDI Model Relationship Question
  • Next by thread: Newbie question: Removing subproj in W2K
  • Index(es):
    • Date
    • Thread