[JBoss JIRA] (JBDS-1899) Help->Project Examples->Show Experimental Sites -- Extraneous "%" character displayed in the JBDS BPEL examples title
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-1899?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-1899.
---------------------------------------
Resolution: Out of Date
This issue have not seen any updates for a year thus we are resolving it as "out of date".
If you believe this jira is still relevant please reopen the issue or open a new one mentioning this jira.
> Help->Project Examples->Show Experimental Sites -- Extraneous "%" character displayed in the JBDS BPEL examples title
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-1899
> URL: https://issues.jboss.org/browse/JBDS-1899
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: integration-platform
> Affects Versions: 4.1.1.GA
> Environment: Version: 4.1.1.CR1
> Build id: v20111018-0116-H1068-CR1
> Build date: 20111018-0116
> Reporter: Len DiMaggio
> Assignee: Brian Fitzpatrick
> Priority: Minor
> Fix For: LATER
>
> Attachments: Screenshot-3.png
>
>
> See the attached screenshot.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBDS-411) Need 64-bit windows support
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-411?page=com.atlassian.jira.plugin.s... ]
Max Rydahl Andersen resolved JBDS-411.
--------------------------------------
Resolution: Out of Date
This issue have not seen any updates for a year thus we are resolving it as "out of date".
If you believe this jira is still relevant please reopen the issue or open a new one mentioning this jira.
> Need 64-bit windows support
> ---------------------------
>
> Key: JBDS-411
> URL: https://issues.jboss.org/browse/JBDS-411
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: visual-page-editor-core
> Affects Versions: 1.1.0.GA
> Reporter: Samuel Mendenhall
> Assignee: Yahor Radtsevich
> Fix For: LATER
>
>
> JBDS is not usable on a 64-bit Windows machine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBDS-1509) JBDS thread looping after call to OS - Seen in DTP connection profile-setting
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-1509?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-1509.
---------------------------------------
Resolution: Out of Date
This issue have not seen any updates for a year thus we are resolving it as "out of date".
If you believe this jira is still relevant please reopen the issue or open a new one mentioning this jira.
> JBDS thread looping after call to OS - Seen in DTP connection profile-setting
> -----------------------------------------------------------------------------
>
> Key: JBDS-1509
> URL: https://issues.jboss.org/browse/JBDS-1509
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: integration
> Affects Versions: 4.0.0.CR1
> Environment: JBDS 4.0 H65 CR1, Fedora 12, Java SE Runtime Environment (build 1.6.0_21-b06)
> Reporter: Paul Nittel
> Assignee: Brian Fitzpatrick
> Fix For: LATER
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> While testing Teiid Designer, I found the software wold go into a loop when I was interacting with the new connection profile process. The point at which the looping started was sonewhat variable, but seemed repeatable within the new CP set of dialogs. To simplify things, I started JBDS and went to the Database Development perspective (rather than Teiid Designer) and stepped through the new CP process. While completing the database connection information, the looping began. Here's part of the stack trace from running it in debug:
> Thread [main] (Suspended)
> OS.Call(int, int, int, int) line: not available [native method]
> Display.sleep() line: 4021
> WizardDialog(Window).runEventLoop(Shell) line: 826
> WizardDialog(Window).open() line: 801
> NewProfileAction(AddProfileViewAction).run() line: 246
> NewProfileAction(Action).runWithEvent(Event) line: 498
> ActionContributionItem.handleWidgetSelection(Event, boolean) line: 584
> ActionContributionItem.access$2(ActionContributionItem, Event, boolean) line: 501
> ActionContributionItem$5.handleEvent(Event) line: 411
> EventTable.sendEvent(Event) line: 84
> MenuItem(Widget).sendEvent(Event) line: 1258
> Display.runDeferredEvents() line: 3540
> Display.readAndDispatch() line: 3161
> Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 2640
> Workbench.runUI() line: 2604
> Workbench.access$4(Workbench) line: 2438
> Workbench$7.run() line: 671
> Realm.runWithDefault(Realm, Runnable) line: 332
> Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 664
> PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 149
> IDEApplication.start(IApplicationContext) line: 115
> EclipseAppHandle.run(Object) line: 196
> EclipseAppLauncher.runApplication(Object) line: 110
> EclipseAppLauncher.start(Object) line: 79
> EclipseStarter.run(Object) line: 369
> EclipseStarter.run(String[], Runnable) line: 179
> NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
> NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25
> Method.invoke(Object, Object...) line: 597
> Main.invokeFramework(String[], URL[]) line: 619
> Main.basicRun(String[]) line: 574
> Main.run(String[]) line: 1407
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBDS-1702) Feature request - queue editor
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-1702?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-1702.
---------------------------------------
Resolution: Out of Date
This issue have not seen any updates for a year thus we are resolving it as "out of date".
If you believe this jira is still relevant please reopen the issue or open a new one mentioning this jira.
> Feature request - queue editor
> -------------------------------
>
> Key: JBDS-1702
> URL: https://issues.jboss.org/browse/JBDS-1702
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: integration-platform
> Affects Versions: 5.0.0.M2
> Reporter: Len DiMaggio
> Fix For: LATER
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Feature request - for a queue editor for JMS providers (JBM, Hornet, Tibco, etc.) for SOA-P in JBDS 5.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBDS-1600) Creating mysql data source creates wrong JAR reference
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-1600?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-1600.
---------------------------------------
Resolution: Out of Date
This issue have not seen any updates for a year thus we are resolving it as "out of date".
If you believe this jira is still relevant please reopen the issue or open a new one mentioning this jira.
> Creating mysql data source creates wrong JAR reference
> ------------------------------------------------------
>
> Key: JBDS-1600
> URL: https://issues.jboss.org/browse/JBDS-1600
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: upstream
> Affects Versions: 4.0.0.GA
> Environment: RHEL6
> Reporter: Peter Larsen
> Assignee: Brian Fitzpatrick
> Labels: jbds, jdbc, upstream
> Fix For: LATER
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> When adding a driver, for instance mySQL, to JBDS, the dialog puts a wrong reference to the JAR file which needs to be corrected by the user.
> If there's no automatic way to detect the location my the driver file, I suggest changing the dialog so the user is told to locate the file instead of hiding the option and having the user correct auto-generated material.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBDS-1505) allow users to submit problem reports from JBDS
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-1505?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-1505.
---------------------------------------
Resolution: Out of Date
This issue have not seen any updates for a year thus we are resolving it as "out of date".
If you believe this jira is still relevant please reopen the issue or open a new one mentioning this jira.
> allow users to submit problem reports from JBDS
> -----------------------------------------------
>
> Key: JBDS-1505
> URL: https://issues.jboss.org/browse/JBDS-1505
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: integration
> Affects Versions: LATER
> Environment: All
> Reporter: Andrew Hecox
> Fix For: 4.x, LATER
>
>
> user-story: as a JBoss customer, I can create a report a problem from JBDS and instantly get suggestions back so that I can easily get help solving the problem I'm working on in my editor
> notes: I think something which allowed a user to create a problem report, as well as send any applicable files, with us sending back instant results (and prior to case creation) would be a good value add to JBDS. We don't yet have a public API for this, but something would be added to our subscriber API:
> https://access.redhat.com/knowledge/docs/Red_Hat_Customer_Portal/
> probably RESTfully modeled in it's own root level domain, eg, /problem or /problem_report, /report, etc... with a synchronous response including suggested KBase articles, community forums, whitepapers, etc...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBDS-587) Need to translate Help/About text including copyright statement
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-587?page=com.atlassian.jira.plugin.s... ]
Max Rydahl Andersen resolved JBDS-587.
--------------------------------------
Resolution: Out of Date
This issue have not seen any updates for a year thus we are resolving it as "out of date".
If you believe this jira is still relevant please reopen the issue or open a new one mentioning this jira.
> Need to translate Help/About text including copyright statement
> ---------------------------------------------------------------
>
> Key: JBDS-587
> URL: https://issues.jboss.org/browse/JBDS-587
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: build
> Affects Versions: 2.0.0.cr1
> Reporter: Sean Flanigan
> Assignee: Sean Flanigan
> Labels: i18n
> Fix For: LATER
>
> Attachments: jbds587a.png, jbds587b.png
>
>
> Help/About JBoss Developer Studio shows the version/copyright information for JBDS.
> This text looks similar to /com.jboss.jbds.product/plugin.properties but is actually overwritten/expanded from
> releng/org.jboss.ide.eclipse.releng/builders/product/product.properties during the build.
> The problem is, if we create a translation fragment plugin for com.jboss.jbds.product, the translators will translate the obsolete information in /com.jboss.jbds.product/plugin.properties, and when a langpack is installed, the up-to-date information will be replaced by obsolete information.
> We need to work out how to handle this better, preferably keeping the translatable text somewhere in com.jboss.jbds.product, not in releng.
> Perhaps we could do something with /com.jboss.jbds.product/about.mappings / about.ini? Ref: http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.platform.doc....
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBDS-1264) DSL Validation
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-1264?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-1264.
---------------------------------------
Resolution: Out of Date
This issue have not seen any updates for a year thus we are resolving it as "out of date".
If you believe this jira is still relevant please reopen the issue or open a new one mentioning this jira.
> DSL Validation
> --------------
>
> Key: JBDS-1264
> URL: https://issues.jboss.org/browse/JBDS-1264
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: drools
> Environment: All
> Reporter: Jim Tyrrell
> Fix For: LATER
>
>
> When authoring a DLS file you will typically have variable names of the type: "{disabilityType}"=customer: Customer(disabilityType == "{disabilityType}") or something like this. If the Customer object does not exist some sort of problem should be noted in the Problems section. Also a DSL might look like this:
> {percentage}=eval(customer.disabledPercent >= {percentage}) This to is a little harder as the customer is a variable that is implied.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBDS-1064) Web Service Create Wizard
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-1064?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-1064.
---------------------------------------
Resolution: Out of Date
This issue have not seen any updates for a year thus we are resolving it as "out of date".
If you believe this jira is still relevant please reopen the issue or open a new one mentioning this jira.
> Web Service Create Wizard
> -------------------------
>
> Key: JBDS-1064
> URL: https://issues.jboss.org/browse/JBDS-1064
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: integration-platform
> Affects Versions: 3.0.0.CR1
> Environment: JBDS 3.0 CR1 and EAP 5 or SOA-P5
> Reporter: Gary Lamperillo
> Assignee: Brian Fitzpatrick
> Priority: Critical
> Fix For: LATER
>
> Attachments: WebService_Gen_Issues.odp
>
>
> The Web Service Create Wizard has a few issues:
> 1) Creates a JSR-109 and an EAR Project, these projects should not be necessary. If an EAR project is already in the workspace, there are some issues encountered with the creation of the JSR-109 project. Neither of these projects can be deleted, once they are created by the wizard. (although sometimes it does not create the JSR-109 project and on workspace restart, this causes an issue with the perspectives)
> 2) The Web Service Create wizard requires JSR-181 annotations. The Wizard should be able to assist in adding these to the class.(check boxes in wizard screen to select which methods to add @WebMethod )
> 3) UDDI integration - unable to set properties for UDDI integration, We should be able to publish with the SOA-P5 juddi 3.0 registry.(would be nice to add subscription/notify hook for Web Service clients, but this is more of a future thing).
> 4) A Web Services preferences screen should be available in the properties to set uddi browser, and other web services preferences like CXF, JBossWS, Sun Metro
> 5) The WTP 1.5 had a SoapUI test web service client, this could be very useful - http://www.eclipse.org/webtools/jst/components/ws/1.5/tutorials/BottomUpW...
> 6) At the minimum, a simple Web Service wizard should be built that edits the web.xml for the servlet and servlet mapping entries. Many customers look at other tooling because we are lacking with this feature. The current WTP wizard should probably be disabled, since it appears the project is almost dead, since the last updates/working group meetings to it were in 2006 -> http://wiki.eclipse.org/Minutes_of_the_JEE_5_Working_Group_meeting_Nov_30...
> Features from the WTP and SoapUI should be reviewed for inclusion in the wizard.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months