[jbosstools-dev] Re: Fwd: [jbosstools-commits] JBoss Tools SVN: r8706 - in trunk/ws/plugins/org.jboss.tools.ws.core: src/org/jboss/tools/ws/core/classpath and 1 other directories.

[gridqian]

Ok. 'this' container is jboss ws container that is created by me. When we
create a jboss ws project, we need add a container to the project 
classpath. This
container is jboss ws container. And this container include jars from EAP4.2
client folder and lib folder.
Now some jars from client folder are same to some jars from lib folder. So I
must filter them. If not, when we export these jars from classpath to 
WEB-INF
lib folder, we will get some errors.

> On Wed, 11 Jun 2008 12:23:20 +0200, gridqian <fqian at redhat.com> wrote:
>
>   
>> Aha, yes, it is my carelessness. Should add jars from client and lib
>> folder of EAP4.2
>> to this container.
>>     
>
> I don't understand what you mean. Which container is "this" ?
>
> p.s. shouldn't we move this to jboss-tools-dev list so Rob et.al. could see it too ? 
>
> /max
>   
>>>> And about these codes that I commit:
>>>> now we copy client folder and lib folder of jboss ws to container. And
>>>> some jars from client
>>>> folder are same to the jars from lib folder. If we export this container
>>>> to web-inf lib folder, we
>>>> will get some errors for this. So I filter them. I do this as:
>>>> when add a jar to entry list, if entry list has it , do not add this jar
>>>> to entry list again.
>>>>
>>>>         
>>> Copy client folder and lib folder of jboss ws to container ? That is not acceptable
>>> in the case of it being EAP 4.2. We must not require alteration of that runtime.
>>> Our support does not support JBoss WS from jboss.org, it only supports what is inside EAP 4.2
>>> thus users should not be required to alter it.
>>>
>>>
>>> /max
>>>
>>>
>>>       
>>     
>
>
>
>