[JBoss JIRA] (JBDS-2437) Cannot deploy BPEL project
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBDS-2437?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBDS-2437:
-----------------------------------------
I installed SOA Tooling 5.0.2.GA into the new JBDS 5.0.2.CR1
> Cannot deploy BPEL project
> --------------------------
>
> Key: JBDS-2437
> URL: https://issues.jboss.org/browse/JBDS-2437
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.2.GA
> Environment: JBDS 5.0.2.CR1 H235 + SOA-P 5.3.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 5.0.2.GA
>
> Attachments: deploy_error.png
>
>
> Cannot deploy a bpel project.
--
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, 4 months
[JBoss JIRA] (JBIDE-10297) Workspace set to default even if set differently
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10297?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-10297.
---------------------------------
Resolution: Done
re-marking this as resolved since this specific issue is fixed, even if it did cause the error.
> Workspace set to default even if set differently
> ------------------------------------------------
>
> Key: JBIDE-10297
> URL: https://issues.jboss.org/browse/JBIDE-10297
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Environment: JBoss Tools 3.3.0 Nightly (2011-11-30_14-04-32-H4078)
> Mac + Ubuntu
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Attachments: jbide-10297.patch
>
>
> Before I installed JBoss Tools into Eclipse workspaces worked fine - Eclipse asks which workspace to use at start time.
> Once I installed JBoss Tools, Eclipse stopped asking me for workspace location on startup. Even if I change the workspace it falls back to default on the next start of Eclipse.
--
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, 4 months
[JBoss JIRA] (JBIDE-13322) Add JBossAS 7.x configuration schemas to eclipse xml catalog
by Samuli Saarinen (JIRA)
Samuli Saarinen created JBIDE-13322:
---------------------------------------
Summary: Add JBossAS 7.x configuration schemas to eclipse xml catalog
Key: JBIDE-13322
URL: https://issues.jboss.org/browse/JBIDE-13322
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers
Reporter: Samuli Saarinen
Assignee: Rob Stryker
JBAS7 configuration schemas could be added to Eclipse XML catalog. This way developer wanting to edit eg. standalone.xml could get auto-complete without the need to import all the schemas by hand.
--
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, 4 months
[JBoss JIRA] (JBIDE-13321) NPE from JBoss Maven tools
by Pete Muir (JIRA)
Pete Muir created JBIDE-13321:
---------------------------------
Summary: NPE from JBoss Maven tools
Key: JBIDE-13321
URL: https://issues.jboss.org/browse/JBIDE-13321
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: maven, Webservices
Environment: JBDS 6.0.0.GA
Reporter: Pete Muir
Assignee: Fred Bricon
When I load the kitchensink quickstart in JBDS, and run Update Project from the Maven menu, I get this NPE :-(
{code}
java.lang.NullPointerException
at org.jboss.tools.maven.core.ProjectUtil.refreshHierarchy(ProjectUtil.java:75)
at org.jboss.tools.maven.jaxrs.configurators.JaxrsProjectConfigurator.installJaxRsFacet(JaxrsProjectConfigurator.java:141)
at org.jboss.tools.maven.jaxrs.configurators.JaxrsProjectConfigurator.installFacets(JaxrsProjectConfigurator.java:127)
at org.jboss.tools.maven.jaxrs.configurators.JaxrsProjectConfigurator.configureInternal(JaxrsProjectConfigurator.java:117)
at org.jboss.tools.maven.jaxrs.configurators.JaxrsProjectConfigurator.configure(JaxrsProjectConfigurator.java:82)
at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:109)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:414)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:351)
at org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:74)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
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, 4 months
[JBoss JIRA] (JBIDE-13272) When using JBDS 6, authentication to a Load Balanced broker fails
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13272?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13272:
------------------------------------------
So it looks like that this was caused by some misconfiguration in the OpenShift environment:
mail from scott on the12/18/2012:
{quote}
Yes, the environment was rebuilt. Both of them. I confirmed it is
working for me now as well - on both environments.
I'm not 100% sure what was misconfigured on the brokers to keep jdbs 6
from functioning. I will continue to monitor this and let you know if
the issue crops back up.
{quote}
I close this issue for now since the bug is not occurring any longer and it looks like it was caused by the env, not by our tooling.
> When using JBDS 6, authentication to a Load Balanced broker fails
> -----------------------------------------------------------------
>
> Key: JBIDE-13272
> URL: https://issues.jboss.org/browse/JBIDE-13272
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: LATER
> Environment: 2 Red Hat Linux 6.3 Load balancer (piranha) add-on systems set up in direct routing mode with a virtual server sending traffic to two brokers (real servers). Brokers are running OpenShift Enterprise 1.0. The brokers are set up to do authentication via LDAP (Windows 2008 R2 Active Directory).
> Reporter: Scott Collier
> Assignee: Andre Dietisheim
> Attachments: ha-broker.png
>
>
> When using jbds 6, Authenticating to a load balanced broker (VIP) does not work. It worked in JBDS 5.
--
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, 4 months
[JBoss JIRA] (JBIDE-13272) When using JBDS 6, authentication to a Load Balanced broker fails
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13272?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-13272.
--------------------------------------
Resolution: Cannot Reproduce Bug
> When using JBDS 6, authentication to a Load Balanced broker fails
> -----------------------------------------------------------------
>
> Key: JBIDE-13272
> URL: https://issues.jboss.org/browse/JBIDE-13272
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: LATER
> Environment: 2 Red Hat Linux 6.3 Load balancer (piranha) add-on systems set up in direct routing mode with a virtual server sending traffic to two brokers (real servers). Brokers are running OpenShift Enterprise 1.0. The brokers are set up to do authentication via LDAP (Windows 2008 R2 Active Directory).
> Reporter: Scott Collier
> Assignee: Andre Dietisheim
> Attachments: ha-broker.png
>
>
> When using jbds 6, Authenticating to a load balanced broker (VIP) does not work. It worked in JBDS 5.
--
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, 4 months
[JBoss JIRA] (JBIDE-13266) Use pack200 to speed up download and install
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13266?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13266:
----------------------------------------
No need to spend effort in making source bundles pack200'ed since pack200 is a compression that only applies to .class files, there is no gain to apply it to sources.
> Use pack200 to speed up download and install
> --------------------------------------------
>
> Key: JBIDE-13266
> URL: https://issues.jboss.org/browse/JBIDE-13266
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng
> Affects Versions: 4.0.0.CR1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.0.1.Final, 4.1.0.Alpha1
>
>
> p2 provides the pack200 stuff, which offers a better compressions for jars, and then that makes downloads faster when installing.
> We should set up our repo to create the pack200'd artifacts.
--
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, 4 months