December 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-4213) Taglibs which defined as facelets.LIBRARIES param in web.xml doesn't show in Web Projects View in Tag Libraries folder.

by Maxim Areshkau (JIRA)

Taglibs which defined as facelets.LIBRARIES param in web.xml doesn't show in Web Projects View in Tag Libraries folder. ----------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4213 URL: https://jira.jboss.org/jira/browse/JBIDE-4213 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml source editing Reporter: Maxim Areshkau Assignee: Viacheslav Kabanovich Fix For: 3.1.0.M1 Steps to reproduce: 1) import into eclipse workspace https://svn.jboss.org/repos/jbosstools/trunk/jsf/tests/org.jboss.tools.js... project 2) open Web Project View 3) open Tag Libraries leaf ASSERT Here should be tag library /tags/facelets.taglib.xml which defined in web.xml as facelets.LIBRARIES context param. -- 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

16 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5421) Input types with no configuration beyond specifying sample data should show some text

by Brian Fitzpatrick (JIRA)

Input types with no configuration beyond specifying sample data should show some text ------------------------------------------------------------------------------------- Key: JBIDE-5421 URL: https://jira.jboss.org/jira/browse/JBIDE-5421 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.GA Reporter: Brian Fitzpatrick Assignee: Xue Peng Fix For: 3.1.0.GA For Input Types without any configuration UI beyond adding a sample input data file, we should show a label or something that says "Specify sample data in the Input Data section." It just looks odd to not have anything showing whether you expand the section or not and might cause some people to think something is wrong or missing. This includes the following input types: - XML - Java - XSD/WSDL -- 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

16 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBDS-660) Server search window during installation doesn't close.

by Ondrej Skutka (JIRA)

Server search window during installation doesn't close. ------------------------------------------------------- Key: JBDS-660 URL: https://jira.jboss.org/jira/browse/JBDS-660 Project: Developer Studio Issue Type: Bug Components: installer Affects Versions: 2.0.0.GA Reporter: Ondrej Skutka Attachments: snapshot6.png During installation of JBDS after searching for jboss servers, the 'server search' window (formerly showing progression) doesn't close and is not repainted anymore. It also cannot be closed by window manager. You can however continue in the installation ignoring the top window. -- 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

16 years, 3 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-5585) XML property value can't mapping to the java bean field

by Xue Peng (JIRA)

XML property value can't mapping to the java bean field ------------------------------------------------------- Key: JBIDE-5585 URL: https://jira.jboss.org/jira/browse/JBIDE-5585 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.CR1 Environment: Smooks 1.2.2 Reporter: Xue Peng Assignee: Tom Fennelly Fix For: 3.1.0.CR2 Attachments: Person.java, smooks-config.xml I create a smooks config file to transform the XML file to a Java bean. But I found that if I mapping the XML property node to java field , the property value doesn't assign to the java field. -- 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

16 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBDS-656) Work of adding additional servers in installer is incorrect.

by Anton Klimkovich (JIRA)

Work of adding additional servers in installer is incorrect. ------------------------------------------------------------- Key: JBDS-656 URL: https://jira.jboss.org/jira/browse/JBDS-656 Project: Developer Studio Issue Type: Bug Components: installer, servers Affects Versions: 2.0.0.GA Reporter: Anton Klimkovich EXECUTE: Run installer EXECUTE: Press Add button On step 5 EXECUTE: Press Browse button and select path to JBoss EAP server (\jbdevstudio20GA\jboss-eap\jboss-as) EXECUTE: Set checkbox to EAP and press ok ASSERT: EAP is added EXECUTE: Finish installation and run JBDS EXECUTE: Open JBoss Server view FAILURE: There is no JBoss EAP server in JBoss Server view. Runtime is absent too. Once I also got an exception but can't get it again. !ENTRY org.eclipse.wst.server.core 4 0 2009-03-10 14:32:28.674 !MESSAGE Could not save servers !STACK 0 java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449) at java.util.AbstractList$Itr.next(AbstractList.java:420) at org.eclipse.wst.server.core.internal.ResourceManager.saveServersList(ResourceManager.java:536) at org.eclipse.wst.server.core.internal.ResourceManager.addServer(ResourceManager.java:632) at org.eclipse.wst.server.core.internal.Server.saveToMetadata(Server.java:408) at org.eclipse.wst.server.core.internal.Base.doSave(Base.java:264) at org.eclipse.wst.server.core.internal.Server.doSave(Server.java:397) at org.eclipse.wst.server.core.internal.ServerWorkingCopy.save(ServerWorkingCopy.java:421) at org.jboss.ide.eclipse.as.core.server.internal.ServerAttributeHelper.save(ServerAttributeHelper.java:116) at org.jboss.ide.eclipse.as.core.server.internal.ServerAttributeHelper.save(ServerAttributeHelper.java:121) at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.save(XPathModel.java:202) at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel$1.run(XPathModel.java:100) 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

16 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-5205) Create FreeMarker Template builder for generating XML messages (from XSD)

by Tom Fennelly (JIRA)

Create FreeMarker Template builder for generating XML messages (from XSD) -------------------------------------------------------------------------- Key: JBIDE-5205 URL: https://jira.jboss.org/jira/browse/JBIDE-5205 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.CR1 -- 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

16 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5310) Determine Smooks XSD and runtime versions

by Brian Fitzpatrick (JIRA)

Determine Smooks XSD and runtime versions ----------------------------------------- Key: JBIDE-5310 URL: https://jira.jboss.org/jira/browse/JBIDE-5310 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Affects Versions: 3.1.0.CR1 Reporter: Brian Fitzpatrick Assignee: Tom Fennelly Fix For: 3.1.0.GA There are a few issues here... 1) You specify a Smooks runtime version in the New Smooks Configuration wizard (1.0, 1.1, and 1.2 appear in the drop-down). If we are truly only supporting version 1.2, we can get rid of this page in the wizard. 2) Previously we were determining the Smooks runtime version based on an element set in the <graph> portion of the configuration. Now that this element and XSD are gone, we need to provide a different way of noting this setting in the configuration that is based on #3. 3) To determine the runtime version, we must look at the component XSDs used by the configuration. This includes CSV, Freemarker, and other XSDs set in the namespace. To determine this, you must look at the combination of XSDs as documented in the table in this document: https://docspace.corp.redhat.com/clearspace/docs/DOC-23650#Schemas_and_Ve... -- 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

16 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5345) Java bean mapping code should check target beans for appropriate bean property setter methods

by Tom Fennelly (JIRA)

Java bean mapping code should check target beans for appropriate bean property setter methods --------------------------------------------------------------------------------------------- Key: JBIDE-5345 URL: https://jira.jboss.org/jira/browse/JBIDE-5345 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.GA Check to make sure the property names and setter methods match up i.e. that it's a proper bean class. Warn the user etc. -- 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

