I just realized this morning that you were using Jetty rather than Tomcat (which I usually use) - And so I thought that might be figuring into your problem.
So I did a fresh build of trunk and tested the Jetty version to see where I would find dojo.js. And, it was right where I thought it would be: http://localhost:8080/dojo/dojo/dojo.js Where did you get the snapshot that you were testing with? And what is the location of the plugin repository that you were pulling in Dojo from? Did you build the snapshot version yourself? And if you did, did you clear out your maven repository before you started? The current builds no longer include the Dojo plugin by default (it needs to be manually pulled in). If you did not do this and you had Dojo available as an installed system module, then you are using an older version. Lots of questions, I know. I just can't understand why you aren't finding Dojo where I am. Let me know what you find, Jay Ivan wrote: > I guess the dojo webapp is deployed with the web context "dojo", so > http://localhost:8080/dojo <---(webapp context) / dojo <-- > (parent folder) / dojo <-- (sub folder, which has a brother folder "dijit") > / dojo.js > > 2008/10/15 Jay D. McHugh <[EMAIL PROTECTED]> > >> Ivan, >> >> The location that you saw is correct (as of Dojo version 1.x). >> >> Ever since they (Dojo) began releases of Dojo that include dijit and >> dojox (those started with 0.9), they have nested those folders within a >> parent dojo folder. >> >> So, the folder structure should be: >> --dojo >> ----dojo >> dojo.js >> <everything else that base dojo needs> >> ----dijit >> <whatever is in dijit> >> >> And the path you would need to specify to access the dojo.js file would be: >> >> http://localhost:8080/dojo/dojo/dojo.js >> >> It still feels like an extra level of directories (to me also). But the >> only alternative to that would be for us to break apart the release from >> Dojo into multiple plugins. Then, there would be a dojo plugin and a >> dijit plugin. But for Geronimo's use of Dojo (and I would assume most >> others) the widgets are a big part of the draw - and splitting Dojo >> apart would be adding extra work to make things more complicated for us >> and users. >> >> Jay >> >> Ivan wrote: >>> After running mvn install on my local svn folder, I checked the file >>> dojo-tomcat-2.2-SNAPSHOT.car in the target folder, it has the same >> structure >>> with the previous one. >>> >>> ---dojo---dojo >>> ---dijit >>> ---WEB-INF >>> ---MENTA-INF >>> >>> Adding the web context "dojo", I guess we still need >>> /dojo/dojo/dojo/dojo.js, have I missed anything ? >>> >>> >>> 2008/10/14 Jay D. McHugh <[EMAIL PROTECTED]> >>> >>>> Ivan, >>>> >>>> Have you had a chance to try a newer snapshot? >>>> >>>> Is Dojo showing up in the correct location for you? >>>> >>>> Jay >>>> >>>> Ivan wrote: >>>>> Just find in the newest snapshot, after I manually install the dojo >>>> plugin, >>>>> it has an extra folder "dojo", currently when we want the refer to >>>> dojo.js, >>>>> the url will be /dojo/dojo/dojo/dojo.js. >>>>> I suggest to repackage the dojo-mini.zip file. >>>>> >>>>> >>>>> 2008/10/8 Lin Sun <[EMAIL PROTECTED]> >>>>> >>>>>> Hi Manu, Ok, making it optional sounds good. >>>>>> >>>>>> Lin >>>>>> >>>>>> On Wed, Oct 8, 2008 at 8:24 AM, Manu George <[EMAIL PROTECTED]> >>>>>> wrote: >>>>>>> Hi Lin, >>>>>>> >>>>>>> I am using it in the EjbServer Portlet I am developing. But I guess >>>>>>> that it can also be made an optional console plugin >>>>>>> >>>>>>> Regards >>>>>>> Manu >>>>>>> >>>>>>> On Wed, Oct 8, 2008 at 1:43 AM, Lin Sun <[EMAIL PROTECTED]> >> wrote: >>>>>>>> Jay, >>>>>>>> >>>>>>>> Right, I don't know how far that work went either. >>>>>>>> >>>>>>>> Thus, I didn't include the dojo-tomcat/jetty6 in the new >>>>>>>> javaee5-tomcat/jetty plugin group(profile), which will be used to >>>>>>>> build the javaee5 assemblies. >>>>>>>> >>>>>>>> Lin >>>>>>>> >>>>>>>> n Tue, Oct 7, 2008 at 3:41 PM, Jay D. McHugh <[EMAIL PROTECTED]> >>>>>> wrote: >>>>>>>>> Lin, >>>>>>>>> >>>>>>>>> Someone was working on upgrading the views in Geronimo to use the >>>>>>>>> widgets in the new version of Dojo. I don't know how far that work >>>>>> went. >>>>>>>>> So, I believe you are correct that the legacy set are the only ones >>>>>> that >>>>>>>>> are currently in use. >>>>>>>>> >>>>>>>>> Jay >>>>>>>>> >>>>>>>>> Lin Sun wrote: >>>>>>>>>> I think these two portlets are using the >> dojo-legacy-tomcat/jetty6. >>>>>>>>>> Nothing except the javaee5 assemblies lists dojo-tomcat/jetty6 as >>>>>>>>>> dependency. >>>>>>>>>> >>>>>>>>>> Lin >>>>>>>>>> >>>>>>>>>> On Tue, Oct 7, 2008 at 3:10 PM, Donald Woods <[EMAIL PROTECTED]> >>>>>> wrote: >>>>>>>>>>> I believe only the Debug Views and Plan Creator portlets need >> Dojo >>>>>> right >>>>>>>>>>> now, which I'm going to remove from the JEE5 assemblies and let >>>> users >>>>>>>>>>> optionally install them, once I've updated the Welcome portlet to >>>>>> include >>>>>>>>>>> some information about what optional Console plugins are >>>>>> available.... >>>>>>>>>>> -Donald >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Lin Sun wrote: >>>>>>>>>>>> Hi, >>>>>>>>>>>> >>>>>>>>>>>> I don't see dojo-tomcat/jetty6 is used by admin console right >> now >>>> in >>>>>>>>>>>> trunk thus I plan to remove it from the javaee5 assembly. Any >>>>>>>>>>>> objection? >>>>>>>>>>>> >>>>>>>>>>>> Whenever we have converted some of our admin console to use >>>>>>>>>>>> dojo-tomcat/jetty6, dojo-tomcat/jetty6 should be automatically >>>>>> pulled >>>>>>>>>>>> into javaee5 assembly via transitive dependency, similar like >>>>>>>>>>>> dojo-legacy-tomcat/jetty6 today. >>>>>>>>>>>> >>>>>>>>>>>> Lin >>>>>>>>>>>> >>>>> >>> >>> > > >
