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 106397 - AM-Deploy breaks deployment
Summary: AM-Deploy breaks deployment
Status: VERIFIED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Identity (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Peter Liu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-12 14:28 UTC by Martin Grebac
Modified: 2007-08-24 16:58 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Grebac 2007-06-12 14:28:28 UTC 
Create web project
Create WS from Java
Open Edit WS Attributes dialog
Switch to AM, Switch to WSIT tab, do nothing in both
Close Edit WS Attributes

am-deploy.xml file is created, and when you try to deploy the project, you get this error:

am-init:
am-deploy:
amConfigFile: /export/home/mg116726/work/builds/glassfish/v2-b41c/domains/domain1/config/AMConfig.properties
amConfigXmlDir: /export/home/mg116726/NetBeansProjects/WebApplication3/src/conf
org.netbeans.modules.identity.profile.api.configurator.ConfiguratorException: Invalid AM_CONFIG_FILE system property.
Please set it to <asroot>/domains/domain1/config/AMConfig.properties.
org.netbeans.modules.identity.profile.api.configurator.ServerProperties.<init>(ServerProperties.java:111)
org.netbeans.modules.identity.profile.api.configurator.impl.dynamic.SecurityMechanismRetriever.getAllMessageLevelSecurityMechanism(SecurityMechanismRetriever.java:78)
...
Comment 1 Peter Liu 2007-06-21 02:07:39 UTC 
This issue is due to the AM_CONFIG_FILE property not properly set in the netbeans.conf.  I am lowering this bug to P2
because there is a workaround.

For beta1, we plan to eliminate the AM_CONFIG_FILE flag and instead implement auto-detection of the am instance. So,
this issue will not show up again.
Comment 2 Peter Liu 2007-07-05 21:02:01 UTC 
This issue has been fixed in the trunk. We no longer depend on the AM_CONFIG_FILE flag anymore.  Instead, we autodetect
the AM installation under the glassfish installation. Furthermore, the am deploy task will exit normally if there is no
am installation under the current appserver target.
Comment 3 Jaroslav Pospisil 2007-08-24 16:58:59 UTC 
VERIFIED