[JBoss JIRA] (JBDS-2735) Ensure the Forge 1 wizards work well
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBDS-2735?page=com.atlassian.jira.plugin.... ]
Vineet Reynolds commented on JBDS-2735:
---------------------------------------
[~burrsutter], from a theoretical perspective, there is one problem I foresee. The generated AngularJS ngResource factories for the server-side JAXRS resources contain relative URLs i.e. they're not Cordova friendly. We'll need to find some scheme to have the user convert them into absolute ones. Or for that matter, we'll have to construct absolute or relative URLs based on the environment (like in TicketMonster).
I'll need to look at the behavior of the generated project in depth to see if there are other problematic areas, but I'm confident that they wont be as critical as the one described above.
> Ensure the Forge 1 wizards work well
> ------------------------------------
>
> Key: JBDS-2735
> URL: https://issues.jboss.org/browse/JBDS-2735
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Burr Sutter
>
--
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
11 years, 1 month
[JBoss JIRA] (JBDS-2735) Ensure the Forge 1 wizards work well
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-2735?page=com.atlassian.jira.plugin.... ]
Burr Sutter commented on JBDS-2735:
-----------------------------------
[~maxandersen]I need to see the "before" and "after" of an AngularJS project targeting old school web vs Cordova-oriented web. My guess is that the HTML, CSS and JS code is virtually identical. The one difference that I am aware of is that the Cordova project is client-side only - therefore the REST endpoints need to live in a Java EE 6 .war. Therefore the URL that the Cordova client code points too will be different.
[~vineet.reynolds]Is the AngularJS code generated by the Forge 1 scaffold compatible with Cordova? Or will it require significant end-user modification before being pulled into our Cordova project? (Gorkem's tool).
> Ensure the Forge 1 wizards work well
> ------------------------------------
>
> Key: JBDS-2735
> URL: https://issues.jboss.org/browse/JBDS-2735
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Burr Sutter
>
--
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
11 years, 1 month
[JBoss JIRA] (JBTIS-149) update BPEL in JBTIS 4.1.2 to include latest Eclipse BPEL 1.0.3
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-149?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBTIS-149 at 8/26/13 12:19 PM:
------------------------------------------------------------
Nick Boldt <nboldt(a)redhat.com> made a comment on [bug 996874|https://bugzilla.redhat.com/show_bug.cgi?id=996874]
The important part in your log is this, which shows you DID in fact install the newer version of Eclipse BPEL 1.0.3:
{code}
org.jboss.tools.bpel.feature (1.2.100.Final-v20130821-0236-B1019) "BPEL Editor"
org.eclipse.bpel.apache.ode.deploy.model (1.0.3.v20130816-0911-H221-CI) "EMF Model for ODE Deployment Descriptor" [Starting]
org.eclipse.bpel.apache.ode.deploy.ui (1.0.3.v20130816-0911-H221-CI) "UI for ODE Deployment Descriptor" [Starting]
org.eclipse.bpel.apache.ode.runtime (1.0.3.v20130816-0911-H221-CI) "Apache ODE Runtime Adapter" [Starting]
org.eclipse.bpel.common.model (1.0.3.v20130816-0911-H221-CI) "BPEL Common Model" [Active]
org.eclipse.bpel.common.ui (1.0.3.v20130816-0911-H221-CI) "BPEL Common UI" [Active]
org.eclipse.bpel.common.wsdl (1.0.3.v20130816-0911-H221-CI) "SOA Commons for WSDL and XML Schemas" [Starting]
org.eclipse.bpel.help (1.0.3.v20130816-0911-H221-CI) "BPEL Help" [Starting]
org.eclipse.bpel.cheatsheet (1.0.3.v20130816-0911-H221-CI) "BPEL Cheatsheet" [Starting]
org.eclipse.bpel.model (1.0.3.v20130816-0911-H221-CI) "BPEL Model" [Active]
org.eclipse.bpel.runtimes (1.0.3.v20130816-0911-H221-CI) "Eclipse BPEL Designer Runtimes" [Active]
org.eclipse.bpel.ui (1.0.3.v20130816-0911-H221-CI) "BPEL Editor" [Active]
org.eclipse.bpel.validator (1.0.3.v20130816-0911-H221-CI) "BPEL Validator Plug-in" [Active]
org.eclipse.bpel.wsil.model (1.0.3.v20130816-0911-H221-CI) "WSIL Model" [Active]
org.eclipse.bpel.xpath10 (1.0.3.v20130816-0911-H221-CI) "XPath Parser 1.0" [Resolved]
{code}
So... if the fix from [~bbrodt] didn't fix the problem, we need to get another fix into http://download.eclipse.org/bpel/site/1.0.3 and go through this song-and-dance again. :(
[~bbrodt], can you verify?
was (Author: jira-bugzilla-migration):
Nick Boldt <nboldt(a)redhat.com> made a comment on [bug 996874|https://bugzilla.redhat.com/show_bug.cgi?id=996874]
The important part in your log is this, which shows you DID in fact install the newer version of Eclipse BPEL 1.0.3:
org.jboss.tools.bpel.feature (1.2.100.Final-v20130821-0236-B1019) "BPEL Editor"
org.eclipse.bpel.apache.ode.deploy.model (1.0.3.v20130816-0911-H221-CI) "EMF Model for ODE Deployment Descriptor" [Starting]
org.eclipse.bpel.apache.ode.deploy.ui (1.0.3.v20130816-0911-H221-CI) "UI for ODE Deployment Descriptor" [Starting]
org.eclipse.bpel.apache.ode.runtime (1.0.3.v20130816-0911-H221-CI) "Apache ODE Runtime Adapter" [Starting]
org.eclipse.bpel.common.model (1.0.3.v20130816-0911-H221-CI) "BPEL Common Model" [Active]
org.eclipse.bpel.common.ui (1.0.3.v20130816-0911-H221-CI) "BPEL Common UI" [Active]
org.eclipse.bpel.common.wsdl (1.0.3.v20130816-0911-H221-CI) "SOA Commons for WSDL and XML Schemas" [Starting]
org.eclipse.bpel.help (1.0.3.v20130816-0911-H221-CI) "BPEL Help" [Starting]
org.eclipse.bpel.cheatsheet (1.0.3.v20130816-0911-H221-CI) "BPEL Cheatsheet" [Starting]
org.eclipse.bpel.model (1.0.3.v20130816-0911-H221-CI) "BPEL Model" [Active]
org.eclipse.bpel.runtimes (1.0.3.v20130816-0911-H221-CI) "Eclipse BPEL Designer Runtimes" [Active]
org.eclipse.bpel.ui (1.0.3.v20130816-0911-H221-CI) "BPEL Editor" [Active]
org.eclipse.bpel.validator (1.0.3.v20130816-0911-H221-CI) "BPEL Validator Plug-in" [Active]
org.eclipse.bpel.wsil.model (1.0.3.v20130816-0911-H221-CI) "WSIL Model" [Active]
org.eclipse.bpel.xpath10 (1.0.3.v20130816-0911-H221-CI) "XPath Parser 1.0" [Resolved]
So... if the fix from @Bob Brodt didn't fix the problem, we need to get another fix into http://download.eclipse.org/bpel/site/1.0.3 and go through this song-and-dance again. :(
@Bob, can you verify?
> update BPEL in JBTIS 4.1.2 to include latest Eclipse BPEL 1.0.3
> ---------------------------------------------------------------
>
> Key: JBTIS-149
> URL: https://issues.jboss.org/browse/JBTIS-149
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BPEL, distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Robert (Bob) Brodt
> Fix For: 4.1.2
>
>
> New content: http://download.eclipse.org/bpel/site/1.0.3 - version 1.0.3.v20130816-0911-H221-CI
> Reason: https://bugzilla.redhat.com/show_bug.cgi?id=996874
--
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
11 years, 1 month
[JBoss JIRA] (JBTIS-149) update BPEL in JBTIS 4.1.2 to include latest Eclipse BPEL 1.0.3
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBTIS-149?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBTIS-149:
-----------------------------------------------
Nick Boldt <nboldt(a)redhat.com> made a comment on [bug 996874|https://bugzilla.redhat.com/show_bug.cgi?id=996874]
The important part in your log is this, which shows you DID in fact install the newer version of Eclipse BPEL 1.0.3:
org.jboss.tools.bpel.feature (1.2.100.Final-v20130821-0236-B1019) "BPEL Editor"
org.eclipse.bpel.apache.ode.deploy.model (1.0.3.v20130816-0911-H221-CI) "EMF Model for ODE Deployment Descriptor" [Starting]
org.eclipse.bpel.apache.ode.deploy.ui (1.0.3.v20130816-0911-H221-CI) "UI for ODE Deployment Descriptor" [Starting]
org.eclipse.bpel.apache.ode.runtime (1.0.3.v20130816-0911-H221-CI) "Apache ODE Runtime Adapter" [Starting]
org.eclipse.bpel.common.model (1.0.3.v20130816-0911-H221-CI) "BPEL Common Model" [Active]
org.eclipse.bpel.common.ui (1.0.3.v20130816-0911-H221-CI) "BPEL Common UI" [Active]
org.eclipse.bpel.common.wsdl (1.0.3.v20130816-0911-H221-CI) "SOA Commons for WSDL and XML Schemas" [Starting]
org.eclipse.bpel.help (1.0.3.v20130816-0911-H221-CI) "BPEL Help" [Starting]
org.eclipse.bpel.cheatsheet (1.0.3.v20130816-0911-H221-CI) "BPEL Cheatsheet" [Starting]
org.eclipse.bpel.model (1.0.3.v20130816-0911-H221-CI) "BPEL Model" [Active]
org.eclipse.bpel.runtimes (1.0.3.v20130816-0911-H221-CI) "Eclipse BPEL Designer Runtimes" [Active]
org.eclipse.bpel.ui (1.0.3.v20130816-0911-H221-CI) "BPEL Editor" [Active]
org.eclipse.bpel.validator (1.0.3.v20130816-0911-H221-CI) "BPEL Validator Plug-in" [Active]
org.eclipse.bpel.wsil.model (1.0.3.v20130816-0911-H221-CI) "WSIL Model" [Active]
org.eclipse.bpel.xpath10 (1.0.3.v20130816-0911-H221-CI) "XPath Parser 1.0" [Resolved]
So... if the fix from @Bob Brodt didn't fix the problem, we need to get another fix into http://download.eclipse.org/bpel/site/1.0.3 and go through this song-and-dance again. :(
@Bob, can you verify?
> update BPEL in JBTIS 4.1.2 to include latest Eclipse BPEL 1.0.3
> ---------------------------------------------------------------
>
> Key: JBTIS-149
> URL: https://issues.jboss.org/browse/JBTIS-149
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BPEL, distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Robert (Bob) Brodt
> Fix For: 4.1.2
>
>
> New content: http://download.eclipse.org/bpel/site/1.0.3 - version 1.0.3.v20130816-0911-H221-CI
> Reason: https://bugzilla.redhat.com/show_bug.cgi?id=996874
--
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
11 years, 1 month
[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III commented on JBDS-2734:
------------------------------------------
To address the question of whether or not we can deliver SwitchYard functionality in Forge 2 - We've spent the last 3 days with the SwitchYard team, porting the Forge1 SwitchYard plugin over to Forge2. It works fine, we just don't have a UI on it yet because we didn't want to consume too much of the SY team's time. Putting a UI on it is a relatively trivial task, as the core addon behavior is already unit and integration tested. (We needed this for the Windup integration, which is why we didn't need a UI right away.) I estimate putting a UI on this to run in JBDS/Forge would take another 8 hours max.
> Forge 2 in JBDS
> ---------------
>
> Key: JBDS-2734
> URL: https://issues.jboss.org/browse/JBDS-2734
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Burr Sutter
>
> Is Forge 2 ready to be included in JBDS ?
--
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
11 years, 1 month
[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ]
Lincoln Baxter III commented on JBDS-2734:
------------------------------------------
Well... I was under the impression that you didn't want to remove Forge 1 from JBDS because we wouldn't be delivering exactly the same solution/commands/etc. But if that's the direction you want to go we could use the original CTRL-4 instead of CTRL-5.
I would love to go 100% to Forge 2 in November, but I don't want anyone be under the impression that things will work the same way or be backwards compatible.
> Forge 2 in JBDS
> ---------------
>
> Key: JBDS-2734
> URL: https://issues.jboss.org/browse/JBDS-2734
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Burr Sutter
>
> Is Forge 2 ready to be included in JBDS ?
--
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
11 years, 1 month
[JBoss JIRA] (JBDS-2707) Unexpected plugin changes between two builds of JBDS
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2707?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-2707:
-------------------------------------
I agree, let's keep an eye on this next time.
> Unexpected plugin changes between two builds of JBDS
> ----------------------------------------------------
>
> Key: JBDS-2707
> URL: https://issues.jboss.org/browse/JBDS-2707
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Affects Versions: 7.0.0.CR1
> Reporter: Martin Malina
> Assignee: Mickael Istria
> Fix For: 7.1.0.Alpha1
>
>
> I was trying to compare the contents of these two installers:
> jbdevstudio-product-universal-7.0.0.GA-v20130717-1700-B362.jar
> jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364.jar
> The only expected difference was in central. But in fact there were many differences in these two plugins:
> org.jboss.netty_3.2.5.Final-20130531-2315.jar
> com.ning.async-http-client_1.6.5.20130531-2315.jar
> I could provide instructions on how to run the comparison using the dist-diff tool that is able to spot differences in classes. But for now let's start with the probable cause.
> In build B364, both of these plugins had this additional file in them:
> eclipse.inf
> with this content:
> #Processed using Jarprocessor
> pack200.conditioned = true
> Now the question is: Why was the option used in B364, but not B362?
> And what are the consequences, if any?
--
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
11 years, 1 month
[JBoss JIRA] (JBDS-2737) Archive old JBDS docs on devstudio.jboss.com
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2737?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2737:
-----------------------------
Attachment: JBDS2737_draft-css.png
Have posted the HTML onto the server [1], but the "DRAFT" watermark is still there:
!JBDS2737_draft-css.png!
So, unless someone has any advice for how to remove that / override the CSS, I'll just remove 'em.
[1] https://devstudio.jboss.com/site/documentation/en-US/Red_Hat_JBoss_Develo...
> Archive old JBDS docs on devstudio.jboss.com
> ---------------------------------------------
>
> Key: JBDS-2737
> URL: https://issues.jboss.org/browse/JBDS-2737
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: documentation
> Affects Versions: 3.0.1.GA, 4.0.1.GA, 4.1.3.GA, 5.0.2.GA, 6.0.0.GA, 7.0.0.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Attachments: JBDS2737_draft-css.png
>
>
> This is a workaround for https://bugzilla.redhat.com/show_bug.cgi?id=983934 because it's easier to download the internet (apparently) than to fix portal code. *sigh*
> Docs will be posted to devstudio.jboss.com/site/documentation/ as they include absolute path references.
> _Hack: 1. Proper solution: 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
11 years, 1 month