16 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5213) "Message Type Wizard" for new and unconfigured <ftl:freemarker> configs

by Tom Fennelly (JIRA)

"Message Type Wizard" for new and unconfigured <ftl:freemarker> configs ----------------------------------------------------------------------- Key: JBIDE-5213 URL: https://jira.jboss.org/jira/browse/JBIDE-5213 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.CR1 One thing we talk about in the wiki document about Input and Output message types was the need to capture message type info from the user (http://www.jboss.org/community/wiki/SmooksEditor-InputandOutputMessageTyp...). I created a Balsamiq screencast for how I think this might: http://www.screencast.com/users/tfennelly/folders/Camtasia/media/7d969b96... -- 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

16 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-1015) RC1 will not start

by Joshua Wulf (JIRA)

RC1 will not start ------------------ Key: JBDS-1015 URL: https://jira.jboss.org/jira/browse/JBDS-1015 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.CR1 Environment: Mac OS X 10.4.11 32-bit PPC, Apple Java 1.5 Reporter: Joshua Wulf Attachments: 1261439578596.log after installing using the installer jar JBDS will not start. Double-clicking on JBoss Developer Studio in the $root/eclipse folder results in an error dialog: "The Eclipse executable launcher was unable to locate its companion shared library" Double-clicking on $root/eclipse/Eclipse results in "An error has occurred. See the log file /Applications/jbdevstudio_3.0_RC1/eclipse/configuration/1261439578596.log" Log file is attached. 3.0.0.M4 runs fine (ok, a little bit slow - but it starts and does stuff) on this machine. -- 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

16 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBDS-1026) Full Publish of ESB projects does not redeploy and also can't deploy at all from eclipse workspace directory (deploy option)

by Aaron Pestel (JIRA)

Full Publish of ESB projects does not redeploy and also can't deploy at all from eclipse workspace directory (deploy option) ---------------------------------------------------------------------------------------------------------------------------- Key: JBDS-1026 URL: https://jira.jboss.org/jira/browse/JBDS-1026 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M4 Environment: Fedora 9, SOA-P 5.0 Beta1, JBDS 3 M4 Reporter: Aaron Pestel Create a new ESB project, add it to a SOA-P server, in the JBossAS view, right-click on the project and choose "Full Publish" - it doesn't republish the project like it used to. Can also modify the project (jboss-esb.xml) and select full publish and it still won't republish, have to remove project from server and re-add project to server. JBDS project now seems to be setup by default to deploy to JBoss deploy directory as opposed to the Ecplise workspace. I changed it to deploy to the workspace (like I think previoius versions defaulted to), and couldn't even get the project to deploy that way. If this isn't reproducible enough, please let me know and I'll attach a project with more clear steps. Thanks! -- 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

16 years, 3 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-5307) Generalize the model creation code

by Tom Fennelly (JIRA)

Generalize the model creation code ---------------------------------- Key: JBIDE-5307 URL: https://jira.jboss.org/jira/browse/JBIDE-5307 Project: Tools (JBoss Tools) Issue Type: Task Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.GA At the moment, we are using the Smooks programmatic APIs to configure the input parser etc for creating the input model. This requires translation of the EMF config model into java code instructions for configuring the Smooks Reader - see JsonInputDataParser, CSVDataParser, EDIDataParser. I think this can be simplified significantly by simply asking Smooks to process the Smooks config and then extracting the reader configuration from the Smooks instance and reuse that to configure an empty Smooks config... and then parse the input to extract the model. The code would be something like this... // Get the Reader config from the Smooks config file.... Smooks smooks1 = new Smooks(smooksConfigStream); ExecutionContext execCtx = smooks1.createExecutionContext(); SmooksResourceConfiguration readerConfig = AbstractParser.getSAXParserConfiguration(execCtx.getDeliveryConfig()); // Create a second "empty" Smooks instance and add the reader config to it.... Smooks smooks2 = new Smooks(); smooks.addConfiguration(readerConfig); // Filter the input message through this second Smooks instance and capture the model in the DOMResult... DOMResult result = new DOMResult(); smooks2.filterSource(new StreamSource(inputMessageStream), result); // And get the model DOM instance (org.w3c.dom.Document)... Document inputModelDOM = (Document) result.getNode(); -- 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

16 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5584) Can't launch smooks config file

by Xue Peng (JIRA)

Can't launch smooks config file ------------------------------- Key: JBIDE-5584 URL: https://jira.jboss.org/jira/browse/JBIDE-5584 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.CR1 Environment: Windows Vista Reporter: Xue Peng Assignee: Tom Fennelly Fix For: 3.1.0.CR2 Attachments: smooks-config.xml When I launch the smooks config file , it always say "Caused by: java.net.URISyntaxException: Illegal character in opaque part at index 2: D:\works\dart_workspaces\smooks_tools\runtime-New_configuration\java_project\src\smooks-config.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

16 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-5545) Change Smooks Run Configuration Output Labels to Match Task Descriptions in the Smooks Config Editor

by Brian Fitzpatrick (JIRA)

Change Smooks Run Configuration Output Labels to Match Task Descriptions in the Smooks Config Editor ---------------------------------------------------------------------------------------------------- Key: JBIDE-5545 URL: https://jira.jboss.org/jira/browse/JBIDE-5545 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.CR2 Reporter: Brian Fitzpatrick Assignee: Tom Fennelly Fix For: 3.1.0.CR2 This is just a minor cleanup task. With the newly cleaned up and formatted output of the Smooks Run Configuration, you now see... [StreamResult ...] |-- |"Insane","George Finklebine","CA","123 Wacky St.","95021" |... |-- [JavaResult Objects...] |-- |> People (beanId = "People") | ... |-- After some discussion, we think that the [StreamResult] and [JavaResult Objects...] labels should be changed to mirror what is seen in the Smooks Configuration Editor task list: * [StreamResult] would become [Templating Results] * [JavaResult Objects...] would become [Java Mapping Results] This should make it easier to reconcile the output from the Smooks Run Configuration with what the user sees in the Smooks Configuration Editor. -- 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

16 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5215) Add a "Missing Input Model" warning on the Java Mappings Task Configuration pane

by Tom Fennelly (JIRA)

Add a "Missing Input Model" warning on the Java Mappings Task Configuration pane -------------------------------------------------------------------------------- Key: JBIDE-5215 URL: https://jira.jboss.org/jira/browse/JBIDE-5215 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: smooks Reporter: Tom Fennelly Fix For: 3.1.0.CR1 At the moment, if you open an existing configuration that has an unconfigured Input task and click on a Java Mappings, the Task Configuration pane for the Java Mappings has all the java beans, but doesn't display any error to tell the user that the Input Task is not configured with an input. I think it should display something where the input would normally be (on the left), with a link to jump to the Input Task config. -- 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

