October 2008 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-2064) JBossESB graphical node/service designer

by Mark Little (JIRA)

JBossESB graphical node/service designer ---------------------------------------- Key: JBIDE-2064 URL: http://jira.jboss.com/jira/browse/JBIDE-2064 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Reporter: Mark Little Attachments: SOA Tooling.pdf Currently the ESB deployment descriptor is XML based but we need it to be graphically oriented. Each ESB service is a collection of actions that are re-usable components. The graphical tool would allow for the construction (within Eclipse) of a service from action chaining. The action descriptions would be storable in a repository (though that is a second level addition). We want to isolate the user from the XML as much as possible because it is prone to errors. Plus, it makes service re-usability more problematical. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-2649) Archives dialog shows warning/errors in wrong location and has a weird no-named label

by Max Rydahl Andersen (JIRA)

Archives dialog shows warning/errors in wrong location and has a weird no-named label ------------------------------------------------------------------------------------- Key: JBIDE-2649 URL: https://jira.jboss.org/jira/browse/JBIDE-2649 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 3.0.0.alpha Reporter: Max Rydahl Andersen Fix For: 3.0.0.beta1 Not sure when this were added but just saw this today: 1) When the destiantion folder is not valid the dialog shows a warning below the field. Nothing is shown in the titleareadialog message area as normal warnings. 2) The label below the field is in a different font and has no name. I assume it shows the physical location for the file ? 3) Why have "Workspace relative" and "Filesystem relative" below the field it influences ? Why not put it above and just have it say "Relative to: (x) Workspace ( ) Filesystem" and avoid the double wording? -- 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

15 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-2844) NPE when trying to publish to JBoss server

by Fikri aidoun (JIRA)

NPE when trying to publish to JBoss server ------------------------------------------ Key: JBIDE-2844 URL: https://jira.jboss.org/jira/browse/JBIDE-2844 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.alpha Reporter: Fikri aidoun Priority: Minor I am getting the NPE exception described below when simply trying to start my JBoss 4.0.4 server. I have defined a Project archive to build an exploded archive (war) under the deploy forlder of my JBoss home. thanks in advance for your help! -- Error Details -- Date: Fri Oct 03 14:42:57 CEST 2008 Message: Could not publish to the server. Severity: Error Plugin: org.eclipse.wst.server.core Session Data: eclipse.buildId=M20080911-1700 java.version=1.5.0_06 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR Command-line arguments: -os win32 -ws win32 -arch x86 Exception Stack Trace: java.lang.NullPointerException at org.jboss.ide.eclipse.as.core.modules.PackageModuleFactory$ArchiveContainerResource.addFilesetAsChild(PackageModuleFactory.java:274) at org.jboss.ide.eclipse.as.core.modules.PackageModuleFactory$DelegateInitVisitor.visit(PackageModuleFactory.java:214) at org.jboss.ide.eclipse.archives.core.model.internal.ArchiveNodeImpl.accept(ArchiveNodeImpl.java:244) at org.jboss.ide.eclipse.archives.core.model.internal.ArchiveNodeImpl.accept(ArchiveNodeImpl.java:249) at org.jboss.ide.eclipse.archives.core.model.internal.ArchiveNodeImpl.accept(ArchiveNodeImpl.java:249) at org.jboss.ide.eclipse.archives.core.model.internal.ArchiveNodeImpl.accept(ArchiveNodeImpl.java:249) at org.jboss.ide.eclipse.archives.core.model.internal.ArchiveNodeImpl.accept(ArchiveNodeImpl.java:232) at org.jboss.ide.eclipse.as.core.modules.PackageModuleFactory$PackagedModuleDelegate.init(PackageModuleFactory.java:397) at org.jboss.ide.eclipse.as.core.modules.PackageModuleFactory$PackagedModuleDelegate.members(PackageModuleFactory.java:402) at org.eclipse.wst.server.core.internal.ModulePublishInfo.fillCache(ModulePublishInfo.java:285) at org.eclipse.wst.server.core.internal.ModulePublishInfo.getDelta(ModulePublishInfo.java:335) at org.eclipse.wst.server.core.internal.ServerPublishInfo.getDelta(ServerPublishInfo.java:368) at org.eclipse.wst.server.core.internal.Server.getPublishedResourceDelta(Server.java:1340) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.getPublishedResourceDelta(ServerBehaviourDelegate.java:652) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:821) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:707) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2404) at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:301) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- 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

15 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-2835) Consider the organization of the Smooks editor plug-ins

by John Graham (JIRA)

Consider the organization of the Smooks editor plug-ins ------------------------------------------------------- Key: JBIDE-2835 URL: https://jira.jboss.org/jira/browse/JBIDE-2835 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: John Graham Assignee: Xue Peng Priority: Minor Fix For: 3.0.0.beta1 Max asks: "Do we really need that many smooks plugins ? There are only one test plugin but 7 plugins and each of them very small and as far as I can see very dependent on each other so why the separation ?" Ideally we'd like an extensible editor where data model types (Java, XML, etc.) can be added to the core, so having separate plug-ins for these makes sense. But probably the model, model.edit and graphical info plug-ins can be consolidated into one model, or perhaps even into the core Smooks plug-in (unless we imagine a use case for the model outside the editor code.) -- 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

