Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] java.lang.reflect.InaccessibleObjectException error in webapp
  • From: "Cantor, Scott" <cantor.2@xxxxxxx>
  • Date: Fri, 23 Aug 2024 15:21:26 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 128.146.138.10) smtp.rcpttodomain=acm.org smtp.mailfrom=osu.edu; dmarc=pass (p=none sp=none pct=100) action=none header.from=osu.edu; dkim=pass (signature was verified) header.d=osu.edu; arc=pass (0 oda=1 ltdi=1 spf=[1,1,smtp.mailfrom=osu.edu] dkim=[1,1,header.d=osu.edu] dmarc=[1,1,header.from=osu.edu])
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=osu.edu; dmarc=pass action=none header.from=osu.edu; dkim=pass header.d=osu.edu; arc=none
  • Arc-message-signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=4BSj/SmvJ0hqa9ZBQgnDS5hjtpQlmJbqqzWOz5GboVI=; b=WoxVsv6v12z2zDfuR+ixK+urFpCB37knkdTqMoGrYt8nmufVkkjK4bd/XpU/5p2qar3IIqqdN0zx6eEy5G5QqWv8Hunl8BREc3qEDPilI39XgYPXPeBQ+aMI3yCFkNSdq07z/LoEYe/ubnJ7vRe21L6bhCgNk1kFbmb+Cp4Nl6jphpXnPN7JikHUYmrUD+JZAcNY1Prj0LmH8ooEyt0VmqUX8KSYr/MkBAmASrCcuFZ2m1/wEZgR363LeeLXApFZiptEVafFvbtDK3Hbx4n75TbDjJbTCBMnz3CqGnkCr2azvb5CsSYQCjQtFrALLNKBp6ZyNjoyiVpGZogG07IHaQ==
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=4BSj/SmvJ0hqa9ZBQgnDS5hjtpQlmJbqqzWOz5GboVI=; b=NdOCzz2p5AqeUN7yZD0t2D/Nb9VxwhrAEuweHK4UIBBrO2qWK1frzXClXIMKr3nLljVC1u5i0wZ7ddOHUi7IwMDCam/pzvo5xlZPMQBzHFkR9cqirRtogDYDxY0U3r+0iE5HMjOQ2wi/9L8xPoC4V5UI6t63T1WAZxsNnqqPstQQZDh1UuxcpCuhMvgun46p/P9plpGq/e8vpulSGhr0/QIOdqOuRMoUS+V6oZ/lseTm51I+mNrrnyp3QMFVppCyRpXAaRfemS3OwLguybZZYNKNdmBBnAmarG+GaialAHIbsN1enXeFzixL8+nyBLIFp1P6At1Lu8XSKa4TZjxnGg==
  • Arc-seal: i=2; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=pass; b=cS6PdUabTNbIb5/bbLL20pWSBapezw0YUqIM0zNy1Q6BOUmHR/wVlW4D0T4QpjrdGDt05ohWNDeif/CMrQgMVjsHRs7crECvIjfm8/2xgGWQkDBraWaB3DdJnufWEnlt6kItOCFylpZxhdY7zcOlIFTkHzGtvHRQz9c7xcTc5UQtgZ6biiOjauiFa+/UKV6S4MmH6AL/sZQw8sBeYFF1/RYBdzTfSU/R1uPda86wVzNURdEO7oLnLYbu4+HLwL9Wnj12STWiBujvONjoUfZVV8X93GpOLl0npdvC83tcsWC1MMOV0kGjF+Og0j043U9D/vpCX2lFfiu47J7Zr2Aknw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=pyteYH75dKtwZRk0j+toECgJ+/Z0t7RIGWaIhKVCj4lufFUcdMWXTwuxJ2mGZZP0JfxVSMAFxVSwcwlwz3W+azdEGqgMPCTBA8a2P+AbHyYDR3Gp7Z+QZNQvy4lQ2hOOSNAKsH6OZDmb01oyj2zTJLt+ZMfPzI4iBb7QHb7hoo1eM59gD8FW0AOkJXJEHPe8DozSekoggrQ6j3DOiWX3EX1lE552CCu4z33CsRxCxeB7NLq0HHNr/OR5GfrthGrJ/zYruqLDbnVthuqMsmIMOhvun1vR3gHBNRTJFdhGJc0/n8qEDu1Gcn4ZCqnQqtx3DhPpRjTWITsM4VBwTag82A==
  • Delivered-to: jetty-users@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/jetty-users/>
  • List-help: <mailto:jetty-users-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=unsubscribe>
  • Thread-index: AQHa9UF+auDpiyfdi0+BzUAGRSNQH7I0sqwA
  • Thread-topic: [jetty-users] java.lang.reflect.InaccessibleObjectException error in webapp
  • User-agent: Microsoft-MacOutlook/16.88.24081116
> How are you using JPMS, if at all?

We're not. The issue is that Java's own iterator implementations expose private classes, Spring can't do anything about that.

Your point about the difference in Iterator type is interesting, but it isn't the explanation because the behavior is different on the same data exposed, so the Iterator would be consistent.

Greg's point is fair, ordering is a possible issue, but it doesn't fit this particular case directly as it's not a function of the objects being accessed, but calling on the iterator itself with hasNext.

If it's order, it's maybe a class loader ordering matter, but that's just a grasp for explanations at this stage.

-- Scott

Back to the top