16 years, 3 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-2532) Defect in GUI. Task Node | Task | Controller Tab Mapped Name displays in the Required Check Box column.

by Steve Hall (JIRA)

Defect in GUI. Task Node | Task | Controller Tab Mapped Name displays in the Required Check Box column. -------------------------------------------------------------------------------------------------------- Key: JBIDE-2532 URL: https://jira.jboss.org/jira/browse/JBIDE-2532 Project: Tools (JBoss Tools) Issue Type: Bug Components: Ganymede Affects Versions: 3.0.0.GA Environment: Eclipse plugin 3.1.3SP2. Installed in Eclipse 3.4.0. Running on Windows XP SP2 Reporter: Steve Hall Priority: Minor Created a Task Node. Added a task. Provided Name in General field. Set Assignment to Swinlane. Filled in the Swimlane Name. On the controller tab I added 6 variables. For each variable, I entered the name and mapped name filed. When I display the data in the GRID, the Mapped Name data shows up under the Required column. This is the associated processdefinition.xml file: <?xml version="1.0" encoding="UTF-8"?> <process-definition xmlns="urn:jbpm.org:jpdl-3.2" name="ProductMusicProducts"> <swimlane name="Talent Scout"> <assignment expression="group(Talent Scout)"></assignment> </swimlane> <swimlane name="Legal Advisor"> <assignment expression="group(Legal Advisor)"></assignment> </swimlane> <swimlane name="Band Member"> <assignment expression="group(Band Member)"></assignment> </swimlane> <swimlane name="Record Producer"> <assignment expression="group(Record Producer)"></assignment> </swimlane> <swimlane name="Artist Development"> <assignment expression="group(Artist Development)"></assignment> </swimlane> <swimlane name="Songwriter"> <assignment expression="group(Songwriter)"></assignment> </swimlane> <swimlane name="Musician"> <assignment expression="group(Musician)"></assignment> </swimlane> <swimlane name="Video Production"> <assignment expression="group(Video Production)"></assignment> </swimlane> <swimlane name="Artist"> <assignment expression="group(Artist)"></assignment> </swimlane> <start-state name="Hold Auditions"> <task name="Hold Auditions" swimlane="Talent Scout"> <description> The hold auditions task </description> <controller> <variable access="read,write,required" name="audDate" mapped-name="Audition Date"></variable> <variable access="read,write,required" name="audLocation" mapped-name="Audition Location"></variable> </controller> </task> <transition to="Select Band Members"></transition> </start-state> <task-node name="Select Band Members"> <task name="Select Band Members" swimlane="Talent Scout"> <description> Assign Band Members </description> <controller> <variable access="read,write,required" name="bm1" mapped-name="Band Member 1"></variable> <variable access="read,write,required" name="bm2" mapped-name="Band Members 2"></variable> <variable access="read,write,required" name="bm3" mapped-name="Band Member 3"></variable> <variable access="read,write" name="bm4" mapped-name="Band Member 4"></variable> <variable access="read,write" name="bm5" mapped-name="Band Member 5"></variable> <variable access="read,write" name="bm6" mapped-name="Band Member 6"></variable> </controller> </task> </task-node> <task-node name="Contract Band Members"> <task name="Contract Band Members"> <controller> <variable access="read,write,required" name="bm1ContractSent" mapped-name="Band Member 1 Contract Sent"></variable> <variable access="read,write,required" name="bm2ContractSent" mapped-name="Band Member 2 Contract Sent"></variable> <variable access="read,write,required" name="bm3ContractSent" mapped-name="Band Member 3 Contract Sent"></variable> <variable access="read,write" name="bm4ContractSent" mapped-name="Band Member 4 Contract Sent"></variable> <variable access="read,write" name="bm5ContractSent" mapped-name="Band Member 5 Contract Sent"></variable> <variable access="read,write" name="bm6ContractSent" mapped-name="Band Member 6 Contract Sent"></variable> </controller> </task> </task-node> <task-node name="All Contracts Agreed"> <task name="All Contracts Agreed" swimlane="Legal Advisor"> <controller> <variable access="read,write,required" name="bm1Agreed" mapped-name="Band Member 1 Agreed"></variable> <variable access="read,write,required" name="bm2Agreed" mapped-name="Band Member 2 Agreed"></variable> <variable access="read,write,required" name="bm3Agreed" mapped-name="Band Member 3 Agreed"></variable> <variable access="read,write" name="bm4Agreed" mapped-name="Band Member 4 Agreed"></variable> <variable access="read,write" name="bm5Agreed" mapped-name="Band Member 5 Agreed"></variable> <variable access="read,write" name="bm6Agreed" mapped-name="Band Member 6 Agreed"></variable> </controller> </task> </task-node> <task-node name="Contract Response"> <task> <controller> <variable access="read,write,required" name="bm1Agreed" mapped-name="BandMember1Agreed"></variable> <variable access="read,write,required" name="bm2Agreed" mapped-name="Band Member 2 Agreed"></variable> <variable access="read,write,required" name="bm3Agreed" mapped-name="Band Member 3 Agreed"></variable> <variable access="read,write" name="bm4Agreed" mapped-name="Band Member 4 Agreed"></variable> <variable access="read,write" name="bm5Agreed" mapped-name="Band Member 5 Agreed"></variable> <variable access="read,write" name="bm6Agreed" mapped-name="Band Member 6 Agreed"></variable> </controller> </task> </task-node> <end-state name="end-state1"></end-state> </process-definition> -- 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

16 years, 3 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4234) Some errors were detected when validating the file "loose.dtd" via the file "ordermanagement1.jpdl.xml" in Seam DVD Store Example Project

by Anton Klimkovich (JIRA)

Some errors were detected when validating the file "loose.dtd" via the file "ordermanagement1.jpdl.xml" in Seam DVD Store Example Project ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4234 URL: https://jira.jboss.org/jira/browse/JBIDE-4234 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.0.1.GA Reporter: Anton Klimkovich EXECUTE: Download Seam DVD Store Example Project into workspace EXECUTE: Look at Problems view FAILURE: Some errors were detected when validating the file "loose.dtd" via the file "ordermanagement1.jpdl.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

16 years, 3 months

7
12
0 / 0

[JBoss JIRA] Created: (JBIDE-5333) Renaming opened jBPM process definition does not work

by Dominik Pospisil (JIRA)

