[JBoss JIRA] Created: (JBIDE-3376) Recreate mechanizm of prefix verification
by Yura Zhishko (JIRA)
Recreate mechanizm of prefix verification
-----------------------------------------
Key: JBIDE-3376
URL: https://jira.jboss.org/jira/browse/JBIDE-3376
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.0.0.cr1
Reporter: Yura Zhishko
Assignee: Maxim Areshkau
Insert next source code:
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="j"%>
<%@ taglib uri="http://richfaces.org/rich" prefix="rich"%>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<html>
<head></head>
<body>
<j:form>
<j:dataTable value="#{bookList.bookList}" var="book">
<f:facet name="header"><j:outputText value="Header" /> </f:facet>
<f:facet name="footer"><j:outputText value="Header" /> </f:facet>
<j:column>
<j:outputText value="#{book.name}" />
</j:column>
<j:column>
<j:outputText value="#{book.name}" />
</j:column>
</j:dataTable>
<j:commandLink action="none" value="Go next page:"/><br></br>
<j:outputText value="Begin" />
</j:form>
</body>
</html>
See the results (screenshot-1). The main cause of this is that we make a verification of parents next way:
<vpe:if
test="parentname()='h:dataTable'|parentname()='h:panelGrid'....
And we take account of only "h"-prefix. This verification doesn't include other named prefix
--
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
17 years, 2 months
[JBoss JIRA] Created: (JBIDE-3520) Incorrect state of groups in Palette editor
by Yura Zhishko (JIRA)
Incorrect state of groups in Palette editor
-------------------------------------------
Key: JBIDE-3520
URL: https://jira.jboss.org/jira/browse/JBIDE-3520
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.0.0.CR2
Reporter: Yura Zhishko
Assignee: Alexey Kazakov
Priority: Minor
1) Open Palette editor.
2) Click on, for example, JSF group.
3) Check state Hidden to "no".
4) Check state Hidden of all subgroups to "yes".
RESULT: No groups are displayed in palette (this is correct). But Hidden state of parent JSF group is "no".
RESOLUTION: If we check the Hidden state of all subgroups to "yes", hidden state of parent group should be "yes", too.
5) Check the Hidden state of any parent (in our example JSF) group to "yes".
6) Check the Hidden state of any subgroup to "no".
RESULT: Nothing happened, no group is displayed.
RESOLUTION: Even if we check the Hidden state of any one subgroups to "no" Hidden state of parent group should be set to "no" automatically (in addition, this subgroup should be displayed in palette).
--
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
17 years, 2 months
[JBoss JIRA] Created: (JBDS-474) Clean-up release download sites for JBT and JBDS befor each release upload
by Denis Golovin (JIRA)
Clean-up release download sites for JBT and JBDS befor each release upload
--------------------------------------------------------------------------
Key: JBDS-474
URL: https://jira.jboss.org/jira/browse/JBDS-474
Project: Developer Studio
Issue Type: Task
Reporter: Denis Golovin
Assignee: Max Rydahl Andersen
We need clean-up because of qualifier in all JBT jars. That means it always add new files with new qualifier in version instead of overwriting them as it was before.
It is not a problem for JBDS builds because hudson has direct access to download site, but it is a problem for JBossTools build which uses scp to upload release to download site. Usually we have several release builds before gold one and that means all builds collected on download site.
We have to find way remove previous build from download site before uploading new one or keep all builds in nightly upload area (each build is its own directory) while we have gold one. Then gold one can be copied to public download site.
--
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
17 years, 2 months
[JBoss JIRA] Created: (JBIDE-3478) NPE when opening Hibernate Console with type JPA
by Juergen Zimmermann (JIRA)
NPE when opening Hibernate Console with type JPA
------------------------------------------------
Key: JBIDE-3478
URL: https://jira.jboss.org/jira/browse/JBIDE-3478
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.0.0.cr1
Environment: Eclipse 3.4.1, WTP 3.0.3
Reporter: Juergen Zimmermann
When opening a console configuration I get this stacktrace (I invoked the Hibernate Console the first time after a couple of weeks and definitely the 1st time using 3.0.0.cr1):
org.hibernate.console.HibernateConsoleRuntimeException: Could not create JPA based Configuration
at org.hibernate.console.ConsoleConfiguration.buildJPAConfiguration(ConsoleConfiguration.java:161)
at org.hibernate.console.ConsoleConfiguration.buildConfiguration(ConsoleConfiguration.java:541)
at org.hibernate.console.ConsoleConfiguration.access$0(ConsoleConfiguration.java:526)
at org.hibernate.console.ConsoleConfiguration$2.execute(ConsoleConfiguration.java:222)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:64)
at org.hibernate.console.ConsoleConfiguration.buildWith(ConsoleConfiguration.java:204)
at org.hibernate.console.ConsoleConfiguration.build(ConsoleConfiguration.java:111)
at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:40)
at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:99)
at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:105)
at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:234)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.reflect.InvocationTargetException
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.hibernate.console.ConsoleConfiguration.buildJPAConfiguration(ConsoleConfiguration.java:146)
... 11 more
Caused by: javax.persistence.PersistenceException: java.lang.NullPointerException
at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:258)
... 16 more
Caused by: java.lang.NullPointerException
at org.hibernate.cfg.annotations.CollectionBinder.buildOrderByClauseFromHql(CollectionBinder.java:851)
at org.hibernate.cfg.annotations.CollectionBinder.bindOneToManySecondPass(CollectionBinder.java:608)
at org.hibernate.cfg.annotations.CollectionBinder.bindStarToManySecondPass(CollectionBinder.java:563)
at org.hibernate.cfg.annotations.CollectionBinder$1.secondPass(CollectionBinder.java:517)
at org.hibernate.cfg.CollectionSecondPass.doSecondPass(CollectionSecondPass.java:43)
at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1130)
at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:316)
at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1115)
at org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1269)
at org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:150)
at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:888)
at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:186)
at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:246)
... 16 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
17 years, 2 months