[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-3333) ESB project wizard and deployment doesn't work at all with WTP 3.03
Denny Xu (JIRA)
jira-events at lists.jboss.org
Mon Dec 15 02:29:37 EST 2008
[ https://jira.jboss.org/jira/browse/JBIDE-3333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denny Xu updated JBIDE-3333:
----------------------------
Attachment: exception.txt
when the ESB project wizard runs with WTP 3.03, it gets an NPE , the exception details is attached.
This is because when we create a VirtualComponent in WTP 3.02 or earlier, we use the following way:
IVirtualComponent c = ComponentCore.createComponent(project);
but in WTP3.03, if we still use this method to create a VirtualComponent, the result of the ComponentCore.createComponent(project) is null,
so the exception occurs.
The algorithm of VirtualComponent creation in WTP3.03 is:
if you have already registered a ComponentFactory in extension point for the Facet, then the VirtualComponent is created using the ComponentFactory
if you have not , then it will check if the project is a flexibleProject, if false, it returns null, if true it returns *new VirtualComponent(project, new Path("/"))*;
in our current case, we can use *new VirtualComponent(project, new Path("/"))* to create it, it will bypass some wtp check , but it is not a standard way to go.
> ESB project wizard and deployment doesn't work at all with WTP 3.03
> -------------------------------------------------------------------
>
> Key: JBIDE-3333
> URL: https://jira.jboss.org/jira/browse/JBIDE-3333
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb
> Affects Versions: 3.0.0.cr1
> Reporter: Denny Xu
> Assignee: Denny Xu
> Priority: Blocker
> Fix For: 3.0.0.cr1
>
> Attachments: exception.txt
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list