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 118335 - Configure Handlers can't work with custom namespaces
Summary: Configure Handlers can't work with custom namespaces
Status: RESOLVED WONTFIX
Alias: None
Product: webservices
Classification: Unclassified
Component: JAX-WS (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Denis Anisimov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-10 10:16 UTC by Jaroslav Pospisil
Modified: 2010-11-12 08:39 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
messages.log (62.93 KB, application/octet-stream)
2007-10-10 10:18 UTC, Jaroslav Pospisil
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Pospisil 2007-10-10 10:16:51 UTC
Build200710090000,JDK1.6,Vista

Open Samples/Identity Blueprints/StockQuoteService/StockQuoteService-war. If you Right-click on Web
Services/StockQuoteService and select Configure Handlers,you'll get RuntimeException. This is caused by 
namespace jws, which is used in handlers.xml file (please move it first from src/java/com/ into src/java/com/samples,
because of issue 118300).When I use default namespace in tags,it works normally.
Attaching messages.log with the issue.
Comment 1 Jaroslav Pospisil 2007-10-10 10:18:21 UTC
Created attachment 50564 [details]
messages.log
Comment 2 Roderico Cruz 2007-10-29 19:53:06 UTC
This is not a show stopper and setting the milestone to future.
Comment 3 Lukas Jungmann 2008-04-14 17:11:57 UTC
moving opened issues where TM != dev to TM=TBD
Comment 4 Roderico Cruz 2008-09-24 15:12:54 UTC
This will require a rewrite of the model.
Comment 5 Milan Kuchtiak 2008-11-28 08:53:03 UTC
Reassigning to mkuchtiak.
Comment 6 Denis Anisimov 2010-10-27 13:54:35 UTC
The original problem is fixed : handlers.xml file in the StockQuoteService example
uses default namespace.
But the model really  has a problem with xml elements with not default namespace.
The fix for this requires rewriting model for handlers.xml.
The best way for this is implement xam/xdm domain specific model instead of 
schema2beans usage.
Comment 7 Denis Anisimov 2010-11-12 08:39:08 UTC
The original problem is fixed .
It relates to StockQuoteService sample project.
Its handlers.xml file now has elements in the default namespace.

On the other hand there is a common problem with schema2beans tool which 
is used for generating object model based on schema or dtd.
Its deserializer is not able to handle correct xml file if its elements 
has prefixes ( defined in the not default namespace ).

This problem is common for any xml descriptor file: web.xml, ....
There is no problem if such file is created inside IDE and is not modified 
outside it . 

The full solution is required to rewriting all XML model based on schema2beans.
So this issue is not just about handlers.xml.
It requires too much resources so closing as wontfix.