geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <david_jen...@yahoo.com>
Subject Re: SchemaConversionUtils/GenericToSpecificPlanConverter woes continue?
Date Thu, 17 Nov 2005 23:41:08 GMT
Your original namespace should now work, see latest change on  
GERONIMO-1175

thanks
david jencks

On Nov 17, 2005, at 3:13 PM, David Jencks wrote:

> If you change the web namespace to  
> http://geronimo.apache.org/xml/ns/j2ee/web-1.0 does it work?
>
> thanks
> david jencks
>
> On Nov 17, 2005, at 3:09 PM, Jacek Laskowski wrote:
>
>> Hi,
>>
>> I'm pretty sure that my recent problems with plans are related to the  
>> last changes to org.apache.geronimo.schema.SchemaConversionUtils or  
>> org.apache.geronimo.web.deployment.GenericToSpecificPlanConverter (it  
>> is because I'm trying to pinpoint the root cause and I'm pointing to  
>> at anything that changes ;))
>>
>> The following plan is changed to the one where all the elements  
>> belong to jet namespace.
>>
>> <application  
>> xmlns="http://geronimo.apache.org/xml/ns/j2ee/application"
>>     parentId="org/apache/geronimo/AdventureDataSource1.0.1"
>>     configId="org/apache/geronimo/Adventure1.0.1">
>>
>>     <module>
>>         <web>adventure.war</web>
>>         <web-app xmlns="http://geronimo.apache.org/xml/ns/web"
>>             xmlns:naming="http://geronimo.apache.org/xml/ns/naming"
>>             configId="NOT_USED">
>>
>> <context-priority-classloader>false</context-priority-classloader>
>>
>>             <naming:service-ref>
>> <naming:service-ref-name>service/OpcPurchaseOrderService</naming: 
>> service-ref-name>
>>                 <naming:port>
>> <naming:port-name>PurchaseOrderIntfPort</naming:port-name>
>>                     <naming:protocol>http</naming:protocol>
>>                     <naming:host>localhost</naming:host>
>>                     <naming:port>8080</naming:port>
>>                     <naming:uri>/consumer/foo/po</naming:uri>
>>                 </naming:port>
>>             </naming:service-ref>
>>             <naming:service-ref>
>> <naming:service-ref-name>service/OpcOrderTrackingService</naming: 
>> service-ref-name>
>>                 <naming:port>
>> <naming:port-name>OrderTrackingIntfPort</naming:port-name>
>>                     <naming:protocol>http</naming:protocol>
>>                     <naming:host>localhost</naming:host>
>>                     <naming:port>8080</naming:port>
>>                     <naming:uri>/consumer/foo/order</naming:uri>
>>                 </naming:port>
>>             </naming:service-ref>
>>             <naming:resource-ref>
>>                 <naming:ref-name>jdbc/CatalogDB</naming:ref-name>
>> <naming:resource-link>AdventureDataSource</naming:resource-link>
>>             </naming:resource-ref>
>>         </web-app>
>>     </module>
>>
>> </application>
>>
>> Am I missing something?
>>
>> Jacek
>>
>


Mime
View raw message