Home » Language IDEs » ServerTools (WTP) » WTP complaining about .deployables in non web projects
| |
| Re: WTP complaining about .deployables in non web projects [message #128637 is a reply to message #128525] |
Tue, 02 August 2005 01:48   |
 Ben Sisson
Messages: 202
Registered: July 2009 |
Senior Member |
|
|
This is a bug (94590) in Eclipse and they are aware of it and it will be
in the next release. I know that a fix was posted for this but I am not
sure where you can go to get this. Also, there are some good write ups
about this error and one has details on how to fix the error when it
occurs. I suggest that you search the WTP articles to find these.
Here is some additional data. I hope this helpls.
I have some additional and intersting information regarding this error. A
quick refresh, I created a top down Web Service from a WSDL document, test
it
and it works perfectly. I then run a Clean (project->clean) on the
project,
with no error message, and it then won't run. I get an error message that
the
method couldn't be found on Axis. The only way (possible work around)
that I
can recover is to recreate the Web Service from the WSDL document which
overlays my changes that I have made when it recreates the schedule.
I will get to the possible cause of the problem and solutino in a minute
but I
want to cover some of my research for verificaiton.
Within the project where my Web Service had existed before, I recreated
the
Web Service from the WSDL file and recorded the files that were updated
(by
change date).
Under the .deployables directory and sub directories the following files
were
updated:
a) server-config.wsdd
b) deploy.wsdd
c) undeploy.wsdd
d) *.class (all the class files were updated)
e) *.jar (all my jar files that are really reference files were updated)
f) *.wsdl (the new Soap wsdl was updated)
Under the Mod directory and sub directories (files typically displayed in
Eclipse) the following files were updated:
a) *.java (all java files)
b) deploy.wsdd
c) undeploy.wsdd
d) *.jar (all my jar files that are really reference files were updated)
e) *.wsdl (the new Soap wsdl was updated)
I then run a Clean (project->clean) on my proejct and check to see which
files
were updated and I noticed the following:
Under .deployables directory and subdirectory:
a) The server-config.wsdd file no longer exists - did not expect)
b) *.class (all the class files were updated - would expect)
Since I had tried to redeploy the project and many other different things
to
resolve the issue, I assumed that my problem must exist in one of the two
areas that changed after the Clean. Since I expect the *.class files to
be
updated I focused on the server-config.wsdd file which no longer appeard.
I
recreated the Web Service again from the WSDL, verified that it was
functioning again, and then made a copy of the server-config.wsdd file. I
then performed the Clean, and verified that the Web Service was broken
again. I then pasted a copy of the original server-config.wsdd file back
into the directory and ran the Web Service again. When I did this the Web
Service corrected itself and worked fine. Therefore, I am concluding
that
the problem is the fact that the Clean deletes and never recreates the
server-
config.wsdd file. For a temporary solution until it is corrected I
recommend
that the server-config.wsdd file be copied and backed up somewhere. If a
clean is performed this file can be pased into the appropriate directory
and
the Web Service can be corrected without having to overlay all your work
with
a complete rebuild of the Web Service.
------- Additional Comment #1 From Chris Brealey 2005-06-25 16:54 [reply]
-------
I wish all bugs were as well explained as this one. Turns out there is
another
for this issue, 94590, so am returning this one as a duplicate. This
should not
be too hard to fix. Thanks - CB.
*** This bug has been marked as a duplicate of 94590 ***
|
|
|
| Re: WTP complaining about .deployables in non web projects [message #128843 is a reply to message #128637] |
Tue, 02 August 2005 12:20 |
Iran
Messages: 32
Registered: July 2009 |
Member |
|
|
Ben, first o all, thanks for your help.
I'm not sure the problem I described have something to do with this bug
you mentioned. Perhaps I misunderstood it.
But anyway, this bug could affect non web projects? My real problem is
when I clean and build a non web project (a Java Project), I receive
that error message (it's in my last post) complaining about absence of
..deployables directory.
Can you please confirm that my problem is related to that bug?
Thank you.
Ben wrote:
> This is a bug (94590) in Eclipse and they are aware of it and it will be
> in the next release. I know that a fix was posted for this but I am
> not sure where you can go to get this. Also, there are some good write
> ups about this error and one has details on how to fix the error when it
> occurs. I suggest that you search the WTP articles to find these.
> Here is some additional data. I hope this helpls.
>
> I have some additional and intersting information regarding this error.
> A quick refresh, I created a top down Web Service from a WSDL document,
> test it and it works perfectly. I then run a Clean (project->clean) on
> the project, with no error message, and it then won't run. I get an
> error message that the method couldn't be found on Axis. The only way
> (possible work around) that I can recover is to recreate the Web Service
> from the WSDL document which overlays my changes that I have made when
> it recreates the schedule.
> I will get to the possible cause of the problem and solutino in a minute
> but I want to cover some of my research for verificaiton.
>
> Within the project where my Web Service had existed before, I recreated
> the Web Service from the WSDL file and recorded the files that were
> updated (by change date).
>
> Under the .deployables directory and sub directories the following files
> were updated:
> a) server-config.wsdd
> b) deploy.wsdd
> c) undeploy.wsdd
> d) *.class (all the class files were updated)
> e) *.jar (all my jar files that are really reference files were updated)
> f) *.wsdl (the new Soap wsdl was updated)
>
> Under the Mod directory and sub directories (files typically displayed
> in Eclipse) the following files were updated:
> a) *.java (all java files)
> b) deploy.wsdd
> c) undeploy.wsdd
> d) *.jar (all my jar files that are really reference files were updated)
> e) *.wsdl (the new Soap wsdl was updated)
>
> I then run a Clean (project->clean) on my proejct and check to see which
> files were updated and I noticed the following:
>
> Under .deployables directory and subdirectory:
> a) The server-config.wsdd file no longer exists - did not expect)
> b) *.class (all the class files were updated - would expect)
> Since I had tried to redeploy the project and many other different
> things to resolve the issue, I assumed that my problem must exist in one
> of the two areas that changed after the Clean. Since I expect the
> *.class files to be updated I focused on the server-config.wsdd file
> which no longer appeard. I recreated the Web Service again from the
> WSDL, verified that it was functioning again, and then made a copy of
> the server-config.wsdd file. I then performed the Clean, and verified
> that the Web Service was broken again. I then pasted a copy of the
> original server-config.wsdd file back into the directory and ran the Web
> Service again. When I did this the Web Service corrected itself and
> worked fine. Therefore, I am concluding that the problem is the fact
> that the Clean deletes and never recreates the server-
> config.wsdd file. For a temporary solution until it is corrected I
> recommend that the server-config.wsdd file be copied and backed up
> somewhere. If a clean is performed this file can be pased into the
> appropriate directory and the Web Service can be corrected without
> having to overlay all your work with a complete rebuild of the Web Service.
>
> ------- Additional Comment #1 From Chris Brealey 2005-06-25 16:54
> [reply] ------- I wish all bugs were as well explained as this one.
> Turns out there is another for this issue, 94590, so am returning this
> one as a duplicate. This should not be too hard to fix. Thanks - CB.
>
> *** This bug has been marked as a duplicate of 94590 ***
>
>
|
|
|
| Re: WTP complaining about .deployables in non web projects [message #128949 is a reply to message #128843] |
Tue, 02 August 2005 15:27 |
Seng Phung Lu
Messages: 62
Registered: July 2009 |
Member |
|
|
Hi Iran,
I wonder if you're running into this bug.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=105462
AFAIK, this error isn't actually harmful, but perhaps just a timing
issue during validation.
Hope that helps,
Seng
Iran wrote:
> Ben, first o all, thanks for your help.
>
> I'm not sure the problem I described have something to do with this bug
> you mentioned. Perhaps I misunderstood it.
>
> But anyway, this bug could affect non web projects? My real problem is
> when I clean and build a non web project (a Java Project), I receive
> that error message (it's in my last post) complaining about absence of
> .deployables directory.
>
> Can you please confirm that my problem is related to that bug?
>
> Thank you.
>
> Ben wrote:
>
>> This is a bug (94590) in Eclipse and they are aware of it and it will
>> be in the next release. I know that a fix was posted for this but I
>> am not sure where you can go to get this. Also, there are some good
>> write ups about this error and one has details on how to fix the error
>> when it occurs. I suggest that you search the WTP articles to find
>> these.
>> Here is some additional data. I hope this helpls.
>>
>> I have some additional and intersting information regarding this
>> error. A quick refresh, I created a top down Web Service from a WSDL
>> document, test it and it works perfectly. I then run a Clean
>> (project->clean) on the project, with no error message, and it then
>> won't run. I get an error message that the method couldn't be found
>> on Axis. The only way (possible work around) that I can recover is
>> to recreate the Web Service from the WSDL document which overlays my
>> changes that I have made when it recreates the schedule.
>> I will get to the possible cause of the problem and solutino in a
>> minute but I want to cover some of my research for verificaiton.
>>
>> Within the project where my Web Service had existed before, I
>> recreated the Web Service from the WSDL file and recorded the files
>> that were updated (by change date).
>>
>> Under the .deployables directory and sub directories the following
>> files were updated:
>> a) server-config.wsdd
>> b) deploy.wsdd
>> c) undeploy.wsdd
>> d) *.class (all the class files were updated)
>> e) *.jar (all my jar files that are really reference files were updated)
>> f) *.wsdl (the new Soap wsdl was updated)
>>
>> Under the Mod directory and sub directories (files typically displayed
>> in Eclipse) the following files were updated:
>> a) *.java (all java files)
>> b) deploy.wsdd
>> c) undeploy.wsdd
>> d) *.jar (all my jar files that are really reference files were updated)
>> e) *.wsdl (the new Soap wsdl was updated)
>>
>> I then run a Clean (project->clean) on my proejct and check to see
>> which files were updated and I noticed the following:
>>
>> Under .deployables directory and subdirectory:
>> a) The server-config.wsdd file no longer exists - did not expect)
>> b) *.class (all the class files were updated - would expect)
>> Since I had tried to redeploy the project and many other different
>> things to resolve the issue, I assumed that my problem must exist in
>> one of the two areas that changed after the Clean. Since I expect the
>> *.class files to be updated I focused on the server-config.wsdd file
>> which no longer appeard. I recreated the Web Service again from the
>> WSDL, verified that it was functioning again, and then made a copy of
>> the server-config.wsdd file. I then performed the Clean, and verified
>> that the Web Service was broken again. I then pasted a copy of the
>> original server-config.wsdd file back into the directory and ran the
>> Web Service again. When I did this the Web Service corrected itself
>> and worked fine. Therefore, I am concluding that the problem is the
>> fact that the Clean deletes and never recreates the server-
>> config.wsdd file. For a temporary solution until it is corrected I
>> recommend that the server-config.wsdd file be copied and backed up
>> somewhere. If a clean is performed this file can be pased into the
>> appropriate directory and the Web Service can be corrected without
>> having to overlay all your work with a complete rebuild of the Web
>> Service.
>>
>> ------- Additional Comment #1 From Chris Brealey 2005-06-25 16:54
>> [reply] ------- I wish all bugs were as well explained as this one.
>> Turns out there is another for this issue, 94590, so am returning this
>> one as a duplicate. This should not be too hard to fix. Thanks - CB.
>>
>> *** This bug has been marked as a duplicate of 94590 ***
>>
>>
|
|
| |
Goto Forum:
Current Time: Mon Jul 08 14:33:33 GMT 2024
Powered by FUDForum. Page generated in 0.04406 seconds |
] 
Search
Help
Register
Login
Home
