- Dieses Thema hat 7 Antworten und 2 Stimmen, und wurde zuletzt aktualisiert vor 1 Jahr von
.
-
Beiträge
-
Hallo an alle, ich beobachte die Entwicklung von dieser Software schon länger, entschloss mich, sie auszuprobieren erst vor wenigen Tagen. Leider kriege ich die Server-Software nach der Installationsanleitung nur zur Hälfte gestärtet. Anmeldung mit dem Client ist danach nicht möglich, vobei die Stratseite des WeilFly-Servers im Browser angezeigt wird. Die Log-Datei füge ich bei.
Die Installation wurde auf einem vor ca. einem Monat frisch installiertem Debian-Sever, Release „Bullseye“. Openjdk version „17.0.6“ 2023-01-17. Auf dem Server wird ein Apache-Server betrieben, der den Port 8080 schon belegt, sodass ich vor dem Starten des Dienstes die Änderung in \wildfly\standalone\configuration\standalone.xml: <socket-binding-group name=“standard-sockets“ default-interface=“public“ port-offset=“${jboss.socket.binding.port-offset:100}“> vorgenommen habe. Wir setzten darüber hinaus rege SSH auf dem Port 22 ein und benutzten die Linux-Firewall GUFW. Unter umständen ist noch etwas zu konfigrieren, vor der ersten inbetriebnahme. Aber ich werde leider aus der Installationasanleitung nicht schlau was. Kann mir evtl. jemand einen Tipp geben?
Grüße
LOG-Datei:
sudo -u j-lawyer-server sh start-server.sh
=========================================================================JBoss Bootstrap Environment
JBOSS_HOME: /opt/j-lawyer-server/wildfly
JAVA: java
JAVA_OPTS: -server -Xms256m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=384m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dlog4j2.formatMsgNoLookups=true –add-exports=java.base/sun.nio.ch=ALL-UNNAMED –add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED –add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED –add-modules=java.se
=========================================================================
09:30:20,727 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.0.Final
09:30:21,208 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.5.Final
09:30:21,216 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
09:30:21,310 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) starting
09:30:21,825 INFO [org.wildfly.security] (ServerService Thread Pool — 26) ELY00001: WildFly Elytron version 1.8.0.Final
09:30:22,248 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute ’security-realm‘ in the resource at address ‚/core-service=management/management-interface=http-interface‘ is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
09:30:22,276 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool — 11) WFLYCTL0028: Attribute ’security-realm‘ in the resource at address ‚/subsystem=undertow/server=default-server/https-listener=https‘ is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
09:30:22,277 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 5) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
09:30:22,671 INFO [org.jboss.as.repository] (ServerService Thread Pool — 8) WFLYDR0001: Content added at location /opt/j-lawyer-server/wildfly/standalone/data/content/45/caf294363b7fa53e14c118e91f2f6da974ada6/content
09:30:22,781 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
09:30:22,799 INFO [org.xnio] (MSC service thread 1-7) XNIO version 3.6.5.Final
09:30:22,804 INFO [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.6.5.Final
09:30:22,845 WARN [org.jboss.as.logging] (Controller Boot Thread) WFLYLOG0012: Replacing handler ‚FILE‘ during add operation. Either the handler type or the module name differs from the initial configuration.
09:30:22,858 INFO [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool — 59) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
09:30:22,858 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 49) WFLYCLINF0001: Activating Infinispan subsystem.
09:30:22,858 WARN [org.jboss.as.txn] (ServerService Thread Pool — 70) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
09:30:22,862 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool — 61) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
09:30:22,868 INFO [org.jboss.as.naming] (ServerService Thread Pool — 62) WFLYNAM0001: Activating Naming Subsystem
09:30:22,868 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool — 51) WFLYRS0016: RESTEasy version 3.6.3.Final
09:30:22,870 INFO [org.jboss.as.security] (ServerService Thread Pool — 68) WFLYSEC0002: Activating Security Subsystem
09:30:22,871 INFO [org.jboss.as.webservices] (ServerService Thread Pool — 72) WFLYWS0002: Activating WebServices Extension
09:30:22,872 INFO [org.jboss.as.jsf] (ServerService Thread Pool — 56) WFLYJSF0007: Activated the following JSF Implementations: [main]
09:30:22,873 INFO [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool — 60) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
09:30:22,889 INFO [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Current PicketBox version=5.0.3.Final
09:30:22,890 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
09:30:22,891 INFO [org.wildfly.extension.io] (ServerService Thread Pool — 50) WFLYIO001: Worker ‚default‘ has auto-configured to 32 core threads with 256 task threads based on your 16 available processors
09:30:22,891 INFO [org.jboss.as.connector] (MSC service thread 1-5) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.12.Final)
09:30:22,931 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Undertow 2.0.19.Final starting
09:30:22,941 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 42) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
09:30:22,948 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = h2
09:30:22,948 INFO [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Starting Naming Service
09:30:22,949 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
09:30:22,982 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 42) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 8.0)
09:30:22,983 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = mysql
09:30:22,994 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 5.0.8.Final
09:30:23,008 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
09:30:23,014 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0010: Unbound data source [java:/jlawyerdb]
09:30:23,030 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 64 (per class), which is derived from the number of CPUs on this host.
09:30:23,031 INFO [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 256 (per class), which is derived from thread worker pool sizing.
09:30:23,044 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool — 71) WFLYUT0014: Creating file handler for path ‚/opt/j-lawyer-server/wildfly/welcome-content‘ with options [directory-listing: ‚false‘, follow-symlink: ‚false‘, case-sensitive: ‚true‘, safe-symlink-paths: ‚[]‘]
09:30:23,049 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server.
09:30:23,051 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
09:30:23,139 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8180
09:30:23,179 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0493: EJB subsystem suspension complete
09:30:23,220 INFO [org.jboss.as.patching] (MSC service thread 1-7) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
09:30:23,224 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:/jlawyerdb]
09:30:23,226 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
09:30:23,242 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-6) WFLYDM0111: Keystore /opt/j-lawyer-server/wildfly/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
09:30:23,250 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/j-lawyer-server/wildfly/standalone/deployments
09:30:23,262 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of „j-lawyer-server.ear“ (runtime-name: „j-lawyer-server.ear“)
09:30:23,293 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/opt/j-lawyer-server/wildfly/standalone/data/activemq/journal,bindingsDirectory=/opt/j-lawyer-server/wildfly/standalone/data/activemq/bindings,largeMessagesDirectory=/opt/j-lawyer-server/wildfly/standalone/data/activemq/largemessages,pagingDirectory=/opt/j-lawyer-server/wildfly/standalone/data/activemq/paging)
09:30:23,318 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221012: Using AIO Journal
09:30:23,331 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8543
09:30:23,365 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
09:30:23,366 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
09:30:23,366 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
09:30:23,366 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
09:30:23,386 INFO [org.jboss.ws.common.management] (MSC service thread 1-7) JBWS022052: Starting JBossWS 5.2.4.Final (Apache CXF 3.2.7)
09:30:23,411 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221034: Waiting indefinitely to obtain live lock
09:30:23,411 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221035: Live Server Obtained live lock
09:30:23,526 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
09:30:23,526 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
09:30:23,526 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
09:30:23,526 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
09:30:23,623 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221007: Server is now live
09:30:23,624 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.6.3.jbossorg-00014 [default, nodeID=37b34b09-da96-11ed-a3e5-0242821fc28c]
09:30:23,632 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 74) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
09:30:23,673 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:/JmsXA
09:30:23,675 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-7) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA]
09:30:23,675 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0119: Unbinding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
09:30:23,676 WARN [org.apache.activemq.artemis.jms.server] (ServerService Thread Pool — 76) AMQ122005: Invalid „host“ value „0.0.0.0“ detected for „http-connector“ connector. Switching to „recht-hr-server“. If this new address is incorrect please manually configure the connector to use the proper one.
09:30:23,677 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 76) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
09:30:23,731 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-3) AMQ151007: Resource adaptor started
09:30:23,731 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatoractivemq-ra
09:30:23,732 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-7) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
09:30:23,732 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
09:30:28,452 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib\jcifs-1.3.18.jar in /content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
09:30:28,452 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib\jsch-0.1.54.jar in /content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
09:30:28,452 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib\commons-vfs2-2.1.jar in /content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
09:30:28,452 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib\commons-net-3.5.jar in /content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
09:30:28,455 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/ws-commons-util-1.0.2.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
09:30:28,455 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/json-simple-2.3.0.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
09:30:28,455 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/log4j-over-slf4j-1.7.30.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
09:30:28,456 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/slf4j-api-1.7.30.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
09:30:28,456 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/jboss-jaxrs-api_2.1_spec-1.0.2.Final.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
09:30:28,456 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/log4j-api-2.17.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
09:30:28,456 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/log4j-core-2.17.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
09:30:28,456 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/log4j-slf4j-impl-2.17.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
09:30:28,461 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry jena-iri-0.9.1.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
09:30:28,461 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry slf4j-api-1.5.6.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
09:30:28,461 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry log4j-1.2.16.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
09:30:28,461 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry java-rdfa-htmlparser-0.4.2-RC2.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
09:30:28,462 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry htmlparser-1.2.1.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
09:30:28,463 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/j-lawyer-server.ear/lib/jaxb-core-2.3.0.1.jar does not point to a valid jar for a Class-Path reference.
09:30:28,465 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/FastInfoset.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,465 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/gmbal-api-only.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,465 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/ha-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,465 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/javax.mail_1.4.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,465 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/jaxws-rt.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,465 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/jaxws-tools.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,465 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/management-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,465 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/mimepull.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,466 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/policy.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,466 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/saaj-impl.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,466 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/stax-ex.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,466 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/stax2-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,466 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/streambuffer.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,466 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/woodstox-core-asl.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,466 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/jaxws-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,466 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/jsr181-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,466 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/javax.annotation.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,466 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/saaj-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,467 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/activation.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,467 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/jaxb-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,467 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/hamcrest-core-1.3.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,467 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry lib/org-netbeans-modules-java-j2seproject-copylibstask.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
09:30:28,472 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry jaxb-runtime-2.3.2.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
09:30:28,472 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry txw2-2.3.2.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
09:30:28,473 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry istack-commons-runtime-3.0.8.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
09:30:28,473 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry stax-ex-1.8.1.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
09:30:28,473 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry FastInfoset-1.2.16.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
09:30:28,473 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry jakarta.activation-api-1.2.1.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
09:30:28,484 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-io.war“)
09:30:28,484 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-war.war“)
09:30:28,484 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-io.war“)
09:30:28,484 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-entities.jar“)
09:30:28,484 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-ejb.jar“)
09:30:28,487 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/jollyday-0.4.7.jar in /content/j-lawyer-server.ear/j-lawyer-server-ejb.jar does not point to a valid jar for a Class-Path reference.
09:30:28,487 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/tika-app-1.5.jar in /content/j-lawyer-server.ear/j-lawyer-server-ejb.jar does not point to a valid jar for a Class-Path reference.
09:30:28,638 INFO [org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Read persistence.xml for j-lawyer-server-ejbPU
09:30:28,662 INFO [org.jboss.as.jpa] (MSC service thread 1-3) WFLYJPA0002: Read persistence.xml for j-lawyer-server-ejbPU
09:30:28,980 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 76) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU‘
09:30:28,982 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 75) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
09:30:28,990 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment j-lawyer-server.ear
09:30:28,996 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool — 75) HHH000204: Processing PersistenceUnitInfo [
name: j-lawyer-server-ejbPU
…]
09:30:28,996 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool — 76) HHH000204: Processing PersistenceUnitInfo [
name: j-lawyer-server-ejbPU
…]
09:30:29,064 INFO [org.hibernate.Version] (ServerService Thread Pool — 75) HHH000412: Hibernate Core {5.3.9.Final}
09:30:29,065 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool — 75) HHH000206: hibernate.properties not found
09:30:29,137 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-7) HV000001: Hibernate Validator 6.0.15.Final
09:30:29,149 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool — 75) HCANN000001: Hibernate Commons Annotations {5.0.5.Final}
09:30:29,263 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment j-lawyer-server-io.war
09:30:29,267 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment j-lawyer-server-war.war
09:30:29,314 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment j-lawyer-server-entities.jar
09:30:29,316 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚PersistenceLifecycleBean‘ in deployment unit ’subdeployment „j-lawyer-server-entities.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:java:global/j-lawyer-server/j-lawyer-server-entities/PersistenceLifecycleBean!org.jlawyer.persistence.PersistenceLifecycleBeanLocal
java:app/j-lawyer-server-entities/PersistenceLifecycleBean!org.jlawyer.persistence.PersistenceLifecycleBeanLocal
java:module/PersistenceLifecycleBean!org.jlawyer.persistence.PersistenceLifecycleBeanLocal
ejb:j-lawyer-server/j-lawyer-server-entities/PersistenceLifecycleBean!org.jlawyer.persistence.PersistenceLifecycleBeanLocal
java:global/j-lawyer-server/j-lawyer-server-entities/PersistenceLifecycleBean
java:app/j-lawyer-server-entities/PersistenceLifecycleBean
java:module/PersistenceLifecycleBean09:30:29,361 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment j-lawyer-io.war
09:30:29,364 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named ‚TemplatesEndpointV6‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:java:global/j-lawyer-server/j-lawyer-io/TemplatesEndpointV6!org.jlawyer.io.rest.v6.TemplatesEndpointLocalV6
java:app/j-lawyer-io/TemplatesEndpointV6!org.jlawyer.io.rest.v6.TemplatesEndpointLocalV6
java:module/TemplatesEndpointV6!org.jlawyer.io.rest.v6.TemplatesEndpointLocalV6
ejb:j-lawyer-server/j-lawyer-io/TemplatesEndpointV6!org.jlawyer.io.rest.v6.TemplatesEndpointLocalV6
java:global/j-lawyer-server/j-lawyer-io/TemplatesEndpointV6
java:app/j-lawyer-io/TemplatesEndpointV6
java:module/TemplatesEndpointV609:30:29,364 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named ‚ContactsEndpointV5‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV5!org.jlawyer.io.rest.v5.ContactsEndpointLocalV5
java:app/j-lawyer-io/ContactsEndpointV5!org.jlawyer.io.rest.v5.ContactsEndpointLocalV5
java:module/ContactsEndpointV5!org.jlawyer.io.rest.v5.ContactsEndpointLocalV5
ejb:j-lawyer-server/j-lawyer-io/ContactsEndpointV5!org.jlawyer.io.rest.v5.ContactsEndpointLocalV5
java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV5
java:app/j-lawyer-io/ContactsEndpointV5
java:module/ContactsEndpointV509:30:29,364 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named ‚CalendarEndpointV4‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/CalendarEndpointV4!org.jlawyer.io.rest.v4.CalendarEndpointLocalV4
java:app/j-lawyer-io/CalendarEndpointV4!org.jlawyer.io.rest.v4.CalendarEndpointLocalV4
java:module/CalendarEndpointV4!org.jlawyer.io.rest.v4.CalendarEndpointLocalV4
ejb:j-lawyer-server/j-lawyer-io/CalendarEndpointV4!org.jlawyer.io.rest.v4.CalendarEndpointLocalV4
java:global/j-lawyer-server/j-lawyer-io/CalendarEndpointV4
java:app/j-lawyer-io/CalendarEndpointV4
java:module/CalendarEndpointV409:30:29,364 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named ‚ContactsEndpointV2‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV2!org.jlawyer.io.rest.v2.ContactsEndpointLocalV2
java:app/j-lawyer-io/ContactsEndpointV2!org.jlawyer.io.rest.v2.ContactsEndpointLocalV2
java:module/ContactsEndpointV2!org.jlawyer.io.rest.v2.ContactsEndpointLocalV2
ejb:j-lawyer-server/j-lawyer-io/ContactsEndpointV2!org.jlawyer.io.rest.v2.ContactsEndpointLocalV2
java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV2
java:app/j-lawyer-io/ContactsEndpointV2
java:module/ContactsEndpointV209:30:29,364 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named ‚ContactsEndpointV1‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV1!org.jlawyer.io.rest.v1.ContactsEndpointLocalV1
java:app/j-lawyer-io/ContactsEndpointV1!org.jlawyer.io.rest.v1.ContactsEndpointLocalV1
java:module/ContactsEndpointV1!org.jlawyer.io.rest.v1.ContactsEndpointLocalV1
ejb:j-lawyer-server/j-lawyer-io/ContactsEndpointV1!org.jlawyer.io.rest.v1.ContactsEndpointLocalV1
java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV1
java:app/j-lawyer-io/ContactsEndpointV1
java:module/ContactsEndpointV109:30:29,365 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named ‚DataBucketEndpointV6‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/DataBucketEndpointV6!org.jlawyer.io.rest.v6.DataBucketEndpointLocalV6
java:app/j-lawyer-io/DataBucketEndpointV6!org.jlawyer.io.rest.v6.DataBucketEndpointLocalV6
java:module/DataBucketEndpointV6!org.jlawyer.io.rest.v6.DataBucketEndpointLocalV6
ejb:j-lawyer-server/j-lawyer-io/DataBucketEndpointV6!org.jlawyer.io.rest.v6.DataBucketEndpointLocalV6
java:global/j-lawyer-server/j-lawyer-io/DataBucketEndpointV6
java:app/j-lawyer-io/DataBucketEndpointV6
java:module/DataBucketEndpointV609:30:29,365 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named ‚SecurityEndpointV1‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/SecurityEndpointV1!org.jlawyer.io.rest.v1.SecurityEndpointLocalV1
java:app/j-lawyer-io/SecurityEndpointV1!org.jlawyer.io.rest.v1.SecurityEndpointLocalV1
java:module/SecurityEndpointV1!org.jlawyer.io.rest.v1.SecurityEndpointLocalV1
ejb:j-lawyer-server/j-lawyer-io/SecurityEndpointV1!org.jlawyer.io.rest.v1.SecurityEndpointLocalV1
java:global/j-lawyer-server/j-lawyer-io/SecurityEndpointV1
java:app/j-lawyer-io/SecurityEndpointV1
java:module/SecurityEndpointV109:30:29,365 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV6‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV6!org.jlawyer.io.rest.v6.CasesEndpointLocalV6
java:app/j-lawyer-io/CasesEndpointV6!org.jlawyer.io.rest.v6.CasesEndpointLocalV6
java:module/CasesEndpointV6!org.jlawyer.io.rest.v6.CasesEndpointLocalV6
ejb:j-lawyer-server/j-lawyer-io/CasesEndpointV6!org.jlawyer.io.rest.v6.CasesEndpointLocalV6
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV6
java:app/j-lawyer-io/CasesEndpointV6
java:module/CasesEndpointV609:30:29,365 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named ‚FormsEndpointV1‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/FormsEndpointV1!org.jlawyer.io.rest.v1.FormsEndpointV1Local
java:app/j-lawyer-io/FormsEndpointV1!org.jlawyer.io.rest.v1.FormsEndpointV1Local
java:module/FormsEndpointV1!org.jlawyer.io.rest.v1.FormsEndpointV1Local
ejb:j-lawyer-server/j-lawyer-io/FormsEndpointV1!org.jlawyer.io.rest.v1.FormsEndpointV1Local
java:global/j-lawyer-server/j-lawyer-io/FormsEndpointV1
java:app/j-lawyer-io/FormsEndpointV1
java:module/FormsEndpointV109:30:29,365 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named ‚SecurityEndpointV6‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/SecurityEndpointV6!org.jlawyer.io.rest.v6.SecurityEndpointLocalV6
java:app/j-lawyer-io/SecurityEndpointV6!org.jlawyer.io.rest.v6.SecurityEndpointLocalV6
java:module/SecurityEndpointV6!org.jlawyer.io.rest.v6.SecurityEndpointLocalV6
ejb:j-lawyer-server/j-lawyer-io/SecurityEndpointV6!org.jlawyer.io.rest.v6.SecurityEndpointLocalV6
java:global/j-lawyer-server/j-lawyer-io/SecurityEndpointV6
java:app/j-lawyer-io/SecurityEndpointV6
java:module/SecurityEndpointV609:30:29,365 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV2‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV2!org.jlawyer.io.rest.v2.CasesEndpointLocalV2
java:app/j-lawyer-io/CasesEndpointV2!org.jlawyer.io.rest.v2.CasesEndpointLocalV2
java:module/CasesEndpointV2!org.jlawyer.io.rest.v2.CasesEndpointLocalV2
ejb:j-lawyer-server/j-lawyer-io/CasesEndpointV2!org.jlawyer.io.rest.v2.CasesEndpointLocalV2
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV2
java:app/j-lawyer-io/CasesEndpointV2
java:module/CasesEndpointV209:30:29,365 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV3‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV3!org.jlawyer.io.rest.v3.CasesEndpointLocalV3
java:app/j-lawyer-io/CasesEndpointV3!org.jlawyer.io.rest.v3.CasesEndpointLocalV3
java:module/CasesEndpointV3!org.jlawyer.io.rest.v3.CasesEndpointLocalV3
ejb:j-lawyer-server/j-lawyer-io/CasesEndpointV3!org.jlawyer.io.rest.v3.CasesEndpointLocalV3
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV3
java:app/j-lawyer-io/CasesEndpointV3
java:module/CasesEndpointV309:30:29,366 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV4‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV4!org.jlawyer.io.rest.v4.CasesEndpointLocalV4
java:app/j-lawyer-io/CasesEndpointV4!org.jlawyer.io.rest.v4.CasesEndpointLocalV4
java:module/CasesEndpointV4!org.jlawyer.io.rest.v4.CasesEndpointLocalV4
ejb:j-lawyer-server/j-lawyer-io/CasesEndpointV4!org.jlawyer.io.rest.v4.CasesEndpointLocalV4
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV4
java:app/j-lawyer-io/CasesEndpointV4
java:module/CasesEndpointV409:30:29,366 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV5‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV5!org.jlawyer.io.rest.v5.CasesEndpointLocalV5
java:app/j-lawyer-io/CasesEndpointV5!org.jlawyer.io.rest.v5.CasesEndpointLocalV5
java:module/CasesEndpointV5!org.jlawyer.io.rest.v5.CasesEndpointLocalV5
ejb:j-lawyer-server/j-lawyer-io/CasesEndpointV5!org.jlawyer.io.rest.v5.CasesEndpointLocalV5
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV5
java:app/j-lawyer-io/CasesEndpointV5
java:module/CasesEndpointV509:30:29,366 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV1‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV1!org.jlawyer.io.rest.v1.CasesEndpointLocalV1
java:app/j-lawyer-io/CasesEndpointV1!org.jlawyer.io.rest.v1.CasesEndpointLocalV1
java:module/CasesEndpointV1!org.jlawyer.io.rest.v1.CasesEndpointLocalV1
ejb:j-lawyer-server/j-lawyer-io/CasesEndpointV1!org.jlawyer.io.rest.v1.CasesEndpointLocalV1
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV1
java:app/j-lawyer-io/CasesEndpointV1
java:module/CasesEndpointV109:30:29,432 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment j-lawyer-server-ejb.jar
09:30:29,437 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚BankDataBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:java:global/j-lawyer-server/j-lawyer-server-ejb/BankDataBeanFacade!com.jdimension.jlawyer.persistence.BankDataBeanFacadeLocal
java:app/j-lawyer-server-ejb/BankDataBeanFacade!com.jdimension.jlawyer.persistence.BankDataBeanFacadeLocal
java:module/BankDataBeanFacade!com.jdimension.jlawyer.persistence.BankDataBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/BankDataBeanFacade!com.jdimension.jlawyer.persistence.BankDataBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/BankDataBeanFacade
java:app/j-lawyer-server-ejb/BankDataBeanFacade
java:module/BankDataBeanFacade09:30:29,437 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚DocumentFolderFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentFolderFacade!com.jdimension.jlawyer.persistence.DocumentFolderFacadeLocal
java:app/j-lawyer-server-ejb/DocumentFolderFacade!com.jdimension.jlawyer.persistence.DocumentFolderFacadeLocal
java:module/DocumentFolderFacade!com.jdimension.jlawyer.persistence.DocumentFolderFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/DocumentFolderFacade!com.jdimension.jlawyer.persistence.DocumentFolderFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentFolderFacade
java:app/j-lawyer-server-ejb/DocumentFolderFacade
java:module/DocumentFolderFacade09:30:29,437 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileFormsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileFormsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormsBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileFormsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormsBeanFacadeLocal
java:module/ArchiveFileFormsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormsBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/ArchiveFileFormsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileFormsBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileFormsBeanFacade
java:module/ArchiveFileFormsBeanFacade09:30:29,438 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚SystemManagement‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/SystemManagement!com.jdimension.jlawyer.services.SystemManagementRemote
java:app/j-lawyer-server-ejb/SystemManagement!com.jdimension.jlawyer.services.SystemManagementRemote
java:module/SystemManagement!com.jdimension.jlawyer.services.SystemManagementRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/SystemManagement!com.jdimension.jlawyer.services.SystemManagementRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/SystemManagement!com.jdimension.jlawyer.services.SystemManagementRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/SystemManagement!com.jdimension.jlawyer.services.SystemManagementLocal
java:app/j-lawyer-server-ejb/SystemManagement!com.jdimension.jlawyer.services.SystemManagementLocal
java:module/SystemManagement!com.jdimension.jlawyer.services.SystemManagementLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/SystemManagement!com.jdimension.jlawyer.services.SystemManagementLocal09:30:29,438 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚ContactSyncService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ContactSyncService!com.jdimension.jlawyer.services.ContactSyncServiceLocal
java:app/j-lawyer-server-ejb/ContactSyncService!com.jdimension.jlawyer.services.ContactSyncServiceLocal
java:module/ContactSyncService!com.jdimension.jlawyer.services.ContactSyncServiceLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/ContactSyncService!com.jdimension.jlawyer.services.ContactSyncServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ContactSyncService
java:app/j-lawyer-server-ejb/ContactSyncService
java:module/ContactSyncService09:30:29,439 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚MappingEntryFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/MappingEntryFacade!com.jdimension.jlawyer.persistence.MappingEntryFacadeLocal
java:app/j-lawyer-server-ejb/MappingEntryFacade!com.jdimension.jlawyer.persistence.MappingEntryFacadeLocal
java:module/MappingEntryFacade!com.jdimension.jlawyer.persistence.MappingEntryFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/MappingEntryFacade!com.jdimension.jlawyer.persistence.MappingEntryFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/MappingEntryFacade
java:app/j-lawyer-server-ejb/MappingEntryFacade
java:module/MappingEntryFacade09:30:29,439 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚FormTypeArtefactBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/FormTypeArtefactBeanFacade!com.jdimension.jlawyer.persistence.FormTypeArtefactBeanFacadeLocal
java:app/j-lawyer-server-ejb/FormTypeArtefactBeanFacade!com.jdimension.jlawyer.persistence.FormTypeArtefactBeanFacadeLocal
java:module/FormTypeArtefactBeanFacade!com.jdimension.jlawyer.persistence.FormTypeArtefactBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/FormTypeArtefactBeanFacade!com.jdimension.jlawyer.persistence.FormTypeArtefactBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/FormTypeArtefactBeanFacade
java:app/j-lawyer-server-ejb/FormTypeArtefactBeanFacade
java:module/FormTypeArtefactBeanFacade09:30:29,439 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CalendarService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceRemote
java:app/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceRemote
java:module/CalendarService!com.jdimension.jlawyer.services.CalendarServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceLocal
java:app/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceLocal
java:module/CalendarService!com.jdimension.jlawyer.services.CalendarServiceLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceLocal09:30:29,439 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚ContainerLifecycleBean‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ContainerLifecycleBean!com.jdimension.jlawyer.services.ContainerLifecycleBeanLocal
java:app/j-lawyer-server-ejb/ContainerLifecycleBean!com.jdimension.jlawyer.services.ContainerLifecycleBeanLocal
java:module/ContainerLifecycleBean!com.jdimension.jlawyer.services.ContainerLifecycleBeanLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/ContainerLifecycleBean!com.jdimension.jlawyer.services.ContainerLifecycleBeanLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ContainerLifecycleBean!com.jdimension.jlawyer.services.ContainerLifecycleBeanRemote
java:app/j-lawyer-server-ejb/ContainerLifecycleBean!com.jdimension.jlawyer.services.ContainerLifecycleBeanRemote
java:module/ContainerLifecycleBean!com.jdimension.jlawyer.services.ContainerLifecycleBeanRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/ContainerLifecycleBean!com.jdimension.jlawyer.services.ContainerLifecycleBeanRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/ContainerLifecycleBean!com.jdimension.jlawyer.services.ContainerLifecycleBeanRemote09:30:29,439 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚FormsService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/FormsService!com.jdimension.jlawyer.services.FormsServiceRemote
java:app/j-lawyer-server-ejb/FormsService!com.jdimension.jlawyer.services.FormsServiceRemote
java:module/FormsService!com.jdimension.jlawyer.services.FormsServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/FormsService!com.jdimension.jlawyer.services.FormsServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/FormsService!com.jdimension.jlawyer.services.FormsServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/FormsService!com.jdimension.jlawyer.services.FormsServiceLocal
java:app/j-lawyer-server-ejb/FormsService!com.jdimension.jlawyer.services.FormsServiceLocal
java:module/FormsService!com.jdimension.jlawyer.services.FormsServiceLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/FormsService!com.jdimension.jlawyer.services.FormsServiceLocal09:30:29,439 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileHistoryBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileHistoryBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileHistoryBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileHistoryBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileHistoryBeanFacadeLocal
java:module/ArchiveFileHistoryBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileHistoryBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/ArchiveFileHistoryBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileHistoryBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileHistoryBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileHistoryBeanFacade
java:module/ArchiveFileHistoryBeanFacade09:30:29,439 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚SearchService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceRemote
java:app/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceRemote
java:module/SearchService!com.jdimension.jlawyer.services.SearchServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceLocal
java:app/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceLocal
java:module/SearchService!com.jdimension.jlawyer.services.SearchServiceLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceLocal09:30:29,439 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CityDataBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CityDataBeanFacade!com.jdimension.jlawyer.persistence.CityDataBeanFacadeLocal
java:app/j-lawyer-server-ejb/CityDataBeanFacade!com.jdimension.jlawyer.persistence.CityDataBeanFacadeLocal
java:module/CityDataBeanFacade!com.jdimension.jlawyer.persistence.CityDataBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/CityDataBeanFacade!com.jdimension.jlawyer.persistence.CityDataBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CityDataBeanFacade
java:app/j-lawyer-server-ejb/CityDataBeanFacade
java:module/CityDataBeanFacade09:30:29,440 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileAddressesBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileAddressesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileAddressesBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileAddressesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileAddressesBeanFacadeLocal
java:module/ArchiveFileAddressesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileAddressesBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/ArchiveFileAddressesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileAddressesBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileAddressesBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileAddressesBeanFacade
java:module/ArchiveFileAddressesBeanFacade09:30:29,440 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚MailboxAccessFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/MailboxAccessFacade!com.jdimension.jlawyer.persistence.MailboxAccessFacadeLocal
java:app/j-lawyer-server-ejb/MailboxAccessFacade!com.jdimension.jlawyer.persistence.MailboxAccessFacadeLocal
java:module/MailboxAccessFacade!com.jdimension.jlawyer.persistence.MailboxAccessFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/MailboxAccessFacade!com.jdimension.jlawyer.persistence.MailboxAccessFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/MailboxAccessFacade
java:app/j-lawyer-server-ejb/MailboxAccessFacade
java:module/MailboxAccessFacade09:30:29,440 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚MailboxSetupFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/MailboxSetupFacade!com.jdimension.jlawyer.persistence.MailboxSetupFacadeLocal
java:app/j-lawyer-server-ejb/MailboxSetupFacade!com.jdimension.jlawyer.persistence.MailboxSetupFacadeLocal
java:module/MailboxSetupFacade!com.jdimension.jlawyer.persistence.MailboxSetupFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/MailboxSetupFacade!com.jdimension.jlawyer.persistence.MailboxSetupFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/MailboxSetupFacade
java:app/j-lawyer-server-ejb/MailboxSetupFacade
java:module/MailboxSetupFacade09:30:29,440 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceRemote
java:app/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceRemote
java:module/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceLocal
java:app/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceLocal
java:module/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceLocal09:30:29,440 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚AddressTagsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/AddressTagsBeanFacade!com.jdimension.jlawyer.persistence.AddressTagsBeanFacadeLocal
java:app/j-lawyer-server-ejb/AddressTagsBeanFacade!com.jdimension.jlawyer.persistence.AddressTagsBeanFacadeLocal
java:module/AddressTagsBeanFacade!com.jdimension.jlawyer.persistence.AddressTagsBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/AddressTagsBeanFacade!com.jdimension.jlawyer.persistence.AddressTagsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/AddressTagsBeanFacade
java:app/j-lawyer-server-ejb/AddressTagsBeanFacade
java:module/AddressTagsBeanFacade09:30:29,440 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚InvoicePositionFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePositionFacade!com.jdimension.jlawyer.persistence.InvoicePositionFacadeLocal
java:app/j-lawyer-server-ejb/InvoicePositionFacade!com.jdimension.jlawyer.persistence.InvoicePositionFacadeLocal
java:module/InvoicePositionFacade!com.jdimension.jlawyer.persistence.InvoicePositionFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/InvoicePositionFacade!com.jdimension.jlawyer.persistence.InvoicePositionFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePositionFacade
java:app/j-lawyer-server-ejb/InvoicePositionFacade
java:module/InvoicePositionFacade09:30:29,440 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CalendarAccessFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarAccessFacade!com.jdimension.jlawyer.persistence.CalendarAccessFacadeLocal
java:app/j-lawyer-server-ejb/CalendarAccessFacade!com.jdimension.jlawyer.persistence.CalendarAccessFacadeLocal
java:module/CalendarAccessFacade!com.jdimension.jlawyer.persistence.CalendarAccessFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/CalendarAccessFacade!com.jdimension.jlawyer.persistence.CalendarAccessFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarAccessFacade
java:app/j-lawyer-server-ejb/CalendarAccessFacade
java:module/CalendarAccessFacade09:30:29,440 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚GroupMembershipFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/GroupMembershipFacade!com.jdimension.jlawyer.persistence.GroupMembershipFacadeLocal
java:app/j-lawyer-server-ejb/GroupMembershipFacade!com.jdimension.jlawyer.persistence.GroupMembershipFacadeLocal
java:module/GroupMembershipFacade!com.jdimension.jlawyer.persistence.GroupMembershipFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/GroupMembershipFacade!com.jdimension.jlawyer.persistence.GroupMembershipFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/GroupMembershipFacade
java:app/j-lawyer-server-ejb/GroupMembershipFacade
java:module/GroupMembershipFacade09:30:29,441 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚AddressBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/AddressBeanFacade!com.jdimension.jlawyer.persistence.AddressBeanFacadeLocal
java:app/j-lawyer-server-ejb/AddressBeanFacade!com.jdimension.jlawyer.persistence.AddressBeanFacadeLocal
java:module/AddressBeanFacade!com.jdimension.jlawyer.persistence.AddressBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/AddressBeanFacade!com.jdimension.jlawyer.persistence.AddressBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/AddressBeanFacade
java:app/j-lawyer-server-ejb/AddressBeanFacade
java:module/AddressBeanFacade09:30:29,441 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CampaignFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CampaignFacade!com.jdimension.jlawyer.persistence.CampaignFacadeLocal
java:app/j-lawyer-server-ejb/CampaignFacade!com.jdimension.jlawyer.persistence.CampaignFacadeLocal
java:module/CampaignFacade!com.jdimension.jlawyer.persistence.CampaignFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/CampaignFacade!com.jdimension.jlawyer.persistence.CampaignFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CampaignFacade
java:app/j-lawyer-server-ejb/CampaignFacade
java:module/CampaignFacade09:30:29,441 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚DocumentTagsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentTagsBeanFacade!com.jdimension.jlawyer.persistence.DocumentTagsBeanFacadeLocal
java:app/j-lawyer-server-ejb/DocumentTagsBeanFacade!com.jdimension.jlawyer.persistence.DocumentTagsBeanFacadeLocal
java:module/DocumentTagsBeanFacade!com.jdimension.jlawyer.persistence.DocumentTagsBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/DocumentTagsBeanFacade!com.jdimension.jlawyer.persistence.DocumentTagsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentTagsBeanFacade
java:app/j-lawyer-server-ejb/DocumentTagsBeanFacade
java:module/DocumentTagsBeanFacade09:30:29,441 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚IntegrationService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceRemote
java:app/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceRemote
java:module/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceLocal
java:app/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceLocal
java:module/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceLocal09:30:29,441 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚FaxQueueBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/FaxQueueBeanFacade!com.jdimension.jlawyer.persistence.FaxQueueBeanFacadeLocal
java:app/j-lawyer-server-ejb/FaxQueueBeanFacade!com.jdimension.jlawyer.persistence.FaxQueueBeanFacadeLocal
java:module/FaxQueueBeanFacade!com.jdimension.jlawyer.persistence.FaxQueueBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/FaxQueueBeanFacade!com.jdimension.jlawyer.persistence.FaxQueueBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/FaxQueueBeanFacade
java:app/j-lawyer-server-ejb/FaxQueueBeanFacade
java:module/FaxQueueBeanFacade09:30:29,441 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileReviewsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileReviewsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileReviewsBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileReviewsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileReviewsBeanFacadeLocal
java:module/ArchiveFileReviewsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileReviewsBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/ArchiveFileReviewsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileReviewsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileReviewsBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileReviewsBeanFacade
java:module/ArchiveFileReviewsBeanFacade09:30:29,441 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚InvoicePoolFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePoolFacade!com.jdimension.jlawyer.persistence.InvoicePoolFacadeLocal
java:app/j-lawyer-server-ejb/InvoicePoolFacade!com.jdimension.jlawyer.persistence.InvoicePoolFacadeLocal
java:module/InvoicePoolFacade!com.jdimension.jlawyer.persistence.InvoicePoolFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/InvoicePoolFacade!com.jdimension.jlawyer.persistence.InvoicePoolFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePoolFacade
java:app/j-lawyer-server-ejb/InvoicePoolFacade
java:module/InvoicePoolFacade09:30:29,441 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚GroupFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/GroupFacade!com.jdimension.jlawyer.persistence.GroupFacadeLocal
java:app/j-lawyer-server-ejb/GroupFacade!com.jdimension.jlawyer.persistence.GroupFacadeLocal
java:module/GroupFacade!com.jdimension.jlawyer.persistence.GroupFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/GroupFacade!com.jdimension.jlawyer.persistence.GroupFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/GroupFacade
java:app/j-lawyer-server-ejb/GroupFacade
java:module/GroupFacade09:30:29,442 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚ReportService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ReportService!com.jdimension.jlawyer.services.ReportServiceRemote
java:app/j-lawyer-server-ejb/ReportService!com.jdimension.jlawyer.services.ReportServiceRemote
java:module/ReportService!com.jdimension.jlawyer.services.ReportServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/ReportService!com.jdimension.jlawyer.services.ReportServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/ReportService!com.jdimension.jlawyer.services.ReportServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/ReportService
java:app/j-lawyer-server-ejb/ReportService
java:module/ReportService09:30:29,442 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CaseSyncSettingsFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CaseSyncSettingsFacade!com.jdimension.jlawyer.persistence.CaseSyncSettingsFacadeLocal
java:app/j-lawyer-server-ejb/CaseSyncSettingsFacade!com.jdimension.jlawyer.persistence.CaseSyncSettingsFacadeLocal
java:module/CaseSyncSettingsFacade!com.jdimension.jlawyer.persistence.CaseSyncSettingsFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/CaseSyncSettingsFacade!com.jdimension.jlawyer.persistence.CaseSyncSettingsFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CaseSyncSettingsFacade
java:app/j-lawyer-server-ejb/CaseSyncSettingsFacade
java:module/CaseSyncSettingsFacade09:30:29,442 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚DrebisService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceLocal
java:app/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceLocal
java:module/DrebisService!com.jdimension.jlawyer.services.DrebisServiceLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote
java:app/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote
java:module/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote09:30:29,442 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚InvoiceTypeFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoiceTypeFacade!com.jdimension.jlawyer.persistence.InvoiceTypeFacadeLocal
java:app/j-lawyer-server-ejb/InvoiceTypeFacade!com.jdimension.jlawyer.persistence.InvoiceTypeFacadeLocal
java:module/InvoiceTypeFacade!com.jdimension.jlawyer.persistence.InvoiceTypeFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/InvoiceTypeFacade!com.jdimension.jlawyer.persistence.InvoiceTypeFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoiceTypeFacade
java:app/j-lawyer-server-ejb/InvoiceTypeFacade
java:module/InvoiceTypeFacade09:30:29,442 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileGroupsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileGroupsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileGroupsBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileGroupsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileGroupsBeanFacadeLocal
java:module/ArchiveFileGroupsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileGroupsBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/ArchiveFileGroupsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileGroupsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileGroupsBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileGroupsBeanFacade
java:module/ArchiveFileGroupsBeanFacade09:30:29,442 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileTagsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileTagsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileTagsBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileTagsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileTagsBeanFacadeLocal
java:module/ArchiveFileTagsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileTagsBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/ArchiveFileTagsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileTagsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileTagsBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileTagsBeanFacade
java:module/ArchiveFileTagsBeanFacade09:30:29,442 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CaseFolderSettingsFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CaseFolderSettingsFacade!com.jdimension.jlawyer.persistence.CaseFolderSettingsFacadeLocal
java:app/j-lawyer-server-ejb/CaseFolderSettingsFacade!com.jdimension.jlawyer.persistence.CaseFolderSettingsFacadeLocal
java:module/CaseFolderSettingsFacade!com.jdimension.jlawyer.persistence.CaseFolderSettingsFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/CaseFolderSettingsFacade!com.jdimension.jlawyer.persistence.CaseFolderSettingsFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CaseFolderSettingsFacade
java:app/j-lawyer-server-ejb/CaseFolderSettingsFacade
java:module/CaseFolderSettingsFacade09:30:29,442 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CalendarSetupFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarSetupFacade!com.jdimension.jlawyer.persistence.CalendarSetupFacadeLocal
java:app/j-lawyer-server-ejb/CalendarSetupFacade!com.jdimension.jlawyer.persistence.CalendarSetupFacadeLocal
java:module/CalendarSetupFacade!com.jdimension.jlawyer.persistence.CalendarSetupFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/CalendarSetupFacade!com.jdimension.jlawyer.persistence.CalendarSetupFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarSetupFacade
java:app/j-lawyer-server-ejb/CalendarSetupFacade
java:module/CalendarSetupFacade09:30:29,443 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileFormEntriesBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileFormEntriesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormEntriesBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileFormEntriesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormEntriesBeanFacadeLocal
java:module/ArchiveFileFormEntriesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormEntriesBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/ArchiveFileFormEntriesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormEntriesBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileFormEntriesBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileFormEntriesBeanFacade
java:module/ArchiveFileFormEntriesBeanFacade09:30:29,443 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚InvoicePoolAccessFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePoolAccessFacade!com.jdimension.jlawyer.persistence.InvoicePoolAccessFacadeLocal
java:app/j-lawyer-server-ejb/InvoicePoolAccessFacade!com.jdimension.jlawyer.persistence.InvoicePoolAccessFacadeLocal
java:module/InvoicePoolAccessFacade!com.jdimension.jlawyer.persistence.InvoicePoolAccessFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/InvoicePoolAccessFacade!com.jdimension.jlawyer.persistence.InvoicePoolAccessFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePoolAccessFacade
java:app/j-lawyer-server-ejb/InvoicePoolAccessFacade
java:module/InvoicePoolAccessFacade09:30:29,443 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CalendarSyncService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarSyncService!com.jdimension.jlawyer.services.CalendarSyncServiceLocal
java:app/j-lawyer-server-ejb/CalendarSyncService!com.jdimension.jlawyer.services.CalendarSyncServiceLocal
java:module/CalendarSyncService!com.jdimension.jlawyer.services.CalendarSyncServiceLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/CalendarSyncService!com.jdimension.jlawyer.services.CalendarSyncServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarSyncService
java:app/j-lawyer-server-ejb/CalendarSyncService
java:module/CalendarSyncService09:30:29,443 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CustomerRelationsService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceLocal
java:app/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceLocal
java:module/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote
java:app/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote
java:module/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote09:30:29,443 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚MappingTableFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/MappingTableFacade!com.jdimension.jlawyer.persistence.MappingTableFacadeLocal
java:app/j-lawyer-server-ejb/MappingTableFacade!com.jdimension.jlawyer.persistence.MappingTableFacadeLocal
java:module/MappingTableFacade!com.jdimension.jlawyer.persistence.MappingTableFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/MappingTableFacade!com.jdimension.jlawyer.persistence.MappingTableFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/MappingTableFacade
java:app/j-lawyer-server-ejb/MappingTableFacade
java:module/MappingTableFacade09:30:29,443 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚AddressService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/AddressService!com.jdimension.jlawyer.services.AddressServiceRemote
java:app/j-lawyer-server-ejb/AddressService!com.jdimension.jlawyer.services.AddressServiceRemote
java:module/AddressService!com.jdimension.jlawyer.services.AddressServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/AddressService!com.jdimension.jlawyer.services.AddressServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/AddressService!com.jdimension.jlawyer.services.AddressServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/AddressService!com.jdimension.jlawyer.services.AddressServiceLocal
java:app/j-lawyer-server-ejb/AddressService!com.jdimension.jlawyer.services.AddressServiceLocal
java:module/AddressService!com.jdimension.jlawyer.services.AddressServiceLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/AddressService!com.jdimension.jlawyer.services.AddressServiceLocal09:30:29,443 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚SecurityService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceLocal
java:app/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceLocal
java:module/SecurityService!com.jdimension.jlawyer.services.SecurityServiceLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceRemote
java:app/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceRemote
java:module/SecurityService!com.jdimension.jlawyer.services.SecurityServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceRemote09:30:29,443 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CampaignAddressesFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CampaignAddressesFacade!com.jdimension.jlawyer.persistence.CampaignAddressesFacadeLocal
java:app/j-lawyer-server-ejb/CampaignAddressesFacade!com.jdimension.jlawyer.persistence.CampaignAddressesFacadeLocal
java:module/CampaignAddressesFacade!com.jdimension.jlawyer.persistence.CampaignAddressesFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/CampaignAddressesFacade!com.jdimension.jlawyer.persistence.CampaignAddressesFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CampaignAddressesFacade
java:app/j-lawyer-server-ejb/CampaignAddressesFacade
java:module/CampaignAddressesFacade09:30:29,443 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileDocumentsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileDocumentsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileDocumentsBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileDocumentsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileDocumentsBeanFacadeLocal
java:module/ArchiveFileDocumentsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileDocumentsBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/ArchiveFileDocumentsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileDocumentsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileDocumentsBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileDocumentsBeanFacade
java:module/ArchiveFileDocumentsBeanFacade09:30:29,444 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚AppOptionGroupBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/AppOptionGroupBeanFacade!com.jdimension.jlawyer.persistence.AppOptionGroupBeanFacadeLocal
java:app/j-lawyer-server-ejb/AppOptionGroupBeanFacade!com.jdimension.jlawyer.persistence.AppOptionGroupBeanFacadeLocal
java:module/AppOptionGroupBeanFacade!com.jdimension.jlawyer.persistence.AppOptionGroupBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/AppOptionGroupBeanFacade!com.jdimension.jlawyer.persistence.AppOptionGroupBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/AppOptionGroupBeanFacade
java:app/j-lawyer-server-ejb/AppOptionGroupBeanFacade
java:module/AppOptionGroupBeanFacade09:30:29,444 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚DocumentFolderTemplateFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentFolderTemplateFacade!com.jdimension.jlawyer.persistence.DocumentFolderTemplateFacadeLocal
java:app/j-lawyer-server-ejb/DocumentFolderTemplateFacade!com.jdimension.jlawyer.persistence.DocumentFolderTemplateFacadeLocal
java:module/DocumentFolderTemplateFacade!com.jdimension.jlawyer.persistence.DocumentFolderTemplateFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/DocumentFolderTemplateFacade!com.jdimension.jlawyer.persistence.DocumentFolderTemplateFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentFolderTemplateFacade
java:app/j-lawyer-server-ejb/DocumentFolderTemplateFacade
java:module/DocumentFolderTemplateFacade09:30:29,444 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚ServerSettingsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ServerSettingsBeanFacade!com.jdimension.jlawyer.persistence.ServerSettingsBeanFacadeLocal
java:app/j-lawyer-server-ejb/ServerSettingsBeanFacade!com.jdimension.jlawyer.persistence.ServerSettingsBeanFacadeLocal
java:module/ServerSettingsBeanFacade!com.jdimension.jlawyer.persistence.ServerSettingsBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/ServerSettingsBeanFacade!com.jdimension.jlawyer.persistence.ServerSettingsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ServerSettingsBeanFacade
java:app/j-lawyer-server-ejb/ServerSettingsBeanFacade
java:module/ServerSettingsBeanFacade09:30:29,444 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚SingletonService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/SingletonService!com.jdimension.jlawyer.services.SingletonServiceRemote
java:app/j-lawyer-server-ejb/SingletonService!com.jdimension.jlawyer.services.SingletonServiceRemote
java:module/SingletonService!com.jdimension.jlawyer.services.SingletonServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/SingletonService!com.jdimension.jlawyer.services.SingletonServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/SingletonService!com.jdimension.jlawyer.services.SingletonServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/SingletonService!com.jdimension.jlawyer.services.SingletonServiceLocal
java:app/j-lawyer-server-ejb/SingletonService!com.jdimension.jlawyer.services.SingletonServiceLocal
java:module/SingletonService!com.jdimension.jlawyer.services.SingletonServiceLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/SingletonService!com.jdimension.jlawyer.services.SingletonServiceLocal09:30:29,444 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚InvoiceService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceLocal
java:app/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceLocal
java:module/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceRemote
java:app/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceRemote
java:module/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceRemote09:30:29,447 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚VoipService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceRemote
java:app/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceRemote
java:module/VoipService!com.jdimension.jlawyer.services.VoipServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceLocal
java:app/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceLocal
java:module/VoipService!com.jdimension.jlawyer.services.VoipServiceLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceLocal09:30:29,447 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚PartyTypeBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/PartyTypeBeanFacade!com.jdimension.jlawyer.persistence.PartyTypeBeanFacadeLocal
java:app/j-lawyer-server-ejb/PartyTypeBeanFacade!com.jdimension.jlawyer.persistence.PartyTypeBeanFacadeLocal
java:module/PartyTypeBeanFacade!com.jdimension.jlawyer.persistence.PartyTypeBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/PartyTypeBeanFacade!com.jdimension.jlawyer.persistence.PartyTypeBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/PartyTypeBeanFacade
java:app/j-lawyer-server-ejb/PartyTypeBeanFacade
java:module/PartyTypeBeanFacade09:30:29,447 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚InvoiceFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoiceFacade!com.jdimension.jlawyer.persistence.InvoiceFacadeLocal
java:app/j-lawyer-server-ejb/InvoiceFacade!com.jdimension.jlawyer.persistence.InvoiceFacadeLocal
java:module/InvoiceFacade!com.jdimension.jlawyer.persistence.InvoiceFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/InvoiceFacade!com.jdimension.jlawyer.persistence.InvoiceFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoiceFacade
java:app/j-lawyer-server-ejb/InvoiceFacade
java:module/InvoiceFacade09:30:29,447 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚FormTypeBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/FormTypeBeanFacade!com.jdimension.jlawyer.persistence.FormTypeBeanFacadeLocal
java:app/j-lawyer-server-ejb/FormTypeBeanFacade!com.jdimension.jlawyer.persistence.FormTypeBeanFacadeLocal
java:module/FormTypeBeanFacade!com.jdimension.jlawyer.persistence.FormTypeBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/FormTypeBeanFacade!com.jdimension.jlawyer.persistence.FormTypeBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/FormTypeBeanFacade
java:app/j-lawyer-server-ejb/FormTypeBeanFacade
java:module/FormTypeBeanFacade09:30:29,447 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚AppUserBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/AppUserBeanFacade!com.jdimension.jlawyer.persistence.AppUserBeanFacadeLocal
java:app/j-lawyer-server-ejb/AppUserBeanFacade!com.jdimension.jlawyer.persistence.AppUserBeanFacadeLocal
java:module/AppUserBeanFacade!com.jdimension.jlawyer.persistence.AppUserBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/AppUserBeanFacade!com.jdimension.jlawyer.persistence.AppUserBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/AppUserBeanFacade
java:app/j-lawyer-server-ejb/AppUserBeanFacade
java:module/AppUserBeanFacade09:30:29,447 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CaseFolderFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CaseFolderFacade!com.jdimension.jlawyer.persistence.CaseFolderFacadeLocal
java:app/j-lawyer-server-ejb/CaseFolderFacade!com.jdimension.jlawyer.persistence.CaseFolderFacadeLocal
java:module/CaseFolderFacade!com.jdimension.jlawyer.persistence.CaseFolderFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/CaseFolderFacade!com.jdimension.jlawyer.persistence.CaseFolderFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CaseFolderFacade
java:app/j-lawyer-server-ejb/CaseFolderFacade
java:module/CaseFolderFacade09:30:29,447 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileBeanFacadeLocal
java:module/ArchiveFileBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/ArchiveFileBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileBeanFacade
java:module/ArchiveFileBeanFacade09:30:29,447 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚DataBucketLoader‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/DataBucketLoader!com.jdimension.jlawyer.services.DataBucketLoaderLocal
java:app/j-lawyer-server-ejb/DataBucketLoader!com.jdimension.jlawyer.services.DataBucketLoaderLocal
java:module/DataBucketLoader!com.jdimension.jlawyer.services.DataBucketLoaderLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/DataBucketLoader!com.jdimension.jlawyer.services.DataBucketLoaderLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/DataBucketLoader!com.jdimension.jlawyer.services.DataBucketLoaderRemote
java:app/j-lawyer-server-ejb/DataBucketLoader!com.jdimension.jlawyer.services.DataBucketLoaderRemote
java:module/DataBucketLoader!com.jdimension.jlawyer.services.DataBucketLoaderRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/DataBucketLoader!com.jdimension.jlawyer.services.DataBucketLoaderRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/DataBucketLoader!com.jdimension.jlawyer.services.DataBucketLoaderRemote09:30:29,448 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CustomHooksService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CustomHooksService!com.jdimension.jlawyer.events.CustomHooksServiceLocal
java:app/j-lawyer-server-ejb/CustomHooksService!com.jdimension.jlawyer.events.CustomHooksServiceLocal
java:module/CustomHooksService!com.jdimension.jlawyer.events.CustomHooksServiceLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/CustomHooksService!com.jdimension.jlawyer.events.CustomHooksServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CustomHooksService
java:app/j-lawyer-server-ejb/CustomHooksService
java:module/CustomHooksService09:30:29,448 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚IntegrationHookFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/IntegrationHookFacade!com.jdimension.jlawyer.persistence.IntegrationHookFacadeLocal
java:app/j-lawyer-server-ejb/IntegrationHookFacade!com.jdimension.jlawyer.persistence.IntegrationHookFacadeLocal
java:module/IntegrationHookFacade!com.jdimension.jlawyer.persistence.IntegrationHookFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/IntegrationHookFacade!com.jdimension.jlawyer.persistence.IntegrationHookFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/IntegrationHookFacade
java:app/j-lawyer-server-ejb/IntegrationHookFacade
java:module/IntegrationHookFacade09:30:29,448 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚AppRoleBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/AppRoleBeanFacade!com.jdimension.jlawyer.persistence.AppRoleBeanFacadeLocal
java:app/j-lawyer-server-ejb/AppRoleBeanFacade!com.jdimension.jlawyer.persistence.AppRoleBeanFacadeLocal
java:module/AppRoleBeanFacade!com.jdimension.jlawyer.persistence.AppRoleBeanFacadeLocal
ejb:j-lawyer-server/j-lawyer-server-ejb/AppRoleBeanFacade!com.jdimension.jlawyer.persistence.AppRoleBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/AppRoleBeanFacade
java:app/j-lawyer-server-ejb/AppRoleBeanFacade
java:module/AppRoleBeanFacade09:30:29,465 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan ‚Infinity Minus ONE +2‘ 9.4.8.Final
09:30:29,548 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900: 3.1.0 (Final)
09:30:29,651 WARN [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (createFile)
09:30:29,651 WARN [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (copyFile)
09:30:29,651 WARN [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (readFile)
09:30:29,651 WARN [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (writeFile)
09:30:29,651 WARN [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (readTextFile)
09:30:29,755 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 75) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
09:30:29,820 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 76) WFLYCLINF0002: Started client-mappings cache from ejb container
09:30:29,834 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.subunit.“j-lawyer-server.ear“.“j-lawyer-server-ejb.jar“.INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit.“j-lawyer-server.ear“.“j-lawyer-server-ejb.jar“.INSTALL: WFLYSRV0153: Failed to process phase INSTALL of subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“
at org.jboss.as.server@8.0.0.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0024: Could not configure component SearchIndexProcessor
at org.jboss.as.ee@16.0.0.Final//org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:106)
at org.jboss.as.server@8.0.0.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)
… 8 more
Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make protected native java.lang.Object java.lang.Object.clone() throws java.lang.CloneNotSupportedException accessible: module java.base does not „opens java.lang“ to unnamed module @184f246c
at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
at java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199)
at java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.proxy.AbstractProxyFactory$1.run(AbstractProxyFactory.java:121)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:318)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.proxy.AbstractProxyFactory.setupCachedProxyFields(AbstractProxyFactory.java:117)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.proxy.AbstractProxyFactory.finalizeStaticConstructor(AbstractProxyFactory.java:93)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.proxy.ProxyFactory.generateClass(ProxyFactory.java:292)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.proxy.AbstractClassFactory.buildClassDefinition(AbstractClassFactory.java:245)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.proxy.AbstractClassFactory.defineClass(AbstractClassFactory.java:198)
at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.proxy.AbstractProxyFactory.getCachedMethods(AbstractProxyFactory.java:162)
at org.jboss.as.ee@16.0.0.Final//org.jboss.as.ee.component.ViewConfiguration.addViewInterceptor(ViewConfiguration.java:119)
at org.jboss.as.ee@16.0.0.Final//org.jboss.as.ee.component.NamespaceViewConfigurator.configure(NamespaceViewConfigurator.java:34)
at org.jboss.as.ee@16.0.0.Final//org.jboss.as.ee.component.DefaultComponentViewConfigurator.configure(DefaultComponentViewConfigurator.java:91)
at org.jboss.as.ee@16.0.0.Final//org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:92)
… 9 more09:30:29,910 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool — 75) HHH000400: Using dialect: org.hibernate.dialect.MySQL55Dialect
09:30:29,949 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool — 75) Envers integration enabled? : true
09:30:30,311 INFO [stdout] (ServerService Thread Pool — 75) Starting j-lawyer.org database migrations…
09:30:30,321 INFO [org.flywaydb.core.internal.license.VersionPrinter] (ServerService Thread Pool — 75) Flyway Community Edition 5.2.1 by Boxfuse
09:30:30,326 INFO [org.flywaydb.core.internal.database.DatabaseFactory] (ServerService Thread Pool — 75) Database: jdbc:mysql://localhost:3306/jlawyerdb (MySQL 5.5)
09:30:30,478 INFO [org.flywaydb.core.internal.command.DbValidate] (ServerService Thread Pool — 75) Successfully validated 122 migrations (execution time 00:00.109s)
09:30:30,488 INFO [org.flywaydb.core.internal.schemahistory.JdbcTableSchemaHistory] (ServerService Thread Pool — 75) Creating Schema History table:jlawyerdb.flyway_schema_history
09:30:30,499 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚flyway_schema_history_pk‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:30,514 INFO [org.flywaydb.core.internal.command.DbBaseline] (ServerService Thread Pool — 75) Successfully baselined schema with version: 1.9.1.0
09:30:30,521 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Current version of schemajlawyerdb: 1.9.1.0
09:30:30,523 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.10.0.0 – UpdateDbVersion
09:30:30,533 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.10.0.1 – SampleMigration
09:30:30,533 INFO [db.migration.V1_10_0_1__SampleMigration] (ServerService Thread Pool — 75) Running migration db.migration.V1_10_0_1__SampleMigration
09:30:30,538 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.10.0.2 – AddIndex
09:30:30,553 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.10.0.3 – RenameTables
09:30:30,691 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.10.0.4 – RemoveOptionGroupRole
09:30:30,701 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.10.0.5 – AddIndex
09:30:30,718 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.10.0.6 – AddTableDocumentTags
09:30:30,725 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_document_tags‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:30,768 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.10.0.7 – BeaProductionEndpoint
09:30:30,776 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.10.0.8 – InitialDocmentTags
09:30:30,798 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.10.0.9 – VersionUpdate
09:30:30,806 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.10.0.10 – MacOsForeignKeyFix
09:30:31,110 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.11.0.0 – AddDepartment
09:30:31,120 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.11.0.1 – AddSmtpPort
09:30:31,129 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.11.0.2 – SyncFix
09:30:31,136 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.12.0.0 – AddTablePartyTypes
09:30:31,143 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_party_types‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:31,214 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.12.0.1 – AddIndexDepartment
09:30:31,232 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.12.0.2 – AddTableFormTypes
09:30:31,239 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_form_types‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:31,244 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_form_types_artefacts‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:31,248 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_case_forms‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:31,251 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_case_forms_entries‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:31,258 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.12.0.3 – AddFormUsageType
09:30:31,267 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.12.0.4 – AddTableSecurityGroups
09:30:31,275 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_security_groups‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:31,281 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_group_memberships‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:31,288 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.12.0.5 – AddAbbrevPrimGroup
09:30:31,324 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.12.0.6 – AddGroupToCase
09:30:31,358 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.12.0.7 – AddTableCaseGroups
09:30:31,368 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_case_groups‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:31,376 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.12.0.8 – ModifyOwnerGroup
09:30:31,385 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.12.0.9 – AddFileNumberExtToCase
09:30:31,397 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.12.0.10 – VersionBump
09:30:31,403 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.0 – VersionBump
09:30:31,409 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.1 – ModifyFormsEntriesLength
09:30:31,420 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.2 – AddFieldsToContacts
09:30:31,471 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.3 – AddFieldsToContacts2
09:30:31,481 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.4 – AddIndexToContacts
09:30:31,493 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.5 – AddDropdownValuesNationality
09:30:31,529 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.6 – AddDropdownValuesLegalForm
09:30:31,536 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.7 – AddDropdownValuesDegrees
09:30:31,545 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.8 – AddDropdownValuesProfessions
09:30:31,552 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.9 – AddIndexToContacts
09:30:31,564 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.10 – AddDropdownValuesCloseGreet
09:30:31,571 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.11 – AddCloudFieldsToUser
09:30:31,583 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.12 – AddDocumentFolderTemplates
09:30:31,587 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_document_folders‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:31,603 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_document_folder_tpls‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:31,609 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.13 – AddCaseFolders
09:30:31,615 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_case_folders‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:31,691 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.14 – AddStandardFolders
09:30:31,700 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.15 – ModifyFormPlaceholdersLength
09:30:31,708 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.16 – ModifyFormEntriesPlaceholdersLength
09:30:31,716 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.17 – AddRootFolders
09:30:31,717 INFO [db.migration.V1_13_0_17__AddRootFolders] (ServerService Thread Pool — 75) Running migration db.migration.V1_13_0_17__AddRootFolders
09:30:31,723 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.18 – VersionBump
09:30:31,729 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.19 – VersionBump
09:30:31,735 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.20 – VersionBump
09:30:31,740 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.21 – FolderStructureFix
09:30:31,740 INFO [db.migration.V1_13_0_21__FolderStructureFix] (ServerService Thread Pool — 75) Running migration db.migration.V1_13_0_21__FolderStructureFix
09:30:31,741 WARN [db.migration.V1_13_0_21__FolderStructureFix] (ServerService Thread Pool — 75) unassigning documents from folders…
09:30:31,742 WARN [db.migration.V1_13_0_21__FolderStructureFix] (ServerService Thread Pool — 75) folder cleanup finished.
09:30:31,747 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.22 – AddRootFolders
09:30:31,747 INFO [db.migration.V1_13_0_22__AddRootFolders] (ServerService Thread Pool — 75) Running migration db.migration.V1_13_0_22__AddRootFolders
09:30:31,751 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.13.0.23 – VersionBump
09:30:31,756 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.14.0.0 – AddCloudPathToUser
09:30:31,764 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.14.0.1 – ModifyPasswordLength
09:30:31,797 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.14.0.2 – CalculatePasswordHashes
09:30:31,798 INFO [db.migration.V1_14_0_2__CalculatePasswordHashes] (ServerService Thread Pool — 75) Running migration db.migration.V1_14_0_2__CalculatePasswordHashes
09:30:31,803 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.14.0.3 – AddDisplayNameToUser
09:30:31,816 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.14.0.4 – MakeRootFolderUnique
09:30:31,817 INFO [db.migration.V1_14_0_4__MakeRootFolderUnique] (ServerService Thread Pool — 75) Running migration db.migration.V1_14_0_4__MakeRootFolderUnique
09:30:31,832 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.14.0.5 – DocumentsBin
09:30:31,844 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.14.0.6 – AddIndexToDocuments
09:30:31,860 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.14.0.7 – UpdateDrebisCredentials
09:30:31,866 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.14.0.8 – AddCaseFolderSettings
09:30:31,873 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_case_folder_settings‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:31,886 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.14.0.9 – VersionBump
09:30:31,889 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.14.1.0 – VersionBump
09:30:31,897 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.15.0.0 – VersionBump
09:30:31,902 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.15.0.1 – RenameTables
09:30:31,915 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.15.0.2 – RenameEventsColumns
09:30:31,942 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.15.0.3 – EventsNewType
09:30:32,014 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.15.0.4 – AddCalendarSetup
09:30:32,019 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_calendar_setup‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:32,046 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.15.0.5 – AddCalendarSecurity
09:30:32,054 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_calendar_access‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:32,059 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.15.0.6 – GrantAccessToCalendars
09:30:32,059 INFO [db.migration.V1_15_0_6__GrantAccessToCalendars] (ServerService Thread Pool — 75) Running migration db.migration.V1_15_0_6__GrantAccessToCalendars
09:30:32,065 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.15.0.7 – MigrateExistingEvents
09:30:32,102 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.15.0.8 – RenameCalendarSetupNameColumn
09:30:32,110 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.15.0.9 – CalculateBeaPasswordHashes
09:30:32,111 INFO [db.migration.V1_15_0_9__CalculateBeaPasswordHashes] (ServerService Thread Pool — 75) Running migration db.migration.V1_15_0_9__CalculateBeaPasswordHashes
09:30:32,114 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 1.15.0.10 – AddIndexCalendarSetup
09:30:32,129 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.0.0.0 – VersionBump
09:30:32,135 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.0.0.1 – AddMailbox
09:30:32,143 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_mailbox_setup‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:32,153 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_mailbox_access‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:32,158 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.0.0.2 – GrantAccessToMailboxes
09:30:32,158 INFO [db.migration.V2_0_0_2__GrantAccessToMailboxes] (ServerService Thread Pool — 75) Running migration db.migration.V2_0_0_2__GrantAccessToMailboxes
09:30:32,159 INFO [db.migration.V2_0_0_2__GrantAccessToMailboxes] (ServerService Thread Pool — 75) no mailbox configuration found for admin
09:30:32,159 INFO [db.migration.V2_0_0_2__GrantAccessToMailboxes] (ServerService Thread Pool — 75) no mailbox configuration found for user
09:30:32,164 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.0.0.3 – MailboxNameUnique
09:30:32,174 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.0.0.4 – VersionBump
09:30:32,180 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.0.1.0 – AddVoipIdToUser
09:30:32,188 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.1.0.0 – AddUserLimit
09:30:32,194 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.1.0.1 – AddMappingTables
09:30:32,200 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_mapping_tables‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:32,206 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_mapping_entries‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:32,257 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.1.0.2 – AddWebHookTables
09:30:32,264 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_integration_hooks‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:32,272 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.1.0.3 – ModifyWebHookTables
09:30:32,319 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.1.0.4 – ModifyFormEntriesLength
09:30:32,362 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.1.0.5 – PopulateMappingTableGendern
09:30:32,545 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.1.0.6 – ModifyCloudPasswordLength
09:30:32,581 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.1.0.7 – DropMailColumns
09:30:32,616 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.1.0.8 – DropMailOutPort
09:30:32,623 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.1.0.9 – CalculateCloudPasswordHashes
09:30:32,624 INFO [db.migration.V2_1_0_9__CalculateCloudPasswordHashes] (ServerService Thread Pool — 75) Running migration db.migration.V2_1_0_9__CalculateCloudPasswordHashes
09:30:32,628 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.1.0.10 – AddCaseSyncSettings
09:30:32,634 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_case_syncs‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:32,637 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.1.0.11 – DropLegacyViews
09:30:32,642 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.1.0.12 – AddDefaultRoleToContact
09:30:32,648 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.1.0.13 – ModifyCloudPasswordLength
09:30:32,684 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.1.0.14 – DropLegacyViews
09:30:32,685 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Unknown VIEW: ‚jlawyerdb.AppUserBean‘ (SQL State: HY000 – Error Code: 4092)
09:30:32,685 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Unknown VIEW: ‚jlawyerdb.AppRoleBean‘ (SQL State: HY000 – Error Code: 4092)
09:30:32,686 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Unknown VIEW: ‚jlawyerdb.ServerSettingsBean‘ (SQL State: HY000 – Error Code: 4092)
09:30:32,686 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Unknown VIEW: ‚jlawyerdb.appuserBean‘ (SQL State: HY000 – Error Code: 4092)
09:30:32,686 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Unknown VIEW: ‚jlawyerdb.approleBean‘ (SQL State: HY000 – Error Code: 4092)
09:30:32,686 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Unknown VIEW: ‚jlawyerdb.serversettingsbean‘ (SQL State: HY000 – Error Code: 4092)
09:30:32,691 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.1.0.15 – DropLegacyViews
09:30:32,691 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Unknown VIEW: ‚jlawyerdb.appuserbean‘ (SQL State: HY000 – Error Code: 4092)
09:30:32,692 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Unknown VIEW: ‚jlawyerdb.approlebean‘ (SQL State: HY000 – Error Code: 4092)
09:30:32,696 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.1.0.16 – DropLegacyViews
09:30:32,702 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.2.0.0 – CalendarSetupDeleteDone
09:30:32,709 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.2.0.1 – DeleteDoneEvents
09:30:32,715 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.2.0.2 – VersionBump
09:30:32,721 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.2.0.3 – DecreaseContactsColumns
09:30:32,721 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) Running migration db.migration.V2_2_0_3__DecreaseContactsColumns
09:30:32,721 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreasing column size for contacts.zipCode
09:30:32,752 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreased to 50
09:30:32,752 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreasing column size for contacts.country
09:30:32,783 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreased to 150
09:30:32,783 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreasing column size for contacts.phone
09:30:32,814 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreased to 150
09:30:32,814 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreasing column size for contacts.fax
09:30:32,846 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreased to 150
09:30:32,847 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreasing column size for contacts.bankCode
09:30:32,873 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreased to 75
09:30:32,873 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreasing column size for contacts.bankAccount
09:30:32,903 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreased to 75
09:30:32,903 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreasing column size for contacts.email
09:30:32,932 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreased to 150
09:30:32,932 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreasing column size for contacts.creator
09:30:32,961 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreased to 150
09:30:32,961 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreasing column size for contacts.lastModifier
09:30:32,995 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreased to 150
09:30:32,995 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreasing column size for contacts.mobile
09:30:33,028 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreased to 150
09:30:33,028 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreasing column size for contacts.trafficInsuranceNumber
09:30:33,055 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreased to 150
09:30:33,055 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreasing column size for contacts.motorInsuranceNumber
09:30:33,090 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreased to 150
09:30:33,090 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreasing column size for contacts.titleInAddress
09:30:33,124 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreased to 100
09:30:33,124 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreasing column size for contacts.profession
09:30:33,160 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreased to 150
09:30:33,161 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreasing column size for contacts.degreePrefix
09:30:33,191 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreased to 100
09:30:33,191 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreasing column size for contacts.degreeSuffix
09:30:33,219 INFO [db.migration.V2_2_0_3__DecreaseContactsColumns] (ServerService Thread Pool — 75) decreased to 100
09:30:33,223 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.2.0.4 – VersionBump
09:30:33,229 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.0 – MailsetupMsExchange
09:30:33,238 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.1 – MailsetupAddTenantId
09:30:33,249 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.2 – DocumentAddVersion
09:30:33,255 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.3 – DocumentAddHighlight
09:30:33,265 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.4 – DocumentAddHighlightDefaults
09:30:33,271 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.5 – PartyTypesAddSequenceNo
09:30:33,279 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.6 – AddInvoicePools
09:30:33,286 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_invoice_pools‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:33,297 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.7 – AddInvoicePoolSecurity
09:30:33,301 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_invoicepool_access‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:33,304 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.8 – GrantAccessToInvoicePools
09:30:33,304 INFO [db.migration.V2_3_0_8__GrantAccessToInvoicePools] (ServerService Thread Pool — 75) Running migration db.migration.V2_3_0_8__GrantAccessToInvoicePools
09:30:33,308 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.9 – UpdateDefaultInvoicePool
09:30:33,314 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.10 – AddInvoices
09:30:33,323 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_invoices‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:33,328 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.11 – AddInvoicePositions
09:30:33,332 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_invoice_positions‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:33,335 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.12 – AddTestInvoicePool
09:30:33,338 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.13 – GrantAccessToInvoicePools
09:30:33,339 INFO [db.migration.V2_3_0_13__GrantAccessToInvoicePools] (ServerService Thread Pool — 75) Running migration db.migration.V2_3_0_13__GrantAccessToInvoicePools
09:30:33,341 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.14 – AddInvoicesCreated
09:30:33,363 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.15 – InvoicePositionUnitsFloat
09:30:33,386 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.16 – InvoiceAddTaxFlag
09:30:33,394 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.17 – CasesAddTimestamps
09:30:33,415 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.18 – CasesSetTimestamps
09:30:33,415 INFO [db.migration.V2_3_0_18__CasesSetTimestamps] (ServerService Thread Pool — 75) Running migration db.migration.V2_3_0_18__CasesSetTimestamps
09:30:33,418 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.19 – AddReportPrivileges
09:30:33,419 INFO [db.migration.V2_3_0_19__AddReportPrivileges] (ServerService Thread Pool — 75) Running migration db.migration.V2_3_0_19__AddReportPrivileges
09:30:33,422 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.20 – AddInvoiceTypes
09:30:33,428 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_invoice_types‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
09:30:33,466 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.21 – AddInvoiceTypesNumberRequired
09:30:33,470 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schemajlawyerdbto version 2.3.0.22 – DeleteOrphanedDocuments
09:30:33,471 INFO [db.migration.V2_3_0_22__DeleteOrphanedDocuments] (ServerService Thread Pool — 75) Running migration db.migration.V2_3_0_22__DeleteOrphanedDocuments
09:30:33,474 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Successfully applied 122 migrations to schemajlawyerdb(execution time 00:02.958s)
09:30:34,045 INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool — 75) HHH000397: Using ASTQueryTranslatorFactory
09:30:34,215 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation („deploy“) failed – address: ([(„deployment“ => „j-lawyer-server.ear“)]) – failure description: {
„WFLYCTL0080: Failed services“ => {„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.INSTALL“ => „WFLYSRV0153: Failed to process phase INSTALL of subdeployment \“j-lawyer-server-ejb.jar\“ of deployment \“j-lawyer-server.ear\“
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0024: Could not configure component SearchIndexProcessor
Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make protected native java.lang.Object java.lang.Object.clone() throws java.lang.CloneNotSupportedException accessible: module java.base does not \“opens java.lang\“ to unnamed module @184f246c“},
„WFLYCTL0412: Required services that are not installed:“ => [
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchIndexProcessor“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingTableFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SecurityService“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.ArchiveFileService.VIEW.\“com.jdimension.jlawyer.services.ArchiveFileServiceLocal\“.LOCAL“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomerRelationsService“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ReportService“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSyncService“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressTagsBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationHookFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.PartyTypeBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupMembershipFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolAccessFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileTagsBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DrebisService“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseSyncSettingsFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePositionFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupFacade“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.FormsService.VIEW.\“com.jdimension.jlawyer.services.FormsServiceLocal\“.LOCAL“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppUserBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ServerSettingsBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileReviewsBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppRoleBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderSettingsFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SystemManagement“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileGroupsBeanFacade“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.SystemManagement.VIEW.\“com.jdimension.jlawyer.services.SystemManagementLocal\“.LOCAL“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.BankDataBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormEntriesBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FaxQueueBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarService“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentTagsBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeArtefactBeanFacade“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.deploymentCompleteService“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppOptionGroupBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceService“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressService“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarAccessFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignAddressesFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormsService“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.ServerSettingsBeanFacade.VIEW.\“com.jdimension.jlawyer.persistence.ServerSettingsBeanFacadeLocal\“.LOCAL“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.VoipService“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormsBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationService“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingEntryFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContactSyncService“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomHooksService“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceTypeFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DataBucketLoader“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SingletonService“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileBeanFacade“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.jndiDependencyService“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderFacade“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.VoipService.VIEW.\“com.jdimension.jlawyer.services.VoipServiceLocal\“.LOCAL“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchService“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSetupFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileHistoryBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderFacade“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.beanmanager“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxAccessFacade“,
„jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\““,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.FaxQueueBeanFacade.VIEW.\“com.jdimension.jlawyer.persistence.FaxQueueBeanFacadeLocal\“.LOCAL“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileDocumentsBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CityDataBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderTemplateFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileAddressesBeanFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContainerLifecycleBean“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxSetupFacade“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileService“
],
„WFLYCTL0180: Services with missing/unavailable dependencies“ => [
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingEntryFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingEntryFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSetupFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSetupFacade]“,
„jboss.naming.context.java.module.j-lawyer-server.j-lawyer-server-io.env.SystemManagement is missing [jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.SystemManagement.VIEW.\“com.jdimension.jlawyer.services.SystemManagementLocal\“.LOCAL]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentTagsBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentTagsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DataBucketLoader.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DataBucketLoader]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarAccessFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarAccessFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationService.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SystemManagement.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SystemManagement]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationService.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxSetupFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxSetupFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ReportService.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ReportService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomerRelationsService.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomerRelationsService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormsService.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormsService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.BankDataBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.BankDataBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeArtefactBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeArtefactBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationHookFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationHookFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderTemplateFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderTemplateFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.PartyTypeBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.PartyTypeBeanFacade]“,
„jboss.deployment.unit.\“j-lawyer-server.ear\“.WeldStartService is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“, jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.jndiDependencyService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormsService.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormsService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileGroupsBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileGroupsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderSettingsFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderSettingsFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomHooksService.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomHooksService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileService.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressService.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressService.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignAddressesFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignAddressesFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchIndexProcessor.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchIndexProcessor]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePositionFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePositionFacade]“,
„jboss.naming.context.java.module.j-lawyer-server.j-lawyer-io.env.ServerSettingsBeanFacade is missing [jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.ServerSettingsBeanFacade.VIEW.\“com.jdimension.jlawyer.persistence.ServerSettingsBeanFacadeLocal\“.LOCAL]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceTypeFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceTypeFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchIndexProcessor.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchIndexProcessor]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContainerLifecycleBean.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContainerLifecycleBean]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSetupFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSetupFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContactSyncService.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContactSyncService]“,
„jboss.naming.context.java.module.j-lawyer-server.j-lawyer-server-io.env.VoipService is missing [jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.VoipService.VIEW.\“com.jdimension.jlawyer.services.VoipServiceLocal\“.LOCAL]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingEntryFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingEntryFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DrebisService.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DrebisService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileGroupsBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileGroupsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileTagsBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileTagsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppOptionGroupBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppOptionGroupBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormEntriesBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormEntriesBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileTagsBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileTagsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceService.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarAccessFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarAccessFacade]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-io.war\“.component.SecurityEndpointV1.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormEntriesBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormEntriesBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderFacade]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-io.war\“.component.CasesEndpointV2.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignAddressesFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignAddressesFacade]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-io.war\“.component.ContactsEndpointV5.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomHooksService.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomHooksService]“,
„jboss.naming.context.java.module.j-lawyer-server.j-lawyer-io.env.ArchiveFileService is missing [jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.ArchiveFileService.VIEW.\“com.jdimension.jlawyer.services.ArchiveFileServiceLocal\“.LOCAL]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-io.war\“.component.FormsEndpointV1.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.BankDataBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.BankDataBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContainerLifecycleBean.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContainerLifecycleBean]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingEntryFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingEntryFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ServerSettingsBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ServerSettingsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.BankDataBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.BankDataBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DrebisService.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DrebisService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.PartyTypeBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.PartyTypeBeanFacade]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-io.war\“.component.\“javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\“.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ServerSettingsBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ServerSettingsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppUserBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppUserBeanFacade]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-io.war\“.component.CasesEndpointV3.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileAddressesBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileAddressesBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormsBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppUserBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppUserBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppOptionGroupBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppOptionGroupBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SecurityService.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SecurityService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationHookFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationHookFacade]“,
„jboss.naming.context.java.module.j-lawyer-server.j-lawyer-server-war.env.VoipService is missing [jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.VoipService.VIEW.\“com.jdimension.jlawyer.services.VoipServiceLocal\“.LOCAL]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-io.war\“.component.\“javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\“.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentTagsBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentTagsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceFacade]“,
„jboss.naming.context.java.module.j-lawyer-server.j-lawyer-io.env.FaxQueueBeanFacade is missing [jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.FaxQueueBeanFacade.VIEW.\“com.jdimension.jlawyer.persistence.FaxQueueBeanFacadeLocal\“.LOCAL]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppRoleBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppRoleBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentTagsBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentTagsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchService.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FaxQueueBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FaxQueueBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchIndexProcessor.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchIndexProcessor]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePositionFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePositionFacade]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-io.war\“.component.ContactsEndpointV1.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomHooksService.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomHooksService]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-io.war\“.component.DataBucketEndpointV6.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxAccessFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxAccessFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderSettingsFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderSettingsFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SingletonService.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SingletonService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseSyncSettingsFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseSyncSettingsFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormsBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileReviewsBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileReviewsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FaxQueueBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FaxQueueBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupMembershipFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupMembershipFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderSettingsFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderSettingsFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSetupFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSetupFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupMembershipFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupMembershipFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchService.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressTagsBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressTagsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignFacade]“,
„jboss.naming.context.java.module.j-lawyer-server.j-lawyer-io.env.VoipService is missing [jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.VoipService.VIEW.\“com.jdimension.jlawyer.services.VoipServiceLocal\“.LOCAL]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupMembershipFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupMembershipFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SingletonService.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SingletonService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSyncService.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSyncService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressService.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SecurityService.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SecurityService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DataBucketLoader.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DataBucketLoader]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DrebisService.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DrebisService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppRoleBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppRoleBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.VoipService.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.VoipService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderTemplateFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderTemplateFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeArtefactBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeArtefactBeanFacade]“,
„jboss.naming.context.java.module.j-lawyer-server.j-lawyer-server-io.env.ServerSettingsBeanFacade is missing [jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.ServerSettingsBeanFacade.VIEW.\“com.jdimension.jlawyer.persistence.ServerSettingsBeanFacadeLocal\“.LOCAL]“,
„jboss.naming.context.java.module.j-lawyer-server.j-lawyer-server-io.env.FaxQueueBeanFacade is missing [jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.FaxQueueBeanFacade.VIEW.\“com.jdimension.jlawyer.persistence.FaxQueueBeanFacadeLocal\“.LOCAL]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchIndexProcessor.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchIndexProcessor]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxAccessFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxAccessFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSyncService.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSyncService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContactSyncService.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContactSyncService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceTypeFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceTypeFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SystemManagement.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SystemManagement]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-io.war\“.component.TemplatesEndpointV6.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceFacade]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-war.war\“.component.\“javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\“.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-io.war\“.component.CasesEndpointV1.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileService.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormsService.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormsService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceTypeFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceTypeFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormsBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormEntriesBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormEntriesBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.BankDataBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.BankDataBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppRoleBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppRoleBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileReviewsBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileReviewsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressTagsBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressTagsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileTagsBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileTagsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContactSyncService.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContactSyncService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingTableFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingTableFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SingletonService.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SingletonService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContainerLifecycleBean.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContainerLifecycleBean]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileAddressesBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileAddressesBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SecurityService.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SecurityService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ServerSettingsBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ServerSettingsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SystemManagement.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SystemManagement]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxAccessFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxAccessFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchService.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingTableFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingTableFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeArtefactBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeArtefactBeanFacade]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-io.war\“.component.\“javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\“.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeArtefactBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeArtefactBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileTagsBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileTagsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppRoleBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppRoleBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseSyncSettingsFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseSyncSettingsFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseSyncSettingsFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseSyncSettingsFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.VoipService.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.VoipService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DrebisService.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DrebisService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileHistoryBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileHistoryBeanFacade]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-io.war\“.component.CalendarEndpointV4.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceTypeFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceTypeFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.VoipService.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.VoipService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CityDataBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CityDataBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileDocumentsBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileDocumentsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileReviewsBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileReviewsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileGroupsBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileGroupsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressTagsBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressTagsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileDocumentsBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileDocumentsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppOptionGroupBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppOptionGroupBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationService.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderFacade]“,
„jboss.naming.context.java.module.j-lawyer-server.j-lawyer-server-war.env.ServerSettingsBeanFacade is missing [jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.ServerSettingsBeanFacade.VIEW.\“com.jdimension.jlawyer.persistence.ServerSettingsBeanFacadeLocal\“.LOCAL]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CityDataBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CityDataBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxSetupFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxSetupFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupMembershipFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupMembershipFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolAccessFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolAccessFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderSettingsFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderSettingsFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomerRelationsService.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomerRelationsService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormEntriesBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormEntriesBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.PartyTypeBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.PartyTypeBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ReportService.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ReportService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CityDataBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CityDataBeanFacade]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.weld.weldClassIntrospector is missing [jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.beanmanager]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolAccessFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolAccessFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppUserBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppUserBeanFacade]“,
„jboss.naming.context.java.module.j-lawyer-server.j-lawyer-io.env.FormsService is missing [jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.FormsService.VIEW.\“com.jdimension.jlawyer.services.FormsServiceLocal\“.LOCAL]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxSetupFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxSetupFacade]“,
„jboss.naming.context.java.module.j-lawyer-server.j-lawyer-io.env.SystemManagement is missing [jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.SystemManagement.VIEW.\“com.jdimension.jlawyer.services.SystemManagementLocal\“.LOCAL]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileAddressesBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileAddressesBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentTagsBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentTagsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseSyncSettingsFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseSyncSettingsFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignAddressesFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignAddressesFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContactSyncService.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContactSyncService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileDocumentsBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileDocumentsBeanFacade]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-war.war\“.component.\“com.jdimension.jlawyer.startup.AutoStartServlet\“.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingTableFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingTableFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ReportService.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ReportService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileDocumentsBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileDocumentsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormsBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarAccessFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarAccessFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceService.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomerRelationsService.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomerRelationsService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarAccessFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarAccessFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomHooksService.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomHooksService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileHistoryBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileHistoryBeanFacade]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-entities.jar\“.component.PersistenceLifecycleBean.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolAccessFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolAccessFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FaxQueueBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FaxQueueBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarService.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSyncService.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSyncService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ReportService.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ReportService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationHookFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationHookFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePositionFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePositionFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.PartyTypeBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.PartyTypeBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SecurityService.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SecurityService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileGroupsBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileGroupsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressBeanFacade]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-io.war\“.component.\“javax.servlet.jsp.jstl.tlv.ScriptFreeTLV\“.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DataBucketLoader.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DataBucketLoader]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolAccessFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolAccessFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarService.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceService.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileService.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingEntryFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingEntryFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileHistoryBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileHistoryBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationService.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarService.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePositionFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePositionFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationHookFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationHookFacade]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-io.war\“.component.CasesEndpointV6.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.VoipService.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.VoipService]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.batch.artifact.factory is missing [jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.beanmanager]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderTemplateFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderTemplateFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SingletonService.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SingletonService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarService.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomerRelationsService.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomerRelationsService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceService.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileService.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingTableFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingTableFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolFacade]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-war.war\“.component.\“javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV\“.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressService.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchService.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSyncService.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSyncService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxAccessFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxAccessFacade]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-io.war\“.component.CasesEndpointV4.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileAddressesBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileAddressesBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressTagsBeanFacade.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressTagsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FaxQueueBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FaxQueueBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppOptionGroupBeanFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppOptionGroupBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolFacade.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileReviewsBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileReviewsBeanFacade]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-io.war\“.component.CasesEndpointV5.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-io.war\“.component.ContactsEndpointV2.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppUserBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppUserBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormsService.Validator is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormsService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxSetupFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxSetupFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DataBucketLoader.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DataBucketLoader]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ServerSettingsBeanFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ServerSettingsBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContainerLifecycleBean.InAppClientContainer is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContainerLifecycleBean]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSetupFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSetupFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderFacade.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderFacade]“,
„jboss.naming.context.java.module.j-lawyer-server.j-lawyer-server-war.env.FaxQueueBeanFacade is missing [jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.component.FaxQueueBeanFacade.VIEW.\“com.jdimension.jlawyer.persistence.FaxQueueBeanFacadeLocal\“.LOCAL]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileHistoryBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileHistoryBeanFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderTemplateFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderTemplateFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderFacade]“,
„jboss.deployment.unit.\“j-lawyer-server.ear\“.deploymentCompleteService is missing [jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-server-ejb.jar\“.deploymentCompleteService]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SystemManagement.ValidatorFactory is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SystemManagement]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignAddressesFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignAddressesFacade]“,
„jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CityDataBeanFacade.InstanceName is missing [jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CityDataBeanFacade]“,
„jboss.deployment.subunit.\“j-lawyer-server.ear\“.\“j-lawyer-io.war\“.component.SecurityEndpointV6.START is missing [jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\“]“
]
}
09:30:34,226 INFO [org.jboss.as.server] (ServerService Thread Pool — 43) WFLYSRV0010: Deployed „j-lawyer-server.ear“ (runtime-name : „j-lawyer-server.ear“)
09:30:34,229 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.deployment.subunit.“j-lawyer-server.ear“.“j-lawyer-server-ejb.jar“.beanmanager (missing) dependents: [service jboss.deployment.subunit.“j-lawyer-server.ear“.“j-lawyer-server-ejb.jar“.batch.artifact.factory, service jboss.deployment.subunit.“j-lawyer-server.ear“.“j-lawyer-server-ejb.jar“.weld.weldClassIntrospector]
service jboss.deployment.subunit.“j-lawyer-server.ear“.“j-lawyer-server-ejb.jar“.component.ArchiveFileService.VIEW.“com.jdimension.jlawyer.services.ArchiveFileServiceLocal“.LOCAL (missing) dependents: [service jboss.naming.context.java.module.j-lawyer-server.j-lawyer-io.env.ArchiveFileService]
service jboss.deployment.subunit.“j-lawyer-server.ear“.“j-lawyer-server-ejb.jar“.component.FaxQueueBeanFacade.VIEW.“com.jdimension.jlawyer.persistence.FaxQueueBeanFacadeLocal“.LOCAL (missing) dependents: [service jboss.naming.context.java.module.j-lawyer-server.j-lawyer-io.env.FaxQueueBeanFacade, service jboss.naming.context.java.module.j-lawyer-server.j-lawyer-server-war.env.FaxQueueBeanFacade, service jboss.naming.context.java.module.j-lawyer-server.j-lawyer-server-io.env.FaxQueueBeanFacade]
service jboss.deployment.subunit.“j-lawyer-server.ear“.“j-lawyer-server-ejb.jar“.component.FormsService.VIEW.“com.jdimension.jlawyer.services.FormsServiceLocal“.LOCAL (missing) dependents: [service jboss.naming.context.java.module.j-lawyer-server.j-lawyer-io.env.FormsService]
service jboss.deployment.subunit.“j-lawyer-server.ear“.“j-lawyer-server-ejb.jar“.component.ServerSettingsBeanFacade.VIEW.“com.jdimension.jlawyer.persistence.ServerSettingsBeanFacadeLocal“.LOCAL (missing) dependents: [service jboss.naming.context.java.module.j-lawyer-server.j-lawyer-io.env.ServerSettingsBeanFacade, service jboss.naming.context.java.module.j-lawyer-server.j-lawyer-server-io.env.ServerSettingsBeanFacade, service jboss.naming.context.java.module.j-lawyer-server.j-lawyer-server-war.env.ServerSettingsBeanFacade]
service jboss.deployment.subunit.“j-lawyer-server.ear“.“j-lawyer-server-ejb.jar“.component.SystemManagement.VIEW.“com.jdimension.jlawyer.services.SystemManagementLocal“.LOCAL (missing) dependents: [service jboss.naming.context.java.module.j-lawyer-server.j-lawyer-io.env.SystemManagement, service jboss.naming.context.java.module.j-lawyer-server.j-lawyer-server-io.env.SystemManagement]
service jboss.deployment.subunit.“j-lawyer-server.ear“.“j-lawyer-server-ejb.jar“.component.VoipService.VIEW.“com.jdimension.jlawyer.services.VoipServiceLocal“.LOCAL (missing) dependents: [service jboss.naming.context.java.module.j-lawyer-server.j-lawyer-server-io.env.VoipService, service jboss.naming.context.java.module.j-lawyer-server.j-lawyer-io.env.VoipService, service jboss.naming.context.java.module.j-lawyer-server.j-lawyer-server-war.env.VoipService]
service jboss.deployment.subunit.“j-lawyer-server.ear“.“j-lawyer-server-ejb.jar“.deploymentCompleteService (missing) dependents: [service jboss.deployment.unit.“j-lawyer-server.ear“.deploymentCompleteService]
service jboss.deployment.subunit.“j-lawyer-server.ear“.“j-lawyer-server-ejb.jar“.jndiDependencyService (missing) dependents: [service jboss.deployment.unit.“j-lawyer-server.ear“.WeldStartService]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressBeanFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressBeanFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressBeanFacade.InstanceName]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressService (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressService.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressService.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressService.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressService.ValidatorFactory]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressTagsBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressTagsBeanFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressTagsBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressTagsBeanFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AddressTagsBeanFacade.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppOptionGroupBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppOptionGroupBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppOptionGroupBeanFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppOptionGroupBeanFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppOptionGroupBeanFacade.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppRoleBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppRoleBeanFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppRoleBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppRoleBeanFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppRoleBeanFacade.ValidatorFactory]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppUserBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppUserBeanFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppUserBeanFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppUserBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.AppUserBeanFacade.ValidatorFactory]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileAddressesBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileAddressesBeanFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileAddressesBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileAddressesBeanFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileAddressesBeanFacade.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileBeanFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileBeanFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileBeanFacade.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileDocumentsBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileDocumentsBeanFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileDocumentsBeanFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileDocumentsBeanFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileDocumentsBeanFacade.InAppClientContainer]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormEntriesBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormEntriesBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormEntriesBeanFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormEntriesBeanFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormEntriesBeanFacade.ValidatorFactory]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormsBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormsBeanFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormsBeanFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormsBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileFormsBeanFacade.InstanceName]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileGroupsBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileGroupsBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileGroupsBeanFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileGroupsBeanFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileGroupsBeanFacade.InstanceName]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileHistoryBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileHistoryBeanFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileHistoryBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileHistoryBeanFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileHistoryBeanFacade.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileReviewsBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileReviewsBeanFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileReviewsBeanFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileReviewsBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileReviewsBeanFacade.ValidatorFactory]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileService (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileService.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileService.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileService.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileService.ValidatorFactory]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileTagsBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileTagsBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileTagsBeanFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileTagsBeanFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ArchiveFileTagsBeanFacade.InstanceName]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.BankDataBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.BankDataBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.BankDataBeanFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.BankDataBeanFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.BankDataBeanFacade.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarAccessFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarAccessFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarAccessFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarAccessFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarAccessFacade.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarService (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarService.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarService.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarService.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarService.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSetupFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSetupFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSetupFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSetupFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSetupFacade.ValidatorFactory]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSyncService (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSyncService.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSyncService.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSyncService.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CalendarSyncService.InAppClientContainer]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignAddressesFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignAddressesFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignAddressesFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignAddressesFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignAddressesFacade.InAppClientContainer]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CampaignFacade.InstanceName]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderFacade.ValidatorFactory]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderSettingsFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderSettingsFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderSettingsFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderSettingsFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseFolderSettingsFacade.InAppClientContainer]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseSyncSettingsFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseSyncSettingsFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseSyncSettingsFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseSyncSettingsFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CaseSyncSettingsFacade.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CityDataBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CityDataBeanFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CityDataBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CityDataBeanFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CityDataBeanFacade.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContactSyncService (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContactSyncService.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContactSyncService.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContactSyncService.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContactSyncService.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContainerLifecycleBean (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContainerLifecycleBean.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContainerLifecycleBean.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContainerLifecycleBean.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ContainerLifecycleBean.ValidatorFactory]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomHooksService (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomHooksService.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomHooksService.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomHooksService.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomHooksService.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomerRelationsService (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomerRelationsService.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomerRelationsService.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomerRelationsService.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.CustomerRelationsService.InAppClientContainer]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DataBucketLoader (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DataBucketLoader.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DataBucketLoader.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DataBucketLoader.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DataBucketLoader.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderFacade.InAppClientContainer]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderTemplateFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderTemplateFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderTemplateFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderTemplateFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentFolderTemplateFacade.InAppClientContainer]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentTagsBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentTagsBeanFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentTagsBeanFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentTagsBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DocumentTagsBeanFacade.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DrebisService (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DrebisService.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DrebisService.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DrebisService.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.DrebisService.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FaxQueueBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FaxQueueBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FaxQueueBeanFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FaxQueueBeanFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FaxQueueBeanFacade.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeArtefactBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeArtefactBeanFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeArtefactBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeArtefactBeanFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeArtefactBeanFacade.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeBeanFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeBeanFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeBeanFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormTypeBeanFacade.InAppClientContainer]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormsService (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormsService.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormsService.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormsService.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.FormsService.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupFacade.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupMembershipFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupMembershipFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupMembershipFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupMembershipFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.GroupMembershipFacade.ValidatorFactory]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationHookFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationHookFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationHookFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationHookFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationHookFacade.InAppClientContainer]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationService (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationService.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationService.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationService.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.IntegrationService.ValidatorFactory]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceFacade.InAppClientContainer]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolAccessFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolAccessFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolAccessFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolAccessFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolAccessFacade.InstanceName]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePoolFacade.InstanceName]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePositionFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePositionFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePositionFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePositionFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoicePositionFacade.ValidatorFactory]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceService (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceService.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceService.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceService.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceService.ValidatorFactory]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceTypeFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceTypeFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceTypeFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceTypeFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.InvoiceTypeFacade.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxAccessFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxAccessFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxAccessFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxAccessFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxAccessFacade.InstanceName]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxSetupFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxSetupFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxSetupFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxSetupFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MailboxSetupFacade.ValidatorFactory]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingEntryFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingEntryFacade.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingEntryFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingEntryFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingEntryFacade.InstanceName]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingTableFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingTableFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingTableFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingTableFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.MappingTableFacade.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.PartyTypeBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.PartyTypeBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.PartyTypeBeanFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.PartyTypeBeanFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.PartyTypeBeanFacade.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ReportService (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ReportService.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ReportService.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ReportService.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ReportService.ValidatorFactory]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchIndexProcessor (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchIndexProcessor.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchIndexProcessor.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchIndexProcessor.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchIndexProcessor.ValidatorFactory]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchService (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchService.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchService.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchService.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SearchService.ValidatorFactory]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SecurityService (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SecurityService.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SecurityService.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SecurityService.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SecurityService.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ServerSettingsBeanFacade (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ServerSettingsBeanFacade.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ServerSettingsBeanFacade.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ServerSettingsBeanFacade.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.ServerSettingsBeanFacade.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SingletonService (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SingletonService.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SingletonService.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SingletonService.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SingletonService.Validator]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SystemManagement (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SystemManagement.Validator, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SystemManagement.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SystemManagement.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.SystemManagement.ValidatorFactory]
service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.VoipService (missing) dependents: [service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.VoipService.ValidatorFactory, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.VoipService.InAppClientContainer, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.VoipService.InstanceName, service jboss.naming.context.java.comp.j-lawyer-server.j-lawyer-server-ejb.VoipService.Validator]
service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU“ (missing) dependents: [service jboss.deployment.subunit.“j-lawyer-server.ear“.“j-lawyer-io.war“.component.DataBucketEndpointV6.START, service jboss.deployment.subunit.“j-lawyer-server.ear“.“j-lawyer-io.war“.component.ContactsEndpointV5.START, service jboss.deployment.subunit.“j-lawyer-server.ear“.“j-lawyer-io.war“.component.“javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV“.START, service jboss.deployment.subunit.“j-lawyer-server.ear“.“j-lawyer-io.war“.component.CasesEndpointV4.START, WFLYCTL0208: … and 21 more ]
WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit.“j-lawyer-server.ear“.“j-lawyer-server-ejb.jar“.INSTALL: WFLYSRV0153: Failed to process phase INSTALL of subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“
WFLYCTL0448: 95 additional services are down due to their dependencies being missing or failed
09:30:34,282 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
09:30:34,284 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://0.0.0.0:10090/management
09:30:34,284 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://0.0.0.0:10090
09:30:34,284 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) started (with errors) in 13843ms – Started 898 of 1458 services (364 services failed or missing dependencies, 365 services are lazy, passive or on-demand)Hallo, danke für die Meldung.
java -version
openjdk version „17.0.6“ 2023-01-17
OpenJDK Runtime Environment (build 17.0.6+10-Debian-1deb11u1)
OpenJDK 64-Bit Server VM (build 17.0.6+10-Debian-1deb11u1, mixed mode, sharing)Gruß
Ich fürchte dass diese Schritte der Install-Anleitung nicht ausgeführt worden sind:
Java installieren, (sofern noch nicht vorhanden – Prüfen mit „java -version“) via Konsole:
sudo apt-get install openjdk-11-jre openjfx
Prüfen Sie, ob Java 11 aktiv genutzt wird:
java -version
sollte eine Version 11 ausgeben. Sollte das nicht der Fall sein (bspw. weil mehrere Javaversionen parallel installiert sind), so kann viasudo update-alternatives –config java
die „Standardversion“ ausgewählt werden.
Bitte mal nachziehen und den Dienst neu starten
service j-lawyer-server restart
Mir ist jetzt allerdings nicht bekannt ob das reicht, da die Installation mit Java 17 statt 11 stattgefunden hat.
VG!
Danke für die Antwort. Schade, dass die Software mit Java 17 nicht kompatibel ist. Wir benötigen unbedingt bei uns die aktuellere Version. In dem Fall werde ich noch etwas abwarten, bevor ich die Software testen kann.
Welche andere Software ist das denn? Es lässt sich sicher eine Lösung finden.
VG
Jens / j-lawyer.orgErstmal vielen Dank für die schnellen Antworten – hier funktioniert das wirklich bestens! Wir setzen bei uns Linux-Software ein, insbesondere nutzen wir Libre Office in debian-backports version, LanguageTool lassen wir bei uns als Server arbeiten und setzten in Strabasic programmierte eigene Dokumentenverwaltungssoftware ein. In Java 11 stürzt bei uns LibreOffice in dieser Konfiguration immer wieder ab und bei Java 17 läuft es ohne Probleme sehr stabil. Ich bin wirklich sehr neugierig auf j-lawyer-Programme, aber zumindest vorerst ist mir die Stabilität der Software, mit der wir jetzt arbeiten, wichtiger. Die j-lawyer-Programmierer kommen ja ohnehin nicht drumrum, die Java-Kompatibilitätsprobleme in Zukunft zu beheben, dann komme ich darauf noch mal gern zurück.
LibreOffice unter Debian nutzt alles ab Java 8 aufwärts:
> https://packages.debian.org/de/sid/ure-javaGrundsätzlich nutzt LibreOffice nur für einige ausgewählte Funktionen eine lokale Javainstallation, in der Regel LibreOffice Base, nicht aber der Writer oder Calc.
Wenn Writer abstürzt, hat das nichts mit der verwendeten Javaversion zu tun.
Strabasic sagt mir nichts, und auch Google gibt dazu nichts aus.
Viele Grüße!
Jens / j-lawyer.org
- Du musst angemeldet sein, um zu diesem Thema eine Antwort verfassen zu können.