JBoss AS Adapter Problems in development environment
by Denis Golovin
Rob, could you help me a little.
I'm faced weird problem with JBoss AS adapter in development environment.
I cannot start Server anymore. It always says
and launch configuration looks empty
Did I miss new plug-in from Server adapter?
Thanks
Denis
17 years, 2 months
seam settings in projects ?
by Max Rydahl Andersen
Hi Denis,
I saw this in the war project generated by seam:
action.package=org.domain.xam.session
eclipse.preferences.version=1
model.package=org.domain.xam.entity
seam.project.connection.profile=max
seam.project.deployment.type=war
seam.runtime.name=seam 1.2.1.AP
seam.test.project=xam-test
test.package=org.domain.xam.test
and when it's as an ear it's:
n.xyz.session
eclipse.preferences.version=1
model.package=org.domain.xyz.entity
seam.ear.project=xyz-ear
seam.ejb.project=xyz-ejb
seam.project.connection.profile=max
seam.project.deployment.type=ear
seam.runtime.name=Seam 1.2.AP
seam.test.project=xyz-test
test.package=org.domain.xyz.test
Got a cpl questions about that:
1) Where is the src destinations stored for entity/test/etc. ? is that
hardcoded ?
2) It doesn't look like the other projects have a setting for which seam
project they are related to. How do I find that out ? Is there any api
for it ?
This is mainly to have a way to based on a selection, find it's project
and then the "parent" seam project to use in default selection in e.g.
wizards.
/max
17 years, 2 months
Call for tags for JBossTools 2.0.0.beta4 / RHDS 1.0.0.beta2
by Marshall Culpepper
Hey guys,
It's that time again..
All the component leads will need to create tags under our /tags
directory for their respective components. As a refresher, make sure to
use the following format in tagging:
If your module name is "hibernate-tools", your tag should look something
like:
/tags/hibernate-tools-${RELEASE}
-- hibernate-tools/
---- plugins/
---- features/
The key is to keep your module's folder name under the tag, so, the
following would be wrong:
/tags/hibernate-tools-${RELEASE}
-- plugins/
-- features/
--
Marshall Culpepper
marshall.culpepper(a)jboss.com
JBoss Tools, Red Hat Developer Studio
17 years, 2 months
xulrunner branch/version in jira
by Max Rydahl Andersen
Hi,
I've created a 2.0.0.xulrunner version in jira so if you fix things on
that branch please use that version when resolving the issue.
If the issue is fixed in both main and xulrunner you mark both versions
when fixing/closing the jira.
Thanks,
/max
17 years, 2 months
Re: [jbosstools-dev] [Fwd: [jbosstools-commits] JBoss Tools SVN: r3757 - in trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui.view: src/org/jboss/tools/hibernate/ui/view/views and 1 other directory.]
by Max Rydahl Andersen
mdryahlenkov(a)exadel.com wrote:
>> Yes.
>> And now that I read it more thoroughly I can see your code is a bit
>> different since it scan's all hibernate console configurations to find
>> the config and possible matching project name.
>>
>> It's not pretty but the following should work:
>>
>> ((EclipseConsoleConfigurationPreferences)consoleConfiguration.getPreferences()).getProjectName();
>>
>> Isn't that what you want ? The java project associated with the console
>> configuration ? (remember that this can be null so remember check for null
>> ;
>>
>
>
> Hello, Max.
>
> Type of consoleConfiguration.getPreferences() is
> EclipseLaunchConsoleConfigurationPreferences. Can you explain me how I can
> get EclipseConsoleConfigurationPreferences object?
My typo. Use EclipseLaunchConsoleConfigurationPreferences.
17 years, 2 months
[Fwd: [jbosstools-commits] JBoss Tools SVN: r3756 - trunk/jst/plugins/org.jboss.tools.jst.web.ui/src/org/jboss/tools/jst/web/ui/action/server.]
by Max Rydahl Andersen
Hi slava,
cool this touch feature is being added.
A couple of questions though:
1) Why is both the manifest.mf and web.xml being touched for ear
deployment ? The war is inside the ear so just touching the ear should
be enough; doesn't touching both trigger risk a double-restart ?
2) We should also check that if the war is inside an ear the ear
descriptor should be touched; and if not in an ear the war descriptor
should be touched. Do we do that already ?
3) The code scans *all* project files multiple times - that can't be
very efficient for large projects.
Since these projects knows where their descriptors are why are we
scanning for them ?
4) btw. seam-gen uses this for ear's:
<target name="restart" depends="explode" description="Restart the
exploded archive">
<touch file="${ear.deploy.dir}/META-INF/application.xml"/>
</target>
Why did you choose manifest.mf for ear ?
Thanks,
/max
17 years, 2 months
Re: [jbosstools-dev] [Fwd: [jbosstools-commits] JBoss Tools SVN: r3757 - in trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui.view: src/org/jboss/tools/hibernate/ui/view/views and 1 other directory.]
by Max Rydahl Andersen
dma(a)exadel.com wrote:
> Hi Michael,
>
> Great that you are trying to fix JBIDE-611.
>
> Got some comments on that:
>
> 1) Any way that this could be done in the hibernate tools plugin instead
> of the unrelated diagram plugin ? (I don't see you are using any
> new plugins for this so should be in the core of hibernate tools imo)
>
> +++
> Yes, hibernate tools core is better place for that code but I thougth I
> can't change this plugin. If I can't use the original code of core how I
> can do it? Should I ask you to make some changes or can I do it myself?
> +++
For this thing where you are only adding an entry to plugin.xml and add
a new class you can just do it your self and i'll look at it when you
commit it.
> 3) This code looks like it is assuming everything are done in mapping
> files and with a cfg.xml file; is that correct ? What about annotated
> classes?
>
> +++
> I remember comment in jira about it. I work with this point now.
> +++
Basically it probably should just try and see if it can find the mapped
class mentioned in hibernate.cfg.xml (if that exists) and if no listing
is found there load the java file.
> 4) you have copied a large chunk of code from hibernate tools plugin to
> locate the default project; why don't you use the existing code for that ?
>
> +++
> You speak about code
>
> ILaunchManager launchManager =
> DebugPlugin.getDefault().getLaunchManager();
> ILaunchConfigurationType launchConfigurationType =
> launchManager.getLaunchConfigurationType(
> "org.hibernate.eclipse.launch.ConsoleConfigurationLaunchConfigurationType" );
> ILaunchConfiguration[] launchConfigurations;
> try {
> launchConfigurations = launchManager.getLaunchConfigurations(
> launchConfigurationType );
> for (int i = 0; i < launchConfigurations.length; i++) { // can't
> believe there is no look up by name API
> ILaunchConfiguration launchConfiguration = launchConfigurations[i];
> if(launchConfiguration.getName().equals(consoleConfiguration.getName()))
> {
> proj =
> ProjectUtils.findJavaProject(launchConfiguration.getAttribute(IConsoleConfigurationLaunchConstants.PROJECT_NAME,
> ""));
> }
> }
> } catch (CoreException e1) {
> ViewPlugin.getDefault().logError("Can't find java project.", e1);
> }
>
> in OpenMappingActionDelegate class. Is that correct?
> +++
Yes.
And now that I read it more thoroughly I can see your code is a bit
different since it scan's all hibernate console configurations to find
the config and possible matching project name.
It's not pretty but the following should work:
((EclipseConsoleConfigurationPreferences)consoleConfiguration.getPreferences()).getProjectName();
Isn't that what you want ? The java project associated with the console
configuration ? (remember that this can be null so remember check for null ;
/max
17 years, 2 months
Re: [jbosstools-dev] [Fwd: [jbosstools-commits] JBoss Tools SVN: r3757 - in trunk/hibernatetools/plugins/org.jboss.tools.hibernate.ui.view: src/org/jboss/tools/hibernate/ui/view/views and 1 other directory.]
by mdryahlenkov＠exadel.com
Hi Michael,
Great that you are trying to fix JBIDE-611.
Got some comments on that:
1) Any way that this could be done in the hibernate tools plugin instead
of the unrelated diagram plugin ? (I don't see you are using any
new plugins for this so should be in the core of hibernate tools imo)
+++
Yes, hibernate tools core is better place for that code but I thougth I
can't change this plugin. If I can't use the original code of core how I
can do it? Should I ask you to make some changes or can I do it myself?
+++
2) Please don't use bogus id's in our plugin.xml like: com.xyz.runXYZ, it
should be something stable and resembling the other id's.
+++
Fixed.
+++
3) This code looks like it is assuming everything are done in mapping
files and with a cfg.xml file; is that correct ? What about annotated
classes?
+++
I remember comment in jira about it. I work with this point now.
+++
4) you have copied a large chunk of code from hibernate tools plugin to
locate the default project; why don't you use the existing code for that ?
+++
You speak about code
ILaunchManager launchManager =
DebugPlugin.getDefault().getLaunchManager();
ILaunchConfigurationType launchConfigurationType =
launchManager.getLaunchConfigurationType(
"org.hibernate.eclipse.launch.ConsoleConfigurationLaunchConfigurationType" );
ILaunchConfiguration[] launchConfigurations;
try {
launchConfigurations = launchManager.getLaunchConfigurations(
launchConfigurationType );
for (int i = 0; i < launchConfigurations.length; i++) { // can't
believe there is no look up by name API
ILaunchConfiguration launchConfiguration = launchConfigurations[i];
if(launchConfiguration.getName().equals(consoleConfiguration.getName())) {
proj =
ProjectUtils.findJavaProject(launchConfiguration.getAttribute(IConsoleConfigurationLaunchConstants.PROJECT_NAME,
""));
}
}
} catch (CoreException e1) {
ViewPlugin.getDefault().logError("Can't find java project.", e1);
}
in OpenMappingActionDelegate class. Is that correct?
+++
/max
17 years, 2 months
