Yeah, it's WTP. I'm using LCDS - the original project was generated using the Flex Builder (plugin) "new project wizard". I would guess similar, and yea I think Eclipse is trying to be a little too fancy and automagic. I agree getting this setup to work properly is a better dev environment, if it works!
I'm not using Ant now (well we do at work, but that's a whole different Flex project) and I don't have any "production environments" -- hehe. This is just a little at-home project for fun (at least it's supposed to be!) That's why I don't want to overkill my env setup. Oh, here's a little something new I've discovered: If I ignore the error and startup the client anyway, it appears that my messaging service connects fine, but a remoting call blows up. So I'm a little suspect that LCDS has something to do with this... I do have a bootstrap service starting up successfully according to my logs, so it's "partially working". --- In flexcoders@yahoogroups.com, "twcrone70" <[EMAIL PROTECTED]> wrote: > > I'm guessing you are using the Web Tools Platform in Eclipse for this... > > Are you using data services from LCDS, Granite or something else? I'm > going to guess tomcat isn't really the issue. Rather eclipse's > attempt at making things "easier" is messing things up. > > If you are making changes to Java code and Flex code around the same > time, getting it to work with WTP is still probably easiest so > wrestling with it will be advantageous for quick development. > > You should probably still use Ant or Maven for your test/production > builds. And if you are making more frequent changes to the Flex- side > and the Java services don't change as much you might build with Ant, > deploy to tomcat, start tomcat and then have eclipse saving your Flex > changes to the 'public' webapps directory of your tomcat deployment. > > That way you could make quick changes to your SWF app and let your > tomcat deployment remain running and keep eclipse out of the server > deployment/management mix. You could also set the base URL in your > Flex project properties to point to the root URI of your tomcat webapp > so selecting 'Run' for the Flex stuff in eclipse will automatically > run it via your browser served up by tomcat. > > Unfortunately, I don't have a quick answer to the tomcat/eclipse issue > although I'll ask around. > > - Todd > > > --- In flexcoders@yahoogroups.com, "ansury2001" <ansury@> wrote: > > > > > > Awesome. Eclipse re-install does nothing to fix this. Giving up, > > switching to Silverlight. (LOL yea right!) > > > > WTH? Could I have borked up something project configuration wise that > > would create this kind of error? The error output is not very helpful. > > > > I really don't feel like wasting another day re-setting up my entire > > project and dev environment from scratch. Maybe I should just use an > > ant build file to deploy like a normal person... > > > > Arg what the heck IS this... I'm in Java hell.. everything is > > starting to look like Ajax and JSP.. > > > > > > Sep 15, 2008 1:07:49 AM org.apache.tomcat.util.net.NioEndpoint > > setSocketOptions > > SEVERE: > > java.lang.NullPointerException > > at org.apache.tomcat.util.net.NioEndpoint.setSocketOptions > > (NioEndpoint.java:1011) > > at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run > > (NioEndpoint.java:1204) > > at java.lang.Thread.run(Unknown Source) > > Sep 15, 2008 1:07:49 AM org.apache.coyote.http11.Http11NioProtocol > > start > > > > > > --- In flexcoders@yahoogroups.com, "ansury2" <ansury2@> wrote: > > > > > > > > > >> just ignore that, it does not shutdown sometimes, a little red > > button > > > in > > > > > eclipse does force it. > > > > > > Heh - here's the kicker - I *was* using the red kill button. It > > > actually wasn't working! Crazy huh? I figured maybe it was killed > > > already but Eclipse didn't know. And I'm pretty sure it was when I > > was > > > trying to kill it that way when it was giving me a goofy "timeout > > > shutting down server" dialog. I've never seen that before... and > > I've > > > been using Eclipse for years. (Although not this "Servers view" > > > function.) > > > > > > >> this is the way eclipse works, you might not want to deploy to > > your > > > > > actual web server, even when developing plugins eclipse works > > like > > > this. > > > > > this allows you to use separate config files for your > > development > > > and your > > > > > local webserver as well. > > > > > > Yeah, I still think it's flexibility overkill. I have a 'server' > > > deployed on my local machine (that's my "dev server") - I wish it > > would > > > just use that install so I could see what it's doing. The way it > > works > > > now, I'm not even 100% sure what config files it's using. It's too > > > "magical" IMO... no sense fighting that though. > > > > > > >>well if you downloaded wtp, just dump that eclipse and extract it > > > again, > > > > > you keep your workspace and it should just work. When i get > > "arb" > > > stuff i > > > > > delete my servers in eclipse and just create them again. > > > > > > > > > I think I downloaded an EE version of Eclipse which had it pre- > > packaged. > > > I've tried re-creating the server in Eclipse but I still get the > > same > > > error. :( > > > > > > >> did you enable a firewall at some point. your error looks like > > > > > the debugger is unable to open a socket to the instance tomcat. > > > > > > I wish it were that simple. I didn't touch any firewall - and it > > gives > > > the same error when running without attaching the debugger. Boo! > > > > > > Thanks for the input - I will probably try and re-setup Eclipse. > > > > > > > > > --- In flexcoders@yahoogroups.com, "Johannes Nel" <johannes.nel@> > > > wrote: > > > > > > > > inline. > > > > > > > > On Sun, Sep 14, 2008 at 8:33 AM, ansury2 ansury2@ wrote: > > > > > > > > > I'm having one of those infamous "IT WTH?!" moments. You > > know, the > > > > > kind where "you have no idea what you did to break it"? I have > > no > > > > > idea what I did to break this apparently fragile as hell project > > > > > setup. > > > > > > > > > > I'm using Eclipse's "Servers view" functionality to startup > > Tomcat. > > > > > Everything worked fine for say two months until suddenly I found > > > that > > > > > I was unable to shutdown Tomcrap. No idea why, maybe I started/ > > > > > stopped too quick or something, but when I tried to shut it > > down, > > > > > Eclipse just sat there for awhile and it timed out: "unable to > > > > > shutdown server" or whatever rubbish. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> just ignore that, it does not shutdown sometimes, a little > > red > > > button in > > > > > eclipse does force it. > > > > > > > > > > Eclipse restart didn't help, I think at that point I was getting > > > > > this error message (instead of a timeout). So I figured I'd > > reboot - > > > > > still NO good. Still getting this stupid error message. Uhoh. I > > have > > > > > to think about this? @#$%! > > > > > > > > > > Apparently I made a mistake trusting this "magic" setup to work > > > > > without fully understanding HOW it works. (The Eclipse docs are > > > > > worthless for understanding what it's doing.) Instead of > > deploying > > > > > the application to Tomcat's webapps directory in it's normal > > > > > installed location, how a normal person would design this > > feature, > > > it > > > > > deploys everything into some bizzare folder in your workspace > > > > > metadata and somehow it just works. (\EclipseWS\.metadata > > \.plugins > > > > > \org.eclipse.wst.server.core\tmp0\wtpwebapps) (HUH? WTH? Why?) > > > > > > > > > > > > > > > > > > >> this is the way eclipse works, you might not want to deploy > > to > > > your > > > > > actual web server, even when developing plugins eclipse works > > like > > > this. > > > > > this allows you to use separate config files for your > > development > > > and your > > > > > local webserver as well. > > > > > > > > > > > > > > > > > > > > > > > Sorry for sounding pissed, but I am - I've wasted basically two > > days > > > > > on this trash with no idea where to go from here. Do I re- > > install > > > > > Tomcat? Eclipse? Setup my workspace again? Why should I have to > > do > > > > > all that? This is the kind of stuff in IT that makes you want > > to say > > > > > "screw it all" and just go into management so the other poor > > suckers > > > > > have to lose their hair doing stuff like this! lol > > > > > > > > > > > > > > > > > > >>well if you downloaded wtp, just dump that eclipse and > > extract it > > > again, > > > > > you keep your workspace and it should just work. When i get > > "arb" > > > stuff i > > > > > delete my servers in eclipse and just create them again. > > > > > > > > > > I doubt anyone can help with this bizzare problem (it's probably > > > more > > > > > of an Eclipse issue but it only spews this error when I deploy > > my > > > > > Flex project!) but here's the console output. Note the > > > > > NullPointerException within NioEndpoint: > > > > > > > > > > >> did you enable a firewall at some point. your error looks > > like > > > > > the debugger is unable to open a socket to the instance tomcat. > > > > > > > > > > > > > > >
