Xulrunner and jQuery Mobile 1.3
by Alexey Kazakov
Hi,
As you know we are working on wizards for our new jQuery Mobile palette:
https://issues.jboss.org/browse/JBIDE-13413
The wizards have a visual preview. We use the SWT Browser for that. But
there is a problem. It actually uses our bundled xulrunner from VPE
which has a limit support of HTML5.
This browser works ok with jQuery Mobile 1.2 but doesn't work at all
with 1.3.
If you don't have VPE installed in your Eclipse than this preview will
work with 1.3 but if you do then the xulrunner from VPE will be used.
We found a workaround for this problem. Our wizards generate code for
the latest jQuery Mobile 1.3 but we use 1.2 for visual preview. In some
cases 1.2 and 1.3 behaves differently and we have to *simulate* jQuery
1.3 widgets using 1.2 code for preview.
But I believe it's going to be a much bigger problem for future versions
of jQuery Mobile.
It's not only about jQuery wizards actually. It's about all eclipse
widgets which use swt browser.
13 years
Re: [jbosstools-dev] AS 7.2/EAP 6.1 (basis for SOA-P 6.0) won't start in JBDS 5 and 6
by Snjezana Peco
On 2/15/2013 6:15 PM, Max Rydahl Andersen wrote:
>> I have tested JBoss EAP 6.1.0.DR4 and JBoss AS 7.2-SNAPSHOT (built using the JBoss AS git master)
>> There are two issues in runtime detection:
>> - JBoss EAP 6.1.0.DR4 is recognized as AS 7.2
>> - JBoss AS 7.2-SNAPSHOT is added as EAP 6.1
>> I think we have to add yet another server type (AS 7.2) and, after that, make runtime detection to recognize JBoss EAP 6.1.0.DR4 correctly.
> Rob already did these afaik: see https://issues.jboss.org/browse/JBIDE-13537
>
> If you spot other things missing let me know - just do that on jbosstools-dev.
>
> btw. since there are no AS 7.2 going to be released to the wild nor any EAP 6.1 available we went with adding an "EAP 6.1 (Tech Preview)" adapter.
I have tested jbosstools master that includes the fix for JBIDE-13537.
If it is planned to release JBoss AS 7.2, we will probably have to add
an AS 7.2 (Tech preview) provider.
Anyway, we have to fix the issue with recognizing the version of JBoss
EAP 6.1.
Snjeza
> Thanks,
> Max
>
>> Snjeza
>>
>> On 2/15/2013 8:37 AM, Max Rydahl Andersen wrote:
>>> Hi guys,
>>>
>>> I realized that you guys might not be aware of the changes on EAP and SOA-P runtime side but
>>> just want to bring to your attention that AS 7.2/EAP 6.1 servers has changed their modules dir layout
>>> making the recognition and classpath handling we had in place for the AS 7.x/EAP 6.x family malfunction (+ a few other cosmetic changes
>>> like use of ansicolors by default in logging output we need to handle)
>>>
>>> Bug is here: https://issues.jboss.org/browse/JBIDE-13537
>>>
>>> We are currently working on a minimal fix for it in 7.0.Alpha1 to be released soon so there is some version of JBDS that will have a way
>>> to start the upcoming EAP 6.1 alpha - that fix is though pretty fragile because there is no EAP 6.1 version available yet so things might change.
>>>
>>> For one it means we no longer have a stable way to provide a classpath out-of-the-box for users not using Maven at this time.
>>>
>>> Once we got something stable we'll evaluate our options with respect to JBDS 6.x.
>>>
>>> p.s. if you have used the EAP 6 DR3 sent around last week you could still use it with the tools since that was based on AS 7.2 stream
>>> before these modules changes made it in. DR4 is first version that has this issue.
>>>
>>> /max
>>>
>
13 years
JBoss Tools Integration Stack Release
by Paul Leacu
Hey all -
We are getting closer to releasing the community JBTIS/ production JBDS Integration Platform. The latest update repo is here:
http://download.jboss.org/jbosstools/updates/integration/juno/integration...
Rob's completed a release process wiki that each component owner should adhere to:
https://community.jboss.org/wiki/IntegrationToolingReleaseProcess
The component owner is responsible for the release of their component. This person is responsible for:
* working with QA and PMs to ensure all requirements are met within the required time frame.
* working within the established engineering processes to ensure the correct version of their component
is integrated into the appropriate version of the aggregate release. (In other words, here are the
stable bits for component A that need to go into IS x.y.).
(see wiki for more details)
The identified component owners are here:
https://issues.jboss.org/plugins/servlet/project-config/JBTIS/components
Please verify that I've identified the correct component owner for your tool. The one loose end that remains is the disposition of the runtime discovery project runtime-soa. The pieces of this project need to be moved into the components they support:
Drools/jBPM and ESB
Once integrated into their new home the new component owners will assume their maintenance and release.
Please reply to me with any issues. This will make your life easier! :)
--paull
13 years