Renaming opened jBPM process definition does not work ----------------------------------------------------- Key: JBIDE-5333 URL: https://jira.jboss.org/jira/browse/JBIDE-5333 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.1.0.M4 Reporter: Dominik Pospisil 1. Open jPMB process definition 2. On jBPM process definition package choose Refactor -> Rename 3. Choose another name 4. Confirm saving changes 5. Modify definiton in opened editor 6. Try to save file Two problems: 1) During refactoring, file is not saved no matter what users choose in refactoring dialog. Unsaved changes are lost. 2) After refactoring saving the file is no longer possible - fails with No such file exception. -- 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

16 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4907) Provide consistent categorization/labelling for jBPM

by Koen Aers (JIRA)

Provide consistent categorization/labelling for jBPM ---------------------------------------------------- Key: JBIDE-4907 URL: https://jira.jboss.org/jira/browse/JBIDE-4907 Project: Tools (JBoss Tools) Issue Type: Task Components: jbpm Reporter: Koen Aers Fix For: 3.1.0.M4 Make sure that the categorization/labelling of the jBPM wizards and preference pages is consistent with the current JBT/JBDS way of doing these things -- 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

16 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5159) Choice to choose whether to use the wizard to generate hbm.xml in Hibernate Tools

by Simon Lo (JIRA)

Choice to choose whether to use the wizard to generate hbm.xml in Hibernate Tools --------------------------------------------------------------------------------- Key: JBIDE-5159 URL: https://jira.jboss.org/jira/browse/JBIDE-5159 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.1.0.M4 Environment: Windows 7 Home Premium, Eclipse 3.5 SR1 Reporter: Simon Lo I hate to generate everything by wizard and being unable to control the output of hbm.xml. It is because our company always have the mismatch problems in column name in database and properties in Java object. It made me so frustrated after using Eclipse Galileo which can only installed JBoss Tools 3.1.x and the behaviour of Hibernate Tools changed so much. I cannot find any option that I can stop the wizard generation and type in everything in hbm.xml by myself. I need to let the wizard to generate everything then delete it to start over. I love the Hibernate Tools before which only generate necessary XML declaration for me and let me do the rest. -- 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

16 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-5589) Smooks config file can't launch when there are multiple "Apply Template" tasks in the file.

by Xue Peng (JIRA)

Smooks config file can't launch when there are multiple "Apply Template" tasks in the file. ------------------------------------------------------------------------------------------- Key: JBIDE-5589 URL: https://jira.jboss.org/jira/browse/JBIDE-5589 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.CR2 Reporter: Xue Peng Assignee: Tom Fennelly Fix For: 3.1.0.CR2 I add two apply template task in process map , when I launch the smooks config file , it will throw a exception in the console. But if I launch the smooks config file with only on template task , it work well. -- 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

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5505) Deploy only server inconcistencies

by Max Rydahl Andersen (JIRA)

Deploy only server inconcistencies ---------------------------------- Key: JBIDE-5505 URL: https://jira.jboss.org/jira/browse/JBIDE-5505 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Max Rydahl Andersen Assignee: Rob Stryker Fix For: 3.1.0.GA 1)JBoss Deploy Only Server does not seem to really have anything to do with JBoss AS. Suggestion: Move to Basic category and call it "Deploy Only Server" 2) In the wizard it says System Copy Server - is that something differeent from deploy only ? Suggestion: align the names 3) I'm forced to specify two directories - why ? I assume something to do with ensuring copying/move goes well across filesystem. Suggestion: Minimum: Explain why it is needed and if there are any limitations (same filesystem a requirement or ?) Best: Don't require the deploy directory! Let it be someething you can specify later on if you get into the situation that really require it ? -- 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

16 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBDS-1030) Need to add jboss-rosetta.jar to the ESB runtime jars

by Aaron Pestel (JIRA)

Need to add jboss-rosetta.jar to the ESB runtime jars ----------------------------------------------------- Key: JBDS-1030 URL: https://jira.jboss.org/jira/browse/JBDS-1030 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M4 Environment: jbods 3.0 m4, soa-p 5.0 beta1 Reporter: Aaron Pestel Currently the set of libraries included in the ESB runtime does not include jboss-rosetta.jar. However, that's one of the most important libraries since it includes the interfaces custom actions have to extend. Without this in the ESB runtime by default, users will have to add an "External Jar" to their build path to get custom actions to build. jboss-as/server/default/deployers/esb.deployer/lib/jbossesb-rosetta.jar -- 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

16 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-4676) Eclipse Utility Project not included in EAR /lib directory on rebuild

by Margot Media (JIRA)

Eclipse Utility Project not included in EAR /lib directory on rebuild --------------------------------------------------------------------- Key: JBIDE-4676 URL: https://jira.jboss.org/jira/browse/JBIDE-4676 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M2 Environment: Eclipse 3.5 w/ JBoss Tools 3.1.0 M2. Using the "JBoss v5.0" server instead of the "JBoss AS 5.1". Reporter: Margot Media I have an application with a single MDB .jar file and 3 Utility Module .jar files. The utility projects are set up to appear in the EAR under the /lib directory. The first time the EAR file is deployed to the server, the /lib directory is populated correctly. However, if I change my source code and republish to the server, the /lib directory is not present! If I remove the EAR file from the server, then re-add it, the /lib directory is created properly. The first time, it looks like this: Code: MyEar.ear |- /lib | |- Utility1.jar | |- Utility2.jar | |- Utility3.jar |- /META-INF | |- MANIFEST.MF |- MyMDB.jar If I change the code in MyMDB.jar, the EAR file is generated like: Code: MyEar.ear |- /META-INF | |- MANIFEST.MF |- MyMDB.jar with the obvious class path problems by not having the utility jar files present. Steps to reproduce: 1. Create new "Java EE Enterprise Application Project" called MyEar using default configuration. 2. Create new "Java EE Utility Project" called Utlity 1 using the default configuration and add it to MyEar 3. Create new "Java EJB Project" called MyMdb using the default configuration and add it to MyEar 4. Set the Utility1.jar file to appear in the lib directory of MyEar 5. Create a class in the Utility1 project w/ some code (eg a POJO with one member and setter/getter) 6. Create MDB in the MyMDB project using the "Message-Driven Bean (EJB 3.x)" wizard 7. Add code to the MDB to make it dependent upon the Utility1 project 8. Start JBoss and deploy MyEar to the server. Verify that the EAR file correctly included the Utility1.jar file in the /lib directory 9. Make a change to the code in MyMDB and republish MyEar. Verify that the EAR does not include the /lib directory at all -- 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

16 years, 3 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5556) SCP server wizard got no ui

by Max Rydahl Andersen (JIRA)

