This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 187998 - Maven + Web Service: Web Services are not recognized
Summary: Maven + Web Service: Web Services are not recognized
Status: RESOLVED DUPLICATE of bug 158999
Alias: None
Product: webservices
Classification: Unclassified
Component: JAX-WS (show other bugs)
Version: 6.x
Hardware: PC Windows 7 x64
: P3 normal with 2 votes (vote)
Assignee: Denis Anisimov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-23 13:34 UTC by puce
Modified: 2011-11-02 15:12 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description puce 2010-06-23 13:34:20 UTC
When creating a Web Service in a Maven project, the IDE doesn't recognize the Web Service, eg. no special icon, no design view
Comment 1 David Konecny 2011-09-20 21:49:07 UTC
Denis, mjanicek (Martin) is going to help with Maven EE support (maven.javaee module). I always considered WS support for Maven (maven.websvc) your or mkuchtiak job (mainly because I've had enough of mine own work :-) but perhaps we should/could reconsider that? How is your relationship to Maven these days Denis? :-) Are you OK looking after this area or ... ?

On the other hand there is not that many issues for WS support in Maven I think.
Comment 2 Denis Anisimov 2011-09-21 05:49:06 UTC
(In reply to comment #1)
> Denis, mjanicek (Martin) is going to help with Maven EE support (maven.javaee
> module). I always considered WS support for Maven (maven.websvc) your or
> mkuchtiak job (mainly because I've had enough of mine own work :-) but perhaps
> we should/could reconsider that? How is your relationship to Maven these days
> Denis? :-) Are you OK looking after this area or ... ?
> 
> On the other hand there is not that many issues for WS support in Maven I
> think.

That's not problem for me actually.
There is just one module maven.jaxws which contains maven specific logic for 
WS ( both JAX-WS and JAX-RS ). I've done a lot of corrections already in this module. So this is not a problem for me keep responsibility for WS in Maven too.

The problem with this bug ( and other bugs you assigned recently) :  they are 
filed against Maven. So I don't get notifications about this .
And don't look at this product type in BZ at all.
They really has wrong product/category actually and should be reassigned to WS.
So feel free to change product/category and assign them to me.
Comment 3 Denis Anisimov 2011-09-21 07:24:19 UTC
Web service is recognized. 
There is special node in the project explorer with special icon.

But the is one issue : no design view for WS.
Will investigate.
Comment 4 Denis Anisimov 2011-09-21 10:58:32 UTC
The design view for JAX-WS inside Maven is just not implemented.
Maven project has no JaxWsModel in its lookup. And there is no Service instance 
for Maven.
Different class should be used to get information about WS. For Maven it is JaxWsService from lightapi module.
The design view code should be adopted to use this alternative of service.
This is TOO much work for upcoming 7.1 release. And it is too risky to do this now.
So I postpone this.
I commit just a basic commented changes which allows to recognize WS data object.

web-main#a0c36255c886
Comment 5 Quality Engineering 2011-09-22 14:54:39 UTC
Integrated into 'main-golden'
Changeset: http://hg.netbeans.org/main-golden/rev/a0c36255c886
User: Denis Anisimov <ads@netbeans.org>
Log: Commented recognition of JAX-WS DataObject in Maven case as initial fix for BZ#187998 - Maven + Web Service: Web Services are not recognized .
Comment 6 Martin Janicek 2011-11-02 14:10:15 UTC
Denis, I have here this one plus few similar WS related issues, so as you suggested in comment #2 I'm going to reassign them into WS category for evaluation (feel free to reassign them back if you think that there need to be done something on my side)
Comment 7 Denis Anisimov 2011-11-02 14:17:38 UTC

*** This bug has been marked as a duplicate of bug 158999 ***