I don't know the acrtual answer, but you could always try DUPLICATING your
project into a new folder and then trying convert to groovy and see what works
and what breaks ;)
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269449#4269449
Reply to the post :
h
This is / was a bug in the m4 release. It has been fixed in svn / trunk. I've
finally gotten annoyed at myself breaking the deployment code quite so often
and so I'm making it a priority this week and next to write unit tests for as
many cases as I can.
View the original post :
http://www.jbo
JIRA link: https://jira.jboss.org/jira/browse/JBIDE-5153
Since this won't be available until a new build it may take a day or two for it
to get into nightlies. As a workaround, you can do the following:
{workspace location}/.metadata/.plugins/org.eclipse.debug.core/.launches is a
folder on y
There is currently no way to do this at all. This usecase was not thought of
when writing the tools. However, luckily, I believe I can have this added very
very very quickly.
The proper place to customize your server startup (arguments etc) is to
double-click on your server to open the server e
nickboldt> need to tell user "no uninstallation required, just update using the
update site!"
;) posting for Nick Boldt
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263814#4263814
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&m
This sounds like a bad build. WTP should have a model provider for dynamic web
projects 2.5 version.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263596#4263596
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4263596
We have a bug opened on eclipse webtools / servertools to add automatic publish
on BUILD events.
I do not think they will accept the idea of automatic publishing on LAUNCH. I
don't think that fits in very well with the current options. Also it took a bit
of fighting to get WTP to add the on-bui
As for what "publish" does, some people run with the automatic publishing NOT
enabled. This means when they make changes to their workspace, they do NOT
publish the changes right away. These users love being in control of when the
publish occurs, and prefer to have the button there to do it.
W
Hmm... I'm not sure when they added 'clean' so I don't think it was there when
I 'forked', but honestly, the history of the JBoss Servers View was that it was
a Common Navigator based view. At the time of the fork, the official "Servers
View" was not common navigator based but was rather a stati
Just to chime in, what Sjnezana said is correct. The Tomcat adapter is not ours
and we cannot control any of its behaviour really. Larry Isaacs is the guy in
charge of that and you can either file a bug / feature request on eclipse
bugzilla or WTP forums / mailing lists for any suggestions you h
does this happen if you take your jar / project and deploy ti once from the
command line via file system copy? is it just a tooling error or does it also
happen always?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4255837#4255837
Reply to the post :
http:
If your re-deploy which is happening after every save is launching an ant task
or some sort of long-running process, you're not using the correct server
adapter. You're using a WTP adapter which is not enhanced for speed.
If you were using the jbosstools server adapter you wouldn't even really
I'd have to see an example project to know for sure (i'm not too familiar with
myeclipse), but I believe it probably depends mostly on the content of your
project/.settings/ folder. Specifically there should be a file in there called
org.eclipse.wst.component.xml (or similar).
I'm also not sur
This question would be better asked on the RULES forum... I doubt very much the
tooling team knows the ecccentricities of the rules engine.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4253118#4253118
Reply to the post :
http://www.jboss.org/index.html?mod
The MBean explorer view was originally a google code project which we took and
expanded on quite a bit. It has no concept of actually starting the JMX server
at all. You must start the server separately.
What the JMX server *can* do is connect to an already running mbean server if
you know how
Are you including already bundled jar files directly in your ear project or are
you setting them up as separate utility projects?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4246249#4246249
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=
Currently touching descriptor files is the best way to redeploy an exploded
deployment. Some deployment types do not require any descriptors, so there's no
clear way to redeploy that deployment without removing it and adding it again.
The workaround of course is to add a stub descriptor and touc
Yeah so um... this was my bad ;) Oops. Was a string externalization error. A
failure on my part.
https://jira.jboss.org/jira/browse/JBIDE-4507
Fixed it now tho =D
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4238450#4238450
Reply to the post :
http://
That's just listing the status as the connection gearsr up. First the server is
down, adn no JNDI connection is available. Then a connection is made, but the
JMX isn't loaded yet. Then JMX is available, but the server is not
"completely" started. And finally, the server is up.
Those are the 4
https://jira.jboss.org/jira/browse/JBIDE-4412
jira posted.
Minimal configurations do not have all those ports listed and the editor is too
strict.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234878#4234878
Reply to the post :
http://www.jboss.org/inde
That's a great idea. We alrady have a JIRA for a modules page on each server,
where the user can say which location on a per-module basis.
Should this be different? Should this be stored inside the project itself as a
custom file in the .settings folder? Benefits of doign this are if you create
Max:
The builder only gets called once when a file is changed, not twice. That one
time, I find out fileX changed. I adjust x.jar to include the newly modified
fileX. However, at no point in this call do I (the archives builder) check if
the OUTPUT file is further included in other archives.
If your server is secured and JMX is not exposed then you must use a different
poller than the JMX poller. You'll need to open the server editor and change
which poller is being used.
Also, if the server does not have JMX exposed, then the tooling can not add the
deployment location to the ser
I'd say it's more "undefined" ;) The approved method for nesting jars is making
one archive configuration where the jar is nested inside the ear straight from
the beginning. For example, your view would look like:
project1
|- ear.ear
|- filesets
|- my.jar
|- jar
When the server is first starting, typically there is no connection at all from
JNDI because the server hasn't even started JNDI yet. This is why you get the
javax.naming.CommunicationException:
A few seconds later, JNDI is bound, but JMX is not. JNDI responds to the
request, and the request r
Also:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=261306
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225512#4225512
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225512
___
Hi xmedeko.
Yes, you're correct in noticing this ;) For some reason, WTP changed it so
that server id and name are always the same now. This is, of course, a bit
problematic.
As for seeing a request for name twice, this reason was also a WTP change in
some part. They added a naming box to the
I've just tested this on 3.0.0.GA in a new workspace (with JBoss 4.2.2.GA) and
am unable to replicate. After doing a full publish, the entire app is
redeployed and the console spits out its usual 211 lines of output.
I can verify this with timestamps. After one full publish, I get the followi
Yes file a JIRA.
I'll have to patch upstream to fix it, I think, but this sounds like a pretty
good idea. I'll try to talk to Angel about it ASAP.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224533#4224533
Reply to the post :
http://www.jboss.org/index
Hi Wiggy:
It's not a bug... its a removed feature in the entire 5.x stream. They rewrote
the microkernal from a JMX kernal to the microcontainer kernal and never
exposed the ability to suspend and resume the deployment scanner.
https://jira.jboss.org/jira/browse/JBAS-6330
It's been re-added in
Hey Chris:
If you're using the WTP-type projects, I haven't investigated this specific
case yet, and can add it to my to-do list.
If on the other hand you're using regular projects and the "Project Archives"
feature, then yes. You can create your project, all your code, etc, open the
Project
Hi Wiggy:
What version of the AS are you using? If you're using 5.0.x then I regret to
inform you that those versions of the AS removed the suspend ability of the
Deployment scanner, and so the deployment scanner is reading the folder before
the entire structure is deployed.
A workaround woul
>5. the files under the project archive direct are not changed.
It's possible the project is not being refreshed... the changes have happened
but on a File api and not an eclipse IResource api and the project needs to be
f5'd before the changes are reflected.
View the original post :
http://
After re-reading this thread from scratch, I've got a few comments.
>>then if i go to jboss deploy directory and delete some class files. i can't
>>re-synchronize.
Yes... this scenerio *will not* *ever* work. The archives model is updated by
the builder, which passes in changed workspace resou
It rebuilds the archive because other users got annoyed, if they didn't have
automatic building on, that they'd have to build their project, then rebuild
the archive, then republish the archive,
It was requested that instead of this, republish should also rebuild.
And so it does.
View the or
That's quite odd. I've not seen those before. I'd been solving similar bugs in
the future stream due to changes in CommonNavigator, but even now I'm not able
to replicate this issue. I'll link it to the JIRA where I'm working on Common
Navigator related bugs, though, to make sure I don't lose t
ESB tools cannot deploy to the standard set of webtools generic server
adapters. You must also download the AS Tools plugins.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212531#4212531
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=post
There is something very wrong with your installation, because 3.0.0.CR1 no
longer has the class org.jboss.ide.eclipse.as.ui.views.server.JBossServer, or
the class org.jboss.ide.eclipse.as.ui.views.server.ServerFrame, or the class
org.jboss.ide.eclipse.as.ui.views.server.ServerTableViewer. All o
I have not yet personally looked up how to introspect a running microcontainer.
While this is a great idea, there are currently other issues that are more of a
priority. As long as the main use cases (ejb's, etc) are taken care of, this is
just a TODO for the future, sadly.
View the original
This should not be failing ;)
In fact I've never had that fail before. I'll have to test it once I get back
from holiday.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4198373#4198373
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=post
The reasons for this behavior was a bug upstream in eclipse WebTools. Details
were posted here: http://relation.to/8932.lace
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197224#4197224
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=post
It's a bug. The creation of a JBoss 5 server starts off using the .metadata
folder to build the EAR, and later tries to add this folder as a scannable
location.
It never gets added by JBoss because, unlike older JBoss versions, JBoss 5.0
does not use JMX as much.
It's obvious that whatever f
This should have been fixed by JBIDE-3368 for the record.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4196608#4196608
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4196608
Cause: Illegal character in path at index 83: file:/C:/apps/w
orkspace3.4.1/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss 4.2
Server/deploy/testseam.war/
WEB-INF/classes
...
Yes it should.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4196606#4196
JBoss 5 does not work by default on new servers. I discovered this over the
weekend. I've yet to discover a way to add a folder to the deployment scanner.
The workaround is after creating a new server, open the server in the server
editor by double-clicking the server. Then switch the deploy lo
The JBossTools server adapter for webtools does exploded deployment by default.
In fact, there's no way to make it do zipped deployment without using the
"project archives" view.
Make sure your server is of the "JBoss, a division of Red Hat" type and not
just "JBoss". The "JBoss" one is cont
Already fixed ;) I think.
[JBoss JIRA] Commented: (JBIDE-3368) In WINDOWS default metadata location
CONTAINS SPACES, no good
Committed a fix earlier today.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195191#4195191
Reply to the post :
http://www.jboss
I develop, run, and test in an x86_64 environment. The drivers you need are
over here:
http://repository.jboss.org/xulrunner/
The xpcom one is required, and the appropriate xulrunner is required.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195145#4195145
48 matches
Mail list logo
