De : todd tredeau [mailto:todd@;wisernet.com] > Envoy� : mercredi 6 novembre 2002 17:04 > � : [EMAIL PROTECTED] > Objet : nightly builds broken since 10/28/02 and.. > > > ll the recent builds since about 9/1/02 have an error > handling directory > drive/names. This is an identical error that was fixed in the Cocoon > Project by Vadim. searching for unknown protocol would find > it. Whatever > the problem is, it is specific to the Novell platform. Changes were > committed to the cocoon cvs to correct the same problem. I > can offer to > test the builds, supply error logs and more information. > > unknown protocol sys: > Recent builds of jetspeed 1.4b2 series >
Can you file a bug about this bugzilla ? I'll check out the cocoon archive to see what is the issue but it's most likely related to the updated xerces or xalan, however if you already have an archive link to provide about thread, that should save me some time... > a warning... when my jetspeed hsql db reached 12mb, the system became > un-stable and un-usable. I believe based on comments from a couple > forums the way it handles itself in memory. I'd suggest an > alternative > if you plan on adding very large amounts of data, to avoid > this issue later. > I don't think HSQL is meant to handle large amount of data. If you have a large portal you should probably configure it to use MySQL rather than hsql. Jetspeed uses HSQL as default because it's convenient for distributing a complete working WAR without external dependencies. > I have questions from people trying to access with WML devices. What > special configuration issues are there for that. Specifically the > question I recently got was; > > Hi, > I am a member of your site. > And I want to customize WML media type. > Please let me know how I check the result of customizing WML. > I have UP.simulator, so I tried to connect > "http://portal.wisernet.com/index.jsp"; after cusotmizing WML, > it failed. > > Let me know the URL in UP.simulator ! > The URL is the same. If the WML support doesn't work, it's most likely because the user-agent is not recognized as a WML browser. In the current releases, you need to edit and recompile the ClientCapabilityMap class to add new user-agent. In the upcoming release, client defintions will be stored in the Registry to enable easier updates of these definitions. -- To unsubscribe, e-mail: <mailto:jetspeed-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:jetspeed-user-help@;jakarta.apache.org>
