[JBoss JIRA] (JBIDE-22228) NPE when deploying to Openshift EAP
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22228?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen reassigned JBIDE-22228:
-------------------------------------------
Assignee: Alexey Kazakov (was: Max Rydahl Andersen)
Bulk moving any issue assigned to me directly to Alexey for his new role.
> NPE when deploying to Openshift EAP
> -----------------------------------
>
> Key: JBIDE-22228
> URL: https://issues.jboss.org/browse/JBIDE-22228
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Environment: Windows 10
> Reporter: Thomas Mäder
> Assignee: Alexey Kazakov
> Fix For: 4.4.x
>
>
> When I try to publish to an EAP in the CDK, I get a NullPointerException:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:309)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:298)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getDeploymentConfig(OpenShiftServerUtils.java:390)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:87)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:311)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-16107) Improve portlet component
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16107?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen reassigned JBIDE-16107:
-------------------------------------------
Assignee: Alexey Kazakov (was: Max Rydahl Andersen)
Bulk moving any issue assigned to me directly to Alexey for his new role.
> Improve portlet component
> -------------------------
>
> Key: JBIDE-16107
> URL: https://issues.jboss.org/browse/JBIDE-16107
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: portal-gatein
> Affects Versions: 4.1.1.CR1
> Reporter: Snjezana Peco
> Assignee: Alexey Kazakov
> Fix For: LATER
>
>
> Currently, the portlet component supports (or it should support) the following runtimes:
> - JBoss Portal 2.7
> - EPP 4.3/5.0/5.1/5.2
> - GateIn 3.x
> - JPP 6.x
> There are three facets:
> - Java Portlet
> - JSF Portlet
> - Seam Portlet
> The required libraries are the following:
> Java Portlet
> - requires portlet-api that is, currently, correctly recognized for some of the above mentioned runtimes.
> However, there is no rule how this library would be recognized, which means it could be broken in some new runtime.
> JSF Portlet
> - requires portletbridge and, optionaly, richfaces libraries
> Those libraries can be added from the server runtimes or a user can use his own distribution that can be added to the JSF Portlet wizard page.
> If a user creates a Seam portlet and selects his richfaces distribution, the richfaces libraries added with the seam facet will be replaced with the user's library because we can't have two richfaces versions in the application.
> If a user doesn't select his richfaces distribution, the richfaces libraries from Seam will be used.
> Currently, there is no rule for adding those libraries. Different server runtimes contain the libraries in different locations. Portletbridge and richfaces distributions also have different structure.
> Seam Portlet
> The Seam portlet uses the standard seam facet and configures web.xml.
> I have tried to deploy and run the seam portlet on JPP 6.1 using the Seam 2.3.2 version from WFK.
> It can be deployed and run. The home page is opened, but I am not sure if all the features work correctly.
> Seam 2.3.2 works properly on EAP 6.1, AS 7.1.1, AS 7.2.0.Final.
> Seam 2.3.1 (the latest community version) requires adding the guava module to the jboss-deployment-structure.xml.
> If a user selects the JBoss Maven Integration facet, the portlet component will create a maven project. It is possible to add portletbridge 2.0.0 as a maven artifact.
> We would probably have to improve this feature.
> We would have to define the following:
> - what server runtimes we want to support in the future (AS 7+ runtimes GateIn 3.5/3.6, JPP
> - what kinds of portlets we would support(Java portlet, JSF portlet, JSF Richfaces... not sure for Seam)
> - how the required libraries (portletbridge, richfaces...) would be added. Is there a rule how they are placed to the server?
> - if we will support only a mavenized portlet (all GateIn 3.6, JPP 6.1 quickstarts are maven projects)
> If we decide to support only mavenized portlets, adding libraries would be much simpler. A user would only need to choose versions, i.e., to define different Maven libraries containers.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-18963) when whatsnew index generation is run on files that refer components that does not exist an error message containing what component is at fault should be printed
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18963?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen reassigned JBIDE-18963:
-------------------------------------------
Assignee: Alexey Kazakov (was: Max Rydahl Andersen)
Bulk moving any issue assigned to me directly to Alexey for his new role.
> when whatsnew index generation is run on files that refer components that does not exist an error message containing what component is at fault should be printed
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18963
> URL: https://issues.jboss.org/browse/JBIDE-18963
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: website
> Affects Versions: 4.2.3.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Alexey Kazakov
> Fix For: LATER
>
>
> today when having invalid components you get something like:
> {code}
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:65:in `block (4 levels) in singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:64:in `each'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:64:in `block (3 levels) in singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:29:in `each'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:29:in `block (2 levels) in singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:27:in `each'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:27:in `block in singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:65533:in `instance_eval'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:65533:in `singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:65531:in `__tilt_70190394039780'
> {code}
> as found in https://github.com/jbosstools/jbosstools-website/pull/311/files
> the logic is all embedded in haml leaving no room for proper error handling.
> should do some basic asserts in the pipeline for that ids actually exists in components.yml or at least just use component id as fall back name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-17483) Quick Fix for Console configuration "" does not exist
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17483?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen reassigned JBIDE-17483:
-------------------------------------------
Assignee: Alexey Kazakov (was: Max Rydahl Andersen)
Bulk moving any issue assigned to me directly to Alexey for his new role.
> Quick Fix for Console configuration "" does not exist
> -----------------------------------------------------
>
> Key: JBIDE-17483
> URL: https://issues.jboss.org/browse/JBIDE-17483
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Reporter: Burr Sutter
> Assignee: Alexey Kazakov
> Fix For: 4.2.x, 4.3.x
>
> Attachments: JBIDE-17483-webnate.zip
>
>
> When using Maven import on "someone else's" project, it is fairly common to get a complaint about the missing Console Configuration. Numerous workarounds have been documented and can be found via Google - some work, some do not - ideally we would offer a quickfix to help address this common error message inside of the IDE.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-9405) Add Preview step to maven profile dialog
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9405?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen reassigned JBIDE-9405:
------------------------------------------
Assignee: Alexey Kazakov (was: Max Rydahl Andersen)
Bulk moving any issue assigned to me directly to Alexey for his new role.
> Add Preview step to maven profile dialog
> ----------------------------------------
>
> Key: JBIDE-9405
> URL: https://issues.jboss.org/browse/JBIDE-9405
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Reporter: Max Rydahl Andersen
> Assignee: Alexey Kazakov
> Fix For: 3.3.x
>
>
> Especially for multiple projects it sometimes feel unsafe to click ok, suggest that we add a Preview... button similar to what is seen under Refactoring that will show the list of projects that will be changed/updated.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-16612) NPE after importing ui project from WFK 2.3
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16612?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen reassigned JBIDE-16612:
-------------------------------------------
Assignee: Alexey Kazakov (was: Max Rydahl Andersen)
Bulk moving any issue assigned to me directly to Alexey for his new role.
> NPE after importing ui project from WFK 2.3
> -------------------------------------------
>
> Key: JBIDE-16612
> URL: https://issues.jboss.org/browse/JBIDE-16612
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, upstream
> Affects Versions: 4.2.0.Alpha2
> Environment: JBDS 8.0.Alpha2b, Linus 64, Fedora 19, OpenJDK 1.7
> Reporter: Jiri Peterka
> Assignee: Alexey Kazakov
> Priority: Critical
> Fix For: 4.2.x, 4.3.x
>
> Attachments: npe-ui-prj-hibernate.png
>
>
> After import there are multiple errors in error log
> {code}
> java.lang.NullPointerException
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentAttribute.getMappingKey(AbstractJavaPersistentAttribute.java:212)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.AbstractPersistentAttributeValidator.validate(AbstractPersistentAttributeValidator.java:33)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentAttribute.validateAttribute(AbstractJavaPersistentAttribute.java:646)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentAttribute.validate(AbstractJavaPersistentAttribute.java:641)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentType.validateAttribute(AbstractJavaPersistentType.java:858)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentType.validateAttributes(AbstractJavaPersistentType.java:852)
> at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaPersistentType.validate(AbstractJavaPersistentType.java:838)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericClassRef.validateJavaManagedType(GenericClassRef.java:444)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericClassRef.validate(GenericClassRef.java:438)
> at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.validateClassRefs(AbstractPersistenceUnit.java:2403)
> at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.validate(AbstractPersistenceUnit.java:2285)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.validatePersistenceUnit(GenericPersistence.java:347)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.validate(GenericPersistence.java:303)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.validate(GenericPersistenceXml.java:243)
> at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericContextRoot.validate(GenericContextRoot.java:248)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.validate(AbstractJpaProject.java:1459)
> at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.validate(HibernateJpaProject.java:289)
> at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.getValidationMessages(AbstractJpaProject.java:1447)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.buildValidationMessages_(InternalJpaProjectManager.java:584)
> at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$BuildValidationMessagesCommand.execute(InternalJpaProjectManager.java:572)
> at org.eclipse.jpt.common.core.internal.utility.command.CommandJobCommandAdapter.execute(CommandJobCommandAdapter.java:50)
> at org.eclipse.jpt.common.core.internal.utility.command.JobCommandJob.run(JobCommandJob.java:42)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
> {code}
> java.lang.NullPointerException
> at org.eclipse.jpt.jpa.ui.internal.structure.MappingStructureItemLabelProviderFactory$AttributeMappingImageDescriptorTransformer.getJpaPlatformUi(MappingStructureItemLabelProviderFactory.java:192)
> at org.eclipse.jpt.jpa.ui.internal.structure.MappingStructureItemLabelProviderFactory$AttributeMappingImageDescriptorTransformer.getAttributeMappingUiDefinition(MappingStructureItemLabelProviderFactory.java:187)
> at org.eclipse.jpt.jpa.ui.internal.structure.MappingStructureItemLabelProviderFactory$AttributeMappingImageDescriptorTransformer.transform(MappingStructureItemLabelProviderFactory.java:182)
> at org.eclipse.jpt.jpa.ui.internal.structure.MappingStructureItemLabelProviderFactory$AttributeMappingImageDescriptorTransformer.transform(MappingStructureItemLabelProviderFactory.java:1)
> at org.eclipse.jpt.common.utility.internal.model.value.TransformationPropertyValueModel.transform(TransformationPropertyValueModel.java:113)
> at org.eclipse.jpt.common.utility.internal.model.value.TransformationPropertyValueModel.engageModel(TransformationPropertyValueModel.java:137)
> at org.eclipse.jpt.common.utility.internal.model.value.AbstractPropertyValueModel.addPropertyChangeListener(AbstractPropertyValueModel.java:83)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractModelItemLabelProvider.<init>(AbstractModelItemLabelProvider.java:65)
> at org.eclipse.jpt.common.ui.internal.jface.ModelItemExtendedLabelProvider.<init>(ModelItemExtendedLabelProvider.java:48)
> at org.eclipse.jpt.jpa.ui.internal.structure.MappingStructureItemLabelProviderFactory.buildPersistentAttributeProvider(MappingStructureItemLabelProviderFactory.java:143)
> at org.eclipse.jpt.jpa.ui.internal.platform.generic.GenericNavigatorItemLabelProviderFactory.buildPersistentAttributeProvider(GenericNavigatorItemLabelProviderFactory.java:150)
> at org.eclipse.jpt.jpa.ui.internal.platform.generic.GenericNavigatorItemLabelProviderFactory.buildProvider(GenericNavigatorItemLabelProviderFactory.java:78)
> at org.eclipse.jpt.jpa.ui.internal.navigator.JpaNavigatorItemLabelProviderFactory.buildProvider(JpaNavigatorItemLabelProviderFactory.java:37)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.addLabelProvider(AbstractItemStructuredStateProviderManager.java:245)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.add(AbstractItemStructuredStateProviderManager.java:241)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.add(ItemTreeStateProviderManager.java:118)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.addAll(AbstractItemStructuredStateProviderManager.java:220)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.add(ItemTreeStateProviderManager.java:121)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.addAll(AbstractItemStructuredStateProviderManager.java:220)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.add(ItemTreeStateProviderManager.java:121)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.addAll(AbstractItemStructuredStateProviderManager.java:220)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.add(ItemTreeStateProviderManager.java:121)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.addAll(AbstractItemStructuredStateProviderManager.java:220)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.add(ItemTreeStateProviderManager.java:121)
> at org.eclipse.jpt.common.ui.internal.jface.AbstractItemStructuredStateProviderManager.addAll(AbstractItemStructuredStateProviderManager.java:231)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.childrenChanged_(ItemTreeStateProviderManager.java:110)
> at org.eclipse.jpt.common.ui.internal.jface.ItemTreeStateProviderManager.childrenChanged(ItemTreeStateProviderManager.java:105)
> at org.eclipse.jpt.common.ui.internal.jface.ModelItemTreeContentProvider.notifyManager(ModelItemTreeContentProvider.java:63)
> at org.eclipse.jpt.common.ui.internal.jface.ModelItemContentProvider.childrenAdded_(ModelItemContentProvider.java:119)
> at org.eclipse.jpt.common.ui.internal.jface.ModelItemContentProvider.childrenAdded(ModelItemContentProvider.java:113)
> at org.eclipse.jpt.common.ui.internal.jface.ModelItemContentProvider$ChildrenListener.itemsAdded(ModelItemContentProvider.java:92)
> at org.eclipse.jpt.common.ui.internal.swt.listeners.SWTCollectionChangeListenerWrapper.forward(SWTCollectionChangeListenerWrapper.java:51)
> at org.eclipse.jpt.common.ui.internal.swt.listeners.SWTCollectionChangeListenerWrapper.forward(SWTCollectionChangeListenerWrapper.java:1)
> at org.eclipse.jpt.common.ui.internal.swt.listeners.SWTListenerWrapperDelegate.forwardEvents(SWTListenerWrapperDelegate.java:92)
> at org.eclipse.jpt.common.ui.internal.swt.listeners.SWTListenerWrapperDelegate$ForwardEventsRunnable.run(SWTListenerWrapperDelegate.java:81)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3746)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3394)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months