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 85733 - setEndpointBinding on MessageSecurityProvider isnt functional for JavaEE 5 projects
Summary: setEndpointBinding on MessageSecurityProvider isnt functional for JavaEE 5 pr...
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P1 blocker (vote)
Assignee: _ pcw
URL:
Keywords: REGRESSION
Depends on:
Blocks: 85732
  Show dependency tree
 
Reported: 2006-09-26 02:07 UTC by Srividhya Narayanan
Modified: 2006-09-26 20:17 UTC (History)
1 user (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 Srividhya Narayanan 2006-09-26 02:07:08 UTC
Create a web/ejb JavaEE5 project. As part of enabling security through
Enterprise Pack wizard the sun DD files are not changed with the
message-security-binding elements.

In the case of ejb I notice that the DD files are not created by default at all.
In the case of web projects  default DD files are being created. I have verified
the parameters I pass to the API and they seem to be valid. In the default
create web service wizard UI, I accept the defaults which creates NewWebService
for me. I pass these as values for the API:
setEndpointBinding(C:\temp\WebApplication10\web\WEB-INF\sun-web.xml, NewWeb
Service, NewWebService, <msbind object that i create").

I dont see any exceptions. It just returns false.

This is a regression of functionality on my side. Unless there is something
wrong in the values I am sending you.. which is quite likely.
Comment 1 Srividhya Narayanan 2006-09-26 02:07:33 UTC
BTW, the service-ref side of API is intact.
Comment 2 _ pcw 2006-09-26 20:17:59 UTC
Closing as INVALID.

Identity module was passing in the wrong names for the endpoint and port. When
the correct names are used, the API works as expected.

Vidhya is going to rewrite the code on identity's side to use the same api for
retrieving names that the server plugin uses (ie via
J2eeModuleProvider.getDeploymentDescriptor()) which hopefully will prevent
future problems of this nature.