Hi, I fear, that there will be no definite answer to your question without an actual reproducer project.
Gruß Richard > Am 15.11.2024 um 20:00 schrieb Niranjan Rao <n...@paymentus.com>: > > Greetings, > > This is most likely operator or configuration error. I'm trying to deploy a > legacy EJB application that currently gets deployed on older version of jboss. > > > I downloaded apache-tomee-plume-9.1.3 and tried deploying the EAR files. > First encountered javax/jakarta issue but tomcat migration tool handled that > nicely. Next issue was JNDI name lookup. With little code change such as > changing the names, it seems like it's loading expected beans/components > correctly. > > I'm still get an error resource not found. Tried enabling the logs at FINE > level and this is what I get in the log files. Just pasting relevant lines. > > I'm not clear if it's just complaining about this error and other beans are > loaded or giving up upon first error encountered. InternalAPIBean does > implement given InternalAPILocal interface. > > > 15-Nov-2024 10:08:48.367 INFO [main] > org.apache.openejb.config.InitEjbDeployments.deploy Auto-deploying ejb > InternalAPIBean: EjbDeployment(deployment-id=InternalAPIBean) > 15-Nov-2024 10:08:48.378 FINE [main] > org.apache.openejb.config.AutoConfig.deploy Bean type of bean InternalAPIBean > is STATELESS > 15-Nov-2024 10:08:48.378 FINE [main] > org.apache.openejb.config.AutoConfig.deploy Container for bean > InternalAPIBean is not set, looking for a suitable container > 15-Nov-2024 10:08:48.378 FINE [main] > org.apache.openejb.config.AutoConfig.getUsableContainer Searching for usable > container for bean: InternalAPIBean. Available application containers: , > available system containers Default Stateless Container, Default Singleton > Container > 15-Nov-2024 10:08:48.378 FINE [main] > org.apache.openejb.config.AutoConfig.getUsableContainer Attempting to find a > matching container for bean: InternalAPIBean from application containers > 15-Nov-2024 10:08:48.379 FINE [main] > org.apache.openejb.config.AutoConfig.getUsableContainer Matching application > container not found. Attempting to find a matching container for bean: > InternalAPIBean from system containers > 15-Nov-2024 10:08:48.379 FINE [main] > org.apache.openejb.config.AutoConfig.matchContainer Container Default > Stateless Container matches container type > org.apache.openejb.assembler.classic.StatelessSessionContainerInfo for bean > InternalAPIBean, this container will be used. > 15-Nov-2024 10:08:48.379 FINE [main] > org.apache.openejb.config.AutoConfig.getUsableContainer Using container > Default Stateless Container for bean InternalAPIBean > 15-Nov-2024 10:08:48.379 FINE [main] > org.apache.openejb.config.AutoConfig.deploy Setting container ID Default > Stateless Container for bean InternalAPIBean > 15-Nov-2024 10:08:48.379 FINE [main] > org.apache.openejb.config.AutoConfig.deploy Container ID for bean > InternalAPIBean is Default Stateless Container > 15-Nov-2024 10:08:48.407 FINE [main] > org.apache.openejb.config.AutoConfig.getResourceId No existing resource found > while attempting to Auto-link unmapped resource-ref 'InternalAPIBean' of type > 'com.pp.core.services.InternalAPILocal' for 'pp-ws.Comp1951901544'. Looked > for Resource(id=InternalAPIBean) and Resource(id=InternalAPIBean)15-Nov-2024 > 10:08:48.409 WARNING [main] > org.apache.openejb.config.ConfigurationFactory.configureApplication Jar not > loaded. <path>/tomee/apache-tomee-plume-9.1.3/apps/pp.ear. Can't find > resource for class com.pp.ws.internal.ServicePortTypeImpl#service. (No > provider available for resource-ref 'null' of type > 'com.pp.core.services.InternalAPILocal' for 'pp-ws.Comp1951901544'.) > > What should I do to resolve these errors. > > Thank you. > -- >