SCP server wizard got no ui --------------------------- Key: JBIDE-5556 URL: https://jira.jboss.org/jira/browse/JBIDE-5556 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Max Rydahl Andersen Assignee: Rob Stryker Fix For: 3.1.0.CR2 -- 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

16 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5566) Implement XML Templating in the Editor

by Brian Fitzpatrick (JIRA)

Implement XML Templating in the Editor -------------------------------------- Key: JBIDE-5566 URL: https://jira.jboss.org/jira/browse/JBIDE-5566 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Affects Versions: 3.1.0.GA, 3.1.0.CR2 Reporter: Brian Fitzpatrick Assignee: Xue Peng Priority: Critical Fix For: 3.1.0.GA, 3.1.0.CR2 Dart, evidently we never created a JIRA for implementing XML Template support in the Smooks editor, but here it is. We need to get this in so we can focus entirely on testing, bug fixing, and cleaning up a few things here and there. -- 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

16 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5558) Reconcile scp vs ssh server type name

by Rob Stryker (JIRA)

Reconcile scp vs ssh server type name ------------------------------------- Key: JBIDE-5558 URL: https://jira.jboss.org/jira/browse/JBIDE-5558 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.CR1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.1.0.CR2 Please pick one name. Is it an ssh server or an scp server? -- 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

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5544) JBoss Server adapter doesn't work for deploying module which contains a sub-module if the "Deploy projects as compressed archives" is selected

by Denny Xu (JIRA)

JBoss Server adapter doesn't work for deploying module which contains a sub-module if the "Deploy projects as compressed archives" is selected ---------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-5544 URL: https://jira.jboss.org/jira/browse/JBIDE-5544 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.CR1 Environment: JBossTools-Update-3.1.0.v200912180601M-H186-RC1.zip Reporter: Denny Xu Assignee: Rob Stryker Priority: Blocker Fix For: 3.1.0.CR1 1.create EAR project p1 and a WAR project p2, open Module Assembly property page and add p1 to p2 as reference, 2. create a SOA-P 5.0 and double click the created server adapter in the server view and select "Deploy projects as compressed archives", 3. publish the server, nothing deployed. -- 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

16 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-1027) JBDS 3.0 M4 does not suport SOA-P 5.0 (ESB 4.7) jboss-esb.xml 1.2 schema

by Aaron Pestel (JIRA)

JBDS 3.0 M4 does not suport SOA-P 5.0 (ESB 4.7) jboss-esb.xml 1.2 schema ------------------------------------------------------------------------ Key: JBDS-1027 URL: https://jira.jboss.org/jira/browse/JBDS-1027 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M4 Environment: Fedora 9, SOA-P 5.0 Beta1, JBDS 3 M4 Reporter: Aaron Pestel ESB project is created with this XML: <jbossesb xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." parameterReloadSecs="5"> needs to be created with this <jbossesb xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." parameterReloadSecs="5"> Probably this is because JBDS 3.0 M4 only supports ESB 4.6 yet and SOA-P 5 is based on 4.7. The 4.6 version does not support the new http-gateway listener (see http_gateway quickstart) Also (probably as expected), when I change to the jbossesb-1.2.0.xsd, the "tree" view of the jboss-esb.xml file editor does not work correctly. -- 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

16 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-5557) Add wizard page for scp server

by Rob Stryker (JIRA)

Add wizard page for scp server ------------------------------ Key: JBIDE-5557 URL: https://jira.jboss.org/jira/browse/JBIDE-5557 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.CR1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.1.0.CR2 -- 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

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5576) java.lang.NullPointerException is occured while creating New File filter or XPath for SCP remote server

by Anton Klimkovich (JIRA)

java.lang.NullPointerException is occured while creating New File filter or XPath for SCP remote server ------------------------------------------------------------------------------------------------------- Key: JBIDE-5576 URL: https://jira.jboss.org/jira/browse/JBIDE-5576 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR1 Reporter: Anton Klimkovich Assignee: Rob Stryker EXECUTE: Opne JBoss Server View EXECUTE: Add SCP Remote server EXECUTE: Try to create new File Filter or XPath FAILURE: java.lang.NullPointerException at org.jboss.ide.eclipse.archives.webtools.filesets.FilesetActionProvider$1.run(FilesetActionProvider.java:208) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) -- 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

16 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5542) Potential NullPointerException in VPE openned on file from project without JBossTools nature

by Denis Golovin (JIRA)

Potential NullPointerException in VPE openned on file from project without JBossTools nature -------------------------------------------------------------------------------------------- Key: JBIDE-5542 URL: https://jira.jboss.org/jira/browse/JBIDE-5542 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.CR2 Reporter: Denis Golovin Fix For: 3.1.0.CR1 I cannot provide exact steps to reproduce it but stack trace tells me that that might happen for any none JBossTools project. For me it happens on project with JSF capabilities. To fix this problem on JBossTools JSF project, it should be closed/opened and VPE starts working. org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) at org.eclipse.swt.SWT.error(SWT.java:3884) at org.eclipse.swt.SWT.error(SWT.java:3799) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) Caused by: java.lang.NullPointerException at org.jboss.tools.vpe.editor.bundle.BundleMap.refreshRegisteredBundles(BundleMap.java:100) at org.jboss.tools.vpe.editor.bundle.BundleMap.refresh(BundleMap.java:343) at org.jboss.tools.vpe.editor.VpeController.refreshTemplates(VpeController.java:1689) at org.jboss.tools.vpe.editor.VpeEditorPart$ActivationListener.handleActivation(VpeEditorPart.java:1075) at org.jboss.tools.vpe.editor.VpeEditorPart$ActivationListener.access$1(VpeEditorPart.java:1064) at org.jboss.tools.vpe.editor.VpeEditorPart$ActivationListener$1.run(VpeEditorPart.java:1059) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) ... 22 more -- 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

16 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5443) Error during JBT Installation from nightly update site

by Jiri Peterka (JIRA)

Error during JBT Installation from nightly update site ------------------------------------------------------ Key: JBIDE-5443 URL: https://jira.jboss.org/jira/browse/JBIDE-5443 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Jiri Peterka -- 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

16 years, 3 months

5
10
0 / 0

[JBoss JIRA] Created: (JBIDE-2023) Population of Action Class / Process Method

by Tom Cunningham (JIRA)

Population of Action Class / Process Method ------------------------------------------- Key: JBIDE-2023 URL: http://jira.jboss.com/jira/browse/JBIDE-2023 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Environment: Mac OS X, nightly 04/04 JBoss Tools build, Europa JEE eclipse build Reporter: Tom Cunningham It would be nice if the ESB editor could somehow populate an action class drop down or do autocompletion of the class name, while at the same time retaining the ability for the user to type in their action class name. Action classes in the drop down should probably be restricted to classes within project which extend AbstractActionLifecycle or AbstractActionPipelineProcessor and the org.jboss.soa.esb.actions package classes. -- 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