15 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-2826) Project archives node shows up on projects that does not have any project archives

by Max Rydahl Andersen (JIRA)

Project archives node shows up on projects that does not have any project archives ---------------------------------------------------------------------------------- Key: JBIDE-2826 URL: https://jira.jboss.org/jira/browse/JBIDE-2826 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Affects Versions: 3.0.0.alpha Reporter: Max Rydahl Andersen Assignee: Rob Stryker Fix For: 3.0.0.beta1 I guess this is because archives builder/nature is enabled on all projects by default or is it just shown without checking if it is relevant ? -- 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

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-2932) Project archive dialog does not say which archive is having issues

by Max Rydahl Andersen (JIRA)

Project archive dialog does not say which archive is having issues ------------------------------------------------------------------ Key: JBIDE-2932 URL: https://jira.jboss.org/jira/browse/JBIDE-2932 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.beta1 Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Minor Fix For: 3.0.0.beta1 The new dialog that shows up when an error occur in project archives does not tell the user which project archive that is having issues. See http://screencast.com/t/4d1IE6zT3 It just says "Error building project archives", couldn't it say "Error building test.jar from Project XYZ archives" ? -- 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

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-2852) An internal error occurend during: "Build Archive Node"

by Vofeka (JIRA)

An internal error occurend during: "Build Archive Node" ------------------------------------------------------- Key: JBIDE-2852 URL: https://jira.jboss.org/jira/browse/JBIDE-2852 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.alpha Reporter: Vofeka Priority: Critical I keep getting this exception each time i try to do a publish an exploded war archive created on a project. creation of the archive and first publish goes fine. But every other publish give me this NPE :-( Thanks in advance for you help and keep up the good work! Cheers -- Error Details -- Date: Mon Oct 06 10:57:02 CEST 2008 Message: An internal error occurred during: "Build Archive Node". Severity: Error Plugin: org.eclipse.core.jobs Session Data: eclipse.buildId=M20080911-1700 java.version=1.5.0_06 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR Command-line arguments: -os win32 -ws win32 -arch x86 Exception Stack Trace: java.lang.NullPointerException at org.jboss.ide.eclipse.archives.core.util.internal.ModelTruezipBridge.getFiles(ModelTruezipBridge.java:212) at org.jboss.ide.eclipse.archives.core.util.internal.ModelTruezipBridge.copyFiles(ModelTruezipBridge.java:144) at org.jboss.ide.eclipse.archives.core.util.internal.ModelTruezipBridge.fullFilesetBuild(ModelTruezipBridge.java:77) at org.jboss.ide.eclipse.archives.core.util.internal.ModelTruezipBridge.fullFilesetBuild(ModelTruezipBridge.java:73) at org.jboss.ide.eclipse.archives.core.build.ArchiveBuildDelegate.fullFilesetBuild(ArchiveBuildDelegate.java:148) at org.jboss.ide.eclipse.archives.core.build.ArchiveBuildDelegate.fullArchiveBuild(ArchiveBuildDelegate.java:124) at org.jboss.ide.eclipse.archives.ui.providers.ArchivesActionProvider$8.run(ArchivesActionProvider.java:318) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- 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

15 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-2876) Open jboss-esb.xml editor when ESB project creation is done.

by Denny Xu (JIRA)

Open jboss-esb.xml editor when ESB project creation is done. ------------------------------------------------------------ Key: JBIDE-2876 URL: https://jira.jboss.org/jira/browse/JBIDE-2876 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Affects Versions: 3.0.0.beta1 Reporter: Denny Xu Assignee: Denny Xu Fix For: 3.0.0.beta1 Once the project is created, the ESB editor should be open automatic for editing jboss-esb.xml -- 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

15 years, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2069) SOI viewer

by Mark Little (JIRA)

SOI viewer ---------- Key: JBIDE-2069 URL: http://jira.jboss.com/jira/browse/JBIDE-2069 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Reporter: Mark Little We need a way of viewing the running SOA-P nodes and being able to drill down into them to see the services deployed on them, the version of the services etc. Then we would like to be able to tie this into the service development and deployment lifecycle: by being able to drag a developed service onto a graphical representation of a service node and have it be deployed automatically by the tool. Some of this may already exist in JON. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-2068) Design-time service creator

by Mark Little (JIRA)

Design-time service creator --------------------------- Key: JBIDE-2068 URL: http://jira.jboss.com/jira/browse/JBIDE-2068 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Reporter: Mark Little When building services within a Service Oriented Infrastructure (SOI) you typically do so by composition of other services. Those other services are typically discovered dynamically either by browsing the registry or by broadcasting to the entire SOI. The information returned by such a search (registry or broadcast) contains service contract information (such as the SLA, type of service, work it offers etc.) and the developer can then select the right service(s) from the list. Newly created services (either composites or atomic) are then published back to the registry (or the SOI). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2008