[
https://issues.apache.org/jira/browse/NETBEANS-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174426#comment-17174426
]
Pete Whelpton edited comment on NETBEANS-4559 at 8/10/20, 4:16 PM:
-------------------------------------------------------------------
Ok - so I have gotten somewhere on what is causing this.
It is since Payara functionality was merged into NB base. What is happening is
that when NB tries to get the default mappings for a Maven Web project, the
first implementation of a {code:java}MavenActionsProvider{code} it finds is an
instance of {code:java}MicroActionsProvider{code} from the Payara Mircro
Project.
This seems to be because the {code:java}MicroActionsProvider{code} is
registered to Maven Web Projects:
{code:java}
@ProjectServiceProvider(
service = MavenActionsProvider.class,
projectType = MAVEN_WAR_PROJECT_TYPE
)
public class MicroActionsProvider implements MavenActionsProvider {
{code}
It *should* be using the {code:java}J2eeActionsProvider.java{code} from the
Maven web project.
The Payara Micro Project has basically a blank entry for the mapping between
Run (Netbeans) and Maven (Package), so that's what we now get in regular Maven
Web projects....
[~jgauravgupta] can you offer any help?
was (Author: peedeeboy):
Ok - so I have gotten somewhere on what is causing this.
It is since Payara functionality was merged into NB base. What is happening is
that when NB tries to get the default mappings for a Maven Web project, the
first implementation of a {code:java}MavenActionsProvider{code} it finds is an
instance of {code:java}MicroActionsProvider{code} from the Payara Mircro
Project.
This seems to be because the {code:java}MicroActionsProvider{code} is
registered to Maven Web Projects:
{code:java}
@ProjectServiceProvider(
service = MavenActionsProvider.class,
projectType = MAVEN_WAR_PROJECT_TYPE
)
public class MicroActionsProvider implements MavenActionsProvider {
{code}
It *should* be using the {code::java}J2eeActionsProvider.java{code} from the
Maven web project.
The Payara Micro Project has basically a blank entry for the mapping between
Run (Netbeans) and Maven (Package), so that's what we now get in regular Maven
Web projects....
[~jgauravgupta] can you offer any help?
> Web Project Properties Dialog fails to save Relative URL
> --------------------------------------------------------
>
> Key: NETBEANS-4559
> URL: https://issues.apache.org/jira/browse/NETBEANS-4559
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Maven
> Affects Versions: 11.3
> Reporter: Bernard
> Priority: Critical
> Attachments: ProjectPropertiesActionRun.png,
> ProjectPropertiesActionRun.png, ProjectPropertiesRun.png,
> PropertiesBefore.png, PropertiesBeforeAfter.png, WebSocketMovieTheater.zip,
> image-2020-08-07-15-48-32-635.png, image-2020-08-09-11-54-50-908.png,
> messages.log
>
>
> Please see attached images and project.
> In the project properties, there is a field "Relative URL" for the page to
> load relative to the context path.
> If I enter it and confirm the dialog, then after re-opening the dialog again,
> the value is lost.
>
> The project is from
> [https://technology.amis.nl/2015/05/14/java-web-application-sending-json-messages-through-websocket-to-html5-browser-application-for-real-time-push/]
> - just adapted to run under NetBeans.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