16 years, 3 months

7
33
0 / 0

[JBoss JIRA] Created: (JBIDE-3378) Seam EL validation does not use same technique as the EL resolver (Continued)

by Tim Evers (JIRA)

Seam EL validation does not use same technique as the EL resolver (Continued) ----------------------------------------------------------------------------- Key: JBIDE-3378 URL: https://jira.jboss.org/jira/browse/JBIDE-3378 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.beta1, 3.0.0.alpha, 2.1.2 Environment: Latest nightly build of JBoss Tools. On eclipse 3.4 SR1. JSF/Facelets/Richfaces/Seam 2.1.x environment Reporter: Tim Evers JBoss Tools does not validate method EL expressions properly if the method name starts with 'is' If I have a method in my SEAM bean like this. public boolean isEditButtonDisplayed() { return true; //removed what this method actually does for example } and then I have in my xhtml this: <gekko:commandButton id="tenureEditButton" value="Edit" action="#{TenureKeyController.editButtonClicked()}" rendered="#{TenureKeyController.isEditButtonDisplayed()}" /> When I validate this it says: "isEditButtonDisplayed" cannot be resolved. It looks like when the validation method sees the word 'is' it automatically thinks that the expression is a value expression. This should not be the case. Infact if I end my expression witih '()' it should always look for a method. The behaviour of the EL validation should be exactly the same as what happens when I run the system. But this is not what is happening. If I change my code to what the JBoss Tools autocomplete says to it actually breaks the application. According to JBoss Tools it says I should have this. <gekko:commandButton id="tenureEditButton" value="Edit" action="#{TenureKeyController.editButtonClicked()}" rendered="#{TenureKeyController.editButtonDisplayed}" /> Which of course will not work when the app is deployed. This is somewhat related to: https://jira.jboss.org/jira/browse/JBIDE-2673 just a different scenario. The fundamental problem is that the rules of validation are not the same as a running app. -- 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

16 years, 4 months

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-5463) BPEL Editor gives validation errors after creating correlation variables

by Jeff DeLong (JIRA)

BPEL Editor gives validation errors after creating correlation variables ------------------------------------------------------------------------ Key: JBIDE-5463 URL: https://jira.jboss.org/jira/browse/JBIDE-5463 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Environment: JBoss BPEL Editor 1.0.0.v200912111224M-H175-RC1 org.jboss.tools.bpel.feature.feature.group on Mac with JDK 1.6 Reporter: Jeff DeLong I created a CorrelationSet with a single correlation variable and four mappings. After doing this and cleaning the project I get four errors: Description Resource Path Location Type The XPath segment "child::receivePolicyQuote" cannot be resolved. PolicyQuoteProcessArtifacts.wsdl /PolicyQuoteProcessService/bpelContent query BPEL Validation Marker Description Resource Path Location Type The XPath segment "child::receivePolicyQuote" cannot be resolved. PolicyQuoteProcessArtifacts.wsdl /PolicyQuoteProcessService/bpelContent query BPEL Validation Marker Description Resource Path Location Type The XPath segment "child::ssn" cannot be resolved. PolicyQuoteProcessArtifacts.wsdl /PolicyQuoteProcessService/bpelContent query BPEL Validation Marker Description Resource Path Location Type The XPath segment "child::ssn" cannot be resolved. PolicyQuoteProcessArtifacts.wsdl /PolicyQuoteProcessService/bpelContent query BPEL Validation Marker I will zip up and attach the project files. -- 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

16 years, 4 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5588) More Nodes button is always shown in the Selection Bar of VPE on Linux

by Yahor Radtsevich (JIRA)

More Nodes button is always shown in the Selection Bar of VPE on Linux ---------------------------------------------------------------------- Key: JBIDE-5588 URL: https://jira.jboss.org/jira/browse/JBIDE-5588 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.CR1 Environment: openSUSE KDE4 Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 3.1.0.CR2 STEPS TO REPRODUCE 1. Open any XHTML file with VPE (on Linux with KDE4). ACTUAL RESULT 'More Nodes...' button is always shown in the Selection Bar (see screenshot1.png). EXPECTED RESULT The button is shown only if there is no place to show all nodes. -- 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

16 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5578) ClassCastException occures when the proper context cannot be created

by Victor Rubezhny (JIRA)

ClassCastException occures when the proper context cannot be created -------------------------------------------------------------------- Key: JBIDE-5578 URL: https://jira.jboss.org/jira/browse/JBIDE-5578 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Victor Rubezhny Assignee: Victor Rubezhny Fix For: 3.1.0.CR2 ClassCastException occures when the proper context cannot be created. See the stack trace below: java.lang.ClassCastException: org.jboss.tools.jst.web.kb.internal.XmlContextImpl at org.jboss.tools.jst.jsp.contentassist.JspContentAssistProcessor.getContext(JspContentAssistProcessor.java:63) at org.jboss.tools.jst.jsp.outline.JSPPropertySourceAdapter.setTarget(JSPPropertySourceAdapter.java:127) at org.jboss.tools.jst.jsp.outline.JSPPropertySourceAdapter.<init>(JSPPropertySourceAdapter.java:103) at org.jboss.tools.jst.jsp.outline.JSPPropertySheetConfiguration$JSPPropertySourceProvider0.getPropertySource(JSPPropertySheetConfiguration.java:56) at org.eclipse.ui.views.properties.PropertySheetEntry.getPropertySource(PropertySheetEntry.java:470) at org.eclipse.ui.views.properties.PropertySheetEntry.setValues(PropertySheetEntry.java:752) at org.eclipse.ui.views.properties.PropertySheetViewer.setInput(PropertySheetViewer.java:973) at org.eclipse.ui.views.properties.PropertySheetPage.selectionChanged(PropertySheetPage.java:510) at org.eclipse.wst.sse.ui.internal.properties.ConfigurablePropertySheetPage.selectionChanged(ConfigurablePropertySheetPage.java:174) at org.eclipse.ui.views.properties.PropertySheet.selectionChanged(PropertySheet.java:361) at org.eclipse.ui.internal.AbstractSelectionService.fireSelection(AbstractSelectionService.java:156) at org.eclipse.ui.internal.AbstractSelectionService.setActivePart(AbstractSelectionService.java:282) at org.eclipse.ui.internal.WorkbenchPagePartList.fireActivePartChanged(WorkbenchPagePartList.java:60) at org.eclipse.ui.internal.PartList.setActivePart(PartList.java:136) at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3528) at org.eclipse.ui.internal.WorkbenchPage.requestActivation(WorkbenchPage.java:3071) at org.eclipse.ui.internal.PartPane.requestActivation(PartPane.java:279) at org.eclipse.ui.internal.EditorPane.requestActivation(EditorPane.java:98) at org.eclipse.ui.internal.presentations.PresentablePart.setFocus(PresentablePart.java:192) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation$1.handleEvent(TabbedStackPresentation.java:94) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:270) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:275) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.handleMouseDown(AbstractTabFolder.java:345) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder$3.mouseDown(AbstractTabFolder.java:79) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:179) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5577) OpenOn for xhtml page from link with <page_name>.jsf

