- This topic has 7 replies, 3 voices, and was last updated 21 years, 1 month ago by
.
-
Posts
-
I have a full J2EE application and for some reason the EJB project’s META-INF does not get deployed to JBoss, any ideas?
Erez
Ok, I got it to work, but still it seems to me that the EJB Deployer assumes that the META-INF should be UNDER some source directory and should be listed in the project properties/build path/source directories.
In my project the EJB Project src dir is a linked resource folder pointing to the real source dir tree, something like the overlapping project example in the Online Help of Eclipse, where the real source dir is shared among several projects.
My META-INF directory was really directly under the EJB Project dir, whereas the ‘src’ dir was pointing somewhere else and not physically placed under the EJB project dir. Only after creating a dummy directory named ‘metadir’ (the name doesn’t really matter) directly under the EJB project dir and placing the META-INF directory in this new directory, and adding the ‘metadir’ to the list of build path/ source directories to the project properties, only then did the EJB deployer deployed my META-INF dir.
I am not quite through with bringing my project up but I feel the whole directory schema should be reviewed as it is quite not easy to get it to work.
Hope this will help someone,
Erez
We understand the concern about a flexible project structure. We are currently reviewing several internal ideas to systematically provide more flexibility. We launched MyEclipse with the dumbed down version that mirrors the container deployment models (EAR, EJB jar, WAR). Everything else is purely arbitrary the difficulty level goes through the roof. Our strategy is what the old guys preach here at Genuitec: get it working, get it working right, make it fast, make it small, make if flexible.
I responded to a similar question on the Support Forum. I can assume that you already have it figured out if you’ve gotten this far.
One last thing to watch are those linked resources. I assume you know they can only be created at the project level which restricts their use in a number of instances where they would really help with a flexible J2EE structure.
Michael
MyEclipse SupportI have just got my project porting from JBuilder 8 Enterprise Edition to MyEclipse done and working at last…
I still have to sit and review the structure but at leat I can say that it took many small adjustments to the default generated structure & settings of MyEclipse’s J2EE project.I also agree that the use of linked resources & paths variables is inconsistent and should be put to work throught the entire Eclipse’s features. But here I cross the lines into the areas of enhancements and suggestions..
Erez
No! All help is welcome and we desparately need more user docs especially migration instructions like your experiences. We have a couple of user doc contributions that we melded into our existing docs.
Michael
MyEclipse SupportErez,
Are there any guidelines for documentation writing?
Also, once you have your docs written you can always use them to enter our Contest to win a little something back for your efforts. That’s of course in addition to the fame and adulation you’ll receive from the user community. 😉
By the way, I think the Contest entries have to be done in either HTML/javascript or Flash.
–Scott
MyEclipse Support
