Hi John, To be honest I don't know a lot about these things. But shouldn't the Oracle AS register a protocol handler for the jndi protocol? That way HiveMind shouldn't have any problems. All the URLResource class does is create a java.net.URL object and makes sure the openStream() method can be called. For this I thought a protocol handler had to be registered.
Regards, --knut On 5/11/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi, > > I have been having a problem with HiveMind 1.1beta2/Tapestry 4alpha3 > (from cvs) on the Oracle app server. Because oracle uses what I think is > a proprietary naming system for jar files > (jndi:C:\some\jar\file.jar\META-INF\hivemodule.xml for example) HiveMind > is not able to load submodules (specifically the Tapestry submodules in > this case). The problem is in org.apache.hivemind.util.URLResource, > which is choking on the jndi: format and returning null. I have got > round it by hacking URLResource to replace jndi:... with jar:file:///C: > and inserting the ! before the path within the jar, but I don't want to > have to do this with every new release of HiveMind. > > Any suggestions? I presume you don't want to build this kind of hack > into HiveMind itself. Anyone else have any experience with HiveMind > OracleAS? > > Just so we are clear, HiveMind finds the basic META-INF/hivemodule.xml > files, but it can't parse the submodules if there are any. > > Thanks in advance > > John Prince > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