by Maxim Areshkau (JIRA)

OpenOn for xhtml page from link with <page_name>.jsf ---------------------------------------------------- Key: JBIDE-5577 URL: https://jira.jboss.org/jira/browse/JBIDE-5577 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Maxim Areshkau Assignee: Denis Maliarevich Fix For: 3.1.0.CR2 #1 Import /home/mareshkau/Projects/jboss/trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/resources/jsf2test project, #2 open page index.html and try to openOn from <a href="pages/components/head2.jsf">h:head (2nd)</a> ASSERT head2.xhtml should be opened Also take into account that link to page can be specified in this was #{facesContext.externalContext.requestContextPath}/<path> -- 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

16 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-4758) EL OpenOns should use new unified EL Resolvers mechanism from org.jboss.tools.common.el

by Alexey Kazakov (JIRA)

EL OpenOns should use new unified EL Resolvers mechanism from org.jboss.tools.common.el --------------------------------------------------------------------------------------- Key: JBIDE-4758 URL: https://jira.jboss.org/jira/browse/JBIDE-4758 Project: JBoss Tools Issue Type: Task Components: JSF Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.1.0.M3 -- 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

16 years, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (JBDS-1036) IDE not displaying the s:link includePageParams attribute in code completion

by Tihomir Surdilovic (JIRA)

IDE not displaying the s:link includePageParams attribute in code completion ---------------------------------------------------------------------------- Key: JBDS-1036 URL: https://jira.jboss.org/jira/browse/JBDS-1036 Project: JBoss Developer Studio Issue Type: Feature Request Affects Versions: 2.1.0 Reporter: Tihomir Surdilovic Since Seam 2.1.1.CR1 attribute "includePageParams" was added to the s:link component (see JIRA https://jira.jboss.org/jira/browse/JBSEAM-3609). This attribute however is not available in the IDE when doing code completion and displaying all attributes of this component. This seems to be fixed in JBT 3.1.M4 -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-1035) IDE not displaying the s:link includePageParams attribute in code completion

by Tihomir Surdilovic (JIRA)

IDE not displaying the s:link includePageParams attribute in code completion ---------------------------------------------------------------------------- Key: JBDS-1035 URL: https://jira.jboss.org/jira/browse/JBDS-1035 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 2.1.0 Reporter: Tihomir Surdilovic Since Seam 2.1.1.CR1 attribute "includePageParams" was added to the s:link component (see JIRA https://jira.jboss.org/jira/browse/JBSEAM-3609. This attribute however is not available in the IDE when doing code completion and displaying all attributes of this component. -- 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

16 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5580) OpenOns don't work for complex ELs.

by Alexey Kazakov (JIRA)

OpenOns don't work for complex ELs. ----------------------------------- Key: JBIDE-5580 URL: https://jira.jboss.org/jira/browse/JBIDE-5580 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF, jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.1.0.CR2 For example, create a page with #{(game.value == 'foo' and game.value == 'foo') ? game.value == 'foo' : false} where "game" is resolvable managed bean, seam context variable or CDI bean. OpenOns should be work. But now it doesn't. -- 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

16 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5579) NullPointerException in EclipseUIUtil.getActiveEditor().

by Victor Rubezhny (JIRA)

NullPointerException in EclipseUIUtil.getActiveEditor(). -------------------------------------------------------- Key: JBIDE-5579 URL: https://jira.jboss.org/jira/browse/JBIDE-5579 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Victor Rubezhny Assignee: Victor Rubezhny Fix For: 3.1.0.CR2 JUnit testing log contains NullPointerException: Stack Trace: java.lang.NullPointerException at org.jboss.tools.common.util.EclipseUIUtil.getActiveEditor(EclipseUIUtil.java:45) at org.jboss.tools.common.util.EclipseUIUtil.isOpenInActiveEditor(EclipseUIUtil.java:62) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:331) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:179) at org.jboss.tools.jst.web.kb.PageContextFactory.createPageContext(PageContextFactory.java:169) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.searchInCach(RefactorSearcher.java:191) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scanForJava(RefactorSearcher.java:174) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scanForJava(RefactorSearcher.java:135) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.scanForJava(RefactorSearcher.java:133) at org.jboss.tools.jsf.el.refactoring.RefactorSearcher.findELReferences(RefactorSearcher.java:105) at org.jboss.tools.seam.internal.core.refactoring.SeamRenameProcessor.renameComponent(SeamRenameProcessor.java:386) at org.jboss.tools.seam.internal.core.refactoring.RenameSeamContextVariableProcessor.checkFinalConditions(RenameSeamContextVariableProcessor.java:71) at org.jboss.tools.seam.core.test.refactoring.SeamContextVariableRefactoringTest.renameContextVariable(SeamContextVariableRefactoringTest.java:47) at org.jboss.tools.seam.core.test.refactoring.SeamContextVariableRefactoringTest.testSeamContextVariable_Component_Rename(SeamContextVariableRefactoringTest.java:132) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.test.UITestApplication.runApplication(UITestApplication.java:138) at org.eclipse.test.UITestApplication.run(UITestApplication.java:60) at org.eclipse.test.UITestApplication.start(UITestApplication.java:210) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) at org.eclipse.core.launcher.Main.main(Main.java:34) -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-5573) Changes to JSP and XHTML files are not saved if the files are opened from linked WEB-ROOT folder

by Yahor Radtsevich (JIRA)

Changes to JSP and XHTML files are not saved if the files are opened from linked WEB-ROOT folder ------------------------------------------------------------------------------------------------ Key: JBIDE-5573 URL: https://jira.jboss.org/jira/browse/JBIDE-5573 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.CR1 Reporter: Yahor Radtsevich Priority: Critical Fix For: 3.1.0.CR2 STEPS TO REPRODUCE: 1. Click New Project->Web/Dynamic Web Project. 2. Enter a name for the project, unselect 'Use default Project contents' , enter a custom directory for the project contents not in the workspace. 3. Click Finish. 4. Select the created project in the Package Explorer, right click it and select Configure->Add JSF Capabilities. 5. Linked 'WEB-ROOT' folder is appeared in the project. 6. Create file index.jsp in the 'WEB-ROOT'. 7. Open the file with JBoss Tools JSP Editor and type anything into it. 8. Save the file and close the editor. 9. Reopen index.jsp. ACTUAL BEHAVIOR: All changes are lost. EXPECTED BEHAVIOR: The changes are saved. -- 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

