October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-186) ModeShape sometimes doesn't publish all models of Teiid VDB

by Randall Hauch (JIRA)

[ https://issues.jboss.org/browse/JBTIS-186?page=com.atlassian.jira.plugin.... ] Randall Hauch edited comment on JBTIS-186 at 10/11/13 9:51 AM: --------------------------------------------------------------- Please verify whether the above stack trace is even related. I suspect the stack trace occurred _when the server was shutdown while ModeShape was actively running the sequencer_. If that's the case, then the sequencing operation would have stopped immediately without saving any content, resulting in "missing information". (ModeShape runs all sequencing activities in the background, and each one is given its own session with which the sequencer reads and writes to the repository. This session is not available to any other components, meaning the session cannot be closed except by the sequencer. But as one might expect shutting down a repository must necessarily close all open sessions, and this includes any sessions being used by sequencing operations running in the background.) Regarding the exception, my guess is that the user too quickly shutdown the server. To fix, simply re-publish the file. If the exception is unrelated, then you might not just be waiting long enough. The sequencing operation is asynchronous (via an internal queue), which means that it may take a few minutes (or longer if the server is under load) for the sequencing output to appear in the repository. To test this out, simply perform your procedure and then repeat step 4 multiple times to see if additional rows show up in the query results. was (Author: rhauch): Please verify whether the above stack trace is even related. I suspect the stack trace occurred _when the server was shutdown while ModeShape was actively running the sequencer_. If that's the case, then the sequencing operation would have stopped immediately without saving any content, resulting in "missing information". (ModeShape runs all sequencing activities in the background, and each one is given its own session with which the sequencer reads and writes to the repository. This session is not available to any other components, meaning the session cannot be closed except by the sequencer. But as one might expect shutting down a repository must necessarily close all open sessions, and this includes any sessions being used by sequencing operations running in the background.) My guess is that the user too quickly shutdown the server. To fix, simply re-publish the file. > ModeShape sometimes doesn't publish all models of Teiid VDB > ----------------------------------------------------------- > > Key: JBTIS-186 > URL: https://issues.jboss.org/browse/JBTIS-186 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: modeshape > Affects Versions: 4.1.3 > Environment: Ubuntu 12.04, JBTIS 4.1.3.Beta4, DV 6.0.0.ER2, sun jdk 1.6 > Reporter: Lucie Fabrikova > Attachments: BooksMode.vdb > > > If I publish a teiid VDB with relational models .xmi in given environment, sometimes some (or all) of the models are not published. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-186) ModeShape sometimes doesn't publish all models of Teiid VDB

by Randall Hauch (JIRA)

[ https://issues.jboss.org/browse/JBTIS-186?page=com.atlassian.jira.plugin.... ] Randall Hauch commented on JBTIS-186: ------------------------------------- Please verify whether the above stack trace is even related. I suspect the stack trace occurred _when the server was shutdown while ModeShape was actively running the sequencer_. If that's the case, then the sequencing operation would have stopped immediately without saving any content, resulting in "missing information". (ModeShape runs all sequencing activities in the background, and each one is given its own session with which the sequencer reads and writes to the repository. This session is not available to any other components, meaning the session cannot be closed except by the sequencer. But as one might expect shutting down a repository must necessarily close all open sessions, and this includes any sessions being used by sequencing operations running in the background.) My guess is that the user too quickly shutdown the server. To fix, simply re-publish the file. > ModeShape sometimes doesn't publish all models of Teiid VDB > ----------------------------------------------------------- > > Key: JBTIS-186 > URL: https://issues.jboss.org/browse/JBTIS-186 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: modeshape > Affects Versions: 4.1.3 > Environment: Ubuntu 12.04, JBTIS 4.1.3.Beta4, DV 6.0.0.ER2, sun jdk 1.6 > Reporter: Lucie Fabrikova > Attachments: BooksMode.vdb > > > If I publish a teiid VDB with relational models .xmi in given environment, sometimes some (or all) of the models are not published. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12274) BrowserSim borks on jquery mobile (RHEL 6.1)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12274?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-12274: ------------------------------------------------- Jiri Pallich <jpallich(a)redhat.com> made a comment on [bug 966571|https://bugzilla.redhat.com/show_bug.cgi?id=966571] Hi Tomas, yes, let us move this issue to RHEL 6.6. It seems the only solution here is to rebase the whole webkitgtk. Cheers, Jiri > BrowserSim borks on jquery mobile (RHEL 6.1) > -------------------------------------------- > > Key: JBIDE-12274 > URL: https://issues.jboss.org/browse/JBIDE-12274 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 3.3.0.CR1 > Environment: RHEL 6.1 > JBoss Developer Studio 5.0.0.CR1 > Reporter: Gabriel De Repentigny > Assignee: Yahor Radtsevich > Labels: upstream > Fix For: 4.0.0.Alpha1, 4.1.x > > Attachments: jQMrefsRemoved.png, midori-browsersim.png, midori-browsersim.png, python-tabbed-browser.png, Screenshot-BrowserSim .png, windows-7_Safari-5.1.2-7534.52.7.png > > > I'm walking through the JBoss Way Ticket Monster lab. JDS's BrowserSim borks while trying to render mobile.html (pasted below) which is part of the tutorial. > The problem seems to be with the jquery mobile js file. If you take that include out, it renders (sans-mobile styling). > {code:xml} > <!DOCTYPE html> > <html> > <head> > <title>jQuery Mobile Template</title> > <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> > <meta name="viewport" content="width=device-width, initial-scale=1" /> > <link rel="stylesheet" > href="http://code.jquery.com/mobile/1.1.0/jquery.mobile-1.1.0.min.css" /> > <script type="text/javascript" > src="http://code.jquery.com/jquery-1.7.1.min.js"></script> > <script type="text/javascript" > src="http://code.jquery.com/mobile/1.1.0/jquery.mobile-1.1.0.min.js"></script> > <script type="text/javascript"> > $(document).on("pageinit", "#page1", function(event){ > alert("Ready To Go"); > }); > $.getJSON("rest/events", function(events) { > // console.log("returned are " + results); > var listOfEvents = $("#listOfItems"); > listOfEvents.empty(); > $.each(events, function(index, event) { > // console.log(event.name); > listOfEvents.append("<li><a href=’#’>" + event.name + "</a>"); > }); > listOfEvents.listview("refresh"); > }); > </script> > </head> > <body> > <div data-role="page" id="page1"> > <div data-role="header"> > <h1>jQuery Mobile</h1> > </div> > <div data-role="content"> > <ul id="listOfItems" data-role="listview" data-inset="true" > data-filter="true"> > <li><a href="">One</a></li> > <li><a href="">Two</a></li> > <li><a href="">Three</a></li> > </ul> > </div> > <div data-role="footer"> > <h4>www.jboss.org/developer</h4> > </div> > </div> > </body> > </html> > {code} -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2796) Created Seam EAR project contains doubled jboss-deployment-structure.xml file

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2796?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2796: ----------------------------- CDW devel_ack: ? CDW pm_ack: ? CDW qa_ack: ? CDW release: ? Target Release: 3.0.2.GA > Created Seam EAR project contains doubled jboss-deployment-structure.xml file > ----------------------------------------------------------------------------- > > Key: JBDS-2796 > URL: https://issues.jboss.org/browse/JBDS-2796 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: seam > Affects Versions: 7.1.0.Alpha1 > Reporter: Tomas Remes > Priority: Minor > > When you generate Seam project called e.g. SeamEar, then you'll get project with doubled jboss-deployment-structure.xml file in: > /SeamEar/WebContent/WEB-INF/ > /SeamEar-ear/EarContent/META-INF/ > I think it's really not necessary and might be also confusing. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2796) Created Seam EAR project contains doubled jboss-deployment-structure.xml file

by Tomas Remes (JIRA)

Tomas Remes created JBDS-2796: --------------------------------- Summary: Created Seam EAR project contains doubled jboss-deployment-structure.xml file Key: JBDS-2796 URL: https://issues.jboss.org/browse/JBDS-2796 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: seam Affects Versions: 7.1.0.Alpha1 Reporter: Tomas Remes Priority: Minor When you generate Seam project called e.g. SeamEar, then you'll get project with doubled jboss-deployment-structure.xml file in: /SeamEar/WebContent/WEB-INF/ /SeamEar-ear/EarContent/META-INF/ I think it's really not necessary and might be also confusing. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15654) New Application wizard: merge existing / new application forms into a single one

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15654?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15654: ------------------------------------- Description: in the new / import application wizard the first page allows you to configure your app. It allows you to choose an existing or create a new app. !configure-application-wizard-page.png! Both forms should be merged into a single form in order to unclutter the current UI which is very crowded already. Assignee: Andre Dietisheim Component/s: openshift > New Application wizard: merge existing / new application forms into a single one > -------------------------------------------------------------------------------- > > Key: JBIDE-15654 > URL: https://issues.jboss.org/browse/JBIDE-15654 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > Attachments: configure-application-wizard-page.png > > > in the new / import application wizard the first page allows you to configure your app. It allows you to choose an existing or create a new app. > !configure-application-wizard-page.png! > Both forms should be merged into a single form in order to unclutter the current UI which is very crowded already. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15654) New Application wizard: merge existing / new application forms into a single one

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15654?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15654: ------------------------------------- Attachment: configure-application-wizard-page.png > New Application wizard: merge existing / new application forms into a single one > -------------------------------------------------------------------------------- > > Key: JBIDE-15654 > URL: https://issues.jboss.org/browse/JBIDE-15654 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > Attachments: configure-application-wizard-page.png > > > in the new / import application wizard the first page allows you to configure your app. It allows you to choose an existing or create a new app. > !configure-application-wizard-page.png! > Both forms should be merged into a single form in order to unclutter the current UI which is very crowded already. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15654) New Application wizard: merge existing / new application forms into a single one

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15654?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15654: ------------------------------------- Fix Version/s: 4.2.0.Alpha1 > New Application wizard: merge existing / new application forms into a single one > -------------------------------------------------------------------------------- > > Key: JBIDE-15654 > URL: https://issues.jboss.org/browse/JBIDE-15654 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Reporter: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15654) New Application wizard: merge existing / new application forms into a single one

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15654?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15654: ------------------------------------- Affects Version/s: 4.2.0.Alpha1 > New Application wizard: merge existing / new application forms into a single one > -------------------------------------------------------------------------------- > > Key: JBIDE-15654 > URL: https://issues.jboss.org/browse/JBIDE-15654 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15654) New Application wizard: merge existing / new application forms into a single one

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-15654: ---------------------------------------- Summary: New Application wizard: merge existing / new application forms into a single one Key: JBIDE-15654 URL: https://issues.jboss.org/browse/JBIDE-15654 Project: Tools (JBoss Tools) Issue Type: Enhancement Reporter: Andre Dietisheim -- 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, 6 months

1
0
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 October 2013