Re: Component Java class lookup

Robert Walker <[email protected]>
Newsgroups gmane.comp.web.webobjects.devel,gmane.comp.web.webobjects.woproject.devel
Message-ID <[email protected]>
Logi,

I'd say your best bet is to avoid that situation altogether by  
avoiding name conflicts.  It's the job of WOComponent.pageWithName 
(String) to lookup the java file for a particular WOComponent name.   
There may be a workaround, but avoidance is the best practice here.

This is really a side-effect of the original Obj-C origins of  
WebObjects (Obj-C doesn't have packages as in Java).  The recommended  
design pattern is to prefix any class names with two capital letters  
(e.g. NSArray, NSDictionary).  Do this in your frameworks with your  
own prefix like XYMyFrameWorkPage.java or XYMyUtilities.java.

On Oct 11, 2006, at 6:09 AM, Logi Helgu wrote:

> I have a Framework[FW] and Project[PR] that both a JAVA file with  
> the same
> name.  In my FW it's a single file and a Component in my PR.  When  
> I run the
> PR the Component looks for the Java file in the FW but not the one  
> in the
> PR.  Is there any way to tell a Component in witch package or  
> "namespace" to
> look in WebObjects( Eclipse )?
>
>     With well-being and veneration,
>
>     Logi Helgu
>
>
>
>
> Fyrirvari á tölvupósti / e-mail disclaimer
> <a href="http://www.us.is/page/fyrirvari">http://www.us.is/page/ 
> fyrirvari</a>
>
>  _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/webobjects-dev/robertwalker1% 
> 40mac.com
>
> This email sent to [email protected]

--
Robert Walker
[email protected]

_______________________________________________
WebObjects-dev mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/webobjects-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.