16 years, 4 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5540) New ESB Project Wizard - Late Error Message: "Please specify the project primary target runtime"

by Burr Sutter (JIRA)

New ESB Project Wizard - Late Error Message: "Please specify the project primary target runtime" ------------------------------------------------------------------------------------------------- Key: JBIDE-5540 URL: https://jira.jboss.org/jira/browse/JBIDE-5540 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Environment: jbdevstudio-win32-3.0.0.v200912111227M-H41-RC1 Reporter: Burr Sutter Attachments: New_ESB_Project_Target_Runtime_Issue.pdf The error message "Please specify the project primary target runtime" shows up late in the wizard flow, it should have shown up on the first screen that asked for the primary target runtime. If the Primary Target Runtime was going to be mandatory, it should have stopped me on the first screen. It could have been defaulted as well, since I had obviously been working with a particular server & runtime in my session. The attached PDF illustrates the workflow. -- 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

16 years, 4 months

4
7
0 / 0

[JBoss JIRA] Created: (JBDS-1025) JBDS 2.1 "Seam Booking Example - EAR mavenized" does not build from commandline

by Tihomir Surdilovic (JIRA)

JBDS 2.1 "Seam Booking Example - EAR mavenized" does not build from commandline ------------------------------------------------------------------------------- Key: JBDS-1025 URL: https://jira.jboss.org/jira/browse/JBDS-1025 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 2.1.0 Reporter: Tihomir Surdilovic The parent pom.xml of the "Seam Booking Example - EAR mavenized" built-in example project does not build when running "mvn clean install" from the command-line. This is because the modules section should be defined properly to match the project structure: <modules> <module>../booking-ejb</module> <module>../booking</module> <module>../booking-ear</module> </modules> Also there is a typo for dependency: <dependency> <groupId>oorg.jboss.tools.seam.test</groupId> <artifactId>seamparent</artifactId> <version>${project.version}</version> <type>war</type> </dependency> "oorg" ? Not sure if this dependency should even be used here. -- 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

16 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBDS-978) Option to avoid test project creation is added in "Seam web project" wizard.h

by Svetlana mukhina (JIRA)

Option to avoid test project creation is added in "Seam web project" wizard.h ----------------------------------------------------------------------------- Key: JBDS-978 URL: https://jira.jboss.org/jira/browse/JBDS-978 Project: JBoss Developer Studio Issue Type: Task Components: Doc - RHDS GSG, Doc - Seam Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc retake screens of the wizard -- 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

16 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5394) BPEL Plugin is not correctly initalizing variables

by Brad Maxwell (JIRA)

BPEL Plugin is not correctly initalizing variables -------------------------------------------------- Key: JBIDE-5394 URL: https://jira.jboss.org/jira/browse/JBIDE-5394 Project: Tools (JBoss Tools) Issue Type: Bug Environment: EAP 5 + Riftsaw 2.0 M2 b61 + JBoss Tools 1.0.0.v200912010817N-H2-RC1 Reporter: Brad Maxwell The BPEL plugin is not correctly initializing the variables. 1) Create a new Process 2) Add an Assign 3) Go to details 4) Click New 5) Select to copy from variable input/payload/inpuy 6) Select to copy to variable HelloWSPartnerLinkRequest.hello/name 7) Click away, it will prompt you to see if you want to create an Initializer 8) Click Yes The code generate is this below. Running this process causes Riftsaw to spit out this error: INFO [org.apache.ode.bpel.runtime.ASSIGN] (ODEServer-29) Assignment Fault: {http://docs.oasis-open.org/wsbpel/2.0/process/executable}selectionFailure,lineNo=80,faultExplanation=No results for expression: {OXPath10Expression name} bpel:copy> <bpel:from> <bpel:literal xml:space="preserve"><tns:hello xmlns:tns="http://jboss.com/examples/ws/Hello" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> </tns:hello> </bpel:literal> </bpel:from> <bpel:to variable="HelloWSPartnerLinkRequest" part="hello"></bpel:to> </bpel:copy> After days of trying various things, I then began comparing my example to the quick starts. I found the issue is 'name' is not being initialized. I hacked the code and added <name xmlns=""/> and it resolved the issue. <bpel:assign validate="no" name="Assign-Input2Request"> <bpel:copy> <bpel:from> <bpel:literal xml:space="preserve"> <tns:hello xmlns:tns="http://jboss.com/examples/ws/Hello" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <name xmlns=""/> </tns:hello> </bpel:literal> </bpel:from> <bpel:to part="hello" variable="HelloWSPartnerLinkRequest"></bpel:to> </bpel:copy> <bpel:copy> <bpel:from part="payload" variable="input"></bpel:from> <bpel:to>$HelloWSPartnerLinkRequest.hello/name</bpel:to> </bpel:copy> </bpel:assign> -- 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

16 years, 4 months

3
16
0 / 0

[JBoss JIRA] Created: (JBIDE-5517) BPEL Editor causing problems installing nightly build

by Jeff DeLong (JIRA)

BPEL Editor causing problems installing nightly build ----------------------------------------------------- Key: JBIDE-5517 URL: https://jira.jboss.org/jira/browse/JBIDE-5517 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Environment: JBossTools-Update-3.1.0.v200912170604N-H64-GA.zip on eclipse-jee-galileo-SR1-linux-gtk.tar.gz on RHEL5 Reporter: Jeff DeLong I installed eclipse-jee-galileo-SR1-linux-gtk.tar.gz and then used the local update archive to install JBossTools-Update-3.1.0.v200912170604N-H64-GA.zip eclipse.buildId=M20090917-0800 java.version=1.5.0_10 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.jee.product Error Thu Dec 17 10:35:17 MST 2009 An error occurred while collecting items to be installed eclipse.buildId=M20090917-0800 java.version=1.5.0_10 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.jee.product Error Thu Dec 17 10:35:17 MST 2009 Problems downloading artifact: osgi.bundle,org.eclipse.bpel.wsil.model,0.5.0.v200912120139. eclipse.buildId=M20090917-0800 java.version=1.5.0_10 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.jee.product eclipse.buildId=M20090917-0800 java.version=1.5.0_10 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.jee.product Error Thu Dec 17 10:35:17 MST 2009 Unpacking fails because intermediate file is empty: /tmp/work7874/p2.optimizers.incoming7872.jar and thee more similar errors. -- 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

16 years, 4 months

4
11
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2009