[JBoss JIRA] (JBIDE-13326) include Juno SR1+ performance fix as new connector on Central
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13326?page=com.atlassian.jira.plugi... ]
Denis Golovin closed JBIDE-13326.
---------------------------------
Resolution: Done
> include Juno SR1+ performance fix as new connector on Central
> -------------------------------------------------------------
>
> Key: JBIDE-13326
> URL: https://issues.jboss.org/browse/JBIDE-13326
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, target-platform, updatesite
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.0.1.Final, 4.0.0.Final
>
> Attachments: JBIDE13226-40x.patch.txt, JBIDE13326-60x.patch.txt, JBIDE13326-JBDS-central.png, JBIDE13326-JBT-central-JavaEE.png, JBIDE13326-JBT-central.png
>
>
> Info: https://bugs.eclipse.org/bugs/show_bug.cgi?id=385272, http://wiki.eclipse.org/Platform_UI/Juno_Performance_Investigation
> Update Site: http://download.eclipse.org/eclipse/updates/4.2 --> Eclipse UI Juno SR1 Optimizations should be installed
> For Juno SR2 maintenance builds >= Nov 21, patch feature not needed.
> We could also consider setting these vmargs when installing JBT (community cental feature?) and/or JBDS BYOE:
> {code}
> -Xmn128m
> -Xms1024m
> -Xmx1024m
> -Xss2m
> -XX:PermSize=256m
> -XX:MaxPermSize=384m
> {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
13 years, 1 month
[JBoss JIRA] (JBIDE-13326) include Juno SR1+ performance fix as new connector on Central
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13326?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13326:
----------------------------------
Release Notes Docs Status: Not Yet Documented
Affects: Release Notes
> include Juno SR1+ performance fix as new connector on Central
> -------------------------------------------------------------
>
> Key: JBIDE-13326
> URL: https://issues.jboss.org/browse/JBIDE-13326
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, target-platform, updatesite
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.0.0.Final, 4.0.1.Final
>
> Attachments: JBIDE13226-40x.patch.txt, JBIDE13326-60x.patch.txt, JBIDE13326-JBDS-central.png, JBIDE13326-JBT-central-JavaEE.png, JBIDE13326-JBT-central.png
>
>
> Info: https://bugs.eclipse.org/bugs/show_bug.cgi?id=385272, http://wiki.eclipse.org/Platform_UI/Juno_Performance_Investigation
> Update Site: http://download.eclipse.org/eclipse/updates/4.2 --> Eclipse UI Juno SR1 Optimizations should be installed
> For Juno SR2 maintenance builds >= Nov 21, patch feature not needed.
> We could also consider setting these vmargs when installing JBT (community cental feature?) and/or JBDS BYOE:
> {code}
> -Xmn128m
> -Xms1024m
> -Xmx1024m
> -Xss2m
> -XX:PermSize=256m
> -XX:MaxPermSize=384m
> {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
13 years, 1 month
[JBoss JIRA] (JBIDE-13326) include Juno SR1+ performance fix as new connector on Central
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13326?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13326:
----------------------------------
Labels: new_and_noteworthy (was: )
> include Juno SR1+ performance fix as new connector on Central
> -------------------------------------------------------------
>
> Key: JBIDE-13326
> URL: https://issues.jboss.org/browse/JBIDE-13326
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, target-platform, updatesite
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.0.0.Final, 4.0.1.Final
>
> Attachments: JBIDE13226-40x.patch.txt, JBIDE13326-60x.patch.txt, JBIDE13326-JBDS-central.png, JBIDE13326-JBT-central-JavaEE.png, JBIDE13326-JBT-central.png
>
>
> Info: https://bugs.eclipse.org/bugs/show_bug.cgi?id=385272, http://wiki.eclipse.org/Platform_UI/Juno_Performance_Investigation
> Update Site: http://download.eclipse.org/eclipse/updates/4.2 --> Eclipse UI Juno SR1 Optimizations should be installed
> For Juno SR2 maintenance builds >= Nov 21, patch feature not needed.
> We could also consider setting these vmargs when installing JBT (community cental feature?) and/or JBDS BYOE:
> {code}
> -Xmn128m
> -Xms1024m
> -Xmx1024m
> -Xss2m
> -XX:PermSize=256m
> -XX:MaxPermSize=384m
> {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
13 years, 1 month
[JBoss JIRA] (JBIDE-13381) ESB Editor fails validation with "http-client-property" property (JBDS-2446), resulting .esb cannot be deployed in JBDS
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13381:
----------------------------------
Release Notes Docs Status: Not Required
> ESB Editor fails validation with "http-client-property" property (JBDS-2446), resulting .esb cannot be deployed in JBDS
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13381
> URL: https://issues.jboss.org/browse/JBIDE-13381
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb
> Affects Versions: 3.3.0.Final-SOA
> Reporter: Brian Fitzpatrick
> Assignee: Brian Fitzpatrick
> Priority: Critical
> Fix For: 3.3.x, 4.0.1.Final
>
> Attachments: JBIDE-13381-3.3.x.patch, jbide-13381.patch, JBIDE-13381_error.png, JBIDE-13381_error_source.png, JBIDE-13381_resolved.png
>
>
> When editing an ESB file (jboss-esb.xml), we have two ways which are using the native XML editor or the visual way.
> When we want to use the property X. We created our service and our SOAPClient using the visual editor, then we have to add the "http-client-property" manually
> <?xml version="1.0"?>
> <jbossesb parameterReloadSecs="5"
> xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..."
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem...">
> <services>
> <service category="c1" description="d1" name="s1">
> <actions>
> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client">
> <property name="wsdl" value="someWsdl"/>
> <property name="SOAPAction" value="noAction"/>
> <property name="endpointUrl" value="http://host/servername">
> <http-client-property name="file" value="httpclient.properties" />
> </property>
> </action>
> </actions>
> </service>
> </services>
> </jbossesb>
> Notice the "http-client-property" in the action property element. The problem is that when using visual editor of this file and adding something new or editing existing thing, the code related to this property is deleted. In the example above, I have the following result, showing what the editor removed: (in this case I just changed the service name from service-test to service-test-edited)
> <?xml version="1.0"?>
> <jbossesb parameterReloadSecs="5"
> xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..."
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem...">
> <services>
> <service category="c1" description="d1" name="s1-edited">
> <actions>
> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client">
> <property name="wsdl" value="someWsdl"/>
> <property name="SOAPAction" value="noAction"/>
> <property name="endpointUrl" value="http://host/servername"/>
> </action>
> </actions>
> </service>
> </services>
> </jbossesb>
> One test we have done is change the XSD used by the JBDS(1.3.1 to the one used in quickstars (1.0.1). The http-client-property worked fine, but other things stopped working. So we need to know what's wrong with the schema and what should make it works fine.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13381) ESB Editor fails validation with "http-client-property" property (JBDS-2446), resulting .esb cannot be deployed in JBDS
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ]
Denis Golovin closed JBIDE-13381.
---------------------------------
Resolution: Done
> ESB Editor fails validation with "http-client-property" property (JBDS-2446), resulting .esb cannot be deployed in JBDS
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13381
> URL: https://issues.jboss.org/browse/JBIDE-13381
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb
> Affects Versions: 3.3.0.Final-SOA
> Reporter: Brian Fitzpatrick
> Assignee: Brian Fitzpatrick
> Priority: Critical
> Fix For: 3.3.x, 4.0.1.Final
>
> Attachments: JBIDE-13381-3.3.x.patch, jbide-13381.patch, JBIDE-13381_error.png, JBIDE-13381_error_source.png, JBIDE-13381_resolved.png
>
>
> When editing an ESB file (jboss-esb.xml), we have two ways which are using the native XML editor or the visual way.
> When we want to use the property X. We created our service and our SOAPClient using the visual editor, then we have to add the "http-client-property" manually
> <?xml version="1.0"?>
> <jbossesb parameterReloadSecs="5"
> xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..."
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem...">
> <services>
> <service category="c1" description="d1" name="s1">
> <actions>
> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client">
> <property name="wsdl" value="someWsdl"/>
> <property name="SOAPAction" value="noAction"/>
> <property name="endpointUrl" value="http://host/servername">
> <http-client-property name="file" value="httpclient.properties" />
> </property>
> </action>
> </actions>
> </service>
> </services>
> </jbossesb>
> Notice the "http-client-property" in the action property element. The problem is that when using visual editor of this file and adding something new or editing existing thing, the code related to this property is deleted. In the example above, I have the following result, showing what the editor removed: (in this case I just changed the service name from service-test to service-test-edited)
> <?xml version="1.0"?>
> <jbossesb parameterReloadSecs="5"
> xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..."
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem...">
> <services>
> <service category="c1" description="d1" name="s1-edited">
> <actions>
> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client">
> <property name="wsdl" value="someWsdl"/>
> <property name="SOAPAction" value="noAction"/>
> <property name="endpointUrl" value="http://host/servername"/>
> </action>
> </actions>
> </service>
> </services>
> </jbossesb>
> One test we have done is change the XSD used by the JBDS(1.3.1 to the one used in quickstars (1.0.1). The http-client-property worked fine, but other things stopped working. So we need to know what's wrong with the schema and what should make it works fine.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13346) DirectoryScanner fails on non-existing folders
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13346?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13346:
----------------------------------
Release Notes Docs Status: Not Yet Documented
Affects: Release Notes
> DirectoryScanner fails on non-existing folders
> ----------------------------------------------
>
> Key: JBIDE-13346
> URL: https://issues.jboss.org/browse/JBIDE-13346
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Archives, JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Environment: Windows XP/Windows 7
> Eclipse 4.3M4
> Reporter: Jesper Skov
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.0.1.Final, 4.1.0.Alpha1
>
> Attachments: org.eclipse.wst.common.component
>
>
> DirectoryScanner can be made to fail on non-existing folders.
> In our setup, these folders are possibly picked up from the Deployment Assembly settings.
> The folders are created by our custom Builder with highest priority, so appears to work properly with everything else in Eclipse.
> But it seems the Archive DirectoryScanner runs before our builder.
> The stack trace looks like this:
>
> {code}
> java.lang.IllegalStateException: basedir C:\udvikler\ws\plugins\jb.it.reuters\build\gen-lib-deployable is not a directory
> at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scanPrepare(DirectoryScanner.java:552)
> at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scan(DirectoryScanner.java:588)
> at org.jboss.ide.eclipse.archives.core.model.DirectoryScannerFactory.createDirectoryScanner(DirectoryScannerFactory.java:66)
> at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent$WorkspaceFilter.<init>(WorkspaceFilesetVirtualComponent.java:100)
> at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent.getRootFolder(WorkspaceFilesetVirtualComponent.java:53)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.consumeComponent(FlatVirtualComponent.java:203)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.addConsumedReferences(FlatVirtualComponent.java:196)
> at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.optimize(ClasspathLibraryExpander.java:47)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.cacheResources(FlatVirtualComponent.java:119)
> at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.fetchResources(FlatVirtualComponent.java:101)
> at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.fetchResource(ClasspathLibraryExpander.java:74)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.getBaseEARLibRefs(J2EEComponentClasspathContainer.java:463)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.requiresUpdate(J2EEComponentClasspathContainer.java:208)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.refresh(J2EEComponentClasspathContainer.java:540)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.processModules(J2EEComponentClasspathUpdater.java:311)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.access$4(J2EEComponentClasspathUpdater.java:295)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob$1.run(J2EEComponentClasspathUpdater.java:336)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.run(J2EEComponentClasspathUpdater.java:321)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {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
13 years, 1 month
[JBoss JIRA] (JBIDE-13435) remove uml2, zest & graphiti from JBT Juno and Kepler target platforms (move into JBTIS target platform(s)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13435?page=com.atlassian.jira.plugi... ]
Denis Golovin closed JBIDE-13435.
---------------------------------
Resolution: Done
> remove uml2, zest & graphiti from JBT Juno and Kepler target platforms (move into JBTIS target platform(s)
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13435
> URL: https://issues.jboss.org/browse/JBIDE-13435
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.0.1.Final, 4.1.0.Alpha1
>
>
> {quote}
> UML2 4.0 is not in your TP, though if I recall correctly (and they haven't removed the requirement) Teiid Designer requires UML2. Should it be added to your TP? I suspect you're resolving that dependency because it's already included in the JBT target platform [5] ? If that's the case then I believe it should be removed from ours and added to yours instead.
> Graphiti 0.9 is in both your TP and the JBT one [5], yet I don't think anything in JBT requires it. It was most likely added to support something in the SOA-P/BRMS tooling space before you started having your own TP. It too should probably be removed from ours in favour of it being in yours - no need to be in both.
> {quote}
> -- [~nickboldt]
> {quote}
> You're correct about uml2 and teiid - we're currently loading that directly from our aggregate site.xml (along with zest needed by esb). I would assume those two would be better served in the base tp as well - I'll let Rob comment. {quote}
> -- [~pleacu]
--
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
13 years, 1 month