OK I worked through the weird error but I have another error. The app launches and I get:
Application: ASBriefsD2W Error: java.lang.IllegalStateException exception Reason: java.lang.IllegalStateException: An Exception occurred while generating the Exception page 'WOExceptionPage'. This is most likely due to an error in 'WOExceptionPage' itself or WebObjects encountered an uncaught exception while creating a Session object. Below are the logs of the original Exception which occured in com.as.Application, then the later Exception in WOExceptionPage. Original Exception: java.lang.IllegalArgumentException: <com.webobjects.appserver._private.WOComponentDefinition> Class 'Main' exists but is not a subclass of WOComponent. WOExceptionPage Exception: java.lang.IllegalArgumentException: <com.as.Application> Class 'Session' exists (interface org.apache.axis.session.Session) but is not a subclass of WOSession. ****************** Theodore Petrosky | IT/Finance Director 917 371-6080 AgencySacks On 1/17/26, 11:14 AM, "Theodore Petrosky" <[email protected] <mailto:[email protected]>> wrote: I wondered __ why my apps would not run. But now, I have a little red check on the app icon as if there were a problem and no files within the application structure are flagged. When I try to run the app, I get: Error: Could not find or load main class com.as.Application Caused by: java.lang.ClassNotFoundException: com.as.Application Where am I hosed? Theodore Petrosky | IT/Finance Director 917 371-6080 AgencySacks On 1/17/26, 10:52 AM, "Henrique Prange" <[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>> wrote: [You don't often get email from [email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification <https://aka.ms/LearnAboutSenderIdentification> <https://aka.ms/LearnAboutSenderIdentification> <https://aka.ms/LearnAboutSenderIdentification>> ] Hello Martino, The certificate has been updated. Can you check if it’s working for you? Cheers, HP > On 16 Jan 2026, at 13:27, Martino Limido via Webobjects-dev > <[email protected] <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>>> wrote: > > Hello, > > I would like to report an issue affecting Maven builds that depend on the > wocommunity Maven repository. > > The HTTPS certificate currently served by: > > https://maven.wocommunity.org/content/groups/public > <https://maven.wocommunity.org/content/groups/public> > <https://maven.wocommunity.org/content/groups/public> > <https://maven.wocommunity.org/content/groups/public>> > > appears to be expired, causing Maven (and Java in general) to fail with PKIX > / certificate validation errors when resolving dependencies and metadata. > > Certificate details as observed: > > - Subject: CN=*.wocommunity.org > - Issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; > CN=Sectigo RSA Domain Validation Secure Server CA > - Start date: Jan 7 00:00:00 2025 GMT > - Expire date: Jan 15 23:59:59 2026 GMT > - SSL verify result: unable to get local issuer certificate (20) > > As a result, standard Maven builds fail when accessing the repository, > especially for SNAPSHOT artifacts and plugin metadata, unless workarounds > such as local proxies or mirrors are used. > > I am reporting this in case the repository maintainers are not yet aware, as > renewing or fixing the certificate chain would immediately restore normal > build behavior for many WebObjects / Wonder projects. > > Thank you for your attention, and for maintaining the WebObjects ecosystem. > > Best regards, > Martino Limido
