Using: MyEclipse 2.5.1, WebLogic 7, Eclipse running under JDK 1.4.1

When we try to deploy our project to WebLogic (as an exploded directory), we notice that properties files in our EJB project haven't been deployed. Is this a known problem?

Thanks,
BC

Are the property files located under a src folder? MyEclipse only deploys EJB Project elements that reside under a src folder.

Michael
MyEclipse Support

support wrote:

Are the property files located under a src folder? MyEclipse only deploys EJB Project elements that reside under a src folder.

Yes. Here's my structure

myapplicationEJB


  + src


      + com.acme.myapplication.ejb.something


          + SomeNonEJBClass.java


          + ...


          + interesting.properties


       + ...


  + src-gen


       + ...

(It probably isn't relevant, but I have multiple source folders).

When I deploy to WebLogic, the interesting.properties file doesn't copy.

We've seen this problem on two different machines.

Thanks,
BC

Can you inspect the .project file for the following build spec?

Code:

<buildCommand> <name>com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder</name> <arguments> </arguments> </buildCommand>

There have been a few cases where this builder has not been properly registered with the project. The 2.6.2 release that rolled out yesterday provides additional checks for this rare case.

Michael
MyEclipse Support

Another check is the "Filtered Resources" preference at Windows->Preferences->Java->Compiler->Build Path (tab). While it is a rare occurence some developers have added additional filters.

Michael
MyEclipse Support

support wrote:

Code: <buildCommand> <name>com.genuitec.eclipse.ast.deploy.core.DeploymentBuilder</name> <arguments> </arguments> </buildCommand>

Yup, I've got that. the project file also has DeploymentDescriptorValidator .

BC

support wrote:

Another check is the "Filtered Resources" preference at Windows->Preferences->Java->Compiler->Build Path (tab). While it is a rare occurence some developers have added additional filters.

No, I just have *.launch, there.

Curiously, though, I've just re-tried this and the problem has disappeared.

Weird.

(It occurs to me that I *might* have been thrown off by the ordering of the files... Eclipse always puts .properties files after the Java classes, and I might have been pattern-matching incorrectly. I've also gone to the other person who had this problem, and he's not having it either. Hmmm.)

Please let us know if you experience any other problems. We continue to mature the deployment infrastructure and your issues and feedback are very important to us.

Regards,

Michael
MyEclipse Support